• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 95
  • Last Modified:

Public Folders Migration from Exchange 2010 to 2013

Hi Experts
I recently migrated our exchange 2010 to 2013,  all mailboxes moved and everything works fine.

i got few concerns related to public folders before i try that on my production servers.

on my Test Bed.  i had following experience while trying to migrate public folders , followed some good online guides used PS1 scripts provided by microsoft to create excel sheet mapping files etc.

all went well according to MS article and we can access public folders on 2013.

but if I look at Exchange 2010 via public folders management console it still shows me all folders,  not sure if its correct i thought they supposed to move to 2013 server during migration process, but looks like its kind of done copy all content to 2013 and kept folder in 2010 as well.
and due to that when i try to delete public folders database on 2010 server it tells me there are public folder replicas , move replicas to another server or delete public folders.
I tried using .\MoveAllReplicas.ps1 -Server Server01 -NewServer Server02  CMD to do that but it failed with below error
--------------------------
 "
You must specify a value with the Replicas parameter.
+ CategoryInfo : InvalidOperation: (\NON_IPM_SUBTRE…YDIBOHF23SPDLT):PublicFolderIdParameter) [], SetRep
licasEmptyException
+ FullyQualifiedErrorId : A21C6F7F
"
---------------------------

tried many online articles and googled a lot but couldn't get beyond above error.

at the end what i did is deleted all public folders that were showing on Exchange 2010 public folders management console.
now deleting these from there not deleted anything on 2013 so yea i can access all public folders from 2013 which are kind of copy of 2010 folders thats what i needed.

and as all folders deteled from 2010 , then i was able to delete public folders database on exchange 2010 and un-install exchange 2010.

above all was done on TEST BED,  and i want to find out if above is fine or if anyone else had similar experience or any best guide to move public folders from 2010 to 2013  ,  

just to ensure i dont mess up my production exchange servers.

Thanks
Harry.
0
H-Singh
Asked:
H-Singh
  • 5
  • 3
2 Solutions
 
Andy MInternal Systems ManagerCommented:
I've only had to migrate public folders once on the 2010 to 2013 migrations I've done and don't recall having to remove the 2010 public folders the way you have described.

I know some guides do appear to be missing some information or don't explain things very well (found this out the first time I did a migration - think I went through several different guides before finding the info I needed).

The one I follow is: http://www.petenetlive.com/KB/Article/0000789.htm and it appears to work very well, never had any issues during or after the migration.

The main area too look out for is towards the end when running the "Set-OrganizationConfig -PublicFolderMigrationComplete:$true" command - this has to be run on the 2010 server, not the 2013 server as some guides indicate.
0
 
SteveCommented:
The issue here is that most guides don't really tell you what to do with the 2010 public folders when you're finished with them.....

Unlike public folder migrations for previous versions of exchange, a 2013 migration isn't 'technically' a public folder migration. public folders have been completely changed in 2013 and don't really bear any resemblance to previous versions of exchange (that's why 'moveallreplicas' didn't work... there aren't any replicas......)

once the migration is finished and your happy the new 'public folders' are working, the old public folders are defunct and can be removed as if you were just decommissioning them. the process you used is fine, but the guide provided by Andy above offers another way to decommission them.

make sure you run the command noted by Andy above though, as that ensures nothing mistakenly looks for the old public folders after the migration.
0
 
H-SinghTechnical DirectorAuthor Commented:
thanks guys, that clears few doubts.

luckily we are not going to need all the public folders and instead we only need to keep around 10-15 of these. what I am thinking to do is EXPORT all public folders to PST from outlook.

then delete all databases including public folders database on exchange 2010.

Create public folder mailbox on exchange 2013 and then from outlook from standalone PST i can copy past folders to public folders.

that will save hassle of going through migration process.

i hope this will work.
thanks
Harry
0
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

 
Andy MInternal Systems ManagerCommented:
That is another way to do it though please note you'll still need to manually remove the public folder database (and contents) from the Exchange 2010 server after you are done as it won't recognize the 2013 public folder mailbox or know it's been migrated.
0
 
H-SinghTechnical DirectorAuthor Commented:
thanks Andy yea if i follow below procedure.

On Outlook : Export All required Public Folders to PST file. ensure it works by attaching to outlook.

On Exchange 2010
Delete all other databases that also got PublicFolders database as default PF database.
Delete All public folders by going in public folders management console.
Delete Last/only Public Folders database.

with above i believe my organization wont have any reference to public folders on exchange 2010.
at this point i can also un-install Exchange 2010 to remove it from organization. (will do this later)

-----------
ON Exchange 2010
Create new Public folder Mailbox
provide myself Root perfmissions to public folders.
then via Outlook i can copy/move public folders from standalone PST.

All done have beer :-)

hope i wont get into any trouble am doing this saturday night.

Regards
Harry
0
 
Andy MInternal Systems ManagerCommented:
Sounds good Harry. Usually what I would do is export the Public Folders to the PST, create the 2013 PF mailbox and import the public folders into that, making sure required users can access it.

Then, I would shutdown the 2010 server for a few days - this will allow you to check that everything works as required before deleting databases/decommissioning the server. (Otherwise you may need to spend time recovering data from backups, changing AD, etc if there is an issue).

If there's no problems after those days then proceed with the decommission as required.

Have a good weekend and hope it goes to plan.
0
 
H-SinghTechnical DirectorAuthor Commented:
Cheers Andy
just quick one , until I don't delete public folders database from exchange 2010  ,
exchange 2013 wont let me create new pubilc folder mailbox  saying public folder installation exists in organization.

or is it best to create with hold for migration via shell.

that means i will have public folders coming from both servers ?
0
 
H-SinghTechnical DirectorAuthor Commented:
just to update, its all sorted now.

on exchange 2010 i ran this cmd "Set-OrganizationConfig -PublicFolderMigrationComplete:$true"

then deleted public folders database on exchange 2010 ,
created new PF Mailbox on exchange 2013.
and imported required public folders via outlook.

exchange 2010 is shut down and all seems working fine.
thanks for advise guys
0
 
H-SinghTechnical DirectorAuthor Commented:
good advise guys, used few points from these to get things sorted on my end. thanks
0
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.

Join & Write a Comment

Featured Post

Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now