?
Solved

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

Posted on 2014-11-11
2
Medium Priority
?
213 Views
Last Modified: 2014-11-13
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.
0
Comment
Question by:Assist-Netopa
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 24

Accepted Solution

by:
VB ITS earned 2000 total points
ID: 40434904
If you only have the one Public Folder that needs to be migrated then I don't see any real issues with the above steps. You can even look at using Outlook to export the contents of the Public Folders to a PST file, then import them into the new PF mailbox in Exchange 2013.
0
 

Author Comment

by:Assist-Netopa
ID: 40434939
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
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
Unified and professional email signatures help maintain a consistent company brand image to the outside world. This article shows how to create an email signature in Exchange Server 2010 using a transport rule and how to overcome native limitations …
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…
Suggested Courses
Course of the Month12 days, 6 hours left to enroll

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question