Do I still need to run sysprep after cloning a vm in Azure?

Question

Hi

I want to create a clone of my current on-prem domain-joined application server towards Azure.

The Azure-one will be renamed and will remain in the same domain.

The on-prem wil be powered on again after the Azure-one has been renamed.

Will I need to run sysprep (or any other tool) in order not to get double SIDs?

Answer 1

Hi Lenvain, Peter

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

Running Sysprep prepares the operating system by removing unique identifiers like the SID, which helps avoid conflicts when both the original and cloned servers are online in a domain.

Sysprep prepares the system for cloning by removing specific data and creating a new SID when the cloned server joins the domain.

Open an elevated command prompt (run as administrator) and execute the following command:

sysprep /generalize /oobe /shutdown

This command prepares the system for cloning and turns it off.

Use your virtualization platform's tools (such as VMware or Hyper-V) to clone the VM after running Sysprep.

Import the cloned VM into Azure, power it on, and rename it as needed.

Before starting the cloned VM, disconnect the network adapter to avoid conflicts. After the VM starts, log in as a local admin and remove it from the domain if needed. Then, reconnect the network adapter and join the server back to the domain to get a new SID.

If you have any further queries, do let us know.

---

If the answer is helpful, please and "Upvote it".