PublicFolder CN=Schema,CN=Microsoft Exchange System Objects,DC=contoso,DC=com
I'm in the preparation stage of migrating our Public Folders from an on-premises Exchange 2016 CU19 server to Exchange Online. Running the SourceSiceValidation.ps1 script outputs several orphaned MEPFs in our Active Directory, and I get a similar output from the ValidateMailEnabledPublicFolders.ps1. The recommendation is to delete the orphaned MEPFs, but I'm running into an oddity that I just don't feel comfortable deleting. There's a PublicFolder named "Schema" in our MESO OU, and it just feels wrong to delete anything named "Schema" in a database. Get-ADObject "CN=Schema,CN=Microsoft Exchange System Objects,DC=***,DC=***" | fl DistinguishedName : CN=Schema,CN=Microsoft Exchange System Objects,DC=***,DC=*** Name : Schema ObjectClass : publicFolder ObjectGUID : 9*******-8***-4***-8***-2*********** Any advice on how to determine if this object really is safe to remove? Thanks!
Deletion of old mail public folders - Exchange 2013 to 1029
Hey all me again! Have migrated from Exchange 2013 to 2019. 2019 is now doing everything. We had used Public Folders in the past but no more. All the folders themselves are gone but there remains some some mail objects that must have been associated. Some I can see were created by us so I have been running disable-mailpublicfolder to delete them. Some have scary names like StoreEvents{395FEF93-3631-4CC3-A8BC-BDD0F7AF32A3}, OAB Version 2, OAB Version 4, microsoft, default, globalevents, schema-root, Offline Address Book. Is it safe to just delete these, then delete the Public Folder Mailbox? get-publicFolder -recurse -ResultSize:Unlimited Name Parent Path ---- ----------- IPM_SUBTREE cheers j