georgedschneider
asked on
Full Mailbox Access
We have an Exchange coexistence scenario between Exchange 2010/2016. I'm having an issue since migrating users from Exchange 2010 to Exchange 2016. Specific users have full mailbox access to all mailboxes in the environment. These users are also members of the organizational management group. There are no issues when the mailboxes that is access is on 2010. As soon as the mailbox is migrated to 2016 it can no longer be accessed by these users. If the user is not a member of organizational management there is no issue. I understand the best practices and the security implication of this configuration but unfortunately this is the setup that is forced upon me. From what I can tell is fullaccess is denied at the 2016 database levels by default. The following command is run to grant full mailbox access on all 2016 databases: Get-mailboxdatases|add-adp ermission -user username -accessrights genericall. The right exists just access is still not granted. Somewhere an inherited right is propagating from the database is my assumption.
You can also look at setting up an admin role for those that need access to all mailboxes.
Hope that helps.
- Exchange 2016 EAC > Permissions > Admin Roles
- Create new Role Group
- Add "ApplicationImpersonation"
and "Mailbox Import Export" roles - Add Members that need access to each mailbox
Hope that helps.
ASKER
My thought was the inherited deny for receive-as at the organizational level. There is no issue on the 2010 mailboxes just the 2016. So what I'm trying to figuring out what is occurring in 2016 differently and what I need to do at the database or org level to resolve.
Did you attempt the suggestion that Ivan (or I) provided?
ASKER
Ivan's suggestion works as well as direct assignment to any mailbox works as well. The issue is I need it to be at the database level like 2010 is so when new users are added the specified individuals have full access without having to run this command. Its the implicit deny for organizational management causing the issue since the user are also a member of this group as well.
ASKER
Wouldn't creating a separate rolegroup have no effect since the users are members of organizationmanagement?
Did you try the role group is suggested?
You are aware that there are roles that are not in the org mgmt role group? Namely, the ones I stated.
You are aware that there are roles that are not in the org mgmt role group? Namely, the ones I stated.
ASKER
Same result when adding them to a new role group.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Definitely not a permission setting that should have been set outside of Exchange originally, IMO.
Personally, I do my best to discourage any full access to all mailboxes at the org or DB level because it is a bad practice as it opens admins up to possible auditing concerns and issues.
http://exchangeserverpro.com/exchange-best-practices-administrator-access-to-user-mailboxes/
Personally, I do my best to discourage any full access to all mailboxes at the org or DB level because it is a bad practice as it opens admins up to possible auditing concerns and issues.
http://exchangeserverpro.com/exchange-best-practices-administrator-access-to-user-mailboxes/
ASKER
I agree with you that under normal operating conditions this is best practice and what I'd rather have in place.
ASKER
This provided the resolution to my issue
try this command:
Get-Mailbox | Add-MailboxPermission -User <username> -AccessRights FullAccess -InheritanceType All -AutoMapping $false
That should give full access to all mailboxes, for user <username>
Regards,
Ivan.