Decomissioning an Exchange Server 2007 server after migrating to Exchange Server 2013

Migrated an Exchange Server 2007 server (bfnep-exch1) to Exchange Server 2013 (xchange13) successfully.  Did not migrate Public Folders because do not care to use Public Folders in 2013.  Running on the 2013 server for months with 2007 server powered-off 6 days a week without any issues.  The 2007 server is power-on on the 7th day for ~ 6-8 hours to keep AD "synced".  Now ready to decommission the 2007 server.

All mailboxes and the OAB were moved to the 2013 server.
Was able to remove the MaIlboxDatabase from 2007 server via Get-MailboxDatabase -Server bfnep-exch1 | Remove-MailboxDatabase command.
Trying to remove the PublicFolderDatabase from 2007 server via Get-PublicFolderDatabase -Server bfnep-exch1 | Remove-PublicFolderDatabase command.  However, an error message is returned stating that the Public Folder Database contains folder replicas.
When I look at the Public Folder Database via the Public Folder Management Console the database is empty.
Running the command Get-PublicFolderStatistics lists 7 entries.  Can these be removed via Get-PublicFolderStatistics | Remove-Public Folder safely?
Looking on the 2013 server shows not Public Folders or Public Databases.
Attached is a file with several screen shots from the 2007 & 2013 servers.
Let me know if any additional info is required.
Thank you.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Will SzymkowskiSenior Solution ArchitectCommented:
If you cannot remove the last public folder sucessfully using the Remove-PublicFolderDatabase via powershell then you only other option would be to use ADSIEdit.

See the TechNet Blog for details


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
bfnepAuthor Commented:
See attached screen shots for the following follow-on questions.

Are all the 7 items in the list generated by Get-PublicFolderStatistics actually in the Public Folder Database or only the last 5?

Will SzymkowskiSenior Solution ArchitectCommented:
Replication needs to happen before you will see the values update.

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

bfnepAuthor Commented:
my concern with deleting the public folder database entry via adsi edit is that I will delete something in the database that will impact my entire exchange organization.

What exactly is each item listed via Get-PublicFolderStatistics command?

EX:/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)
EX:/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)
Internet Newsgroups

If i delete the database how does this affect this list or exchange organization as a whole?
bfnepAuthor Commented:
After removing public folder database via ADSI Edit some of my users are getting a  popup "The Microsoft Exchange administrator made a change that requires you to quit and restart outlook."

The last step (which I have not taken yet)  to decommission my Exchange 2007 server is to uninstall the server.  Will this clear this popup issue or must I take some corrective action before uninstall the 2007 server?
Will SzymkowskiSenior Solution ArchitectCommented:
When a configuration change has happened on the Exchange server and users have their outlook clients open this is a typical message to close and re-open it. You need to uninstall Exchange from the server. This is the correct way to remove Exchange from the domain.

It will remove all of the appropriate entries in Active Directory as well.

bfnepAuthor Commented:
New update: everyone gets the popup this morning after powering-on their PCs.  If they click OK, close and reopen Outlook they still randomly get the popup.

Is there anything else I should check before I uninstall Exchange 2007?

Thanks for the help on this issue.
Will SzymkowskiSenior Solution ArchitectCommented:
No that should be it. When you uninstall Exchange it will do an initial pre-requist check and if everything is removed from the Exchange sevrer you will be able to uninstall it successfully.

bfnepAuthor Commented:
After uninstalling Exchange 2007 users continued getting the popup.  I found out that the public folder database on my Exchange 2013 server was pointing to a deleted object.  I needed to drill down to the properties of the Mailbox Database in ADSIEDIT & set the value of “msExchHomePublicMDB” to be blank. Afterwards, a restart of the Information Store Service resolved the issue.  See attached document for the details.
bfnepAuthor Commented:
I needed to complete this last step to remove the old Public Folder reference.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.