Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 780
  • Last Modified:

Cloned Win7 VM in domain

Hi there.

Have a Win7 workstation VM on a 2008 R2 domain.

I've cloned it to spin up the copy in order to save time with configuration of the 2nd one.

However have just realised that I need the new one to have a different SID on the domain. How can I remove it and join it with a new SID without affecting the domain membership of the first VM??

Thanks in advance!
BH
0
butterhook
Asked:
butterhook
  • 4
  • 3
  • 3
  • +3
9 Solutions
 
bluedanCommented:
1) Uncheck Connected & Connected at Power on for the Clone Win 7 VM's vNic, before you start it up.
2) Log on to Clone Win7 VM, it's not connected to network
3) Change to new IP address, computer name for Clone Win 7 VM and join it to workgroup.
4) Enable vNic
5) Log on to Win 7 VM using local admin account and join the Win 7 VM back to domain.

Hope this helps.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Can I ask a question Why do you need the CLONED VM to have a NEW SID?

Despite what you may have been told and think about Machine SIDS

read this:-

The Machine SID Duplication Myth

The only reason if you need to use WSUS, because WSUS uses a unique identifier, which is set/reset by the Sysprep process.

This is not to be confused with the Machine SID.

So if you do not use WSUS, not a problem!
0
Transaction-level recovery for Oracle database

Veeam Explore for Oracle delivers low RTOs and RPOs with agentless transaction log backup and transaction-level recovery of Oracle databases. You can restore the database to a precise point in time, even to a specific transaction.

 
butterhookAuthor Commented:
Subhash - will all the applications be on the resultant VM after running SysPrep?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
I would never recommend Sysprep after installing applications, as they can break.
0
 
RickEpnetCommented:
The SID change in not really the issue you cannot have both machines with the same name and IP address. The Name is the biggest issue. Do what bluedan said and you will be fine.
0
 
RickEpnetCommented:
By the way once you do what bluedan said you will get a new Domain SID anyway.
0
 
butterhookAuthor Commented:
The reason for the whole operation is to save time installing the applications that are already on the source VM.

Is this a bad idea(tm)?
0
 
RickEpnetCommented:
Not necessarily it would depend on the application.
0
 
Subhashish LahaCommented:
Which applications you're going to install?

I have used sysprep images installed with applications many times and it never broke any applications.

I think you should read this article.
http://4sysops.com/archives/why-sysprep-is-an-obligatory-windows-deployment-tool-part-1-all-the-important-sysprep-functions/

http://4sysops.com/archives/why-sysprep-is-an-obligatory-windows-deployment-tool-part-2-unique-sids-are-necessary/
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
@RickEpnet Domain SID, not Machine SID.
0
 
RickEpnetCommented:
Yes that is what I said Domain SID.
0
 
David Johnson, CD, MVPOwnerCommented:
Sysprep as part of the process does remove the computer from the domain
0
 
butterhookAuthor Commented:
Thanks for your feedback everyone. Based on this response, I'm building a fresh new VM.
Charlie
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

  • 4
  • 3
  • 3
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now