I gave myself full access rights to a user's mailbox and did what I needed to do using OWA. But now, in my Outlook I have their mailbox and I can't remove it. Their name does NOT appear in 'open additional mailbox'

If I remove full access rights on ESM I can't open the mailbox in Outlook, and if I give myself full access rights again I can. But I can't remove or close it. I tried the REGEDIT HKCU edit and so removed the key with the user's name in it and restarted Oulktook. The mailbox added itself while I watched.

I deleted my Mail profile then added it back using another profile name. The ^$^%$^$ mailbox still appears.

Any ideas on how to get rid of it?

Thanks

Hi,

What version of Outlook and Exchange server are you using?

http://technet.microsoft.com/en-us/library/aa995948.aspx

How to Delete an Exchange Server Mail Box:

http://www.tech-faq.com/how-to-delete-an-exchange-server-mail-box.html

Hope that helps.

• Proposed as answer by stin Tuesday, October 09, 2012 4:40 PM

Hi,

What version of Outlook and Exchange server are you using?

http://technet.microsoft.com/en-us/library/aa995948.aspx

How to Delete an Exchange Server Mail Box:

http://www.tech-faq.com/how-to-delete-an-exchange-server-mail-box.html

Hope that helps.

• Proposed as answer by stin Tuesday, October 09, 2012 4:40 PM

Hi,

What version of Outlook and Exchange server are you using?

http://technet.microsoft.com/en-us/library/aa995948.aspx

How to Delete an Exchange Server Mail Box:

http://www.tech-faq.com/how-to-delete-an-exchange-server-mail-box.html

Hope that helps.

• Proposed as answer by stin Tuesday, October 09, 2012 4:40 PM

Hi,

What version of Outlook and Exchange server are you using?

http://technet.microsoft.com/en-us/library/aa995948.aspx

How to Delete an Exchange Server Mail Box:

http://www.tech-faq.com/how-to-delete-an-exchange-server-mail-box.html

Hope that helps.

I'm running Outlook 2010 x86 and Exchange 2010 SP1.

The error message when I try and close the mailbox is "This group of folders is associated with an email account. To remove the account click the File tab, and on the Info tab, click Account Settings. Select the email account, then click remove."

But it's not there!

I don't wish to delete the mailbox as it belongs to an active user. I simply wish to remove it from my Outlook.

Hi,

As the warning indicates, you have to remove the account to remove the folders. Then you can add this account again.

Hi,

As the warning indicates, you have to remove the account to remove the folders. Then you can add this account again.

What he is saying, is that there isn't a way to remove the account from Outlook. The accounts in question don't show up in the File > Account Settings > Account Settings > Outlook Profile > More Settings > Advanced.

I too am having this problem, and so is another admin here. I would be interested to know if you enabled online archive TheTrueDrBob, because we hadn't experienced this problem until we turned on Exchange Archiving on the mailboxes in question.

I too have experienced this issue too, with a lousy resolution.  So far what I've found to work is having to go into ADSIEdit.msc, Domain context, and drill down to the account you wish to be removed from, and look for the "MSExchDelegateListLink" attribute and remove yourself from that list.  The next time you start Outlook 2010, the ghost "additional" mailbox should disappear after a few minutes.

I am a little disturbed that I would still have access to this other mailbox AFTER I removed the permissions to it, but because of this MSExchDelegateListLink attribute, that I still did.

If you go to the location in Outlook to Add addition mailboxes, and add one, it seems that you see the rest.  Doesn't help with removing the one you no long have access to.  So, it's hard to say if it's one bug or two, the mailboxPermission PS command exchange uses, doesn't seem to check/clear the MSExchDelegateListLink attribute, and possibly another bug with Outlook not actually listing "Addition Mailboxes" unless you add one, then you see many.

• Proposed as answer by Korbyn Saturday, October 16, 2010 6:43 PM
• Marked as answer by TheTrueDrBob Tuesday, October 30, 2012 7:22 PM

I too have experienced this issue too, with a lousy resolution.  So far what I've found to work is having to go into ADSIEdit.msc, Domain context, and drill down to the account you wish to be removed from, and look for the "MSExchDelegateListLink" attribute and remove yourself from that list.  The next time you start Outlook 2010, the ghost "additional" mailbox should disappear after a few minutes.

I am a little disturbed that I would still have access to this other mailbox AFTER I removed the permissions to it, but because of this MSExchDelegateListLink attribute, that I still did.

If you go to the location in Outlook to Add addition mailboxes, and add one, it seems that you see the rest.  Doesn't help with removing the one you no long have access to.  So, it's hard to say if it's one bug or two, the mailboxPermission PS command exchange uses, doesn't seem to check/clear the MSExchDelegateListLink attribute, and possibly another bug with Outlook not actually listing "Addition Mailboxes" unless you add one, then you see many.

• Proposed as answer by Korbyn Saturday, October 16, 2010 6:43 PM
• Marked as answer by TheTrueDrBob Tuesday, October 30, 2012 7:22 PM

I too have experienced this issue too, with a lousy resolution.  So far what I've found to work is having to go into ADSIEdit.msc, Domain context, and drill down to the account you wish to be removed from, and look for the "MSExchDelegateListLink" attribute and remove yourself from that list.  The next time you start Outlook 2010, the ghost "additional" mailbox should disappear after a few minutes.

I am a little disturbed that I would still have access to this other mailbox AFTER I removed the permissions to it, but because of this MSExchDelegateListLink attribute, that I still did.

If you go to the location in Outlook to Add addition mailboxes, and add one, it seems that you see the rest.  Doesn't help with removing the one you no long have access to.  So, it's hard to say if it's one bug or two, the mailboxPermission PS command exchange uses, doesn't seem to check/clear the MSExchDelegateListLink attribute, and possibly another bug with Outlook not actually listing "Addition Mailboxes" unless you add one, then you see many.

• Proposed as answer by Korbyn Saturday, October 16, 2010 6:43 PM
• Marked as answer by TheTrueDrBob Tuesday, October 30, 2012 7:22 PM

I too have experienced this issue too, with a lousy resolution.  So far what I've found to work is having to go into ADSIEdit.msc, Domain context, and drill down to the account you wish to be removed from, and look for the "MSExchDelegateListLink" attribute and remove yourself from that list.  The next time you start Outlook 2010, the ghost "additional" mailbox should disappear after a few minutes.

I am a little disturbed that I would still have access to this other mailbox AFTER I removed the permissions to it, but because of this MSExchDelegateListLink attribute, that I still did.

If you go to the location in Outlook to Add addition mailboxes, and add one, it seems that you see the rest.  Doesn't help with removing the one you no long have access to.  So, it's hard to say if it's one bug or two, the mailboxPermission PS command exchange uses, doesn't seem to check/clear the MSExchDelegateListLink attribute, and possibly another bug with Outlook not actually listing "Addition Mailboxes" unless you add one, then you see many.

I am also seeing this with Outlook 2010 and Exchange 2010 SP1.  The accounts have been removed from the profile settings, yet they still show up in Outlook.  I've deleted profiles, deleted all the files including the .OST files, created new profiles with different names, but whatever I do, when I open the mailbox, the additional account folders are there.

I also created a profile on a seperate machine with Outlook 2007 and the additional accounts are NOT there.  I need to try this with a seperate machine and Outlook 2010 to be sure, but this seems to be a problem with Outlook 2010 at the client vs in AD/Exchange.

