Select the product you need help with
Add-ADPermission cmdlet together with a DomainController parameter fails in an Exchange Server 2010 environmentArticle ID: 2698899 - View products that this article applies to. SymptomsConsider 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 CauseThis 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. ResolutionTo resolve this issue, install the following update rollup: 2706690
(http://support.microsoft.com/kb/2706690/
)
Description of Update Rollup 4 for Exchange Server 2010 Service Pack 2 StatusMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. More informationFor more information about the Enable-Mailbox cmdlet, go to the following Microsoft website: General information about the Enable-Mailbox cmdlet For more information about the Add-ADPermission cmdlet, go to the following Microsoft website:
(http://technet.microsoft.com/en-us/library/aa998251.aspx)
General information about the Add-ADPermission cmdlet
(http://technet.microsoft.com/en-us/library/bb124403.aspx)
Properties | Article Translations
|


Back to the top








