There are known issues with guest customizations not entirely working with this build of Windows 10. I don't think there are any known workarounds presently. What version of vSphere (vCenter and ESXi) are you running?
We are currently using vSphere Web Client Version 18.104.22.1680 Build 8170132 and ESXi 6.0.0, 3380124.
Whats odd is that the sysprep seems to go through and then everything just stops.
This may also be attributed to the fact that you are 2.5 *years* behind on ESXi patches for the release you're on.
I am upgraded now and running VMware ESXi, 6.5.0, 8294253. My customization script is still not working. I cannot rename and add the vm to the domain using the customization.
Has anyone been able to get a Windows 10 1803 vm to rename and join domain automatically?
I've had no issues with my 1803 template when doing my customization via vRealize Orchestrator. It changes the name/joins the domain without issue. This is working on a cluster with an older 6.0U2 and on a cluster with a mix of 6.5 and 6.7 hosts. VMware tools version is 10.2.5 in all cases.
I am having the same issue. Found this thread here in my Google searching. I am running VSphere 6.0U3. I just tried upgrading to the latest VMTools 10.3.2 but that hasn't appeared to solve it for me.
Same issue with my environment as well.
The C:\Windows\Temp\guestcust.log reads the following:
DEBUG] Executing command C:\Windows\system32\sysprep\sysprep.exe /quiet /generalize /oobe /reboot /unattend:C:\Windows\Panther\unattend.xml
DEBUG] Successfully executed command C:\Windows\system32\sysprep\sysprep.exe /quiet /generalize /oobe /reboot /unattend:C:\Windows\Panther\unattend.xml
VCSA 6.7 9433931
ESXi 6.7 9484548
Windows 10 1803 September Release
VMware Tools 10.3.2
If you drop the command C:\Windows\system32\sysprep\sysprep.exe /quiet /generalize /oobe /reboot /unattend:C:\Windows\Panther\unattend.xml into a command prompt it will run as expected.
your vmtools version is too old so it could be problem.upgrade vmware tools and try it should work.
after rename vm perform vmotion, and change current datastore to different datastore after vmotion your all vm files and directory that the files are located in will b rename and if you want to change datastore to previous datastore again perform vmotion.your files and directory will remain renamed.
rkoria2007, I think you responded to the wrong thread.
Did anybody ever find an answer to this?
Hello, I had the same problem. This problem appers, trought the Windows 10 Apps, which are installed per User / User Profile. In one of your user accounts, is the installation (upgrading) from this apps not finished. That is the problem. Windows needs for sysprep clean user profiles. The easiest way to solve this, is to create a new local admin account. After this, you delete all other accounts and profiles. Then you test the new admin account and if it work, you can shutdown the virtual machine. Then you convert the machine to a template and starts the cloning. Now should the cloning prozess work.
Hey Guys, in my Case it was the .NET 3.5 witch i had installed through Control Panel (Software -> Windows-Features).Remove it and the Deployment was sucessfull (in my case).
your Solution does't worked for me. Tested a few minutes ago.
The error does not occur in Windows 10 1809! I have edited my template the same way but with 1809 it works.
Maybe this is a Solution/Workaround for you.