Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
Add-ADPermission cmdlet together with a DomainController parameter fails in an Exchange Server 2010 environment
Article ID: 2698899 - View products that this article applies to.
Consider the following scenario:
User wasn't found. Please make sure you've typed it correctly.
+ CategoryInfo : InvalidArgument: (:) [Add-ADPermission], ManagementObjectNotFoundException
+ FullyQualifiedErrorId : Error ID,Microsoft.Exchange.Management.RecipientTasks.AddADPermission
This issue occurs because the Exchange server does not use the specified global catalog server when an Active Directory session is created after the role-based access control (RBAC) scope verification process is complete.
To resolve this issue, install the following update rollup:
(http://support.microsoft.com/kb/2706690/ )Description of Update Rollup 4 for Exchange Server 2010 Service Pack 2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the Enable-Mailbox cmdlet, go to the following Microsoft website:
General information about the Enable-Mailbox cmdletFor more information about the Add-ADPermission cmdlet, go to the following Microsoft website:
General information about the Add-ADPermission cmdlet
Article ID: 2698899 - Last Review: August 16, 2012 - Revision: 5.0