This is a third and the last post in my Mailbox Manager series. Please go here for Part 1 and here for Part 2!
Here are some of the most frequently asked questions that we have seen on Mailbo...
Updated Jul 01, 2019
Version 2.0
Blog Post
Yes, applying the hotfix listed in http://support.microsoft.com/?id=883351 resolves this issue. Note: This may not fix users that are currently experiencing the problem.
- To fix the users that were previously affected by this, we would need to touch each of the users in Active Directory so
that the RUS will update them.
- To do this, create a new Mailbox Manager Policy that encompasses all Exchange
users. Move this policy up in priority so that it is higher than any other MM
policy. Doing this will update all users with this new policy and remove the
additional MM policies.
- Once this is done, go ahead and delete the temporary policy that you created. When that policy is deleted, the correct policy will be applied to all users.
- To fix the users that were previously affected by this, we would need to touch each of the users in Active Directory so
that the RUS will update them.
- To do this, create a new Mailbox Manager Policy that encompasses all Exchange
users. Move this policy up in priority so that it is higher than any other MM
policy. Doing this will update all users with this new policy and remove the
additional MM policies.
- Once this is done, go ahead and delete the temporary policy that you created. When that policy is deleted, the correct policy will be applied to all users.