Need to clone machine joined to domain Windows 7

[Majestic]

Hi,

I intend to clone a machine that is already joined to a domain to 2 identical machines using Acronis. From what I recall there is an issue of unique SIDs that causes issues after you clone. The domain profiles have licensed software I don't want to lose. Some google searching indicated one option is to use sysprep to de-join the machine from the domain manually then rejoin it (I suppose?) What is the best way to do this without causing an issue with both software and the domain controller itself?

Majestic

 

[TenYardFight]

Would like to know this too! Maybe it's not an issue anymore?

 

[dgiles79]

I haven't had any problems cloning Windows 7 PCs on the domain. Just run sysprep, choose the OOBE option in the top box (also check generalize if you plan on installing it to different hardware), then choose Quit in the second box. After it shuts down, you can clone the drive.

 

[drjones]

I have cloned exactly two Win7 machines that were part of a domain; I believe one I used acronis and one I used an EaseUS bootable CD.

Both worked out flawlessly.

A clone is a clone.

However, I did use identically sized drives and for one of them may have even used the exact same model #. Shouldn't matter too much, but I went that route anyway...

EDIT: Ahhh...wait....you want to turn one machine into two?

Don't think that's a good idea. Will probably cause problems with the SID and/or PC name being identical. Would like to hear from others on this.

With how long the cloning took, I could have easily done a fresh install of Windows & most basic software (Office, Adobe, etc) in the same time or less.

Cloning is a big help when you're trying to keep intact a machine that's already heavily used & customized.

What exactly is your end goal here and why can't you just do a clean install?

 

[moss]

Mythbusters please!! Same SID = no problem.

Although its been sometime since I've looked into it, I believe there is another identifier which is modified by Sysprep which needs to be unique if you're using WSUS for updates.

 

[jbartlett323]

Correct! SID's haven't truely mattered since NT days, however anyone whos cloned much will tell you XP has issue with em too...
As for the original question, yes you can clone it. Dont even have to run Sysprep (but is recommended, got some research in your future if you do!)...
Ideally, you would dis-join the machine from the domain, clone it, rename before hooking to network, hook-up and re-join domain and your good... Done this more than a few times, never had an issue one... But would like to stress Sysprep is a proper step...

 

[brandonkick]

I'm not sure I understand this.

Are you trying to take one machine, and clone it over to two other machines and retain all of the software functionality that you had before?

If it you were capable of doing this, you are more then likley to be violating copyrights and the TOS on several softwares.

If you want to create "backups" of the machine, to protect against failure then that might be slightly different (although I doubt it).

But trying to turn one workstation into three isn't a good or legal idea in almost any situation.

 

[Majestic]

Okay just to update I was not sure how it was going to end up. To give a clearer idea of the situation, I had 1 machine with Microsoft Office and Windows 7 professional and some other software such as Autocad in there. I had not entered any license information for Office nor Windows 7 yet but I had joined the machine to the Domain and had entered some licenses already (with the intention to update manually after to all purchased licenses).

In any case all machines were identical and I wanted to finish one then simply clone to 3 others (2 were left when I decided I wanted to clone because it was taking do much time. ) I would then rename the machines on the domain. My concern was that I would have conflicts or bigger issues on the domain Controller and perhaps software licensing issues.

In the end I did not clone and completed all of the machines one by one which is I believe a huge waste of time but did not want to risk it.

If there is an easy way to do this I would love to know it ? I will try some of your suggestions above with sysprep in a VMware environment with almost all the same factors and see what happens.

Thanks everybody for the input and perhaps next time I will clone them.

As a side note why are some people so up in arms about copyright issues ?? I never once said I was pirating anything ?!

Thanks

Majestic

 

[Majestic]

I haven't had any problems cloning Windows 7 PCs on the domain. Just run sysprep, choose the OOBE option in the top box (also check generalize if you plan on installing it to different hardware), then choose Quit in the second box. After it shuts down, you can clone the drive.

I will try that in VMware. Thanks !

Majestic

 

[jbartlett323]

Dont try to clone a machine already joined to a domain, you will lose the domain account for both host and clone, then have to remove and rejoin both machines. Be sure to have the machine not joined to the domain before the clone, then join after rename, else you WILL have issues. (this comes from experience!)

Otherwise, glad you got er done in the end!

 

[brandonkick]

Okay just to update I was not sure how it was going to end up. To give a clearer idea of the situation, I had 1 machine with Microsoft Office and Windows 7 professional and some other software such as Autocad in there. I had not entered any license information for Office nor Windows 7 yet but I had joined the machine to the Domain and had entered some licenses already (with the intention to update manually after to all purchased licenses).

In any case all machines were identical and I wanted to finish one then simply clone to 3 others (2 were left when I decided I wanted to clone because it was taking do much time. ) I would then rename the machines on the domain. My concern was that I would have conflicts or bigger issues on the domain Controller and perhaps software licensing issues.

In the end I did not clone and completed all of the machines one by one which is I believe a huge waste of time but did not want to risk it.

If there is an easy way to do this I would love to know it ? I will try some of your suggestions above with sysprep in a VMware environment with almost all the same factors and see what happens.

Thanks everybody for the input and perhaps next time I will clone them.

As a side note why are some people so up in arms about copyright issues ?? I never once said I was pirating anything ?!

Thanks

Majestic

Mostly because not everyone is aware of what does/doesn't break the law, and because I feel it's downright wrong to do something shady (even if you don't know it's wrong, because it's your job to know).

I never once said you were intentionally trying to pirate software, just letting you know that from what I understood the potential to violate TOS/Copyrights was good.

In any event my advice for the future would be to fully set up the machine, install all softwares and windows updates and then do a sysprep/oobe before making the image.

Then once the image is deployed, enter any license information into the programs and make the domain hookups afterwards.