WDit
asked on
Unable to add user to Send As on a distribution group.
I am having trouble adding someone to be able to "Send As" a distribution group in the Exchange 2016 GUI. When I click on the "plus" sign next to "Send As" the list from the GAL only shows 30 objects instead of the 600+ objects that are in the GAL. Is there something corrupt somewhere? If I click on the "plus" sign next to "Send on Behalf" the entire GAL list shows up. This is the same even with a new group or any of the existing groups. Any assistance you can provide would be greatly appreciated.
ASKER
I tried using PS too and it errors out with permissions error. I checked and the admin account I am using to manage Exchange has full permissions to all distribution lists.
Active Directory operation failed on domaincontroller.domain.com. This error is not retriable. Additional information:
Access is denied.
Active directory response: 00000005: SecErr: DSID-03152D7B, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
+ CategoryInfo : WriteError: (0:Int32) [Add-ADPermission], ADOperationException
+ FullyQualifiedErrorId : [Server=EXCHANGESERVER,RequestId=0dac371d-df37-42f9-90b7-06682dea4085,TimeStamp=8/11/2022 11
:06:34 AM] [FailureCategory=Cmdlet-ADOperationException] 104E2289,Microsoft.Exchange.Management.RecipientTasks.Add
ADPermission
+ PSComputerName : exchangeserver.domain.com
Active Directory operation failed on domaincontroller.domain.com. This error is not retriable. Additional information:
Access is denied.
Active directory response: 00000005: SecErr: DSID-03152D7B, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
+ CategoryInfo : WriteError: (0:Int32) [Add-ADPermission], ADOperationException
+ FullyQualifiedErrorId : [Server=EXCHANGESERVER,RequestId=0dac371d-df37-42f9-90b7-06682dea4085,TimeStamp=8/11/2022 11
:06:34 AM] [FailureCategory=Cmdlet-ADOperationException] 104E2289,Microsoft.Exchange.Management.RecipientTasks.Add
ADPermission
+ PSComputerName : exchangeserver.domain.com
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
maybe you can use workaround via Exchange Shell to add permissions.
Open in new window