Windosw Server 2003 RRS feed

  • Question

  • A business has an existing Windows Server 2003, ADS Domain that consists of two domain controllers in a single domain tree, and multiple Windows XP Professional domain clients.

    One of the domain controllers decides, on its own, that it no longer wants to be a working computer.  It decides instead, to be a very large doorstop.

    The domain controller that “died” happens to be the first domain controller that was created when the domain was built.  Users show up to work that day…

    can they still login to the domain?


    a.       Any conclusions as to what happens to the business when a domain controller goes down.

    Jacq smccmaine
    • Moved by Hengzhe Li Tuesday, September 27, 2011 11:19 AM off topic (From:MSDN, TechNet, and Expression Profile and Recognition System Discussions)
    Monday, September 26, 2011 12:14 PM


  • The users should be able to logon if DNS is available, and the clients are configured correctly. If the server that died is the only one with DNS configured, then users won't be able to function (the cannot resolve names into ip addresses). Also, if all FSMO roles are on the DC that died, users won't be able to change their passwords (requires the PDS Emulator role). You should seize any FSMO roles that were on the DC that died, so they are moved to the remaining DC. And of course you should promote another DC soon so that your redundancy is restored.

    For more information, please post your question on the Directory Services forum:


    Experts there can give you links to documents explaining all of the issues, how to resolve them, and also what to do ahead of time to ensure users are not impacted when this happens.


    Richard Mueller - MVP Directory Services
    Monday, September 26, 2011 4:46 PM