Adding machine back to 2003 domain

[stre1026]

Hi All -

I'm pretty sure I can't do this, but I figured I'd ask anyway.

When I re-image or replace a machine that is a domain member, I have to manually delete the machine from AD and wait for my DCs to replicate before I join the new machine. Otherwise, I get an error that says the machine already exists and it's joining under the old name (which is the name I gave the machine I built the image on). Is there a way I can make AD overwrite the domain machine without having to delete it manually each time? It get annoying when I swap out many machines in a row.

Thanks,
Steve

 

[mrdenny]

Unfornitually I don't think that there is. However if you remove them from AD when you first pull them off the network by the time that you are ready to add them back the delete should have replicated.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[ArizonaGeek]

Here is the solution I've come up with to combat that problem with our Ghost images.

I make sure to do all the updates and usual installs, I make the computer name TempGX620 (For our Dell GX620 machines) or whatever for each of our various model computers, I leave them off the domain then create an image.

When I have to reimage a machine all I have to do is run thru updates (since MS has been releasing quite a few lately) change the name of the machine, reboot, then add it to the domain.

Seems to be the easiest thing I've found to do.

Good luck

 

[stre1026]

Thanks guys,

I thought there was no other method of doing this. I guess I will just have to live with the replication time. We have 3 DCs currently as we are in the middle of a 2000 to 2003 migration so eventually, 1 of the DCs will be going away. Hopefully the 2003 migration will speed up our replication time. We had a lot of problems with our DCs replicating in 2000 anyway.

Steve

 

[Roadki11]

Just an added note, i always do a sysprep before i image my machines. it eliminates the issues you describe above and it keeps you more in compliance with licensing. just my 2 cents worth

RoadKi11