Scenario D: Active Directory failure
Applies To: Dynamics CRM 2013
In most environments, it’s highly unlikely that Active Directory will fail on its own, because more than one Active Directory domain controller should be installed.
Scenario D recovery
Recover from a failed domain controller
Reinstall the Windows Server 2012 or Windows Server 2008 operating system.
Perform a system state restore.
Make sure that you have a method for recovering from an Active Directory failure. Regardless of the size of your environment, you should consider having multiple domain controllers with regular backups of the system state. If your backups aren’t current, any data that belongs to Microsoft Dynamics CRM objects in Active Directory will be orphaned in SQL Server and therefore will be unrecoverable. Any changes that are made in CRM, such as adding new users or queues, requires that Active Directory is backed up immediately after the change.
One major problem can occur with Active Directory that stops Microsoft Dynamics CRM from functioning. If an administrator unintentionally deletes the organizational unit (OU) that corresponds to a CRM deployment, Microsoft Dynamics CRM becomes inoperable. Similarly, if any of the OU security groups that are created by Microsoft Dynamics CRM are deleted (such as PrivUserGroup, ReportingGroup, PrivReportingGroup, or SQLAccessGroup), Microsoft Dynamics CRM will no longer function correctly. In either of these events, an authoritative restore of Active Directory restores the deleted OU, and security groups, to their original state.
If you can’t restore an Active Directory backup, you can create new security groups by reinstalling Microsoft Dynamics CRM Server 2013 as a new deployment. After the installation is complete you can import the organization databases using Microsoft Dynamics CRM Deployment Manager.
For more information about Active Directory backup and recovery, see Steps for Backing Up and Recovering AD DS.
© 2016 Microsoft Corporation. All rights reserved. Copyright