VMware Cloud Community
adamadamadam
Contributor
Contributor
Jump to solution

Customize Template Causes Blue Screen

Hi Everyone

I've come across something odd.

I have a Windows Server 2008 R2 SP1 (64x) template.

Its a standard build, with nothing on it accept the latest updates.

When I got to deploy machine from template the deployed machine works fine.

But when I choose to customise the machine (as I would like it to generate a new SSID) and fill in all the details, the VM blue screens and reboots constantly.

Any suggestions?

Im trying to get a copy of the blue screen but havent figured out how to stop it from rebooting yet.

(ESXi 4.1)

0 Kudos
1 Solution

Accepted Solutions
Rubeck
Virtuoso
Virtuoso
Jump to solution

Im afraid not 😞 The build version for vCenter 4.1 Update 1 is Build 345043

See release notes here: http://www.vmware.com/support/vsphere4/doc/vsp_vc41_u1_rel_notes.html , which states:

Additional Guest Operating System Customization Support: vCenter Server now supports customization of the following guest operating systems:

  • Windows 7 SP1 (x32 and x64)
  • Windows Server 2008 R2 SP1  (x32 and x64)
  • RHEL 6.0 (x32 and x64)
  • RHEL5.5 (x32 and x64)

/Rubeck

View solution in original post

0 Kudos
14 Replies
Rubeck
Virtuoso
Virtuoso
Jump to solution

You need to have vCenter 4.1 Update 1 installed to customize 2008 R2 SP1.... Is this what you've got?

/Rubeck

0 Kudos
adamadamadam
Contributor
Contributor
Jump to solution

I've got:

VMware vCenter Server

Version 4.1.0

Build 258902

Is that right?

0 Kudos
Rubeck
Virtuoso
Virtuoso
Jump to solution

Im afraid not 😞 The build version for vCenter 4.1 Update 1 is Build 345043

See release notes here: http://www.vmware.com/support/vsphere4/doc/vsp_vc41_u1_rel_notes.html , which states:

Additional Guest Operating System Customization Support: vCenter Server now supports customization of the following guest operating systems:

  • Windows 7 SP1 (x32 and x64)
  • Windows Server 2008 R2 SP1  (x32 and x64)
  • RHEL 6.0 (x32 and x64)
  • RHEL5.5 (x32 and x64)

/Rubeck

0 Kudos
adamadamadam
Contributor
Contributor
Jump to solution

Thanks, at least I know whats causing the problem now.

Thank you for the help.

0 Kudos
Rubeck
Virtuoso
Virtuoso
Jump to solution

You're most welcome.. 🙂

/Rubeck

0 Kudos
ChrisTurner
Contributor
Contributor
Jump to solution

Hi,

I am having the same issue. The version I am running is ESX, 4.1.0, 348481 but i belive that the version stated in the forum is an earlier one.

Does any one know whether you need the specified version?

Thanks

Chris

0 Kudos
Rubeck
Virtuoso
Virtuoso
Jump to solution

ESX version is one thing, vCenter another.... What build is your vCenter version?

/Rubeck

0 Kudos
ChrisTurner
Contributor
Contributor
Jump to solution

Hi

Thanks for the quick reply. In the about section of my Vsphere client it tells me this,

Regards

Chris

0 Kudos
Rubeck
Virtuoso
Virtuoso
Jump to solution

Which is all OK.... Hmmm.. Has to be something in that template VM which might be causing it.

I've got an enviroment here with identical build numbers, and deploying a R2 SP1 VM from template works just fine...     The template VM is clean, with only updated VMTools installed...

Besides this, Im kinda lost to what the issue might be. Sorry 😞

/Rubeck

0 Kudos
ChrisTurner
Contributor
Contributor
Jump to solution

The template was a test server for a big citrix xenapp6 role out. I basically have a clean install of enterprise 2008 r2 fully patched and installed a basic setup of citrix without any database connections. I have also previously tried freshly installed 2008 r2 and no joy. Oh and yes the tools are fully up to date.

I’m stuck

Chris

0 Kudos
savagej
Contributor
Contributor
Jump to solution

For what it's worth, I'm also running into this issue, but only with Server 2008 R2 SP1. Without SP1, customization works fine. I also have the same vCenter version as Chris.

I know we don't need special sysprep files for Windows versions from 2008-on, but where does "support" for customizing SP1 come from? Is there a file we could check?

0 Kudos
ChrisTurner
Contributor
Contributor
Jump to solution

I finally got it working!!

I did a few thing so not sure which one worked but here is what I did,

1. Logged onto original machine

a. Removed it from the domain

b. Removed a snapshot (I didn’t know was there)

c. Shut down the machine

2. I cloned the machine to a template but stored it in a network location accessible to all the ESX servers rather that a local RAID.

3. Once complete I deployed from template using the wizard.

After all the cloning was done the original boot up took around 25mins but came up with all the new settings.

Hope this helps

Chris

0 Kudos
Superenigmatix
Contributor
Contributor
Jump to solution

There is now a KB article about this here:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=200450...

I tried the second solution as it was quicker and it worked for me. I don't have the latest version of VCenter and I will now upgrade, but the fix still worked.

Cheers

sE

0 Kudos
NachoHeeledge
Contributor
Contributor
Jump to solution

This worked a treat for me, thanks Smiley Happy

**Smoke Me A Kipper, I'll Be Back For Breakfast**
0 Kudos