Customization specification keeps applying after every reboot

[TheVMinator]

I have a customization specification that keeps applying itself after every reboot.  If I try to change any of the settings that it applies such as networking settings, after a reboot the settings are set back to what comes from the customization specification.  How can I stop this from happening?

Thanks

[tacticsbaby]

I had the same problem. In my case, it was the wrong (old) version of sysprep files in virtual center. Hope this helps.

[TheVMinator]

OK thanks. Actually what I would really like to do is just stop the customization spec from applying without having to redeploy the virtual machine.  The VM is fine and has been in production for a while and has lots of stuff installed on it and the customization spec keeps attempting to apply itself every time it reboots.  I just want it to stop. Can I modify the files in the datastore in such a way as to stop this?

Thanks

[idle-jam]

the customization from vcenter should only happen once and not everytime .. can you find in anything that is on OS level is causing the culprit?

[bulletprooffool]

Have a look at the disk settings for your VM - is it possible theat the Disks are configured as 'non persistent' disks?

this would mewan that your write are not stored, so you end up effectively 'rebuilding' the VM at each boot.

[a_p_]

Only a thought. Does the VMUpgradeHelper service run on your VM? Maybe this causes the issue.

http://kb.vmware.com/kb/1015572

Reg-Keys can be found at: HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware Tools\VMUpgradeHelper

André

[TheVMinator]

When the machine boots, before the OS is fully up, it gives the "VMware Image customization is in progress" message like it normally would if it was having a customization spec applied for the first time.  I'm aware this is only supposed to happen when the VM is first deployed - in this case it is happening a long time and many reboots after it has been deployed and is being used.  I don't see anything in the OS that looks abnormal but then I'm not sure where to look.  What is it that actually makes this "VMware Image customization is in progress" task run?  I tried disabling the VMupgrade helper service and rebooted - same issue - in particular the default gateway keeps disappearing.

FYI the registry keys do exist for VMupgrade helper.

Thanks

[EagleEngineer]

I was having the exact same problem. The trick appears to be changing the settings in the registry under the "Guest Customization" Key. I changed the DWORD Name data value of "CustomizationInProgress" from the 1 to 0, and it stopped. On a side note, I checked another system, and it does not appear that the "Guest Customization" key exists or is created if you do not do post-install customization. I deleted the key entirely, as the machine affected is a development system. I am not sure I would recommend that for a production system, as the change from 1 to 0 in the above DWORD worked, but thought it was worth a mention.

Here is the registry path for me (Windows Server 2008 R2 [x64])

"HKLM\SOFTWARE\Wow6432Node\VMWare,Inc.\Guest Cutomization\"

For a 32 bit system, just skip the Wow6432Node part.

Hope this helps.

[TheVMinator]

OK thanks for the input.

[KUmemoto]

I'm also having the same issue on a W2K8R2 VM.  I changed the DWORD Name data value of "CustomizationInProgress" from the 1 to 0 and the message still persists.

Any other options or recommendations?

[tlyczko]

I have the same problem -- the registry key change does not work for me, either.

It happened like so:

1) changed a VM to template

2) deployed new VM

3) new VM on startup did not follow its usual setup and sysprepping etc., stayed on ctrl-alt-del forever till I logged in

4) I had to actually change the VM name which normally cloning does for us

5) re-IP'd and joined to domain

6) also deleted the leftover sysprep folder which should have gone away by itself

now the message keeps appearing -- but ONLY in vCenter console view, NOT in regular RDP sessions

Any solutions???? will try again tomorrow, too tired now not to make mistakes

Thank you, Tom

[Stevew05]

I had the same issue with Win2008 R2 SP1 and used the steps from this person's blog to resolve the issue.  I also used psGetSid to verify that the SID was changed on the new VM.

http://blog.laspina.ca/ubiquitous/vmware_image_customization_in_progress

psGetSid Link:

http://technet.microsoft.com/en-us/sysinternals/bb897417.aspx