- #Getting the problem domain of the database back in focus how to#
- #Getting the problem domain of the database back in focus Pc#
If this is the case, you’ll have to seize the roles. If the domain has serious-enough problems, you may not be able to transfer the roles. After you’ve transferred each role, click OK to close the properties sheet.
To transfer the role, click the Change button. As you go through each tab on the properties sheet, you’ll see the name of the server that presently holds the designated role and the name of the server that you selected to transfer the role to. You’ll see the Operations Master properties sheet. Finally, right-click on the domain name and select the Operations Master command from the context menu. Now, select the domain controller that you want to transfer the role to from the list of domain controllers and click OK. Next, right-click on the domain name and select the Connect To Domain Controller command from the resulting context menu. To transfer a role, open Active Directory Users And Computers. Then, attempt to transfer the roles to it.
#Getting the problem domain of the database back in focus Pc#
If no other domain controllers exist within the domain, try temporarily installing a copy of Windows 2000 Server onto a spare PC and making the spare server a domain controller. Once you’ve determined which server holds the domain-level operation master roles, try transferring those roles to another domain controller. For detailed instructions on locating the various server roles, see “Understanding Windows 2000 domain controller operations master roles.” When the entire domain fails, the other domains usually won’t be able to communicate with the failed domain and also cease to function. If the forest-level roles are handled by a domain controller within the failing domain and the rest of your domains seem to be functioning correctly, it’s a good indication that you may simply have a domain-level role failure rather than an entire domain failure. If the forest-level roles are being handled by a domain controller within the failing domain, you certainly don’t want to do anything to disrupt the servers that are performing the server-level roles. You need to make note of the forest-level roles as well as the domain-level roles. The first step to recovering from such a problem is to note which servers are performing which roles. Therefore, there’s a chance that, rather than having a corrupt Active Directory database, you may simply have a domain controller that’s failing to perform its designated roles.
A domain can’t function if the domain-level operation master roles aren’t being performed. Some of these roles are forest-based and others are domain-based. If you’re sure you’re ready, let’s roll the dice.Īs you may recall, various operations master roles are associated with some of the critical Active Directory functions. These techniques may solve your problem, but they stand an equal chance of destroying Active Directory completely. You should also make sure that you’ve tried every other possible diagnostic and repair technique before attempting to work through any of the techniques that I’m about to discuss. Make absolutely certain that you have a good backup of your entire Active Directory before you try any of these techniques. Recovering from a domain-level Active Directory failure is a major undertaking.
#Getting the problem domain of the database back in focus how to#
I’ll show you how to recover from a domain-level Active Directory failure and avoid this worst-case scenario. You may be able to salvage the domain, but, if you can’t, you may have to strip the domain bare, delete the domain, re-create the domain, and finally, add the servers back into the domain. What could possibly be worse than having a server on your network crash? How about having every server on your network become inaccessible because of a massive, domain-wide Active Directory failure? As horrifying as a total domain failure may sound, the solution could be just as scary.
Ignore the odds and prepare for the worst, as Brien Posey shows you how to recover from this unlikely but devastating event. Having an entire Active Directory domain fail is almost unthinkable. Recovering from a complete domain-level Active Directory crash