Jorge
Wed Jul 09 04:13:28 PDT 2008
make it a GC
transfer all FSMOs
do the other stuff already mentioned
demote the old one (or just turn it off for 1 day or so to see what goes
wrong. if something goes wrong. turn it back on again and solve what needs
to be solved)
no rejoining and norestting permissions
by the way: aleays have at least 2 DCs!
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto # MVP Identity & Access - Directory Services #
BLOG (WEB-BASED)-->
http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)-->
http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* How to ask a question -->
http://support.microsoft.com/?id=555375
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test ANY suggestion in a test environment before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"Mmaxx" <mmaxx@webmail.co.za> wrote in message
news:dYGdnXmuN-4I4unVnZ2dnUVZ8vydnZ2d@saix.net...
> Jorge de Almeida Pinto [MVP - DS] wrote:
>> install a new DC, move roles/services over and reconfigure servers,
>> clients and dhcp clients to point to the new dns server if it hosts dns
>>
> SO if I understand you correctly, I need to :
>
> Install fresh server 2oo3 etc on new hardware,
> Bring AD etc online as non GC domain controller
> Install all the services I used on the old domain controller here, and
> ensure replication is working ok
> update dhcp to supply new dc's ip
> demote old dc
> promote new dc
>
> And I wont have to rejoin clients to the domain or reset permissions?
>
> Thanks
>
> Max