We do NOT have Exchange Archiving setup on any of our mailboxes.

I also have the same issue with Outlook 2010 and SP1, just tried the adsitedit fix and waiting to see if it it disappears.

It worked.

I found the following article on this and why it happens. 

http://www.stevieg.org/2010/08/auto-mapping-shared-mailboxes-in-exchange-2010-sp1-with-outlook-2010/

It turns out this is a feature according to this article.  In the comments below the article you will see that others still had to go remove themselves from the MSExchDelegateListLink attribute, and we had to do the same.  My question is why, when I remove full mailbox access from the mailbox in question, doesn't the MSExchDelegateListLink attribute get removed? 

The information here in this thread and in the article I've linked solved this for us.  Fortunately we have few additional mailboxes where users have full mailbox access outside of their own.

Using Exchange 2010 SP1 and 2008 R2 and Outlook 2010 (migrated from exchange 2007 SP2)

I am facing the same problem

Problem only appeared after upgrading to Exchange 2010 SP1

Tried all possible ways to remove additional mailboxes all fruitless 

i have noticed when editing schema 

there are no values in this attribute for user

msExchDelegateListLink

and there are multiple values for following attribute 

msExchDelegateListBL

and I tried to delete these values but I receive following message 

"The attribute cannot be modified because it is owned by the system."

these entries look like 

msExchDelegateListBL: CN=Jennifer Eder,OU=Reservation,OU=Al-Qouz,OU=Planet,DC=darling,DC=local

msExchDelegateListBL: CN=Hani Khamis Hamad,OU=Head Office,OU=Planet,DC=darling,DC=local

msExchDelegateListBL: CN=Zhou Yun,OU=Chinese Inbound,OU=Head Office,OU=Planet,DC=darling,DC=local

msExchDelegateListBL: CN=Payroll Head Office,OU=Human Resources,OU=Head Office,OU=Planet,DC=darling,DC=local

msExchDelegateListBL: CN=Jay Kumar,OU=Head Office,OU=Planet,DC=darling,DC=local

msExchDelegateListBL: CN=sumith,OU=2010-Remove,DC=darling,DC=local

• Edited by Abdul Jaleel Malik Wednesday, October 27, 2010 4:20 PM more info

Using Exchange 2010 SP1 and 2008 R2 and Outlook 2010 (migrated from exchange 2007 SP2)

I am facing the same problem

Problem only appeared after upgrading to Exchange 2010 SP1

Tried all possible ways to remove additional mailboxes all fruitless 

i have noticed when editing schema 

there are no values in this attribute for user

msExchDelegateListLink

and there are multiple values for following attribute 

msExchDelegateListBL

and I tried to delete these values but I receive following message 

"The attribute cannot be modified because it is owned by the system."

these entries look like 

msExchDelegateListBL: CN=Jennifer Eder,OU=Reservation,OU=Al-Qouz,OU=Planet,DC=darling,DC=local

msExchDelegateListBL: CN=Hani Khamis Hamad,OU=Head Office,OU=Planet,DC=darling,DC=local

msExchDelegateListBL: CN=Zhou Yun,OU=Chinese Inbound,OU=Head Office,OU=Planet,DC=darling,DC=local

msExchDelegateListBL: CN=Payroll Head Office,OU=Human Resources,OU=Head Office,OU=Planet,DC=darling,DC=local

msExchDelegateListBL: CN=Jay Kumar,OU=Head Office,OU=Planet,DC=darling,DC=local

msExchDelegateListBL: CN=sumith,OU=2010-Remove,DC=darling,DC=local

• Edited by Abdul Jaleel Malik Wednesday, October 27, 2010 4:20 PM more info

Using Exchange 2010 SP1 and 2008 R2 and Outlook 2010 (migrated from exchange 2007 SP2)

I am facing the same problem

Problem only appeared after upgrading to Exchange 2010 SP1

Tried all possible ways to remove additional mailboxes all fruitless 

i have noticed when editing schema 

there are no values in this attribute for user

msExchDelegateListLink

and there are multiple values for following attribute 

msExchDelegateListBL

and I tried to delete these values but I receive following message 

"The attribute cannot be modified because it is owned by the system."

these entries look like 

msExchDelegateListBL: CN=Jennifer Eder,OU=Reservation,OU=Al-Qouz,OU=Planet,DC=darling,DC=local

msExchDelegateListBL: CN=Hani Khamis Hamad,OU=Head Office,OU=Planet,DC=darling,DC=local

msExchDelegateListBL: CN=Zhou Yun,OU=Chinese Inbound,OU=Head Office,OU=Planet,DC=darling,DC=local

msExchDelegateListBL: CN=Payroll Head Office,OU=Human Resources,OU=Head Office,OU=Planet,DC=darling,DC=local

msExchDelegateListBL: CN=Jay Kumar,OU=Head Office,OU=Planet,DC=darling,DC=local

msExchDelegateListBL: CN=sumith,OU=2010-Remove,DC=darling,DC=local

• Edited by Abdul Jaleel Malik Wednesday, October 27, 2010 4:20 PM more info

Using Exchange 2010 SP1 and 2008 R2 and Outlook 2010 (migrated from exchange 2007 SP2)

I am facing the same problem

Problem only appeared after upgrading to Exchange 2010 SP1

Tried all possible ways to remove additional mailboxes all fruitless 

i have noticed when editing schema 

there are no values in this attribute for user

msExchDelegateListLink

and there are multiple values for following attribute 

msExchDelegateListBL

and I tried to delete these values but I receive following message 

"The attribute cannot be modified because it is owned by the system."

these entries look like 

msExchDelegateListBL: CN=Jennifer Eder,OU=Reservation,OU=Al-Qouz,OU=Planet,DC=darling,DC=local

msExchDelegateListBL: CN=Hani Khamis Hamad,OU=Head Office,OU=Planet,DC=darling,DC=local

msExchDelegateListBL: CN=Zhou Yun,OU=Chinese Inbound,OU=Head Office,OU=Planet,DC=darling,DC=local

msExchDelegateListBL: CN=Payroll Head Office,OU=Human Resources,OU=Head Office,OU=Planet,DC=darling,DC=local

msExchDelegateListBL: CN=Jay Kumar,OU=Head Office,OU=Planet,DC=darling,DC=local

msExchDelegateListBL: CN=sumith,OU=2010-Remove,DC=darling,DC=local

• Proposed as answer by Edbert Thursday, September 06, 2012 12:36 PM

• Proposed as answer by Edbert Thursday, September 06, 2012 12:36 PM

• Proposed as answer by Edbert Thursday, September 06, 2012 12:36 PM

I also have exactly the same problem.

When I add additional mailboxes to my account, I can not get rid of them again. After removing them from the Outlook 2010 Exchange Profile without any error, they add themselves up the Outlook folder list automatically, yet they don't show up in the "open additional maibox" dialogue anymore.

The ADSIedit stuff explained in this thread worked, though ...  but that can't be the solution.

Ah yes, we are on Exchange 2010 SP1 and Outlook 2010 aswell.

PLEASE MICROSOFT, FIX THIS.

I found an explanation of this here:

http://www.howexchangeworks.com/2010/09/auto-mapping-mailboxes-with-full-access.html

the bug only seems to be, that the attribute MSExchDelegateListLink is _NOT_ removed from the user when I remove full access from that mailbox. So you get that mailbox mapped over and over, even if full access does not exist anymore. Auto-Mapping Mailboxes I have full access rights for is a nice feature, but they should be auto-removed again when full access is removed.

