Can't rename domain PC after Sysprep

[Guest]

I have prepared a PC for Sysprep-an XP SP2 PC joined to our domain and
applications added. This was sysprepped and ghosted across to identical PCs.

However, when trying to rename the PCs from the default auto-generated name,
the name appears to change, but when I try to join the domain I get the error
that it can't be done and has been joined under the old name.

Is this something to do with incorrect SIDs? I used the correct version of
sysprep and didn't disable the new SID option so I'm not sure where I've gone
wrong?

Now I have lots of PCs that can't be joined to the domain! None of the PC
names I want to user exist in the domain either, so this is very frustrating.

 

[Adam Leinss]

I have prepared a PC for Sysprep-an XP SP2 PC joined to our domain
and applications added. This was sysprepped and ghosted across to
identical PCs.

However, when trying to rename the PCs from the default
auto-generated name, the name appears to change, but when I try to
join the domain I get the error that it can't be done and has been
joined under the old name.

Is this something to do with incorrect SIDs? I used the correct
version of sysprep and didn't disable the new SID option so I'm
not sure where I've gone wrong?

Now I have lots of PCs that can't be joined to the domain! None of
the PC names I want to user exist in the domain either, so this is
very frustrating.

Ghosting an image joined to a domain is bad, bad, evil bad! Make sure
you unjoin the domain before capturing the image, then it should work.

You can script the joining to the domain in the sysprep.inf file.

Adam

 

[gazzafield]

Ghosting an image joined to a domain is bad, bad, evil bad! Make sure
you unjoin the domain before capturing the image, then it should work.

My company does it all the time. It's simple. make image, sysprep, delete
accounts from Server, Start mini setup. VoilA!

 

[Hunter01]

My company does it all the time. It's simple. make image, sysprep, delete
accounts from Server, Start mini setup. VoilA!

Where does the rename occur, and how does the computer then connect to
the domain when it has not been "added" with its' new identity to the
domain?

 

[gazzafield]

Where does the rename occur, and how does the computer then connect to the
domain when it has not been "added" with its' new identity to the domain?

During mini setup give the computer name you want. this can be the same or
different. You can also join a domain during the mini setup at which point
it joins the domain.

 

[Hunter01]

During mini setup give the computer name you want. this can be the same or
different. You can also join a domain during the mini setup at which point
it joins the domain.

But wouldn't that effectively mean it was not in the domain at the point
of imaging if it needs to rejoin the domain? That's the bit I don't get,
or how it would work if it were a domain member dumped straight back
onto multiple other machines with suddenly changed names, not matching
up to any domain account.

Ahhhh, from a quick look it seems Sysprep will remove any domain
membership, so it would effectively not be a domain member when it
mattered. We manually remove the PC's from domain before creating source
images, but perhaps that's just a hang-over from our pre-sysprep days.

 

[Adam Leinss]

Ahhhh, from a quick look it seems Sysprep will remove any domain
membership, so it would effectively not be a domain member when it
mattered. We manually remove the PC's from domain before creating
source images, but perhaps that's just a hang-over from our
pre-sysprep days.

Sysprepping a domain joined PC is not recommended. If the OP is having
problems joining the domain with his image, I would leave it off the
domain before capturing the image.

Adam

 

[gazzafield]

Sysprepping a domain joined PC is not recommended. If the OP is having
problems joining the domain with his image, I would leave it off the
domain before capturing the image.

I've done hundreds of the things. Never had a problem.