Solved

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

Posted on 2006-06-12
2
401 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

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

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

Suggested Solutions

Are you unable to synchronize your OST (Offline Storage Table) file with Microsoft Exchange Server? Is your OST file exceeding 2 GB size limit? In Microsoft Outlook 2002 and earlier versions, there is a 2 GB size limit for the OST file. If the file …
cPanel is a Unix based web hosting control panel that provides a graphical interface and automation tools designed to simplify the process of hosting a web site. cPanel utilizes a 3 tier structure that provides functionality for administrators, rese…
This Micro Tutorial will give you a basic overview how to record your screen with Microsoft Expression Encoder. This program is still free and open for the public to download. This will be demonstrated using Microsoft Expression Encoder 4.
Sending a Secure fax is easy with eFax Corporate (http://www.enterprise.efax.com). First, just open a new email message. In the To field, type your recipient's fax number @efaxsend.com. You can even send a secure international fax — just include t…

861 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

Need Help in Real-Time?

Connect with top rated Experts

23 Experts available now in Live!

Get 1:1 Help Now