Hello thatguyfromtheplace,
It will not turn off itself. In a single forest domain you can make all DC's
Global catalog servers.
http://support.microsoft.com/kb/223346/en-us
Make sure the new server is using itself as preferred with the fixed ip instead
of loopback 127.0.0.1. Also all clients have to point to the new DNS server
as preferred to logon if the old server is down.
For DNS see here:
http://support.microsoft.com/kb/825036
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!!
http://www.blakjak.demon.co.uk/mul_crss.htm
> I have an old server 2000 DC that is being removed. I've run into a
> bit of a snag and could use a little guidance. The new DC (single DC
> environment) is running 2003 Enterprise and I've already DC Promo'd
> and transferred the FSMO roles, installed DNS and since it's an AD
> integrated DNS just let it replicate. I've got everything transferred
> over but I can't log in if i take the old DC off the network, i'd like
> to be able to have the old one for a short term just in case there is
> an issue. I keep getting errors pointing to GCS, and from my
> understanding (please correct me if I'm wrong) the infrastructure
> master turns itself off in a single DC domain and lets the DC run GCS,
> if another DC exists (even if it can't be contacted) the PDC will
> force the infrastructure master role to enabled and push all GCS
> functionality to the other server(s). How do I forcefully demote the
> old DC from the domain while it's not connected to the network so that
> if there's an issue i can swap the two machines in place in order to
> temporarily maintain functionality while troubleshooting the issue?
>
> http://forums.techarena.in
>
Similar Threads
Linear Mode