This is what needs to be fixed by Microsoft in an upcoming patch. Please someone of MS reply to this.

Im having the same issue as everyone in here but identical to Abdul Jaleel Maliks issue. I have no one in the list but many in the listBL. When I try to remove them, I get the "Cannot be modified because its owned by the system" error message. I have done these tow things to try to get rid of that error:

------

In HKEY_LOCAL_MACHINE\System \CurrentControlSet\Services\NTDS\Parameters, create the following value:
Value name: Allow System Only Change
Data type: REG_DWORD
Value data: 1
Then close the registry and now you should be able to modify through ADSIEDIT .

------

this did not work. I also tried this:

------

Login as a member of Schema Admins (preferably on the Schema Master FSMO)
Launch LDP.EXE
Connect to the Schema Master FSMO using LDP.EXE
Bind to the Schema Master using an account with Schema Admin permissions.
From the Browse menu, choose Modify
In the Modify dialog box, leave the DN field blank, and type schemaUpgradeInProgress in the Attribute field. In the Value field, enter the number 1. Click the Enter button, then click the Run button.
Close the Modify dialog box.
Launch ADSIEDIT.MSC and modify the mAPIID values for the necessary attributes . (You may need to wait for the Active Directory to replicate.)
Run LDP again, and change the value of schemaUpgradeInProgress from 1 to 0.
From the Active Directory Schema console, right click on the console and choose "Reload the Schema"

------

During this, i tired to edit the values of the ListBL attribute and it gave a database error and the a schema error.

Any thoughts on this would be greatly appreciated

This worked for me...same problem.

I was using Outlook 2007 and Exchange 2010 SP1

Sorry I should be more clear.  Korbyn's solution of editing the MSExchDelegateListLink attribute worked to resolve this issue.

• Proposed as answer by Gene Lawin Tuesday, January 11, 2011 5:21 AM

This worked for me...same problem.

I was using Outlook 2007 and Exchange 2010 SP1

Sorry I should be more clear.  Korbyn's solution of editing the MSExchDelegateListLink attribute worked to resolve this issue.

• Proposed as answer by Gene Lawin Tuesday, January 11, 2011 5:21 AM

This worked for me...same problem.

I was using Outlook 2007 and Exchange 2010 SP1

Sorry I should be more clear.  Korbyn's solution of editing the MSExchDelegateListLink attribute worked to resolve this issue.

• Proposed as answer by Gene Lawin Tuesday, January 11, 2011 5:21 AM

This worked for me...same problem.

I was using Outlook 2007 and Exchange 2010 SP1

Sorry I should be more clear.  Korbyn's solution of editing the MSExchDelegateListLink attribute worked to resolve this issue.

I have tried the ADSI edit and removed the entry, but I still see the maibox and cannot remov

Yep I have the same thing happening this is completely un-acceptable using adsiedit is only dangerous and makes absolutely no sense to use it to fix something that should simply be addressed properly.

We just paid alot of money to upgrade to ex 2010 and server 2008 even had someone from microsoft do the installation to be sure nothing was done wrong.  And now i see this.  Seriously? this is terrible. Think about it this is like mounting all shares automatically that each eser has permission to.  Makes no sense at all.  MS YOU NEED TO FIX THIS.  There isn't anyway im hacking a brand new installation of Exchange.  Fix it properly so that when the mailbox is removed from additonal mailboxes ... it goes AWAY.

Thank you.

No problem.  Steve seems to have found a way to disable the feature, though Ihaven't tried it myself.

http://www.stevieg.org/2011/02/disable-exchange-2010-sp1s-auto-shared-mailbox-mapping/

And as far as I can tell, no, MS doesn't appear to be listening, this has been a known issue to us non-MS people since 2010 beta, with no signs or indications that it will be resolved... :(

• Proposed as answer by Steve GoodmanMicrosoft contingent staff Saturday, May 14, 2011 8:15 AM

No problem.  Steve seems to have found a way to disable the feature, though Ihaven't tried it myself.

http://www.stevieg.org/2011/02/disable-exchange-2010-sp1s-auto-shared-mailbox-mapping/

And as far as I can tell, no, MS doesn't appear to be listening, this has been a known issue to us non-MS people since 2010 beta, with no signs or indications that it will be resolved... :(

• Proposed as answer by Steve GoodmanMicrosoft contingent staff Saturday, May 14, 2011 8:15 AM

No problem.  Steve seems to have found a way to disable the feature, though Ihaven't tried it myself.

http://www.stevieg.org/2011/02/disable-exchange-2010-sp1s-auto-shared-mailbox-mapping/

And as far as I can tell, no, MS doesn't appear to be listening, this has been a known issue to us non-MS people since 2010 beta, with no signs or indications that it will be resolved... :(

• Proposed as answer by Steve GoodmanMicrosoft contingent staff Saturday, May 14, 2011 8:15 AM

Korbyn

Your solution worked for me, thanks a lot!

No problem.  Steve seems to have found a way to disable the feature, though Ihaven't tried it myself.

http://www.stevieg.org/2011/02/disable-exchange-2010-sp1s-auto-shared-mailbox-mapping/

And as far as I can tell, no, MS doesn't appear to be listening, this has been a known issue to us non-MS people since 2010 beta, with no signs or indications that it will be resolved... :(

I read this article and reversed the steps on the Exchange sever. By removing myself from the Full Access Permission field and restarting Outlook fixed the issue for me. No need to mess with ADSIEdit.

http://www.stevieg.org/2010/08/auto-mapping-shared-mailboxes-in-exchange-2010-sp1-with-outlook-2010/

• Proposed as answer by SGB_7 Tuesday, October 30, 2012 9:13 AM

• Proposed as answer by SGB_7 Tuesday, October 30, 2012 9:13 AM

• Proposed as answer by SGB_7 Tuesday, October 30, 2012 9:13 AM

In Exchange 2010 Service Pack 1 (SP1), Outlook 2007 and Outlook 2010 clients automatically map to any mailbox to which a user has Full Access permissions. If a user is granted Full Access permissions to another user's mailbox or to a shared mailbox, Autodiscover automatically loads all mailboxes to which the user has full access. If the user has full access to a large number of mailboxes, performance issues may occur when starting Outlook. For example, in some Exchange organizations, administrators have full access to all the mailboxes in the organization. In this case, upon starting, Outlook attempts to open all mailboxes in the organization. Users can’t control this behavior and have no way to turn it off.

http://technet.microsoft.com/en-us/library/bb676551.aspx

Thank you, however, the topic of this discussion, is that AFTER you've removed the permissions, you HAVE to go perform additional cleanup steps, like going into ADSIedit, and clear/clean the "MSExchDelegateListLink" OTHERWISE the user STILL has the other mailbox listed in their Outlook profile and STILL has ACCESS to the mailbox for which you believe you have removed said permissions on.

A slight security hole, and one that unless a security audit is checking all the MSExchDelegateListLink fields and validating against actual assigned permssions.  And I've been waiting since RC1 for them to fix the powershell so that when full permissions are removed, that the MSExchDelegateListLink field is cleaned up too. 

As per previous posting, the way to the way to add mailbox permissions without the AutoMap feature can be found in the following article:  http://www.stevieg.org/2011/02/disable-exchange-2010-sp1s-auto-shared-mailbox-mapping/ 

