Question Locked

Professinal disagreement

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am having a disagreement with a peer on a WindowsXP/Active Directory question. When installing (we are actually Ghosting) a new PC, at the point where the name for the PC is entered, he says that information about the PC has been entered in AD and if the PC is turned off at that point corruption or damage will be made to AD. I say that at that point no connection has been made with the Network at all, the network hardware has not even been configured so no damage can be done to the network or AD.

The reason for the our initial discussion is that a third peer has been turning off the newly cloned PC at that point. He then takes the PC to it final destination to complete the process. I will agree that it is not good. You should complete the process or do not let it start, but no network damage is being done.

What are your thoughts and where can I go to prove my point if I am in fact correct.

3 replies

by Former member

Naming a machine has nothing to do with AD. However, if you're joining a domain or AD, then you start talking to the DC. Even then, you can't corrupt the AD.

There is no harm in setting up the computer remotely, so I don't see your point there.

by Member 36153210

I did a trace today after imaging the PC. No packets until after the network was configured. I saved the trace as proof.

This discussion is closed to new replies.