In some cases you are forced to hard-remove public folders from Exchange. You can use ADSI Edit to delete these folders.
Open ADSI-Edit and got to configuration
Navigate to this path:
CN=Exchange Administrative Group (FYDIBOHF23SPDLT)
Now you can delete the PF-Database you want to get rid off.
CN=First administrative Group
Super..Excellent..!!! Keep going:)
Excellent its very helpful...!!!
But want to highlight one more thing. Once you delete the Public folder database directly from adsiedit then there are many entries in adsiedit which will point to "Deleted objects" like sitefolderserver.
Also mention to correct those settings
it is one thing to say "hey, I found a great article on how to do this, here are the steps..." and then cite the source....but to copy and paste, including the spelling errors, and take credit as though you completely came up with it yourself is essentially
I have to remove a public folder database and server from our exchange environment. This is an old exchange 2010 (A) server that holds some 200gb of obselete data which is not being replicated over to 2 (B and C) other newly built exchange 2010 PF servers.
Can I use Exfolders to stop replication to this server? mailbox databases are pointed to server B. Here is my step by step:
1. Stop replication to Server A. Ensure it completes. Ensure server B and C has the relevent PFs that is required for business by running the get- publicfolderreplicationreport script.
2. Dismount the PF database on Server A. Allow sufficient time to ensure there are no errors or PF availability issues for end users.
3. Uninstall Exchange 2010 binaries from Server A. Disjoin server from the domain. remove any remnants from ADSIedit if needed.
Will this be the most graceful way to remove this server from the environment? I want to ensure it is totally seamless to the end users.