To quote Steve:  "...this isn't a universally-desired feature,..."

We use the following workaround:

Scheduling a batch script with the following commands to delete the msExchDelegateListLink attribute from every AD object.:

adfind.exe -b cn=users,dc=domain,dc=com -f "msExchDelegateListLink=*" -dsq | admod.exe msExchDelegateListLink:-: -safety 50

or if you're sure

adfind.exe -b cn=users,dc=domain,dc=com -f "msExchDelegateListLink=*" -dsq | admod.exe msExchDelegateListLink:-: -unsafe

The AD tools you find under

http://www.joeware.net/freetools/tools/admod/

http://www.joeware.net/freetools/tools/adfind/

Best regards

Joerg Maletzky

Korbyn,

Thank you, thank you, thank you.  I have been looking for this solution for months off and on and I've never been able to identify it; but your directions above solved it for me.  You are awesome!!!

... So far what I've found to work is having to go into ADSIEdit.msc, Domain context, and drill down to the account you wish to be removed from, and look for the "MSExchDelegateListLink" attribute and remove yourself from that list.  The next time you start Outlook 2010, the ghost "additional" mailbox should disappear after a few minutes...

... So far what I've found to work is having to go into ADSIEdit.msc, Domain context, and drill down to the account you wish to be removed from, and look for the "MSExchDelegateListLink" attribute and remove yourself from that list.  The next time you start Outlook 2010, the ghost "additional" mailbox should disappear after a few minutes...

Thanks for this Korbyn. Worked a treat for me.

Outlook 2010
Exchange 2010 

• Proposed as answer by Stickett Wednesday, October 12, 2011 8:38 PM
• Unproposed as answer by Stickett Wednesday, October 12, 2011 8:39 PM

• Proposed as answer by Stickett Wednesday, October 12, 2011 8:38 PM
• Unproposed as answer by Stickett Wednesday, October 12, 2011 8:39 PM

• Proposed as answer by Stickett Wednesday, October 12, 2011 8:38 PM
• Unproposed as answer by Stickett Wednesday, October 12, 2011 8:39 PM

In outlook 2007 this is what worked for me. I first went to exchange management console and removed full access permission for the user in question from that mailbox. Then I opened the outlook profile with the mailboxes that could not be removed and CLICKED THE + SIGN TO THE LEFT OF THE NAME. Once the error message came up that the mailbox is not accessable, outlook removed the mailbox entirely from the profile. I tested this on 4 different mailboxes and it has worked every time. I did close outlook everytime by using the file then go down to exit and wait 5 seconds. Then reopen outlook to remove the next mailbox.

I hope this helps. Note I did not try this on outlook 2010. It shoud work the same way. We have exchange 2010 Sp1 and I was working with outlook 2007.

Good luck.

From an Exchange of view, this (enabling or disabling the additional mailbox centrally) makes complete sense.

What is wrong is the poor and misleading error message in Outlook 2010. The message MAY be correct for POP3/Imap/etc account configurations, but is NEVER correct for an Exchange configuration.

So MS please make Outlook a bit smarter. Outlook knows that these user mailboxes are configured by Exchange, and not in the local profile, so throw an error message that give the user correct, helpful information.

• Edited by John Brits Thursday, November 03, 2011 7:28 PM

From an Exchange of view, this (enabling or disabling the additional mailbox centrally) makes complete sense.

What is wrong is the poor and misleading error message in Outlook 2010. The message MAY be correct for POP3/Imap/etc account configurations, but is NEVER correct for an Exchange configuration.

So MS please make Outlook a bit smarter. Outlook knows that these user mailboxes are configured by Exchange, and not in the local profile, so throw an error message that give the user correct, helpful information.

• Edited by John Brits Thursday, November 03, 2011 7:28 PM

From an Exchange of view, this (enabling or disabling the additional mailbox centrally) makes complete sense.

What is wrong is the poor and misleading error message in Outlook 2010. The message MAY be correct for POP3/Imap/etc account configurations, but is NEVER correct for an Exchange configuration.

So MS please make Outlook a bit smarter. Outlook knows that these user mailboxes are configured by Exchange, and not in the local profile, so throw an error message that give the user correct, helpful information.

• Edited by John Brits Thursday, November 03, 2011 7:28 PM

From an Exchange of view, this (enabling or disabling the additional mailbox centrally) makes complete sense.

What is wrong is the poor and misleading error message in Outlook 2010. The message MAY be correct for POP3/Imap/etc account configurations, but is NEVER correct for an Exchange configuration.

So MS please make Outlook a bit smarter. Outlook knows that these user mailboxes are configured by Exchange, and not in the local profile, so throw an error message that give the user correct, helpful information.

No problem.  Steve seems to have found a way to disable the feature, though Ihaven't tried it myself.

http://www.stevieg.org/2011/02/disable-exchange-2010-sp1s-auto-shared-mailbox-mapping/

And as far as I can tell, no, MS doesn't appear to be listening, this has been a known issue to us non-MS people since 2010 beta, with no signs or indications that it will be resolved... :(

Thanks Korbyn, this worked for me. What I had was another users Inbox showing in my Outlook. When I checked I was on the Full Access Permissions list for this user, so I removed my entry from the list and then I could remove their Inbox from Outlook via the Account Settings dialog.

igs

• Edited by IGS_Support Wednesday, November 23, 2011 2:10 PM

No problem.  Steve seems to have found a way to disable the feature, though Ihaven't tried it myself.

http://www.stevieg.org/2011/02/disable-exchange-2010-sp1s-auto-shared-mailbox-mapping/

And as far as I can tell, no, MS doesn't appear to be listening, this has been a known issue to us non-MS people since 2010 beta, with no signs or indications that it will be resolved... :(

Thanks Korbyn, this worked for me. What I had was another users Inbox showing in my Outlook. When I checked I was on the Full Access Permissions list for this user, so I removed my entry from the list and then I could remove their Inbox from Outlook via the Account Settings dialog.

igs

• Edited by IGS_Support Wednesday, November 23, 2011 2:10 PM

No problem.  Steve seems to have found a way to disable the feature, though Ihaven't tried it myself.

http://www.stevieg.org/2011/02/disable-exchange-2010-sp1s-auto-shared-mailbox-mapping/

And as far as I can tell, no, MS doesn't appear to be listening, this has been a known issue to us non-MS people since 2010 beta, with no signs or indications that it will be resolved... :(

Thanks Korbyn, this worked for me. What I had was another users Inbox showing in my Outlook. When I checked I was on the Full Access Permissions list for this user, so I removed my entry from the list and then I could remove their Inbox from Outlook via the Account Settings dialog.

igs

• Edited by IGS_Support Wednesday, November 23, 2011 2:10 PM

No problem.  Steve seems to have found a way to disable the feature, though Ihaven't tried it myself.

http://www.stevieg.org/2011/02/disable-exchange-2010-sp1s-auto-shared-mailbox-mapping/

And as far as I can tell, no, MS doesn't appear to be listening, this has been a known issue to us non-MS people since 2010 beta, with no signs or indications that it will be resolved... :(

Thanks Korbyn, this worked for me. What I had was another users Inbox showing in my Outlook. When I checked I was on the Full Access Permissions list for this user, so I removed my entry from the list and then I could remove their Inbox from Outlook via the Account Settings dialog.

igs

