Solved

Sysprep Source PC Ran Setup on Restart and Clone Domain Join Fails

Posted on 2006-06-12
2
403 Views
Last Modified: 2008-03-03
I ran sysprep using the Sysprep GUI on a PC configured for cloning to other identical hardware.  I created an image of the source drive using Ghost 2003.

When I rebooted the source PC to WinXP the minisetup started and showed the name of the PC to be changed to the name indended for assignment to the clone.

I was suprised to see minisetup run on the source PC and was concerned about the computer name change.

I changed the name of source PC back to the original name and was able to join the Win 2003 domain.

When I cloned the destination PC and booted to WinXP it too ran minisetup as intended.  Joining the domain, however, failed with a message indicating that a user account with the same name was already logged on.

What caused the failure?  Is there a way to get the cloned system to join the domain?  Would you expect any other problems with the source or cloined PCs?

CRM

0
Comment
Question by:crm-serv
2 Comments
 
LVL 15

Accepted Solution

by:
venom96737 earned 500 total points
ID: 16885558
its supposed to change the name its asking you what you want to name the computer you are about to clone once you changed it back to the original name it named that cloned computer that and then both computers had the same name and the domain will not allow this.  To fix this change the name of the cloned computer.
0
 

Author Comment

by:crm-serv
ID: 16887025
venom96737,

The actual steps I used seem to be different than I understand your post assumes.

The actual sequenc of events:
 1. ran sysprep on the source pc
 2. imaged source pc disk to the clone pc disk
 3. started the source pc and noted that minisetup ran and assigned the clone name to the
     source pc.
 4. changed the name of the source pc to its correct name
 5. joined the source pc to the domain
 6. started the cloned pc and noted that minisetup ran and assigned correct computer name
 7. join cloned pc to the domain failed

The cloned pc name was not listed in Active Directory after these operations.

Could there be a SID conflict?  

If I run syssprep on the cloned pc would that reset the SID on that computer?

CRM
0

Featured Post

The Eight Noble Truths of Backup and Recovery

How can IT departments tackle the challenges of a Big Data world? This white paper provides a roadmap to success and helps companies ensure that all their data is safe and secure, no matter if it resides on-premise with physical or virtual machines or in the cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

If you build your web application in Visual Studio you'll get at least a few binaries, or .DLL, files in your bin folder. However, there is more compiling to be done. Normally this would happen when an ASP.NET resource within the web site is request…
Step by step guide to Clean and Sort your windows registry! Introduction: Always remember: A Clean registry = Better performance = Save your invaluable time In this article we're going to clear our registry manually! Yes, manually! The e…
Two types of users will appreciate AOMEI Backupper Pro: 1 - Those with PCIe drives (and haven't found cloning software that works on them). 2 - Those who want a fast clone of their boot drive (no re-boots needed) and it can clone your drive wh…
Email security requires an ever evolving service that stays up to date with counter-evolving threats. The Email Laundry perform Research and Development to ensure their email security service evolves faster than cyber criminals. We apply our Threat…

809 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question