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: 426
  • Last Modified:

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

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
crm-serv
Asked:
crm-serv
1 Solution
 
venom96737Commented:
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
 
crm-servAuthor Commented:
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

Become an Android App Developer

Ready to kick start your career in 2018? Learn how to build an Android app in January’s Course of the Month and open the door to new opportunities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now