Does cloned VM regenerate Windows SID?

Mohamed Elzaki Lv1Posted 19 Apr 2024 10:07

I would like to make sure that the cloned VM will regenerate a new Windows SID to avoid any conflict in domain registration.

Does it work automatically after finishing the cloning? or shall I do it manually? and how?

Newbie517762 has solved this question and earned 10 coins.

Posting a reply earns you 2 coins. An accepted reply earns you 20 coins and another 10 coins for replying within 10 minutes. (Expired) What is Coin?

Enter your mobile phone number and company name for better service. Go

HiHi,

When a virtual machine (VM) is cloned, it retains the same Security Identifier (SID) as the original VM. This can result in problems when attempting to join the cloned VM to an Active Directory domain, as duplicate SIDs can cause conflicts. To ensure smooth operation and prevent domain registration issues, it is recommended to manually change the SID after cloning by utilizing the Sysprep (System Preparation Tool).
Is this answer helpful?
Farina Ahmed Lv5Posted 23 Apr 2024 13:25
  
Yes, when you clone a VM, Windows typically generates a new SID automatically to prevent conflicts. It's handled during the cloning process, so there's usually no need for manual intervention.
mdamores Posted 23 Apr 2024 15:31
  
in most cases, Windows will regenerate a new SID automatically when you clone a VM. But sometimes it's not. In any case you experience this you need to do use SysPrep
Enrico Vanzetto Lv4Posted 23 Apr 2024 15:44
  
Hi, on my honest opinion, i regenerate every time Windows sid on a cloned VM. This to safely use the cloned vm as sysprep removes computer-specific information such as installed drivers and the computer security identifier (SID). This allows you to safely reuse your clone.
Newbie517762 Lv5Posted 23 Apr 2024 16:23
  
HiHi,

When a virtual machine (VM) is cloned, it retains the same Security Identifier (SID) as the original VM. This can result in problems when attempting to join the cloned VM to an Active Directory domain, as duplicate SIDs can cause conflicts. To ensure smooth operation and prevent domain registration issues, it is recommended to manually change the SID after cloning by utilizing the Sysprep (System Preparation Tool).
pmateus Lv2Posted 23 Apr 2024 16:36
  
Hi,

You can use the Sysinternals PsGetSid tool to view a machine’s SID by running it with no command-line arguments.
If the SID is the same you will need to regenerate a new one.
Zonger Lv5Posted 23 Apr 2024 20:44
  
Cloning a VM typically involves creating an identical copy of the original VM, including its SID (Security Identifier) unless specific steps are taken to sysprep the VM. To ensure a new SID is generated automatically, you should use the Sysprep tool provided by Windows. After cloning, run Sysprep on the cloned VM, selecting the generalize option, which will strip the SID and prepare the system for deployment. This process will automatically generate a new SID upon the next boot, avoiding conflicts in domain registration.
Newbie290036 Posted 24 Apr 2024 08:58
  
When cloning a virtual machine (VM) with Windows, it is essential to ensure that the cloned VM receives a new Security Identifier (SID) to avoid conflicts in a domain environment.

VMware:
a. After cloning the VM, power off the original VM and the cloned VM.
b. Edit the settings of the cloned VM and change the UUID (Unique Universal Identifier) by modifying the generated machine ID. You can find this setting in the VM's summary or options, depending on the VMware version.
c. Power on the cloned VM and perform a Windows installation or a system repair. This will generate a new SID during the process.

Hyper-V:
a. Power off the original VM and the cloned VM.
b. In the cloned VM's settings, change the Generation 1 VM to Generation 2. This will change the UUID and trigger a new SID generation.
c. Power on the cloned VM and perform a Windows installation or a system repair. This will generate a new SID during the process.
jerome_itable Lv3Posted 25 Apr 2024 08:38
  
Yes, cloning a Sangfor VM should automatically regenerate a new Windows Security Identifier (SID) to prevent domain registration conflicts. This is a standard practice for most VM cloning procedures, including Sangfor HCI.

Verifying Automatic SID Regeneration:

While automatic regeneration is the norm, it's always good practice to verify on the cloned VM. Here's how you can check:

    Log in to the cloned Windows VM.
    Press Windows Key + R to open the Run dialog.
    Type cmd and press Enter to open a command prompt window.
    In the command prompt, type wmic system get sid and press Enter.

This command will display the current SID of the Windows system. You can compare this SID with the original VM to confirm it's different.
Prosi Lv3Posted 25 Apr 2024 23:29
  
Hi
Windows SID needs to be changed after copying a virtual machine directory (1000528) | VMware KB

I Can Help:

Change

Trending Topics

Board Leaders