I too have experienced this issue too, with a lousy resolution.  So far what I've found to work is having to go into ADSIEdit.msc, Domain context, and drill down to the account you wish to be removed from, and look for the "MSExchDelegateListLink" attribute and remove yourself from that list.  The next time you start Outlook 2010, the ghost "additional" mailbox should disappear after a few minutes.

Thank you!  That worked perfectly!

Environment: Exchange 2010 Standard SP1, Outlook 2010.

• Proposed as answer by SGB_7 Tuesday, October 30, 2012 9:15 AM

I too have experienced this issue too, with a lousy resolution.  So far what I've found to work is having to go into ADSIEdit.msc, Domain context, and drill down to the account you wish to be removed from, and look for the "MSExchDelegateListLink" attribute and remove yourself from that list.  The next time you start Outlook 2010, the ghost "additional" mailbox should disappear after a few minutes.

Thank you!  That worked perfectly!

Environment: Exchange 2010 Standard SP1, Outlook 2010.

• Proposed as answer by SGB_7 Tuesday, October 30, 2012 9:15 AM

I too have experienced this issue too, with a lousy resolution.  So far what I've found to work is having to go into ADSIEdit.msc, Domain context, and drill down to the account you wish to be removed from, and look for the "MSExchDelegateListLink" attribute and remove yourself from that list.  The next time you start Outlook 2010, the ghost "additional" mailbox should disappear after a few minutes.

Thank you!  That worked perfectly!

Environment: Exchange 2010 Standard SP1, Outlook 2010.

• Proposed as answer by SGB_7 Tuesday, October 30, 2012 9:15 AM

I too have experienced this issue too, with a lousy resolution.  So far what I've found to work is having to go into ADSIEdit.msc, Domain context, and drill down to the account you wish to be removed from, and look for the "MSExchDelegateListLink" attribute and remove yourself from that list.  The next time you start Outlook 2010, the ghost "additional" mailbox should disappear after a few minutes.

Thank you!  That worked perfectly!

Environment: Exchange 2010 Standard SP1, Outlook 2010.

works for me. thanks "Korbyn"

Exch 2010 SP1 and Outlook 2010 32bit as client.

• Edited by TSO Wednesday, January 04, 2012 11:02 PM

works for me. thanks "Korbyn"

Exch 2010 SP1 and Outlook 2010 32bit as client.

• Edited by TSO Wednesday, January 04, 2012 11:02 PM

works for me. thanks "Korbyn"

Exch 2010 SP1 and Outlook 2010 32bit as client.

• Edited by TSO Wednesday, January 04, 2012 11:02 PM

works for me. thanks "Korbyn"

Exch 2010 SP1 and Outlook 2010 32bit as client.

The issue has been "Finally" solved in Exchange 2010 SP2

http://technet.microsoft.com/en-us/library/hh529943.aspx

and

http://technet.microsoft.com/en-us/library/hh529924.aspx

also for reference ...

Remove-MailboxPermission -Identity jaleel -User 'Malik' -AccessRight FullAccess -InheritanceType All 

or 

ADD-MailboxPermission -Identity Jaleel -User 'Malik' -AccessRight FullAccess -InheritanceType All -Automapping $false

I disagree that it's been solved in SP2 - at least that's what I've experienced with superficial testing.

I applied Exch SP2 and the client automap function was still hosed. All was verified correct by drilling down in ADSIedit user attributes as well (good info - thanks to the thread contributors!). I tried from EMC to add and then remove the additional account for good measure. Power Shell also was unable to remove additional boxen with an add followed by remove motion.

I finally smoked the mail profile on the workstation involved. Now automap doesn't work at all for that machine but additional accounts can be added via Outlook client (Backstage -> Account Setting -> Account Setting -> Change -> More Settings -> Advanced tab -> Add -> interesting box name -> ok -> next -> finish.

Automap is a groovy feature that still works the majority of the time so I'm happy :-) Just have to use the manual workaround (above client side manual mapping) if needed after adding the required user under EMC "Manage Full Access Permission"

• Proposed as answer by Dale Lewis Monday, January 30, 2012 10:16 PM

I disagree that it's been solved in SP2 - at least that's what I've experienced with superficial testing.

I applied Exch SP2 and the client automap function was still hosed. All was verified correct by drilling down in ADSIedit user attributes as well (good info - thanks to the thread contributors!). I tried from EMC to add and then remove the additional account for good measure. Power Shell also was unable to remove additional boxen with an add followed by remove motion.

I finally smoked the mail profile on the workstation involved. Now automap doesn't work at all for that machine but additional accounts can be added via Outlook client (Backstage -> Account Setting -> Account Setting -> Change -> More Settings -> Advanced tab -> Add -> interesting box name -> ok -> next -> finish.

Automap is a groovy feature that still works the majority of the time so I'm happy :-) Just have to use the manual workaround (above client side manual mapping) if needed after adding the required user under EMC "Manage Full Access Permission"

• Proposed as answer by Dale Lewis Monday, January 30, 2012 10:16 PM

I disagree that it's been solved in SP2 - at least that's what I've experienced with superficial testing.

I applied Exch SP2 and the client automap function was still hosed. All was verified correct by drilling down in ADSIedit user attributes as well (good info - thanks to the thread contributors!). I tried from EMC to add and then remove the additional account for good measure. Power Shell also was unable to remove additional boxen with an add followed by remove motion.

I finally smoked the mail profile on the workstation involved. Now automap doesn't work at all for that machine but additional accounts can be added via Outlook client (Backstage -> Account Setting -> Account Setting -> Change -> More Settings -> Advanced tab -> Add -> interesting box name -> ok -> next -> finish.

Automap is a groovy feature that still works the majority of the time so I'm happy :-) Just have to use the manual workaround (above client side manual mapping) if needed after adding the required user under EMC "Manage Full Access Permission"

• Proposed as answer by Dale Lewis Monday, January 30, 2012 10:16 PM

I disagree that it's been solved in SP2 - at least that's what I've experienced with superficial testing.

I applied Exch SP2 and the client automap function was still hosed. All was verified correct by drilling down in ADSIedit user attributes as well (good info - thanks to the thread contributors!). I tried from EMC to add and then remove the additional account for good measure. Power Shell also was unable to remove additional boxen with an add followed by remove motion.

I finally smoked the mail profile on the workstation involved. Now automap doesn't work at all for that machine but additional accounts can be added via Outlook client (Backstage -> Account Setting -> Account Setting -> Change -> More Settings -> Advanced tab -> Add -> interesting box name -> ok -> next -> finish.

Automap is a groovy feature that still works the majority of the time so I'm happy :-) Just have to use the manual workaround (above client side manual mapping) if needed after adding the required user under EMC "Manage Full Access Permission"

• Proposed as answer by Bruce Hewer Tuesday, March 20, 2012 5:20 PM
• Unproposed as answer by Bruce Hewer Tuesday, March 20, 2012 5:20 PM

• Proposed as answer by Bruce Hewer Tuesday, March 20, 2012 5:20 PM
• Unproposed as answer by Bruce Hewer Tuesday, March 20, 2012 5:20 PM

• Proposed as answer by Bruce Hewer Tuesday, March 20, 2012 5:20 PM
• Unproposed as answer by Bruce Hewer Tuesday, March 20, 2012 5:20 PM

Log out and back in and mailbox is gone!!

