Exchange 2013/2010
Does anyone have a Pro and Con list for Automapping in Exchange. I am putting together reasons why we should maintain this. I am fighting a battle with some of my users who hate Automapping and want it to go away. I love the ease of administration but they dislike it because every remote machine they log into adds it automatically which is a plus for me.
this is just an art of administration
My art of administration as follows
if a user want automapping, add them directly to to the mailbox
if a user don't want automapping, add the user to a DL, and add the DL to the mailbox (automapping will not cascade down to the user)
This way, all fullmailbox rights will be added as automapping enabled (no changes happen there)
The biggest thing i notice is if a user have too many fullmailboxes rights, outlook 2010 by default only cache 50GB and if you have setup your outlook to cached share mailbox right, when over 50GB, you start to have warning/error that you can't send emails because it is over 50gb on local machine, took me a hour to root cause such issues.
My art of administration as follows
if a user want automapping, add them directly to to the mailbox
if a user don't want automapping, add the user to a DL, and add the DL to the mailbox (automapping will not cascade down to the user)
This way, all fullmailbox rights will be added as automapping enabled (no changes happen there)
The biggest thing i notice is if a user have too many fullmailboxes rights, outlook 2010 by default only cache 50GB and if you have setup your outlook to cached share mailbox right, when over 50GB, you start to have warning/error that you can't send emails because it is over 50gb on local machine, took me a hour to root cause such issues.
ASKER
Anything else
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You should make your own case but I suspect the company/users don't care how easy your admin is.