Meinolf
Wed Aug 13 13:10:17 PDT 2008
Hello MSNewsgrp,
On the running DC/DNS make sure that you use AD integrated zones on the DNS
server. So it also replicates the DNS zones to the new server. Is there another
DC in the site? Make sure the new DC points to an up and running DNS server
as preferred DNS on the NIC, no other server. Also make this new DC DNS server
and Global catalog server after promotion. When AD database and DNS is fully
replicated change the preferred DNS server to itself and another DNS as secondary
on the new DC. If you have configured FORWARDERS on the main DNS server,
you have also configure them on the new DNS server. Server configs will not
be replicated, only the sites.
Configure AD Sites and services for the site and subnet and move the new
DC to the site after promotion. So all clients at the remote site will use
this DC for authentication first. Also if DNS is replicated( take round about
15 minutes) reconfigure all machines at the remote site to use the site DNS
as preferred DNS and another as secondary.
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
> We have a remote site connected via PtP fiber ethernet 60MBps. I am
> promoting 1 server to a DC. Is there any special
> precaution/consideration for this new DC or AD changes?
>
> Thanks
>
> Kirl
>