Korbyns solution works fine... I had the exact same issue, add users (Prof 2 & 3) for admin purposes to my profile (prof1) - attempt to remove and they are not present in the profile view and cannot be closed or removed from your profile... Delete all profiles from the local disk, and registry and they still appear next time you open outlook.. This is because they are assigned to the mailbox in the back end - open the Exch mailbox (prof1) from another computer with MFCMAPI and you still see them...

However if you do as Korbyn says and look up these accounts in AD (prof 2 & 3) - and use some attribute level editor such as ADSIEdit - you will see the (prof1) user DN present in the (prof 1 & 2) user accounts under MSExchDelegateListLink attribute - clear from here, reopen outlook and wait 5 (to 30) min - the additional profiles should vanish..

Thanks Korbyn, this was an annoying problem to have in a secure env..

However - the very fact these accounts clear themselved from the 'open additional Mailboxes' section seems a bug to me! This worked fine in all previous versions of outlook..

I did have the same issue with Office 365 Exchange Online. I was going to follow Korbyn's advice but stumbled on another solution that does not involve ADSIEdit.msc. This is assuming you are using the 'offline' Outlook program installed on your computer. Here is what I did:

* Exit Outlook.

* Remove the access rights through powershell, i.e.
  remove-mailboxpermission -identity [EmailBoxToRemove] -user [EmailBoxToRemoveFrom] -accessRight FullAccess -inheritancetype All

* Start Outlook and go to File ->Info->Cleanup Tools->Archive. Scroll down to the account from which you removed the access rights and click the arrow to drill down the folders. At that point Outlook will freeze for some 10-30 seconds. When it comes back the account is not listed for archiving anymore. After you cancel out of that dialog box it will also be gone from Outlook.

I am not sure if this works under all circumstances but it did for me in two cases. I guess Outlook realizes that it does not have the access rights and then removes the link without having to manually do it through ADSIEdit.msc.

• Proposed as answer by BARBRI Tuesday, June 26, 2012 3:50 PM

I did have the same issue with Office 365 Exchange Online. I was going to follow Korbyn's advice but stumbled on another solution that does not involve ADSIEdit.msc. This is assuming you are using the 'offline' Outlook program installed on your computer. Here is what I did:

* Exit Outlook.

* Remove the access rights through powershell, i.e.
  remove-mailboxpermission -identity [EmailBoxToRemove] -user [EmailBoxToRemoveFrom] -accessRight FullAccess -inheritancetype All

* Start Outlook and go to File ->Info->Cleanup Tools->Archive. Scroll down to the account from which you removed the access rights and click the arrow to drill down the folders. At that point Outlook will freeze for some 10-30 seconds. When it comes back the account is not listed for archiving anymore. After you cancel out of that dialog box it will also be gone from Outlook.

I am not sure if this works under all circumstances but it did for me in two cases. I guess Outlook realizes that it does not have the access rights and then removes the link without having to manually do it through ADSIEdit.msc.

• Proposed as answer by BARBRI Tuesday, June 26, 2012 3:50 PM

I did have the same issue with Office 365 Exchange Online. I was going to follow Korbyn's advice but stumbled on another solution that does not involve ADSIEdit.msc. This is assuming you are using the 'offline' Outlook program installed on your computer. Here is what I did:

* Exit Outlook.

* Remove the access rights through powershell, i.e.
  remove-mailboxpermission -identity [EmailBoxToRemove] -user [EmailBoxToRemoveFrom] -accessRight FullAccess -inheritancetype All

* Start Outlook and go to File ->Info->Cleanup Tools->Archive. Scroll down to the account from which you removed the access rights and click the arrow to drill down the folders. At that point Outlook will freeze for some 10-30 seconds. When it comes back the account is not listed for archiving anymore. After you cancel out of that dialog box it will also be gone from Outlook.

I am not sure if this works under all circumstances but it did for me in two cases. I guess Outlook realizes that it does not have the access rights and then removes the link without having to manually do it through ADSIEdit.msc.

• Proposed as answer by BARBRI Tuesday, June 26, 2012 3:50 PM

I did have the same issue with Office 365 Exchange Online. I was going to follow Korbyn's advice but stumbled on another solution that does not involve ADSIEdit.msc. This is assuming you are using the 'offline' Outlook program installed on your computer. Here is what I did:

* Exit Outlook.

* Remove the access rights through powershell, i.e.
  remove-mailboxpermission -identity [EmailBoxToRemove] -user [EmailBoxToRemoveFrom] -accessRight FullAccess -inheritancetype All

* Start Outlook and go to File ->Info->Cleanup Tools->Archive. Scroll down to the account from which you removed the access rights and click the arrow to drill down the folders. At that point Outlook will freeze for some 10-30 seconds. When it comes back the account is not listed for archiving anymore. After you cancel out of that dialog box it will also be gone from Outlook.

I am not sure if this works under all circumstances but it did for me in two cases. I guess Outlook realizes that it does not have the access rights and then removes the link without having to manually do it through ADSIEdit.msc.

Korbyn's fix worked for me as well, thanks for the info!

I am surprised this bug has existed for so long.  Having access after full access is removed is very dangerous IMO.  This means I will now have to audit AD for other instances where people have access they shouldn't.

 Exchange 2010 using Outlook 2007.

When removing the mailbox from my account it only changed "Mailbox - username" to "username".

Thanks Tom WH, removing full access permissions cleared it up for me.  It did take 5-10 minutes to sync.

Korbyn, I know you say this topic is for after removing permissions but my searching brought me to this thread and without Tom WH's post I would still be searching... or using ADSIedit  to clean MSExchDelegaeListLink...for nothing.

[quote]

So far what I've found to work is having to go into ADSIEdit.msc, Domain context, and drill down to the account you wish to be removed from, and look for the "MSExchDelegateListLink" attribute and remove yourself from that list.  The next time you start Outlook 2010, the ghost "additional" mailbox should disappear after a few minutes.

[/quote]

This worked for me, proposed as answer. Removing permissions to the mailbox on Exchange 2010 did NOT fix the problem. I saw the same behavior from Outlook 2007 and Outlook 2010, so it seems to be an AD problem not Exchange or Outlook.

I have made easy to follow userguide for myself , but maybe someone can use this to ease his task : 

www.note.id.lv/2012/12/cannot-remove-additional-mailbox-in.html

Directly using ADSI Edit to try to solve this issue really is not the way to go.

This is a feature of Exchange 2010 SP1 (and later) called AutoMapping and this is enabled by default for all mailboxes that you enabled Full Access for (for all newly set Full Access permissions since implementing Exchange 2010 SP1 or later). These mailboxes are added/removed automatically to Outlook via AutoDiscover and are not exposed in the Exchange account configuration in Outlook. Therefor, users cannot automatically remove these mailboxes themselves.

An administrator can set the automapping property for a specific user on a mailbox to "false" to prevent the mailboxes from being mapped automatically in Outlook. Abdul Jaleel Malik already mentioned this in his reply earlier in this thread.

For additional info, also see: Cant remove additional Exchange mailboxes

This did not work for me because no mailboxes were in the location.

Bill

This did not work for me because no mailboxes were in the location.

I have this same issue, but a few complications:

1) I am not an administrator on the domain or in exchange, so

2) I don't have access to ADSIedit and can't do anything specifically with AD or exchange

3) I don't have multiple extra mailboxes, I have multiple instances of the SAME mailbox showing

4) I need access to the one extra mailbox I'm using, so I can't have rw permissions to it revoked

So basically I have this showing in outlook:

[My mailbox]

