Wednesday, 31 October 2012

Microsoft Dynamics CRM 2011 - Failure Recovery for Scenario: Active Directory Failure

In most environments, it is highly unlikely that Active Directory will fail on its own, because more than one Active Directory domain controller should be installed. 

To recover from a failed domain controller, follow these steps:

  • Reinstall the Windows Server 2003 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 are not current, any data that belong 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 Microsoft Dynamics CRM, such as adding new Microsoft Dynamics CRM 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 Microsoft Dynamics CRM deployment, it becomes inoperable. Similarly, if any of the OU security groups that are created by Microsoft Dynamics CRM are deleted (such as PrivUserGroup, ReportingGroup, PrivReportingGroup, SQLAccessGroup, or UserGroup), 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.

My above blog is based on Microsoft's Official information.
I hope this blog about 'Microsoft Dynamics CRM 2011 - Failure Recovery for Scenario: Active Directory Failure' was informative. Please feel free to leave your comments.

No comments:

Post a Comment