Hi
When we create new VM from the Windows SErver 2016 template that created in VMware. It gave error.
"A specified parameter as not correct. spec.options.changeSID"
The 'Generate new SID' option was not selected when create the VM because we have already performed sysprep in the template.
What could be the issue? Is there a workaround?
Thank you
Hello,
Try the steps outlined here:
https://communities.vmware.com/thread/507180
by proden20
"
Use the "guest customization" feature when cloning or deploying from template, and "Generate a New SID." It works well. In addition to any possible application-specific SID bindings, I've seen Windows Update failures in WSUS environments. Mark Russinovich makes note of that as well:
"Note that Sysprep resets other machine-specific state that, if duplicated, can cause problems for certain applications like Windows Server Update Services (WSUS), so MIcrosoft's support policy will still require cloned systems to be made unique with Sysprep."
"
Bob
-o- If you found this comment useful please click the 'Helpful' button and/or select as 'Answer' if you consider it so, please ask follow-up questions if you have any -o-
KB article giving more information to the same effect:
Alternatively, you can use QuickPrep to customize the linked-clone desktops.
Bob
-o- If you found this comment useful please click the 'Helpful' button and/or select as 'Answer' if you consider it so, please ask follow-up questions if you have any -o-
Hi,
Thanks for the info.
However, we 'create' new VM from template instead of 'Clone' - does it make a different in term of sysprep?
When we use 'OS Customization' to generate SID when 'Create' new VM from template - no error, however doubt that it actually generate a SID properly.
Comparing 'Create' new VM, with and without select the generated SID option for Windows Server 2012/2016 template.
With 'generated SID' --- no error, however the BootExecute registry is set to:
autocheck autochk /q /v*
sysprepDecrypter.exe
>> This cause VM to sysprep every time when it is reboot (which cause some option issues).
Is this incompatible issue of version VMware with WS2012/2016? or is this a bug?
Is there a workaround?
I have what appears to be exactly the same problem with a 2016 template. When I run sysprep within Windows and check Generate new SID in the customization spec I experience the following when deploying a new VM from template:
no error, however the BootExecute registry is set to:
autocheck autochk /q /v*
sysprepDecrypter.exe
>> This causes VM to sysprep every time it is rebooted and the customization spec doesn't appear to apply (VM is not named properly, etc)
If I run sysprep in the template and don't generate a new SID in the Customization spec, I get 'specified parameter was not correct: spec.options.changeSID' error during the clone process
If I don't run sysprep in the image and use Generate New SID in the customization spec the VM errors out and won't boot.
Do we need to handle customization specs differently with Windows 2016?