Link to home
Start Free TrialLog in
Avatar of Assist-Netopa
Assist-NetopaFlag for United Kingdom of Great Britain and Northern Ireland

asked on

How to safely remove 2007 legacy Public folders during 2013 co-existence

Dear Experts

We've been having many issues during our migration for Exchange 2007 SP3 CU14 to Exchange 2013 CU6 with interim update to resolve the DB dismounting and EAS proxy issues.

Our environment consists of a small organisation, ie one 2007 exchange and one Exchange 2013.

I need to plan for the removal of the legacy public folders, of which there is only one in use. I will even move this to a shared mailbox rather than worry about migrating to a modern PF. Given that there is only one PF in use could I simply:

1) Delete the legacy PF's after checking the important one is OK as a shared mailbox
2) Remove the Public folder database using these guidlines:

http://technet.microsoft.com/en-us/library/aa998329(v=exchg.80).aspx

3) Finally go ahead and decommission Exchange 2007

With all the research I have done many articles seem to be older than regarding CU6 era information or talking about migrating them first which I don't think is necessary in our case.
ASKER CERTIFIED SOLUTION
Avatar of VB ITS
VB ITS
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Assist-Netopa

ASKER

Thanks, I guess that's what I thought it's just there have been so many issues with Exchange, whether that's hotfixes, permissions, split dns, activesync, EAS, proxying ... don't know what to believe any longer..

Not even going to use a PF Database/Mailbox just a normal mailbox as you'd first have to remove legacy public folders. Just going to try and K.I.S.S