Windows 11 LTSC - from gold image to VDI pool - MachineGuid?

Simone Eusebi Lv1Posted Apr-23-2026 19:46

Hi everyone,
I'm facing this problem. I have a gold image made by Windows 11 LTSC.
When I convert it to template in order to create then a pool of VDI, every single Vms created have a different UUID (correct: this is done by hypervisor and the corresponding flag is turned on in vm-template) but the same MachineGuid.
When I create pool, all Vdi-Vms are joined to my AD and having the same MachineGuid can be a seriuos problem.
Is still necessary sysprep the gold image before create pool? Is it not a task invoked by on-borad Sangfor VDC tools?

dhileepan has solved this question and earned 20 coins.

Posting a reply earns you 2 coins. An accepted reply earns you 20 coins and another 10 coins for replying within 10 minutes. (Expired) What is Coin?

Enter your mobile phone number and company name for better service. Go

Yes — Sysprep is still required before converting a Windows gold image into a template on Sangfor HCI.

Sysprep Workflow
1. Prepare the Gold Image (Before Sysprep)
This is where most issues originate.

Inside your base VM, complete all configuration before running Sysprep.

Install & configure:

Latest Windows updates

Required VDI applications (Office, browsers, etc.)

Drivers (virtIO tool if needed)

Clean up the system:

Delete temp files:
cleanmgr /sagerun:1

Clear event logs:
wevtutil el | ForEach-Object { wevtutil cl "$_" }

Remove test/local user profiles

Important:

Do not join the domain yet

Ensure a local administrator account exists

Disable any auto‑login settings

2. Remove EPP/AV Agents (If Installed)
Most endpoint protection tools break Sysprep.
Uninstall them now — you can reinstall after deployment.

3. (Optional but Recommended) Create an unattend.xml
This helps automate first boot.

Common settings include:

Auto‑generated hostname

Skip OOBE screens

Auto domain join (optional)

4. Run Sysprep
Open an elevated CMD:

Code
C:\Windows\System32\Sysprep\sysprep.exe
Use these options:

System Cleanup Action: OOBE

Generalize

Shutdown

Or via CLI:

sysprep /generalize /oobe /shutdown

5. What Sysprep Actually Resets
Understanding this helps avoid identity conflicts later.

Sysprep resets:

MachineGuid

Windows SID

Device identity

Activation state

Hardware bindings

Sysprep removes:

Cached drivers (partially)

Event logs

User‑specific data

6. Do NOT Boot the VM After Sysprep
Once the VM shuts down:

Stop here. Do not power it on again.

If you boot it:

Windows regenerates identity

The "gold state" is lost

You must Sysprep again

7. Convert the VM to a Template
When converting:

check-> Enable UUID generator ->this should be checked by default


8. Deploy Your VDI Pool
Each new VM will now:

Generate a unique MachineGuid

Have a unique SID

Join AD cleanly

Avoid duplicate identity issues

Quick Validation After Deployment
Inside a few deployed VDIs, run:

reg query HKLM\SOFTWARE\Microsoft\Cryptography /v MachineGuid

All values should be different.
Is this answer helpful?
dhileepan Lv1Posted Apr-24-2026 14:57
  
Yes — Sysprep is still required before converting a Windows gold image into a template on Sangfor HCI.

Sysprep Workflow
1. Prepare the Gold Image (Before Sysprep)
This is where most issues originate.

Inside your base VM, complete all configuration before running Sysprep.

Install & configure:

Latest Windows updates

Required VDI applications (Office, browsers, etc.)

Drivers (virtIO tool if needed)

Clean up the system:

Delete temp files:
cleanmgr /sagerun:1

Clear event logs:
wevtutil el | ForEach-Object { wevtutil cl "$_" }

Remove test/local user profiles

Important:

Do not join the domain yet

Ensure a local administrator account exists

Disable any auto‑login settings

2. Remove EPP/AV Agents (If Installed)
Most endpoint protection tools break Sysprep.
Uninstall them now — you can reinstall after deployment.

3. (Optional but Recommended) Create an unattend.xml
This helps automate first boot.

Common settings include:

Auto‑generated hostname

Skip OOBE screens

Auto domain join (optional)

4. Run Sysprep
Open an elevated CMD:

Code
C:\Windows\System32\Sysprep\sysprep.exe
Use these options:

System Cleanup Action: OOBE

Generalize

Shutdown

Or via CLI:

sysprep /generalize /oobe /shutdown

5. What Sysprep Actually Resets
Understanding this helps avoid identity conflicts later.

Sysprep resets:

MachineGuid

Windows SID

Device identity

Activation state

Hardware bindings

Sysprep removes:

Cached drivers (partially)

Event logs

User‑specific data

6. Do NOT Boot the VM After Sysprep
Once the VM shuts down:

Stop here. Do not power it on again.

If you boot it:

Windows regenerates identity

The "gold state" is lost

You must Sysprep again

7. Convert the VM to a Template
When converting:

check-> Enable UUID generator ->this should be checked by default


8. Deploy Your VDI Pool
Each new VM will now:

Generate a unique MachineGuid

Have a unique SID

Join AD cleanly

Avoid duplicate identity issues

Quick Validation After Deployment
Inside a few deployed VDIs, run:

reg query HKLM\SOFTWARE\Microsoft\Cryptography /v MachineGuid

All values should be different.

I Can Help:

Change

Board Leaders

lungluk...

Weekly Questioners