VMware vSphere

 View Only
Expand all | Collapse all

Unable to generate new SID

  • 1.  Unable to generate new SID

    Posted Jan 25, 2022 08:50 AM

    Hello Folks,

    I have wrinkle. I would like to create Windows 10 Pro with different SID. As far as I know I have to create file within "VM Customization Specification". I have performed 3 option:

    1. Use Custom SysPrep answer file

    Markus_VMware_1-1643100435808.png

    Markus_VMware_2-1643100453656.png

     

    2. Generate a new security identity (SID)

    Markus_VMware_3-1643100467943.png

     

    3. Both 1 option and 2 simultaneously

    Markus_VMware_4-1643100491892.png

    Markus_VMware_5-1643100502733.png

     

    Unfortunately I got on my 3 test Windows machine the same SID.

    Markus_VMware_6-1643100553084.png

     

    I created from template using 3 different option but still nothing. Even name of PC should have append numeric value does not work. All 3 machines have the name of computer.

    My Virtual Machine does not belong to domain but i think it does not matter. They should have different SID after using customization specification using either SysPrep or Generate new SID

    Best Regards,

    Markus



  • 2.  RE: Unable to generate new SID

    Posted Feb 08, 2022 11:53 AM

    Any updates FOLKS



  • 3.  RE: Unable to generate new SID

    Posted Jan 17, 2024 08:31 PM

    Exact same problem



  • 4.  RE: Unable to generate new SID

    Posted Jan 18, 2024 04:38 PM

    Microsoft limits cloning to 3. You must use Microsoft SYSPREP for the 4th clone. This might be your problem.  Here is a procedure:

     

    Introduction: 

    • When you clone an existing VM (and want to create an entirely new VM) using the VMware wizard option to run SYSPREP and generate a new SID will likely fail without any warning or errors generated. You get a new machine but it still has the same SID.  :^( 

      

    How-To Fix: 

     

    Disable network adapter 

     

    Restart VM. After a restart (Note: VMware may attempt sysprep and this takes a restart to complete and fail, so wait) 

    Rename computer and add to a workgroup, restart VM again.

     

    Elevated CMD prompt reset MSDTC  

         C:\Windows\System32\msdtc -uninstall  

         C:\Windows\System32\msdtc -install  

     

    Deactivate and set for activation:

         REGEDIT HKLM\Software\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform\SkipRearm to 1  

         REGEDIT HKLM\SYSTEM\Setup\Status\SysprepStatus, change DWORD value of CleanupState to 2 

         REGEDIT HKLM\SYSTEM\Setup\Status\SysprepStatus, change DWORD value of GeneralizationState to 7 

         Use the volume license generic KMS client key to reset activation to “not activated” (see https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys for the generic KMS client setup keys) 

         Elevated command prompt (for example, Win2012R2 generalized activation key):  

              C:\Windows\System32\cscript.exe slmgr.vbs /ipk d2n9p-3p6x9-2r39c-7rtcd-mdvjx 

     

    Run SYSPREP in elevated CMD prompt: 

         C:\Windows\System32\Sysprep\sysprep.exe /generalize /oobe /reboot 

     

    Bonus: Do it all again if you get error "Fatal error occurred while trying to sysprep the machine." This could be required because Microsoft allows an activated image to be cloned only 3 times. Running through the procedure twice seems to fix matters. D'oh!  :^/ 

     

    Sysprep will restart and then prompt for initial values 

    Restart  

    Enable network adapter, rename computer and add to domain, restart 

    Move the computer object from the Computers OU to the appropriate OU, allow AD to replicate this move 

    Run elevated GPUPDATE /FORCE 

      

     

    Documentation: 

     

     

    Display SID of a computer: 

    • Download SysInternals PsGetsid tool. 
    • Execute PsGetsid64.exe (you may target a remote computer or run locally) 

     

     

    List Duplicate SIDs of all computers: