Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 781
  • Last Modified:

Outlook 2010 creating large OST for Fully Managed Mailboxes

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.
0
bm_alvarez
Asked:
bm_alvarez
  • 3
  • 2
  • 2
  • +1
1 Solution
 
BlueComputeCommented:
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?
0
 
bm_alvarezAuthor Commented:
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.
0
 
Simon Butler (Sembee)ConsultantCommented:
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

Simon.
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
BlueComputeCommented:
Sorry for the incorrect info bm_alvarez...  every day's a school day!
0
 
bm_alvarezAuthor Commented:
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
0
 
Simon Butler (Sembee)ConsultantCommented:
You should check that you are on Exchange 2010 SP2.
http://technet.microsoft.com/en-gb/library/hh135098(v=exchg.141).aspx

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

Simon.
0
 
bm_alvarezAuthor Commented:
Updating Exchange 2010 to SP2 during this weekend's maintenance window. I will update this question after that maintenance is complete.
0
 
Karen FalandaysTraining SpecialistCommented:
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.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 3
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now