[Extra mailbox]

[Extra mailbox]

[Extra mailbox]

Like the original poster in this thread, when I right-click on any of the redundant extra mailboxes and click "close", it tells me that the mailbox is associated with an email account.  But the "open these additional mailboxes" dialog is blank - there are zero entries there.  And in any case, I don't want to close them all - I need to access that mailbox... but I would like to have it show up just once instead of multiple times.

This is most certainly not a "feature".  This is a bug, and an annoying one at that.  Are there any client-side solutions anyone has found that will remedy this issue?

Thanks so much in advance for your help!

SOLUTION:

(this is in Outlook 2010)

Click on your main exchange account.

Go to File/Info/Account Settings.

Select your main Exchange account and click Change.

Click More Settings in the bottom right corner.

Select Advanced tab.

Now you can see your added account(s) and remove them as you wish.

• Proposed as answer by Jerry_D Tuesday, January 29, 2013 11:38 AM

SOLUTION:

(this is in Outlook 2010)

Click on your main exchange account.

Go to File/Info/Account Settings.

Select your main Exchange account and click Change.

Click More Settings in the bottom right corner.

Select Advanced tab.

Now you can see your added account(s) and remove them as you wish.

• Proposed as answer by Jerry_D Tuesday, January 29, 2013 11:38 AM

SOLUTION:

(this is in Outlook 2010)

Click on your main exchange account.

Go to File/Info/Account Settings.

Select your main Exchange account and click Change.

Click More Settings in the bottom right corner.

Select Advanced tab.

Now you can see your added account(s) and remove them as you wish.

• Proposed as answer by Jerry_D Tuesday, January 29, 2013 11:38 AM

SOLUTION:

(this is in Outlook 2010)

Click on your main exchange account.

Go to File/Info/Account Settings.

Select your main Exchange account and click Change.

Click More Settings in the bottom right corner.

Select Advanced tab.

Now you can see your added account(s) and remove them as you wish.

@Jerry_D
No, it is not. This topic is about automapped mailboxes and not manually mapped ones.

Also, don't directly propose your own answers as THE answer. That is not what the system is for.

I've seen the same issue at atleast 1 of our customers. I'ts been more than 2 years since the start of this thread and still no fix from Microsoft.... I'm currently in the process of fixing this for 1 customer (again!)....

Come on Microsoft, show us why we pay you so much money to use the products!

Korbyn:

Thank you so much for this solution.  It worked just as you described.  The other "solutions"  I found refer to a registry entry that isn't in my registry.  I'm using Office 2013 (x64) on Windows 8 Pro with Media Center (x64) with Exchange 2010 via Small Business Server 2011.

Would you be able to describe your train-of-thought for finding this solution?

Directly using ADSI Edit to try to solve this issue really is not the way to go.

This is a feature of Exchange 2010 SP1 (and later) called AutoMapping and this is enabled by default for all mailboxes that you enabled Full Access for (for all newly set Full Access permissions since implementing Exchange 2010 SP1 or later). These mailboxes are added/removed automatically to Outlook via AutoDiscover and are not exposed in the Exchange account configuration in Outlook. Therefor, users cannot automatically remove these mailboxes themselves.

An administrator can set the automapping property for a specific user on a mailbox to "false" to prevent the mailboxes from being mapped automatically in Outlook. Abdul Jaleel Malik already mentioned this in his reply earlier in this thread.

For additional info, also see: Cant remove additional Exchange mailbox

I had the same issue with Outlook 2010 and SBS 2011. In the end, to resolve it I:

- removed the users permissions to the additional mailbox I'd removed from Outlook. 
- switched off cache mode in Outlook, and restarted Outlook.
- switched on cache mode again and restarted Outlook.

Then the mailboxes disappeared. Didn't touch ASDIedit.

Not even sure how my accounts got here, but this answer is dead on.  Thanks!

Perfect.  Thank you so much.

Hi,

I have resolved today, turned off cached mode, checked mailbox access was removed in exchange, deleted .ost file and restarted outlook.

Thanks

You don't need to disable and enable cached mode (requiring the index to rebuild).

Close Outlook, remove access rights on Exchange server, launch Outlook and expand the extra mailbox; it will disappear.

• Proposed as answer by Kurt Fritz Tuesday, July 16, 2013 5:06 PM

You don't need to disable and enable cached mode (requiring the index to rebuild).

Close Outlook, remove access rights on Exchange server, launch Outlook and expand the extra mailbox; it will disappear.

• Proposed as answer by Kurt Fritz Tuesday, July 16, 2013 5:06 PM

You don't need to disable and enable cached mode (requiring the index to rebuild).

Close Outlook, remove access rights on Exchange server, launch Outlook and expand the extra mailbox; it will disappear.

• Proposed as answer by Kurt Fritz Tuesday, July 16, 2013 5:06 PM

I too have experienced this issue too, with a lousy resolution.  So far what I've found to work is having to go into ADSIEdit.msc, Domain context, and drill down to the account you wish to be removed from, and look for the "MSExchDelegateListLink" attribute and remove yourself from that list.  The next time you start Outlook 2010, the ghost "additional" mailbox should disappear after a few minutes.

I am a little disturbed that I would still have access to this other mailbox AFTER I removed the permissions to it, but because of this MSExchDelegateListLink attribute, that I still did.

If you go to the location in Outlook to Add addition mailboxes, and add one, it seems that you see the rest.  Doesn't help with removing the one you no long have access to.  So, it's hard to say if it's one bug or two, the mailboxPermission PS command exchange uses, doesn't seem to check/clear the MSExchDelegateListLink attribute, and possibly another bug with Outlook not actually listing "Addition Mailboxes" unless you add one, then you see many.

Thanks!, this was the only I found I could fix a stuck mailbox for a user where the mailbox they had been given permission to was now disabled!

• Proposed as answer by BampaJ Thursday, September 19, 2013 2:57 PM
• Unproposed as answer by BampaJ Thursday, September 19, 2013 2:57 PM

I too have experienced this issue too, with a lousy resolution.  So far what I've found to work is having to go into ADSIEdit.msc, Domain context, and drill down to the account you wish to be removed from, and look for the "MSExchDelegateListLink" attribute and remove yourself from that list.  The next time you start Outlook 2010, the ghost "additional" mailbox should disappear after a few minutes.

I am a little disturbed that I would still have access to this other mailbox AFTER I removed the permissions to it, but because of this MSExchDelegateListLink attribute, that I still did.

If you go to the location in Outlook to Add addition mailboxes, and add one, it seems that you see the rest.  Doesn't help with removing the one you no long have access to.  So, it's hard to say if it's one bug or two, the mailboxPermission PS command exchange uses, doesn't seem to check/clear the MSExchDelegateListLink attribute, and possibly another bug with Outlook not actually listing "Addition Mailboxes" unless you add one, then you see many.

Thanks!, this was the only I found I could fix a stuck mailbox for a user where the mailbox they had been given permission to was now disabled!

• Proposed as answer by BampaJ Thursday, September 19, 2013 2:57 PM
• Unproposed as answer by BampaJ Thursday, September 19, 2013 2:57 PM

I too have experienced this issue too, with a lousy resolution.  So far what I've found to work is having to go into ADSIEdit.msc, Domain context, and drill down to the account you wish to be removed from, and look for the "MSExchDelegateListLink" attribute and remove yourself from that list.  The next time you start Outlook 2010, the ghost "additional" mailbox should disappear after a few minutes.

