Same issue here with 2012 r2 customization. This is the second customer I experience issues. At the first the rolled out template was corrupt and we made a call at microsoft. They were unable to ...
See more...
Same issue here with 2012 r2 customization. This is the second customer I experience issues. At the first the rolled out template was corrupt and we made a call at microsoft. They were unable to determine what was wrong with the server and decided we should reinstall our domain controller and exchange 2013 server..Strange part was I rolled out 3 servers from the same template and 2 were bad and 1 was good (according to Microsoft). Now the second customer I cannot even get it working with customization. Customer 1: vCenter appliance 5.5 update B / ESXi 5.5 HP Version Customer 2: vCenter Server 5.5 Update B / ESXi 5.5 HP Version Guestcust.log: [2014-01-30T12:03:15 INFO] GuestCustUtil invoked. [2014-01-30T12:03:15 INFO] Params: customize -sealparam "/quiet /generalize /oobe /reboot" -nics 4000 -schedulenativeunobfusc [2014-01-30T12:03:15 DEBUG] Registry value 'CustomRescheduleFlags' is not set. Returning default value: 0 [2014-01-30T12:03:15 INFO] Checking for Windows Sysprep Respecialize operation. [2014-01-30T12:03:15 DEBUG] Sysprep process is not running. [2014-01-30T12:03:15 INFO] Windows Sysprep Respecialize operation was not detected. [2014-01-30T12:03:15 DEBUG] Customization in progress set to 1 at 2014-Jan-30 12:03:15 [2014-01-30T12:03:15 DEBUG] Rpci: Sending request='deployPkg.update.state 4 0 C:\Windows\TEMP\vmware-imc\guestcust.log' [2014-01-30T12:03:15 DEBUG] Rpci: Sent request='deployPkg.update.state 4 0 C:\Windows\TEMP\vmware-imc\guestcust.log', reply='', len=0, status=1 [2014-01-30T12:03:15 DEBUG] Successfully opened key SYSTEM\CurrentControlSet\Control\Session Manager\ [2014-01-30T12:03:15 DEBUG] Size of reg_multi_sz 27. [2014-01-30T12:03:15 DEBUG] Read multi_sz value from registry autocheck autochk /q /v *, size 27. [2014-01-30T12:03:15 DEBUG] string value from registry autocheck autochk /q /v *. [2014-01-30T12:03:15 DEBUG] Returning 1 elements [2014-01-30T12:03:15 DEBUG] Got BootExecute from session mgr. [2014-01-30T12:03:15 DEBUG] Native App sysprepDecrypter.exe, arguments '' [2014-01-30T12:03:15 DEBUG] Copied file sysprepDecrypter.exe to C:\Windows\system32\sysprepDecrypter.exe [2014-01-30T12:03:15 DEBUG] Updated boot execute value. [2014-01-30T12:03:15 DEBUG] Successfully created/opened key SOFTWARE\VMware, Inc.\Guest Customization\ [2014-01-30T12:03:15 DEBUG] New boot execute: [2014-01-30T12:03:15 DEBUG] autocheck autochk /q /v * [2014-01-30T12:03:15 DEBUG] sysprepDecrypter.exe [2014-01-30T12:03:15 DEBUG] System Drive: C: [2014-01-30T12:03:15 DEBUG] Moving directory 'sysprep' to 'C:' [2014-01-30T12:03:16 DEBUG] select * from win32_networkadapter where Manufacturer != 'Microsoft' and ServiceName != 'VMnetAdapter' and manufacturer is not null and MACAddress is not null [2014-01-30T12:03:16 DEBUG] Found 0 objects. Pointer 0. return code -2147217398(0x8004100a) [2014-01-30T12:03:16 DEBUG] Rpci: Sending request='deployPkg.update.state 4 101 C:\Windows\TEMP\vmware-imc\guestcust.log@WinMgmt : ' [2014-01-30T12:03:16 DEBUG] Rpci: Sent request='deployPkg.update.state 4 101 C:\Windows\TEMP\vmware-imc\guestcust.log@WinMgmt : ', reply='', len=0, status=1 [2014-01-30T12:03:16 ERROR] error number 8004100a, WinMgmt : [2014-01-30T12:03:16 INFO] GuestCustUtil exiting. The setupact.log is clean and the setuperr.log is clear (0 kb). An other interesting part is when I deploy "vm from template" the VMXNET3 NIC is not connected (turned of in vm) while it is connected in the Template itself (i checked with edit settings). Seems VMware is making a few mistakes in this one. Please fix it as I have a project running and want to roll out a template cause of memory sharing etc! -- [2014-01-30T12:03:16 DEBUG] select * from win32_networkadapter where Manufacturer != 'Microsoft' and ServiceName != 'VMnetAdapter' and manufacturer is not null and MACAddress is not null [2014-01-30T12:03:16 DEBUG] Found 0 objects. Pointer 0. return code -2147217398(0x8004100a) This is where it goes wrong. It does not see a NIC... I think it is important in a server ;-).