Differences

This shows you the differences between two versions of the page.

--- computing:windows:sysprep [2011/12/26 13:29]
gcooper created
+++ computing:windows:sysprep [2015/09/10 12:33] (current)
gcooper
@@ Line 1: / Line 1: @@
 ====== Sysprep ======
+===== Preserve Activation =====
+**Windows 10**: http://www.tenforums.com/tutorials/3020-windows-10-image-customize-audit-mode-sysprep.html
+**Windows Vista/7**: http://www.microsoft.com/en-us/download/confirmation.aspx?id=5114
+**Windows XP**: https://technet.microsoft.com/en-us/library/bb457078.aspx
+<file>
+sysprep -reseal -activated
+</file>
+===== Fatal Error =====
+http://social.technet.microsoft.com/Forums/windows/en-US/425bd101-8a87-488c-b2e2-9f2f8113a0d9/sysprep-fatal-error-occurred-while-trying-to-sysprep-the-machine?forum=w7itproinstall
+Worked on Windows Server 2012 R2:
+In Registry Editor, set the value of GeneralizationState under HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus to 7, then run sysprep again.
 ===== Windows XP =====
@@ Line 11: / Line 31: @@
 ==== Windows Activation ====
-If you've ever tried to update a master image (Ghost, Acronis Trueimage, etc.) in order to deploy multiple Windows XP Pro systems, you may have run into this special error message:
+**Error: "Your grace period limit has been reached and will not be reset"**
-"Your grace period limit has been reached and will not be reset"
-[quote source="www.mcse.ms thread"]
 In Windows XP Professional, Sysprep can reset Windows Product Activation a maximum of three times.
 This causes a problem when deploying the image on other pc's as the image is redundant after 30 days of it being created.
-e.g. create image on 1st sept - can deploy on other pc's in sept but when deploy the image on a pc in Oct it has expired and wont let me log on.
+e.g. create image on 1st sept - can deploy on other PCs in sept but when deploy the image on a pc in Oct it has expired and wont let me log on.
-[/quote]
 There is a solution buried in Microsoft KB308554:
-(all actions tested on Windows XP Pro SP2 with an OEM Product Key - a big thanks to Amit in MS Tech Support!)
+  - Update your master system with applications and patches.
+  - Run ''sysprep -factory'' and reboot.
-. Update your master system with applications and patches.
+  - Activate Windows.
-. Run 'sysprep -factory' & reboot.
+  - Run ''sysprep -reseal -activated''. No error message about the grace period appears this time!
-. Activate windows.
+  - Use the prepped system's drive as your fresh master image for deployment.
-. Run 'sysprep -reseal -activated'. No error message about the grace period appears this time!
-. Use the prepped system's drive as your fresh master image for deployment.
 A fatal error occurred while trying to sysprep the machine
-Sysprep was probably run more than 3 times on the machine.  To show:
+**Error: Sysprep was probably run more than 3 times on the machine.**
+To show:
+<file>
 slmgr /dlv
+</file>
 Generally speaking, to sysprep the image on a single computer for multiple times, you need to configure the Microsoft-Windows-Security-SPP | SkipRearm to 1 in the unattend.xml file.
@@ Line 43: / Line 61: @@
 In Registry Editor
+<file>
 HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus\GeneralizationState = 7
+</file>
 Then run sysprep again.
@@ Line 49: / Line 69: @@
 If the same issue still persists, please uninstall the MSDTC and re-install it
-To uninstall MSDTC:		msdtc -uninstall
+To uninstall MSDTC:
+<file>
+msdtc -uninstall
+</file>
+To reinstall  MSDTC:
-To reinstall  MSDTC:		msdtc –install
+<file>
+msdtc -install
+</file>

Virtual Architects Support Wiki

User Tools

Site Tools

Differences

Page Tools