Anticipated first question-
Windows 2003 standard with AD at Windows 2003 functional level. DCs
are NOT R2. All are at SP2.
Only one location (for the current AD domain).
--
RMc
richardmccl...@aspca.org wrote on 01/14/2010 01:23:34 PM:
Greetings!
Our network and AD structure have
This is a path to problems.
I recommend that after you demote a DC, and BEFORE CLICKING THE REBOOT BUTTON,
go and remove DNS Server. Reboot. Go clean up DNS on another DC in the same or
a covering site ASAP.
After you have run all of your demotions, use dcdiag and dnslint and netdiag to
Your DNS servers will remain DNS servers after you DCPROMO them to remove
AD. You will need to uninstall the DNS service from the servers to remove
it, if you fee it's necessary. You have a few options available to you
depending on how you have restructured your new environment. You can
choose to
Down clients could be handled by DHCP as far as the DNS but I would have all
of them go through a restart after the changes are made to DHCP just to
force things to work. Servers I would put on the new DNS servers before
anything else just to get them done but that assumes you are statically
If you want to have the server to be demoted continue to work as DNS Server,
you can get the zone from AD integrated to file based.
Other than that if you demote a DC, it will definately stopped doing any
function which was integrated as part of its former role.
~ Finally, powerful
