Exchange 2010 used ASDI Edit to delete Public Folder Database

I am completing an Exchange 2010 to Exchange 2013 Migration.  Before decommissioning my Exchange 2010 Server I went through the article - http://www.sbsfaq.com/?p=3862 - 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:

https://blogs.technet.microsoft.com/mukutdas/2015/09/11/remove-public-folder-using-adsiedit/

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!
Chad SamsIT ManagerAsked:
Who is Participating?
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.

Hasin Ahmed ChoudharyExchange AdministratorCommented:
1) Check if PFDb was defined for 2010 databases. Try to make it null.
2) For 2013 Db, I am sure it won't be as you never used that PF.


Rest everything should be okay, as legacy PF will not be used from exchange 2013 onwards.
0

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
Chad SamsIT ManagerAuthor Commented:
Hello Hasin,

I did go to -

CN-Services, CN=Microsoft Exchange, CN=your organization name, CN=Administrative Groups, CN=Administrative Group (FYDIBOHF23SPDLT), CN=Databases

and went into each Database and cleared the field/attribute msExchHomePublicMDB.  I'm thinking this has disconnected the databases pointing to the Public Folder DB.

I really appreciate the re-assurance!  I will leave the question open a little longer to see if you have a comment on how I changed the  msExchHomePublicMDB attribute on each database.  Also, will leave it open to see if anyone else has any other thoughts.  You taking the time to answer my question has been very encouraging.  Thanks!
0
Chad SamsIT ManagerAuthor Commented:
Thanks Hasin, you helped me to rest easier with the ASDI Edit Deletion.
0
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
Powershell

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.