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-adpermission -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.
georgedschneiderAsked:
Who is Participating?
 
georgedschneiderConnect With a Mentor Author Commented:
I removed the deny for receive as  for organization management which which set at the Microsoft Exchange level using adsiedit.  This allowed us the ability to set full access at the database level using Get-mailboxdatases|add-adpermission -user username -accessrights genericall.  This prevent the inherited implict deny from being inherited.
0
 
IvanSystem EngineerCommented:
Hi,

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.
0
 
Todd NelsonSystems EngineerCommented:
You can also look at setting up an admin role for those that need access to all mailboxes.

  • 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.
2
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
georgedschneiderAuthor Commented:
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.
0
 
Todd NelsonSystems EngineerCommented:
Did you attempt the suggestion that Ivan (or I) provided?
0
 
georgedschneiderAuthor Commented:
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.
0
 
georgedschneiderAuthor Commented:
Wouldn't creating a separate rolegroup have no effect since the users are members of organizationmanagement?
0
 
Todd NelsonSystems EngineerCommented:
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.
0
 
georgedschneiderAuthor Commented:
Same result when adding them to a new role group.
0
 
Todd NelsonSystems EngineerCommented:
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/
0
 
georgedschneiderAuthor Commented:
I agree with you that under normal operating conditions this is best practice and what I'd rather have in place.
0
 
georgedschneiderAuthor Commented:
This provided the resolution to my issue
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.