Howdy All,

So I just completed a public folder migration from Exchange 2010 to Exchange 2013.  Everything went really well except now all the mail enabled PFs that came across are all showed as not mail enabled even though they are mail enabled.  Meaning, in the EAC under public folders every PF has a no beside their name for mail enabled even though we have about 50 folders that are mail enabled and are working.

So now when I need to disable a mail enabled folder I cant.  If I enable the folder for mail, it now has two email address, the old one and the new one.  How does one go about managing these old mail enabled PFs????

What do you see when you enter the command:

Get-MailPublicFolder

Hi,

How about the result when you run the above command? whether the same as you see in EAC?

Best regards,

Thanks for the reply guys.

The above command gave me a list of all the PFs that I have.  A bunch apparently are in a corrupted state but not my email enabled PFs.

I did figure out the solution to my problem though and this is what worked for me.

In ADSIedit I found all my public folders.  When I took in each mail enabled object I could see that it has an email address.

1. Under the following attributes I cleared the value:
   1. Mail
   2. Mailnickname
   3. proxyAddress (SMTP)
   4. shownInAddressBook
2. Wait about 5 minutes and then mail enable the PF folder that I want.

In most cases it the email address took the name of the public folder (desired result), in some cases the old email address was still floating around and I had to disable and re-enable the PF to get the desired result.

Now the issue that I have seen is that users that have emailed this PF before have it cached in their outlook which doesnt work anymore.  They must clear this cache and re-type in the email address, then everything is great.

Hope this helps someone else out.

Cheers!

• Marked as answer by toolbox 16 hours 4 minutes ago

The only reason you would have had to do this is if you had some sort of corruption.  The objects for mail-enabled public folders are in Active Directory (under Microsoft Exchange System Objects) and they aren't affected by the public folder migration.

Note that you should only mail-enable public folders that require it.  It's not necessary that they all be mail-enabled unless you need them to have an SMTP address.  My experience is that seldom do more than a few public folders require that.

Hi Ed,

The only reason that I became of aware of this issue is that 5 of the PFs have an auto-reply message so when a user gets the auto-reply message it says the secondary hierarchy email address instead of the actual PF email address (in our case mailbox1@xyz.xom).  The above solution was the only way I could figure it out.