Outlook Auto-Mapping was added as a feature when Microsoft Exchange Server 2010SP1 was released. It allows Outlook 2007 SP2 and later to automatically map any mailbox where a user has Full Access permission.
If a user had Full Access permission to many different mailboxes, this meant all of them would be opened and accessible in Outlook. At first glance this seemed like a great idea, but as more of my users starting experiencing auto-mapping I soon found it was becoming a nightmare. However, the release of SP2 for Exchange 2010 brought relief and allowed administrators to disable Outlook auto-mapping for users with full access permissions.
It's possible to disable Outlook Auto-mapping using Exchange Management Shell, when you have a request for Full Access permissions you can disable Auto-Mapping immediately using the following command:
Add-MailboxPermission-Identity Mailboxname -User Username-AccessRight FullAccess -Automapping$false
the flag -Automapping$false disable the automapping feature
The following command removes auto-mapping for an existing mailbox by removing the permissions from the mailbox and then re-applying the Full Access permissions with Automapping set to $false. You will be asked to confirm that you want to remove the permissions at which point you answer yes.
$FixAutoMapping=Get-MailboxPermission-Identity sharedmailbox|where{$_.AccessRights-eq"FullAccess"-and$_.IsInherited-eq$false}$FixAu
As you can see, the ability to disable Outlook Auto-mapping through PowerShell is simple to use when setting up Full Access permissions to another mailbox. The next time a user complains that Outlook is slow, you now have another tool in your troubleshooting toolbox to try. Take a look at Outlook and see if they are opening multiple mailboxes that aren’t listed in their profile. If they do, disabling Auto-Mapping might just do the trick.
- 0 Users Found This Useful
Related Articles
Always reply with the same email address
Assume you have a new email account for utixo@newdomain.com which you want to use when replying...
"400 Bad Request" error when a user accesses the Options in OWA (Exchange Server 2010)
The error occurs because the user does not have a time zone value specified on the mailbox in...
Exchange 2010 how to set Client Access Priority
This is the shell command to associate the database to the client access server:...
How do I change my password in Outlook Web App 2016 (OWA)?
If you need to change your password go to Outlook Web App : https://mail.utixo.eu Log in using...
Set up SPF to help prevent email spoofing
SPF determines whether or not a sender is permitted to send on behalf of a domain. If the sender...
Powered by WHMCompleteSolution
