Re: one of two dc's crashed

You will need to clean up the old dc's metadata, otherwise it will haunt
you.
http://support.microsoft.com/Default.aspx?id=216498

Make sure that you have all the fsmo roles residing on your existing dc. To
find out run netdom query fsmo on your existing dc, if all 5 roles don;t
exist on the new dc then seize the roles.
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B255504

I would assume that the existing dc must be a GC otherwise your users
wouldn't be able to logon.

How about DNS? Do your clients point to the old DC for dns services? If so
you will have to visit them and remove this entry. Same for WINS.


--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

"myweb" <meiweb@xxxxxx> wrote in message
news:59710d1b7a38c8dc4d95f37b60@xxxxxxxxxxxxxxxxxxxxxxx
Hello Andy,

You didn't have any backup solution for your lost DC to bring it back?
If you really want to build up a new one first check if the existing DC
has all 5 FSMO rules and is a GC server. Even it must have installed a
running DNS. The NIC must point to the running DNS server.Also check
before you start with the promotion from the new server that it has a
fixed ip address and is also pointing to the running DNS server for a good
replication of your AD.

AND MOST IMPORTANT: CREATE A BACKUP OR IMAGE OF YOUR RUNNING DC
BEFORE!!!!!!!

Best regards

myweb
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.



in my domain of two dc's one crashed last night (2000 server). On the
dc that is still standing I can see the old dc listed. I have no plans
to bring the old dc back, however I plan to use a different member
server and promote that to a dc. Am I going to come across problems
leaving the crashed dc listed. The domain seems to be working if a
little slow!





.

Relevant Pages

  • Re: one of two dcs crashed
    ... You didn't have any backup solution for your lost DC to bring it back? ... The NIC must point to the running DNS server.Also check before you start with the promotion from the new server that it has a fixed ip address and is also pointing to the running DNS server for a good replication of your AD. ... I have no plans ...
    (microsoft.public.win2000.active_directory)
  • Re: Use second Domain controller
    ... Your environment can stay workable for quite some time with some of the fsmo ... To learn where the fsmo roles currently reside: ... If you don't have the tools installed, install them from your server install ... Windows 2000 domain controller in the domain. ...
    (microsoft.public.windows.server.active_directory)
  • Re: INBOUND / OUTBOUND REPLICATION DISABLE
    ... Since we have no other dc in our organisation except this server ... state restore which might also affect my exchange server. ... transfer FSMO roles to the new DC. ... Transfer of domain naming FSMO failed, proceeding with seizure ... ...
    (microsoft.public.windows.server.active_directory)
  • Re: INBOUND / OUTBOUND REPLICATION DISABLE
    ... except this server running exchange" ... MVP Windows Server - Directory Services ... transfer FSMO roles to the new DC. ... > Transfer of domain naming FSMO failed, proceeding with seizure ... ...
    (microsoft.public.windows.server.active_directory)
  • Re: System State Restore Troubles
    ... How to Find the FSMO Role Owners Using ADSI and WSH: ... > I am restoring my current Small Business Server 2000 to a test system so I ... > Computer: THOMAS ... > server connections: Connect to server Thomas ...
    (microsoft.public.windows.server.active_directory)