Link to home
Avatar of emrichbke
emrichbkeFlag for United States of America

asked on

I am Ghosting Copying a Windows 7 Hard Drive on a domain. Do I need to do Sysprep? How

I am ghosting a Windows 7 Hard Drive to another computer, both on the same domain.  Do I need to do Sysprep? How?  I ghosted the HD fine, booted up fine, but the original computer came back with the message "The security database on the server does not h ave a computer account for this workstation trust relationship".  I went through the network wizzard and reattached it to the domain.  Do I need to run sysprep on the new machine with the identical hard drive? Thanks
Avatar of Iain MacMillan
Iain MacMillan
Flag of United Kingdom of Great Britain and Northern Ireland image

you should run Sysprep before you image the drive, or you will run into this issue everytime, and cause issues with SID's and Active Directory.
Avatar of emrichbke

ASKER

Thanks. But the drive I'm using to copy is being used by someone. Doesn't sysprep remove it from the domain.
ASKER CERTIFIED SOLUTION
Avatar of Iain MacMillan
Iain MacMillan
Flag of United Kingdom of Great Britain and Northern Ireland image

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Great!
OK. Thanks, that answers my question.  Unfortunately in my enviroment, I only need to clone this one machine due to many custom software fixes, so that another user can use the software.  I ran sysprep on the new machine and it ran through the OOBE settings, and attached to the domain with no issues. So I guess I'll just see what happens. Thanks!
Avatar of BtechB
BtechB

Yes you always need to run sysprep on a PC that will be in a domain enviroment and with Win7 you pretty much need to do it if your not in order to not break the activation process. You can always add it back after the image is complete by just giving it the same name. The sysprep strips all the unique information from the system and creates new on each new hardware that the image is placed on. Without sysprep each PC is not unique but a clone and Domains do not like that. There is another big consideraiton your should take into account when using Sysprep for a domain and that is the default profile. Do not run sysprep as a domain user and try to copy that profile you will have all kinds of little annoying headaches down the road. Especailly with MS based products. Here are the steps to follow and do it right.
http://support.microsoft.com/kb/973289

Sysprep and Windows 7 is a huge topic and I know everyones needs are different. My advice do some reading and a lot of testing. Read this forum as well and be sure to set SKIP REARM or you will create a brick after 3 tests.
http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/f2805904-9a18-405a-ba97-10773bbe5ea5

Good luck.
Having done this before, I agree with everyone else, but I believe my scenario was similar to yours... I believe if you remove the PC from the domain, change the PC name, then add it back to the domain, you should be fine.  I'd try that before I go sysprepping a machine to reimage this one again.