I am a little disturbed that I would still have access to this other mailbox AFTER I removed the permissions to it, but because of this MSExchDelegateListLink attribute, that I still did.

If you go to the location in Outlook to Add addition mailboxes, and add one, it seems that you see the rest.  Doesn't help with removing the one you no long have access to.  So, it's hard to say if it's one bug or two, the mailboxPermission PS command exchange uses, doesn't seem to check/clear the MSExchDelegateListLink attribute, and possibly another bug with Outlook not actually listing "Addition Mailboxes" unless you add one, then you see many.

Thanks!, this was the only I found I could fix a stuck mailbox for a user where the mailbox they had been given permission to was now disabled!

• Proposed as answer by BampaJ Thursday, September 19, 2013 2:57 PM
• Unproposed as answer by BampaJ Thursday, September 19, 2013 2:57 PM

Hi there.

Try this.  It worked for me.

Add-MailboxPermission -Identity <shared mailbox alias> -User <your mailbox alias> -AccessRights FullAccess -InheritanceType All -Automapping $false

http://www.msoutlook.info/question/673

Maybe some of you already have posted this, but the easiest way I found is to log in to AD with the Exchange module and find the user you want to delete from your Outlook list.

In properties you find the Attribute editor tab, and delete your name from the "msExchDelegateListLink".

Worked for me.

Roger

• Proposed as answer by sysmangler Sunday, October 13, 2013 6:01 PM

Maybe some of you already have posted this, but the easiest way I found is to log in to AD with the Exchange module and find the user you want to delete from your Outlook list.

In properties you find the Attribute editor tab, and delete your name from the "msExchDelegateListLink".

Worked for me.

Roger

• Proposed as answer by sysmangler Sunday, October 13, 2013 6:01 PM

Maybe some of you already have posted this, but the easiest way I found is to log in to AD with the Exchange module and find the user you want to delete from your Outlook list.

In properties you find the Attribute editor tab, and delete your name from the "msExchDelegateListLink".

Worked for me.

Roger

• Proposed as answer by sysmangler Sunday, October 13, 2013 6:01 PM

I was having the same issue Outlook and Exchange 2010 (which brought me here) but in my case removing myself from the 'full access' permissions from the user in EMC which I had given myself in order to verify a mail receipt issue fixed the problem.  After a few minutes and a close/reopen of outlook the 3 users I was testing disappeared. 

Thank you for the ADSIEdit tip! Worked perfectly.

As frustrating as this was, for multiple users at multiple sites, it was a good excuse to get our servers all up to date SP and CU wise ;-)

Log into your EMC console.

Recipient Configuration --> Mailbox --> Select the mailbox that still shows up on you local Outlook --> Select Action from the menu at the top --> click Manage Full Access Permission and the wizard will open --> your own account should be in the list so select it and hit the red X --> click OK then Finish

• Edited by RockyMtnHi Wednesday, June 11, 2014 1:46 PM Typo...

Log into your EMC console.

Recipient Configuration --> Mailbox --> Select the mailbox that still shows up on you local Outlook --> Select Action from the menu at the top --> click Manage Full Access Permission and the wizard will open --> your own account should be in the list so select it and hit the red X --> click OK then Finish

• Edited by RockyMtnHi Wednesday, June 11, 2014 1:46 PM Typo...

Log into your EMC console.

Recipient Configuration --> Mailbox --> Select the mailbox that still shows up on you local Outlook --> Select Action from the menu at the top --> click Manage Full Access Permission and the wizard will open --> your own account should be in the list so select it and hit the red X --> click OK then Finish

• Edited by RockyMtnHi Wednesday, June 11, 2014 1:46 PM Typo...

My situation is a tad bit different.
May mail server "fatally" crashed and instead of wasting time bringing it back online, I expedited my already in the works decision to host it.  So my mail server is down.  All domain admins have 2 mailboxes we cannot seem to get rid of no matter what I try.  The msExchDelegateListLink holds none of our names in it.

Where do you suggest I go from here?  It's quite annoying to say the least!

This looks like an old thread now - But I wanted to update it as it relates to what I had to do to fix this issue in an Exchange 2013 / Outlook 2013 environment.

Close Outlook...

REGEDIT Search for the 'name' of the account in the local registry (PC running Outlook)

ei: John Smith

Delete that entire registry entry (not just the key you found)

Then in ADSI - find 'John Smith'

CN=John Smith,OU=SomeGroup,DC=contoso,DC=local

Then clear out the value in the noted field: MSExchDelegateListLink

After doing both, the 'John Smith' item was removed from the account list / panel.

Simply editing / clearing the MSExchDelegateListLink in ADSI did not work.

Only removing the registry Entry - It repopulates the entry when Outlook restarts.

Doing both of those, took care of it for me.

For me solution was

Remove-MailboxPermission -Identity Test1 -User Test2 -AccessRights FullAccess -InheritanceType All

(Exchange 2010 SP3)

Hi All,

My environment is Exchange 2013 CU7 / OLK 2010 Sp2.  I have trolled thru and applied many of the fixes listed here over the last day, but would still see the mailboxes listed. 

Today I removed one more (having had access to quite a few) and bingo, ALL of the additional mailboxes disappeared.  I know this isn't a solution as such, but highlights the issue remains in Exchange 2013.

I had 11 mailboxes plus mine, and either by skill / ignorance / luck / magic, all mailboxes disappeared from OLK upon removing no. 11 via EAC.  I do not intend to try granting myself access to them again in the hope of duplicating the issue and the outcome, nor do I propose this as a solution, just an fyi.

this really worked for me!

Thanks!

As an Exchange 2013 admin and domain admins, I have granted myself full access to several resources and other mailboxes for troubleshooting purposes.

Sometimes, like today my Outlook 2007 will not open and repeated prompts for a password.

Previously I had also removed my full access permission to those mailboxes and like everyone else, they stayed in my Outlook.

I used the powershell to successfully disable automapping for the accounts I could recall I had previously added.

The attribute editor in AD also works when removing myself from msExchDelegateListLink.

I can tell because the registry key now has less entries in it. 

HK_CU\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\MyName

Is there a powershell command to disable automapping for all accounts for myself only, when I can not recall what mailboxes there were?

I do not wish to turn it off for other users who have legitimate need to see those mailboxes... just get the dozen or so out of my profile.

Automapping is a great idea but it appears MS has little desire to remove the DelegateList attribute when full access is removed...this is an old thread.

thanks for your advice.

Andy

I tried this command to attempt to remove myself from all automapping:

$FixAutoMapping = Get-MailboxPermission sharedmailbox |where {$_.AccessRights -eq "FullAccess" -and $_.IsInherited -eq $false and $_.User -eq "First Last"}
$FixAutoMapping | Remove-MailboxPermission
$FixAutoMapping | ForEach {Add-MailboxPermission -Identity $_.Identity -User $_.User -AccessRights:FullAccess -AutoMapping $false}

[PS] C:\temp>.\RemoveFullAccessPermsAndy.ps1
At C:\temp\RemoveFullAccessPermsAndy.ps1:1 char:127
+ ... ted -eq $false and $_.User -eq "First Last"}
+                    ~~~
Unexpected token 'and' in expression or statement.
    + CategoryInfo          : ParserError: (:) [], ParseException
    + FullyQualifiedErrorId : UnexpectedToken

Same error when trying $_User -eq "andy.last" as well.