By AOMEI / Last Updated October 24, 2019

To install same operating system on many computers simultaneously, Microsoft releases many practical tools such as Windows Deployment Services (WDS), Microsoft Deployment Toolkit (MDT) and so on. Typically, users should first create system image backup for Windows Server 2012. Then take these tools to deploy the image to other computers over the same network.

About Sysprep in Server 2012

However, after deployment, issues like WSUS incompatibility, Volume License key activation errors often happen to Microsoft Office products. Besides, other non Microsoft products such as Citrix may not work correctly. These problems owe largely to duplicate SIDs (System Identifiers).

When users install Windows, the OS allocates the computer with a unique SID. Each time you copy the system image, the SID will be also copied. Duplicate SID will appear on the same network, which is not allowed. Thus, you need to clear the SID information before deploying.

Luckily, Sysprep (Microsoft system preparation tool) can be used to complete this task. Built into Server 2012, Sysprep works well to clean out SID information and generalize a new SID for every server image copied from the original image. Note that, all the security, identification and boot information will be wiped out at the same time.

How to run Sysprep in Server 2012?

Follow the steps below to use Sysprep in Windows Server 2012.

1. Press Windows logo key + X at the same time. Then choose Command Prompt (Admin) from the menu.

2. Type cd \Windows\System32\Sysprep and then press Enter.

3. Sysprep can be run in 2 modes, the GUI mode and the command line. GUI mode is highly recommended. Please type sysprep and then press Enter.

* If you want to explore the command line, type sysprep /h and then press Enter.

4. Choose Enter System Out-of-Box Experience (OOBE) and turn on the Generalize checkbox. Select Shutdown in Shutdown Options. Then click OK.

Sysprep

* Enter System Out-of-Box Experience (OOBE): causes the system to mimic the first boot screens.

* Generalize: removes system specific information from the computer.

* Shutdown: shutdown the computer when done.

*The above instructions also work with Sysprep in Server 2016.

Once the computer is shut down, you can use any available technique to deploy the server image to multiple computers. However, sometimes many users find Sysprep not working when Generalize is checked.

That is to say, the original SID information can’t be deleted so that the server image can’t be deployed remotely. Is there a way to deploy the system without running Sysprep in Windows Server? The answer is yes if you read on.

Alternative way to deploy OS to multiple computers

One such method is using AOMEI Image Deploy (AID) Free. This is an integrated program that is designed to deploy (restore or clone) system image to multiple computers over network. You don’t need to perform Sysprep before deployment. Compared to Windows built-in tools, this program is relatively simple to use.

With AID, maximum 20 computers can be deployed simultaneously. More pleasing, you can deploy system to unlimited computers after upgrading to AID Technician. Windows 10/8.1/8/7/Vista/XP and Server 2003/2008/2012/2016 (including 32/64-bit, R2/SBS system) are supported. Let’s see how it works.

Preparations before deployment

  • Download and install AID on your server computer.

  • Confirm that the server computer and all the client computers are in the same segment.

  • Make sure that all the target computers support PXE boot.

  • The disk sequence numbers for installing system in client computers must be the same. Move out other disks and only keep the destination disk for image deployment.

  • Create system image backup with AOMEI Backupper Server on the central server computer. Choosing a network shared folder or NAS as the destination path when creating system backup.

1. Open AID to choose Create WinPE automatically (create a bootable ISO file of your system) or Create bootable WinPE ISO manually (add custom drivers into WinPE).

ISO File

2. Keep only one DHCP server in the LAN. Click Enable DHCP if you have no DHCP server. Then click Next to visit the second window.

Second Interface

3. Start all the client computers from network boot.

Boot

4. The status of all client computers will be displayed in the AID. When a client computer connects to AID successfully, you can get "Client computers connected". Click I confirm all the client computers which need to be deployed are online when all client computers are connected. Then click Next.

Connect

5.1. Click Browse to select your image file.

5.2. Select the client computers you need or click All to select all connected computers.

5.3. Input the destination disk number. If you keep only one disk in all client computers, the disk number should be 0.

5.4. Adjust the number of the computers that will be deployed.

Browse

5.5. Set the computer name by clicking Settings. Then click OK.

Settings

Tips:

  • Set IP: click it to preset IP address (in Technician edition).

  • Universal Restore: choose it to deploy system to computers with different hardware (in Technician version).

6. Confirm your operations and then click Start Deploy. After deploying, you can choose whether to shut down or restart the client computers.

Start Deploy

Conclusion

SID cleanup can be performed by running Sysprep in Server 2012 before deploying an operating system to multiple devices. However, Sysprep doesn’t always work fine. In case Sysprep fails, deploy your system with AOMEI Image Deploy (AID) Free. Moreover, this utility also applies to deploy image to multiple virtual machines.