Sysprep - Windows Server reactivation

For those of you who create Windows server templates (for me, in VMware ESXi 3.5), ever spin up a new VM only to be greeted by the Windows activation process or the 30-day grace period out of time?  It's maddening because one of the options apparently allows online registration, but you can't get to the TCP/IP settings to enable the network to be able to do it!  And I hate trying to call up the activation line, to the point where it's easier to fish out an older or different server image and try again.

What worked for me:  c:\sysprep\sysprep -activated –reseal –mini

Here are some links and notes for more information:

Sysprep Tools and Settings  (description of parameters including command-line and sysprep.inf answer file)

How to use the Sysprep tool to automate successful deployment of Windows XP (more command-line params)

How Sysprep Works  (check out the section Resetting Windows Activation; for Vista, 7, Server 2008 read up on SkipRearm setting which apparently allows you to run Sysprep without resetting the activation clock).

Preserving OEM Pre-Activation when Re-installing Windows Server 2003 R2


I. Using “sysprep –reseal –mini” Command   [add  -activated  also!]

OEM pre-activation can be preserved when Sysprep.exe is run to reseal the system using the –reseal – mini switches by following these steps.
  • Create a file named sysprep.inf using a text editor such as Notepad that contains the information shown below substituting the appropriate product key.
    [UserData]
    ProductKey =”XXXXX-XXXXX-XXXXX-XXXXX-XXXXX”
  • Save the sysprep.inf file in the c:\sysprep\ folder.
  • Run c:\sysprep –reseal –mini 

Comments

Popular posts from this blog

Domain registrar pricing comparison (2014)

How to block the Admiral anti ad-block detection message

usoclient.exe in Windows 10 wakes up my PC with Wake Source: Unknown