Beginning with Exchange 2010 then on to Exchange 2013. User who used the client Outlook 2007/2010/and 2013 had a new feature called automapping.
Automapping takes advantage of Exchange auto-discovery services to map mailboxes in which a user has “Full Access” permissions granted.
This is very helpful to the end-user as he or she is no longer required to know or learn how to add additional mailboxes to Outlook.
The not so helpful side is when a user’s access is removed and a ghosted mailbox folder exists in Outlook that the user is unable to remove. Attempts to close the mailbox result in a message that reads:
This group of folders is associated with an e-mail account. To remove the account, click the File Tab, and on the info tab, click Account Settings, Select the e-mail account, and then click Remove.
Thanks’s but this doesn’t work. In fact, even on a clean install of Outlook the user still has the ghost folders associated with their Outlook Client.
So to tackle this issue, I used ADSIedit.
- Open ADSIEdit (WinKey R to open Run and type adsiedit.msc)
- Connect to the Default Naming Context. (Click OK)
- Locate the mailbox that you once were granted Full Access Permissions and …
- Right-click on the object, view properties.
- Scroll down to MsExchDelegateListLinked attribute.
- Click Edit, select the User Object and click Remove your information.
Now give it a little time for the change to replicate out in our Active Directory, you will later find these folders to be gone.
To prevent this from occurring when adding mailboxes you could always run the following command to disable automapping:
Add-MailboxPermission -Identity firstname.lastname@example.org
-User email@example.com -AccessRights FullAccess
Update from the comments 6/5/2017:
To find the mailbox, you actually find the AD user account, under the OU=Domain Name, within ADSIEdit. – Thanks ‘ splunch ‘ for the info.