Force a DC to authenticate

[HelpPls]

Hello all -

I currently have 2 DC's, 1 W2K (1st DC in the environment) and 1 W2K3. I am
planning on taking the W2K DC down and rebuilding it from scratch with W2K3
and then promoting it as my 2nd DC. I have already transferred ALL roles to
the new W2K3 DC and set up DNS on it. I pointed all my clients to the new
DNS as well. Is there anything else I need to do before demoting it? Also,
is there a way to force my new W2K3 DC to authenticate everyone so I know my
W2K DC is not "serving" anyone?

Thanks - Sean

 

[Laura E. Hunter \(MVP\)]

A very "low-tech" way to stop a DC from servicing logon requests is to stop
the Netlogon service. It's a good, non-destructive way to make sure that
your 2K3 server is functioning properly as a DC before you go the full monty
of taking the 2K server offline and reformatting it.

To answer your first question, it sounds like you have all of your bases
covered - just make sure that your DNS server contains the appropriate SRV
records for the 2K3 domain controller.

 

[Hank Arnold]

Are you running DHCP? If it's on the original, you'll need to set it up on
the new server, authorize it and un-authorize it on the old server.