Preparing the Image for Deployment

Article
08/19/2016

Updated: October 4, 2012

Applies To: Windows Server 2012 Essentials, Windows Server 2012 R2 Essentials

A typical tool for preparing an image is sysprep.exe. Running this tool generalizes the image and shuts down the server so that the Initial Configuration will run when the server that contains the image is restarted. All modifications to the image must be complete before you run sysprep.exe.

Note

You can reset the Windows Product Activation a maximum of three times by using sysprep.exe.

To prepare the image

Delete SkipIC.txt that you have you added.
Open an elevated command prompt window. Click Start, right click Command Prompt, and then select Run as Administrator.
Run the following command to reset the registry key so that the user will have the full grace period before the server becomes noncompliant.
```
%systemroot%\system32\reg.exe add HKLM\Software\Microsoft\ServerInfrastructureLicensing /v Rearm /t REG_DWORD /d 1 /f  
```
Run the following command to add the registry key to display key, language page, locale page and EULA page. By default these pages will not display during initial configuration. Hence, if you are releasing a preinstalled box, you need to add this registry key. However, if you are releasing a DVD, you should not add this key, as these pages will display during WinPE and initial configuration.
```
%systemroot%\system32\reg.exe add "HKLM\Software\microsoft\windows server\setup" /v ShowPreinstallPages /t REG_SZ /d true /f  
```
Disable the initial configuration key page if your box is pre-keyed. The key page will only show when ShowPreinstallPages = true and KeyPreInstalled != true.
```
%systemroot%\system32\reg.exe add "HKLM\Software\microsoft\windows server\setup" /v KeyPreInstalled /t REG_SZ /d true /f  
```
Run the following command to add the registry key if you want to disable the hardware requirement checks. This is only for your pre-installed box that does not meet the hardware requirement. If you are releasing a DVD, or, your box meets the hardware requirement, it is recommended to not add this key.
```
%systemroot%\system32\reg.exe add "HKLM\Software\microsoft\windows server\setup" /v HWRequirementChecks /t REG_DWORD /d 0 /f  
```
(Optional) Remove the logs under %programdata%\Microsoft\Windows Server\Logs.

Prepare the unattended xml file for sysprep as shown in the following template.

<unattend xmlns="urn:schemas-microsoft-com:unattend" xmlns:ms="urn:schemas-microsoft-com:asm.v3">  

  <settings pass="oobeSystem">  
    <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="https://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="https://www.w3.org/2001/XMLSchema-instance">  

      <!-- Must have -->  
      <OOBE>  
         <HideEULAPage>true</HideEULAPage>  
      </OOBE>  
      <!-- Must have -->  
      <AutoLogon>   
        <Enabled>true</Enabled>   
        <Username>Administrator</Username>   
        <Domain>.</Domain>   
        <Password>   
          <!--You can set any password you like, but keep it consistent with password settings -->       
          <Value>Admin@123</Value>   
          <PlainText>true</PlainText>   
        </Password>   
      </AutoLogon>   
      <UserAccounts>   
       <AdministratorPassword>   
         <!--You can set any password you like, but keep it consistent with auto logon settings -->       
         <Value>Admin@123</Value>   
         <PlainText>true</PlainText>   
       </AdministratorPassword>   
      </UserAccounts>  

      <!-- Optional -->  
      <OEMInformation>  
         <HelpCustomized>true</HelpCustomized>  
         <Manufacturer>OEM name</Manufacturer>  
         <Model>model name</Model>  
         <SupportHours>hours</SupportHours>  
         <SupportPhone>123-456-7890</SupportPhone>  
         <SupportURL>https://www.contoso.com</SupportURL>  
      </OEMInformation>  

    </component>  

  </settings>  

  <settings pass="specialize">  
    <component name="Microsoft-Windows-Shell-Setup" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="amd64">  
      <!-- Must have -->  
      <ComputerName>Server</ComputerName>          
      <!-- Optional -->  
      <ProductKey>XXXXX-XXXXX-XXXXX-XXXXX-XXXXX</ProductKey>  
    </component>  
  </settings>  
</unattend>

Run the following command for sysprep.

%systemroot%\system32\sysprep\sysprep.exe /generalize /OOBE /unattend:xxx.xml /Quit

Important

You can also add the unattend.xml under %systemdrive% instead of as a parameter of sysprep. If the file is located under c:\ it will covered by user’s settings, but if used as a parameter of sysprep, it will not be covered by user’s settings. The unattend.xml under %systemdrive% will be deleted each time the server restarts. Hence, ensure that after you create unattend.xml under %systemdrive%, the server is not restarted.

Run the following command to add the registry key to skip Windows OOBE key page.

%systemroot%\system32\reg.exe add "HKLM\Software\microsoft\Windows\CurrentVersion\Setup\OOBE" /v SetupDisplayedProductKey /t REG_DWORD /d 1 /f

Run the following command to add the registry key to skip Windows language select page.

%systemroot%\system32\reg.exe add "HKLM\Software\microsoft\Windows\CurrentVersion\Setup\OOBE" /v SetupDisplayedLanguageSelection /t REG_DWORD /d 1 /f

Important

You must perform the last 2 steps, or else the Windows OOBE page will come up which is due with initial configuration page and break remotely administered server scenario.

Shut down the box after sysprep, you can capture an image or restart the server to continue Initial Configuration from a client computer.

Important

Partners who are planning to create server recovery media must capture the image and create the recovery media before proceeding to the next step.

Share via

Preparing the Image for Deployment

To prepare the image

Additional resources