One of the features introduced in Exchange 2010 SP1 which had mixed response was the auto mapping of mailboxes in Outlook, to which the user had full access to. Though it is a good feature, there was no control over it and some admins found it very frustrating, especially the ones that had users with too many shared mailboxes.
Microsoft has listened to the customer feedback and have put a parameter that can control the auto mapping.
As an admin, you can specify whether auto mapping should be enabled or not, when a user is given full access. The parameter is called “AutoMapping”. By default, auto mapping is enabled.
Run the following command to give a user full access without auto mapping.
Add-MailboxPermission –identity <user mailbox> –User <user who needs access> –AccessRights FullAccess –InheritanceType All –AutoMapping $false.
In Exchange 2010 SP2, the msExchDelegateListLink is updated properly when a user’s permission is removed, an issue that has been going on for a while. It worked for me with UR5 (read here), though some of my readers had difficulty with it.
With 2010 SP2, does it work properly for all of you?
Hi Rajith,
The future is great but iam having some difficulties,
Iam trying to remove the Automapping on a Office365 enviroment mailbox,
Problem is the automapping originated in the mail enviroment before Office365 (in a regular exchange) at least we believe so :)
So the part of Add-mailboxPermission -Identity “user” is giving me the error “user” was not found
not really an error i think because the alias indeed doesnt exist ?
nevertheless the user is having these half mapped boxes in his outlook
Is there a way to remove all these automappings, regardless of the alias ?
Kind Regards, Rene
Rajith, thank you for your post.
How can I determine who has automapping set to false (or true) on a given mailbox. Get-MailboxPermission does not do the trick. Thank you.
Is there a reason why I get this error?
[PS] C:\Windows\system32>Add-MailboxPermission -Identity userA@domain.com -User userB@domain.com -AccessRights FullAccess -AutoMapping $false
A positional parameter cannot be found that accepts argument ‘-AutoMapping’.
+ CategoryInfo : InvalidArgument: (:) [Add-MailboxPermission], ParameterBindingException
+ FullyQualifiedErrorId : PositionalParameterNotFound,Add-MailboxPermission
Hi Stephen,
Why is there a mailto field in the command? Remove that and try.
This is a great feature…to fix the last “feature.” I went through a client migration from 2010 and this issue popped up. Some users had 20+ full access mailboxes and the network was swamped with automappings, which hammered the server and clients alike. Glad you found this!
Indeed a welcome fix Kyle.