This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(86.4, 99%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EIE%3C/text%3E%3C/svg%3E)
We have Exchange 2019 DAG on premise, recently we have added a domain user (will be new Exchange Admin) in Organization Management group. But still he has no permission on Exchange Admin Console. One he login to ECP he is getting same page like a normal user.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 22%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKY%3C/text%3E%3C/svg%3E)
Hi @IT Engineer,
Are the Exchange DAG member servers in different AD sites?
If yes, please force the AD replication between the sites and see if it can help with this issue.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi Kael,
No they are in the same site. We checked at AD side user appears in the organization management group.
Please note: we are in the process of migration from Exchange 2016 Dag to Exchange 2019 both are in different sites both site has AD. however the user need to access 2019 dag so we added him at our 2019 site as we checked it reflects at the 2016 Dag and AD site as well.
But the problem is still the same he has no access to Admin console.
Thanks for the information.
Are the Exchange 2016 and 2019 in the same AD forest (in other words it is the same Exchange organization)?
And is the "Organization Management" role group the built-in one? (not a custom role group)
Please have a check if the permission is present on the affected Exchange server with this cmdlet in Exchange Management Shell:
Get-RoleGroupMember "Organization Management"
If it is present, please try remove and re-add the permission via cmdlet and see if it makes any difference:
Remove-RoleGroupMember "Organization Management" -Member "user email address"
Add-RoleGroupMember "Organization Management" -Member "user email address"
Hi,
I am writing here to confirm with you how thing going now?
Please let us know if you would like further assistance.