VMware Cloud Community
novell1
Enthusiast
Enthusiast

Sysprep on VM with Windows 2012r2 failed

Hi,

on a vCenter 5.0 we can clone and use sysprep with Windows 2003/2008/2008r2 without a problem. If we do this with Windows 2012r2  with the button "generalize" the VM will not start anymore.

I did that on a other environment 5.1 and 5.5 with the same result. On a new vcenter with the latest build 5.5U2 it works.

Is there a trick to clone a VM Windows 2012r2 (HW Version 😎 on a vCenter5.0?

Thanks!

regards

Werner

0 Kudos
5 Replies
nettech1
Expert
Expert

How many times has it been syspreped prior?

If your source is a VM run slmgr /dlv and post the results here. if it's a template, convert to vm and run the same command.

Are you running 5.0 or 5.0 U2 ?

Thanks

0 Kudos
novell1
Enthusiast
Enthusiast

Hallo Nettech1

thanks! It is a standard VM, we clone it and do an regular sysprep. I will do the command on monday!

thanks!

Novell1

0 Kudos
novell1
Enthusiast
Enthusiast

Hi nettech1

I get this Output

Output slmgr -dlv_2015-02-23.jpg

Nothing Special...

0 Kudos
nettech1
Expert
Expert

Can you post Setuperr.log file located in the \Windows\System32\Sysprep\Panther on the source machine?

Do you see something similar to the errors below in your setuperr.log?

Error [0x0f0082] SYSPRP LaunchDll: Failure occurred while executing 'C:\Windows\System32\slc.dll, SLReArmWindows', returned error code -1073425657

Error [0x0f0070] SYSPRP RunExternalDlls: An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = -1073425657

Error [0x0f00a8] SYSPRP WinMain: Hit failure while processing sysprep generalize providers; hr = 0xc004d307

Are you using an answer file?

0 Kudos
novell1
Enthusiast
Enthusiast

Hi Nettech1,

thanks! I did a look over the logfiles (size and content) on the original Master VM, the filesize of setuperr.log was "0". But  you did bring me on the right path! I installed a complete new Windows 2012r2 master VM, after that I cloned this vm and the sysprep did start after the reboot normally! So the problem was on the original Master VM!

Thanks for your hint!

regards

werner

0 Kudos