Get-Message cmdlet does not respect the defined write scope in Exchange Server 2010

Applies to: Exchange Server 2010 Service Pack 3Exchange Server 2010 EnterpriseExchange Server 2010 Standard

Symptoms


A Role Based Access Control (RBAC) role assignee who you want to restrict from running *-Message cmdlets, such as the Export-Message cmdlet, cannot be restricted from running these cmdlets by using a custom write scope.

Resolution


To resolve this issue, install the following update rollup:
2936871 Update Rollup 6 for Exchange Server 2010 Service Pack 3

Status


Microsoft has implemented this feature in Update Rollup 6 for Exchange Server 2010 Service Pack 3.

More Information


For more information about RBAC, go to the following Microsoft website:For more information about *-Message cmdlets, go to the following Microsoft website: For more information about a similar issue for the *-Queue cmdlets, click the following article number to view the article in the Microsoft Knowledge Base:
2501070 A RBAC role assignee can stop queue processing on an Exchange Server 2010 Hub Transport server or an Exchange Server 2010 Edge Transport server that is outside the role assignment scope