troubleshooting Question

Exchange 2010 used ASDI Edit to delete Public Folder Database

Avatar of Chad Sams
Chad Sams asked on
PowershellExchangeDatabasesEmail Servers
3 Comments1 Solution151 ViewsLast Modified:
I am completing an Exchange 2010 to Exchange 2013 Migration.  Before decommissioning my Exchange 2010 Server I went through the article - - to delete out my Public Folder Database on the Exchange 2010 Server.  We didn't use Public Folders, so there was no data in the lone Public Folder Database.  

Following the article, I made sure and removed any Public Folder hosted Offline Address Lists.  I made sure no mailbox databases were associated with the Public Folder Database (according to the article).  I then came to the last step of removing the Public Folder Database by using PowerShell.  I tried the removal on Exchange 2013 and it didn't remove the Public Folder - had an error.  I skimmed the error and saw in the article where if you have Internet Newsgroups from Exchange 2003 use ASDI Edit to manually remove it.  This is where I made the mistake.  If I would have read the error closer I would have seen all I had to do was run PowerShell on the Exchange 2010 box and then it would have deleted out the Public Folder Database without any problems.

Instead, I went into ASDI Edit.  Navigated to CN-Services, CN=Microsoft Exchange, CN=your organization name, CN=Administrative Groups, CN=Administrative Group (FYDIBOHF23SPDLT), CN=Databases.  I found the Public Folder Database and I then deleted it.  After doing it, I was concerned about there being pointers in other entries pointing to the Public Folder Database I had just manually deleted.  I did find an article before deleting and it had a comment at the bottom that mentioned I needed to clear out the SiteFolderServer entry in the properties of the Exchange Administrative Group.  I have done this step.  Below is the article:

Are there anymore AD Objects that reference/point to the Public Folder Database I manually deleted in AD?  Should I be concerned?  Doing this has really bothered me because I know how quirky Exchange can be when things aren't done by the book.  Any assurance or guidance would be greatly appreciated before I move forward with decommissioning the Exchange 2010 Server.  Thanks!
Hasin Ahmed Choudhary
Exchange Administrator

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 1 Answer and 3 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 3 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros