Consider the following scenario:
- You have some database availability groups (DAGs) in a Microsoft Exchange Server 2010 environment.
- You create a management role assignment in the environment.
- You assign management roles to a role assignee.
- You define the scope of the role assignment to a member mailbox server in a DAG.
- The role assignee tries to make some changes to another DAG that is outside the scope of the management role group by using one of the following cmdlets:
This issue occurs because there is no Role Based Access Control (RBAC) scope validation when Exchange Server 2010 runs *-DatabaseAvailabilityGroup cmdlets.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about management role scopes, go to the following Microsoft website:New-DatabaseAvailabilityGroup cmdlet, go to the following Microsoft website:Set-DatabaseAvailabilityGroup cmdlet, go to the following Microsoft website:Remove-DatabaseAvailabilityGroup cmdlet, go to the following Microsoft website: Stop-DatabaseAvailabilityGroupcmdlet, go to the following Microsoft website: Start-DatabaseAvailabilityGroup cmdlet, go to the following Microsoft website:
Article ID: 2720017 - Last Review: Dec 14, 2012 - Revision: 1
Microsoft Exchange Server 2010 Service Pack 1, Microsoft Exchange Server 2010 Service Pack 2