Outlook 2010 creating large OST for Fully Managed Mailboxes

Posted on 2013-01-16
Last Modified: 2013-04-22
I have a client who wants to be able to open and view employees mailboxes. In Exchange 2003 I simply gave him permissions and he could access the mailbox via OWA. When we migrated to Exchange 2010 on a 2011 SBS over a year ago I gave him Full Managed Access and he could again access the mailboxes at first through OWA and then with Outlook 2010 they showed up automatically.

Recently he received a new PC with the latest version of Outlook 2010 and it added these managed mailboxes to his local OST file making it huge. I unchecked caching shared mailboxes and still the OST includes all mailboxes. Not using Cache makes Outlook crawl because it is trying to be real-time to all the mailboxes.

How can I give him access to be able to open every mailbox without it creating a large OST? I need quick access to his Mailbox and occasional access to the others. Accessing them through Outlook 2010 or OWA is acceptable.
Question by:bm_alvarez
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
  • 2
  • +1
LVL 14

Expert Comment

ID: 38785275
The cached mailboxes won't automatically be removed from the OST, you will need to blow it away and let Outlook build a new one.

Granting a user full access permissions on a mailbox won't normally cause it to be automatically opened in Outlook.  You should be able to simply grant permissions on all mailboxes, uncheck the 'cache additional mailboxes' and away you go.

Do the additional mailboxes show up in Outlook under the heading 'Managed Folders?

Author Comment

ID: 38785333
What you described is how it used to work but with Outlook 2010 SP1 there is an Auto Mapping feature for all Full Access Mailboxes. I did remove the OST file and had Outlook create a new one and it also included all the Full Access Mailboxes, this is with Cache Shared Mailboxes unchecked.
LVL 63

Accepted Solution

Simon Butler (Sembee) earned 300 total points
ID: 38786144
You can disable automapping using PowerShell. It requires Exchange 2010 SP2 and has to be done on each mailbox in turn:

Add-MailboxPermission "Shared Mailbox" -User -AccessRights FullAccess -AutoMapping:$false

SuperAntiSpyware Licenses Discounted by 25% !

Exclusive offer to Experts Exchange Members!
Buy SuperAntiSpyware License(s) from us and save 25% on the regular purchase price.
- Includes Full SuperAntiSpyware Vendor Support Entitlements
- Your Subscription does not begin until you activate your license
- Buy for your friends

LVL 14

Expert Comment

ID: 38786971
Sorry for the incorrect info bm_alvarez...  every day's a school day!

Author Comment

ID: 38796830
When I try the PowerShell cmdlet I get an error: "A parameter cannot be found that matches parameter name 'Automapping'.

The command I entered was:
Add-MailboxPermission -Identity xxxxxx -User 'xxx xxxxx' -AccessRight FullAccess -Automapping $false
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 38798345
You should check that you are on Exchange 2010 SP2.

If not then you will have to update the server first.


Author Comment

ID: 38815817
Updating Exchange 2010 to SP2 during this weekend's maintenance window. I will update this question after that maintenance is complete.
LVL 18

Expert Comment

by:Karen Falandays
ID: 39100295
I've requested that this question be closed as follows:

Accepted answer: 300 points for Sembee2's comment #a38798345

for the following reason:

This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
This video discusses moving either the default database or any database to a new volume.
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to:…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question