Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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


View products that this article applies to.

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.

↑ Back to the top


Resolution

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

↑ Back to the top


Status

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

↑ Back to the top


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

↑ Back to the top


Keywords: kbqfe, kbfix, kbsurveynew, kbexpertiseadvanced, kb

↑ Back to the top

Article Info
Article ID : 2927265
Revision : 1
Created on : 1/7/2017
Published on : 5/27/2014
Exists online : False
Views : 154