>>>>>>> ahhhhh. now I understand
>>>>>>>
>>>>>>> ok, try the following
>>>>>>>
>>>>>>> introduce a NEW w2k3 DC into the existing domain (which is just 1 DC) and
>>>>>>> also make it a GC and a DNS server. After the promotion the domain will have
>>>>>>> two DCs, one unhealthy and one healthy
>>>>>>> from the healthy DC start exporting stuff that needs to be exported (.e.g
>>>>>>> DHCP stuff, etc.)
>>>>>>> Shutdown the UNhealthy DC
>>>>>>> on the healthy DC clean the AD metadata of the UNhealhty DC
>>>>>>> on the healthy DC seize ALL FSMO to the healthy DC
>>>>>>>
>>>>>>> use the following commands to check the health of the healthy DC:
>>>>>>> DCDIAG /C /D /V
>>>>>>> GPOTOOL /CheckAcl /Verbose
>>>>>>>
>>>>>>> if thats OK do:
>>>>>>> ADPREP /FORESTPREP
>>>>>>> ADPREP /RODCPREP (if you want to use RODCs, does not hurt if you do this!)
>>>>>>> ADPREP /DOMAINPREP /GPPREP
>>>>>>>
>>>>>>> Install the W2K8 DC, make it a GC, a DNS server and transfer the FSMO roles
>>>>>>> to the W2K8 DC
>>>>>>> demote the healthy w2k3 DC and remove from domain
>>>>>>>
>>>>>>> it should be something like this
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> Cheers,
>>>>>>> (HOPEFULLY THIS INFORMATION HELPS YOU!)
>>>>>>>
>>>>>>>
>>>>>>> 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!
>>>>>>> ------------------------------------------------------------------------------------------
>>>>>>> ------------------------------------------------------------------------------------------
>>>>>>> "Ryguy" <Ryguy@discussions.microsoft.com> wrote in message
>>>>>>> news:2FA0F36C-BA12-4A54-A6BF-9547E542C782@microsoft.com...