Slightly OT, but very important:
Please be aware that Exchange 2010 SP2 is now OUT OF SUPPORT.
You must be on Exchange 2010 SP3 to be in support.
P.S. -- I also dislike AutoMap. Almost as much as I dislike Yammer.
-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Richard Stovall
Sent: Friday, August 8, 2014 2:42 PM
To: [email protected]
Subject: Re: [Exchange] Full Access mailbox stays in Outlook, can't be removed.
I have always used the one below without the "-InheritanceType ALL" switch.
Add-MailboxPermission "[email protected]" -User [email protected]
-AccessRights FullAccess -AutoMapping:$false
I think this only works with Exchange 2010 SP2 and above.
On Fri, Aug 8, 2014 at 2:17 PM, Beckers, Shawn (IT Services)
<[email protected]> wrote:
> May I ask what command/commands you use in EMS to do this?
>
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Richard Stovall
> Sent: Friday, August 08, 2014 11:23 AM
> To: [email protected]
> Subject: Re: [Exchange] Full Access mailbox stays in Outlook, can't be
> removed.
>
> I dislike the automap feature. I always add mailboxes to other users'
> accounts using EMS.
>
> On Fri, Aug 8, 2014 at 12:03 PM, Maglinger, Paul <[email protected]> wrote:
>> I had a case today where a user was granted full access to a mailbox.
>> Automapping kicked in and the mailbox appeared in the user’s Outlook client.
>> The user no longer needed access so I removed the full access. The
>> mailbox didn’t go away and I was unable to remove it from Outlook.
>> This caused me to search for a solution and I did find several such
>> as using ADSIedit and others using the EMS. I used the EMS and put in:
>>
>>
>>
>> # Add-MailboxPermission -Identity JeroenC -User 'Mark Steele'
>> -AccessRight FullAccess -InheritanceType All -Automapping $false
>>
>>
>>
>> And it worked.
>>
>>
>>
>> My question is that these solutions are almost 3 years old. Why is
>> this still a problem? Seems that if automapping puts it there it
>> should also be able to remove it.
>>
>>
>>
>> -Paul
>
>
