Welcome to our Support Portal. Search for answers using the search box below.,
Generalize a machine …
“Generalize” most likely refers to the Windows Sysprep process — stripping machine-specific data (SID, drivers, product keys, etc.) from a Windows installation so the image can be deployed to other laptops without conflicts. Here’s the standard process:
1. Prepare the reference laptop
- Install Windows, updates, and all standard apps/drivers you want in the image.
- Remove any user-specific accounts, files, or personal data.
- Uninstall unnecessary bloatware or trial software.
- Run Disk Cleanup / clear temp files to shrink the image.
2. Run Sysprep
Sysprep is located at:
C:\Windows\System32\Sysprep\sysprep.exeRun it with these typical options:
sysprep /generalize /oobe /shutdown- /generalize — removes machine-specific info (SID, hardware IDs, activation state)
- /oobe — resets the machine to boot into the Out-of-Box Experience (like a fresh Windows setup) on next boot
- /shutdown — shuts the machine down after sysprep finishes (so you can capture an image)
Optional: add an /unattend:answerfile.xml if you want to automate the OOBE screens (region, account creation, etc.) on first boot.
3. Capture the image
After the laptop shuts down, boot from a WinPE/imaging tool (like DISM, MDT, SCCM, or a third-party imaging tool) and capture the disk/partition as a .wim or similar image file.
dism /capture-image /imagefile:C:\image.wim /capturedir:D:\ /name:"GeneralizedImage"4. Deploy to other laptops
Apply the captured image to target machines:
dism /apply-image /imagefile:C:\image.wim /index:1 /applydir:D:\Each laptop will then boot into OOBE and generate its own unique SID, drivers get re-detected, and it behaves like a fresh install rather than a clone.
Important notes
- Sysprep has a limited run count (usually ~3–8 times) before Windows blocks further generalization — plan your imaging workflow accordingly.
- Don’t generalize a machine that’s already been sysprepped and deployed — do it once on the clean reference machine.
- If you’re using Autopilot, Intune, or SCCM, there are wizard-based flows that call Sysprep under the hood — you may not need to run it manually.