Exchange 2010 to 2016 Public Folder Migration

I have migrated our public folders from our Exchange 2010 server to our new  Exchange 2016 folder.  Afterwards, users that have mailboxes on the 2010 sever cannot access the public folders.  The few users that I have moved to the new 2016 can access the public folders.
Any advice as to what is going on?
David BarmanAsked:
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.

AmitIT ArchitectCommented:
As far as I know, this is by design and you cannot do much. As Microsoft has changed Public folder completely. You need to all mailboxes to 2016. Best practice to move PF at the end.
David BarmanAuthor Commented:
Eeew.. I wish the technet article would have mentioned that.
AmitIT ArchitectCommented:
Here is the MS KB:

Due to the changes in how public folders are stored, legacy Exchange mailboxes are unable to access the public folder hierarchy on Exchange 2013 or Exchange 2016 servers or on Exchange Online. However, user mailboxes on Exchange 2016 servers can connect to legacy public folders. Exchange 2016 public folders and legacy public folders can’t exist in your Exchange organization simultaneously. This effectively means that there’s no coexistence between versions. Migrating public folders to Exchange Server 2016 or Exchange Online is currently a one-time cutover process.

For this reason, it’s recommended that prior to migrating your public folders, you should first migrate your legacy mailboxes to Exchange 2016 or Exchange Online.

Let me know, if any further doubt.

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
Ensure Business Longevity with As-A-Service

Using the as-a-service approach for your business model allows you to grow your revenue stream with new practice areas, without forcing you to part ways with existing clients just because they don’t fit the mold of your new service offerings.

David BarmanAuthor Commented:
Another add issue. Any users with mailboxes on the new server can't send mail to mailboxes on the 2010 server. In addition, those users that have been moved, the mail icon in Windows control panel won't open. It gives an error "The operating system is not presently configured to run this application"

Adam BrownSenior Systems AdminCommented:
The typical migration plan for Public folders going into Exchange 2013 and later calls for migrating them *last* because of this very issue. 2016 mailboxes can read public folder data on a 2010 server (as long as there is configuration on the server to forward public folder requests to the 2010 server. If, by change, you still have your Public Folder databases online, you may be able to offline the public folder mailboxes and reconfigure things to point to 2010, but I don't know if that will work without issues). Unfortunately, there's no easy way to migrate mailboxes back from 2016 to 2010. You can try to look at some of the Exchange migration software solutions out there like BinaryTree, MigrationWiz, or Quest's Migration Manager, though. One or more may provide the capability to reverse this in the event of a failure or issue, but I haven't worked with them all and haven't had a public folder migration to work on in nearly 4 years, so I can't say for certain if any of them support this.

That said, if you can move your plans for migrating mailboxes forward, I would recommend getting people onto 2016 sooner rather than later if they can't access public folders and need to for their work.
Adam BrownSenior Systems AdminCommented:
In addition, those users that have been moved, the mail icon in Windows control panel won't open. It gives an error "The operating system is not presently configured to run this application"

This should only happen if you are currently running a new version of Outlook with the mail profiles from an old version of Outlook, or are running a version of outlook that doesn't work with Exchange 2016 (Outlook 2007 and earlier, for info).
AmitIT ArchitectCommented:
For your another issue, I advise you to open new case. So, EE can focus properly. As far this question is concerned, you have the right answer given by me.
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.