I'm running 2010 SP1 Ru3v3, we migrated some time back from Exchange 2003 and I've just been tidying up a whole bunch of orphaned Public Folder entries in the MESO container. Can someone confirm which of my System Public Folders should be mail-enabled please? We only have a single Exchange 2010 server. I found I cannot mail-enable a System Public Folder from EMC or EMS as when I try I get the message: Mail enabling a public folder as a subtree root or under NON_IPM_SUBTREE isn't allowed. Path: \NON_IPM_SUBTREE\schema-root\Default Which suggests that the system public folders that show as mail-enabled are some sort of leftover/legacy thing from 2003 (which ISRT had a habit of mail-enabling pretty much everything by default?). I don't know how well this will paste but here's a get-publicfolder of the System tree. [PS] C:\Windows\system32>Get-PublicFolder "\non_ipm_subtree" -recurse Name Parent Path ---- ----------- NON_IPM_SUBTREE EFORMS REGISTRY \NON_IPM_SUBTREE Organization Forms \NON_IPM_SUBTREE\EFORMS REGISTRY Events Root \NON_IPM_SUBTREE EventConfig_oldsite1 \NON_IPM_SUBTREE\Events Root EventConfig_MAIL01 \NON_IPM_SUBTREE\Events Root OFFLINE ADDRESS BOOK \NON_IPM_SUBTREE /o=contoso/cn=addrlists/cn=oabs/cn=Default Offline Address List \NON_IPM_SUBTREE\OFFLINE ADDRESS BOOK OAB Version 2 \NON_IPM_SUBTREE\OFFLINE ADDRESS BOOK\/o=contoso/cn=addrlists/cn=oabs/cn=Default Offline ... OAB Version 3a \NON_IPM_SUBTREE\OFFLINE ADDRESS BOOK\/o=contoso/cn=addrlists/cn=oabs/cn=Default Offline ... OAB Version 4 \NON_IPM_SUBTREE\OFFLINE ADDRESS BOOK\/o=contoso/cn=addrlists/cn=oabs/cn=Default Offline ... EX:/o=contoso/ou=Exchange Administrative Group (FYDIBOHF23SPDLT) \NON_IPM_SUBTREE\OFFLINE ADDRESS BOOK EX:/o=contoso/ou=oldsit \NON_IPM_SUBTREE\OFFLINE ADDRESS BOOK OAB Version 2 \NON_IPM_SUBTREE\OFFLINE ADDRESS BOOK\EX:/o=contoso/ou=oldsit EX:/o=contoso/ou=CORPORATE \NON_IPM_SUBTREE\OFFLINE ADDRESS BOOK OAB Version 2 \NON_IPM_SUBTREE\OFFLINE ADDRESS BOOK\EX:/o=contoso/ou=CORPORATE OWAScratchPad{7E6750A8-379D-4182-AAA4-3FD4EA98C76C} \NON_IPM_SUBTREE OWAScratchPad{A2C4EBF1-DE4F-437B-A7F2-3CB2C9689F58} \NON_IPM_SUBTREE OWAScratchPad{B6191D35-3630-45BC-A88A-CA5A2ACC99CB} \NON_IPM_SUBTREE SCHEDULE+ FREE BUSY \NON_IPM_SUBTREE EX:/o=contoso/ou=Exchange Administrative Group (FYDIBOHF23SPDLT) \NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY EX:/O=contoso/OU=EXTERNAL (FYDIBOHF25SPDLT) \NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY EX:/o=contoso/ou=oldsit \NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY EX:/o=contoso/ou=CORPORATE \NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY schema-root \NON_IPM_SUBTREE Default \NON_IPM_SUBTREE\schema-root microsoft \NON_IPM_SUBTREE\schema-root exchangeV1 \NON_IPM_SUBTREE\schema-root\microsoft StoreEvents{7E6750A8-379D-4182-AAA4-3FD4EA98C76C} \NON_IPM_SUBTREE globalevents \NON_IPM_SUBTREE\StoreEvents{7E6750A8-379D-4182-AAA4-3FD4EA98C76C} internal \NON_IPM_SUBTREE\StoreEvents{7E6750A8-379D-4182-AAA4-3FD4EA98C76C} StoreEvents{A2C4EBF1-DE4F-437B-A7F2-3CB2C9689F58} \NON_IPM_SUBTREE globalevents \NON_IPM_SUBTREE\StoreEvents{A2C4EBF1-DE4F-437B-A7F2-3CB2C9689F58} internal \NON_IPM_SUBTREE\StoreEvents{A2C4EBF1-DE4F-437B-A7F2-3CB2C9689F58} StoreEvents{B6191D35-3630-45BC-A88A-CA5A2ACC99CB} \NON_IPM_SUBTREE globalevents \NON_IPM_SUBTREE\StoreEvents{B6191D35-3630-45BC-A88A-CA5A2ACC99CB} internal \NON_IPM_SUBTREE\StoreEvents{B6191D35-3630-45BC-A88A-CA5A2ACC99CB}

I'm running 2010 SP1 Ru3v3, we migrated some time back from Exchange 2003 and I've just been tidying up a whole bunch of orphaned Public Folder entries in the MESO container. Can someone confirm which of my System Public Folders should be mail-enabled please? Hi Paul, Not a single one of the System Folders needs to be mailenabled. ..and you can also delete all of the system folders that Exchange 2010 doesn't use and those would be: Events Root EventConfig_oldsite1 EventConfig_MAIL01 OWAScratchPad* schema-root (including the subfolders) StoreEvents* Exchange 2000 running in mixed mode back in the days, used to mailenable all public folders and I would think that is the reason so you have so many of them.Martina Miskovic

Hi Martina, Thank you very much :) We went from 5.5 to 2003 to 2010 so I guess that explains some of it. So I can do a recursive get-publicfolder | disable-mailpublicfolder on the non_ipm_subtree to tell Exchange the folders aren't mail enabled, then I can delete the orphaned aliases from the MESO container and that seems to take care of the mail-enabled problem. Respectfully, how confident are you that I can delete the other folders you've listed? They don't take up space so if there's any danger of it breaking anything I'd sooner leave them around (the only thing I can think of is we use BES though I don't see why it would use those).

Respectfully, how confident are you that I can delete the other folders you've listed? 100% sure and no..it will not break anything.Martina Miskovic

Perfect, so basically the only "Public Folder" entries I should ever see in the MESO container are the ones for folders I have chosen to be mail-enabled, there is nothing that is supposed to be there by default? I had around 3500 orphans to remove so want to be sure I haven't inadvertently removed anything critical - I bounced the Exchange services afterwards and no errors in any event logs.

Perfect, so basically the only "Public Folder" entries I should ever see in the MESO container are the ones for folders I have chosen to be mail-enabled, there is nothing that is supposed to be there by default? Right on the money! It used to be to easy to remove/delete Public Folder Databases in the past (Exchange 2003 SP1 and earlier) and that left a lot of orphaned objects in MESO. Martina Miskovic

Perfect thanks Martina, appreciate it!

Happy to have helped! Have a good Saturday.Martina Miskovic

One more thing.. so I've mail-disabled all the NON_IPM_SUBTREE, that was fine. I removed everything you confirmed was OK to remove, all fine except for Events Root: [PS] C:\Windows\system32>Remove-PublicFolder "\non_ipm_subtree\events root" Confirm Are you sure you want to perform this action? Removing public folder "\NON_IPM_SUBTREE\events root". [Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"): y Cannot delete the object '\NON_IPM_SUBTREE\events root'. Please make sure that you specified the correct identity and t hat you have the correct permissions to delete it. + CategoryInfo : NotSpecified: (0:Int32) [Remove-PublicFolder], MapiPartialCompletionException + FullyQualifiedErrorId : EFA114FB,Microsoft.Exchange.Management.MapiTasks.RemovePublicFolder I've tried this from EMC, EMS, logged on as myself, logged on as domain/enterprise/schema Administrator, same result. Would you have any suggestions please?

It might work with MFCMapi, but if it doesn't...just keep the folder. You can still maildisable it.Martina Miskovic

It might work with MFCMapi, but if it doesn't...just keep the folder. You can still maildisable it. Martina Miskovic It appeared to work, but when I came out and went back in it was still there. Cosmetically it's no problem, it just concerns me a little that this may come back to bite me down the line. I'll start a fresh thread with a suitable subject, I do now only have the mail-enabled folders that I would expect, which is a good thing.

Ok, interesting. I will follow the other thread and post if I think of something. (My first thought was that the folder is just a place holder without a replica configured. Just like OFFLINE ADDRESS BOOK and SCHEDULE+ FREE BUSY, so maybe if you give it replica, Mfcmapi will work)Martina Miskovic

First thing I checked was replicas - I only have one Exchange box anyway, but its Public Folder Store is on the replica list. Interesting what you said about OFFLINE ADDRESS BOOK and SCHEDULE+ FREE BUSY as I'd noticed the parent folders don't have replicas but the subfolders do, same as EFORMS REGISTRY.