PREVIOUS: Exchange 2016: Public Folder migration Part 1
In part one of public folder migration, we prepared our environment. Then we ran all the necessary scripts to size and create the new public folder mailbox hierarchy.
In this second and final part of our series, we will copy the data from the legacy public folder databases into our newly created modern public folders. We will also finalize the migration process.
Step 3: Data Migration
Let’s start moving our data. First, let’s create the migration batch. From the Exchange 2016 server issue the following command.
C:\> New-MigrationBatch -Name PFMigration -SourcePublicFolderDatabase (Get-PublicFolderDatabase -Server EX10) -CSVData (Get-Content C:\PFScripts\FolderToMailbox.csv -Encoding Byte) -NotificationEmails headgeek@exchangeservergeek.com
In our example:
-Name specifies a display name to help identify the batch.
-SourcePublicFolderDatabase (-Server) specifies the 2010 server hosting the public folder database. In my lab, this is called EX10.
-CSVData specifies the path to our map file we created in part one of our series. We had called this FolderToMailbox.csv and saved it to C:\PFScripts.
-NotificationEmails specifies where to email the batch migration report. This is optional.
C:\> New-MigrationBatch -Name PFMigration -SourcePublicFolderDatabase (Get-PublicFolderDatabase -Server EX10) -CSVData (Get-Content
C:\PFScripts\FolderToMailbox.csv -Encoding Byte) -NotificationEmails headgeek@exchangeservergeek.com
Identity Status Type TotalCount
-------- ------ ---- ----------
PFMigration Created PublicFolder 1
[PS] C:\>This only creates the job. To start the actual data copy run the following command. If you named your job anything other than PFMigration you will need to change that here.
C:\> Start-MigrationBatch PFMigration
We can check the progress of the batch by logging into the Exchange Admin Center. Once logged in, navigate to Recipients >> Migration tab.
From here we will see our PFMigration job and its current status. Before issuing the previous command it would have shown a status of “Created”. Once we started the batch it switches to “Syncing”.
Selecting the batch and clicking the View Details link, will give us a deeper insight into what is happening with the batch.
From here we can see greater detail into the progress of our PFMigration batch. We can see that 5 items have synced, nothing has been skipped and, so far no errors are reported. The real magic is the Download the report for this user link. This link is a detailed play by play of everything the migration is doing. Including any additional information on errors. It’s great for troubleshooting purposes.
If you are interested in what my detailed migration report looked like check this link.
You can also see the same report in PowerShell by issuing the following command. You will need to replace PFMigration with the name of your batch if different.
C:\> Get-MigrationUser -Batch PFMigration | Get-MigrationUserStatistics -IncludeReport | fl
Eventually, your migration will show a status of Synced. In addition, the report will list a percentage of 95 and indicate it was automatically suspended. This means the initial seed of data has been completed. However, your new public folder mailbox it is not yet live. If you take no action the migration job will perform an incremental copy every 24 hours until you complete the batch. Keep in mind completing the batch will force downtime for your public folders. It may be best to perform these next tasks under a maintenance window.
Step 4: Completing the Migration
Now that the data is seeded its time to flip the switch.
Warning: This will take your public folders offline. You may wish to schedule this during a maintenance window.
Okay, let’s switch back to the 2010 server.
From the Exchange Management Shell run this command. Users will be blocked from accessing Public Folders.
C:\> Set-OrganizationConfig –PublicFoldersLockedForMigration:$true
Warning: It can take some time for this lock command to propagate through your network. It’s not uncommon for this change to take several hours for a large network. The next two commands will fail until the change is replicated through the network.
Let’s switch back to the 2016 server again.
From the Exchange Management Shell run the following.
C:\> Set-OrganizationConfig -PublicFoldersEnabled Remote
Now let’s complete the batch. Be sure to rename PFMigration to the name of your batch, if different. Hit enter to accept the default action of Yes.
C:\> Complete-MigrationBatch PFMigration Confirm Are you sure you want to perform this action? Complete migration batch "PFMigration"? [Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"):
The batch status will switch to Completing. During this time a final incremental sync is performed. Once finished the status column will display Completed. How long this takes depends on how many changes have been made in public folders since the initial seed, or, last incremental sync. Cleanup and replication are also performed in the environment.
If you are curious about what the final report contains check out this link.
You should also see your folder structure appear under the Public Folders > Public Folders tab. You may need to hit the refresh (
) button. This is where you manage public folders going forward.
Now we need to test. Issue this command against one of your test users. In this command, I am assigning the public folder mailbox that contains the new hierarchy to user Rory Williams.
Tip: I recommend using a non-administrative user for this next test. I’ve seen strange errors when using administrative accounts for testing purposes.
C:\> Set-Mailbox -Identity rwilliams -DefaultPublicFolderMailbox "Public Folder Mailbox 1"
You can access Public Folders with either Outlook 2010 or greater or Outlook Web App. From either of these programs check the hierarchy, check content, check permissions, and check mail settings. If it doesn’t look right Microsoft recommends using their rollback method documented here.
If everything looks great then run the following command on 2016 to deploy to all other users.
C:\> Get-Mailbox -PublicFolder | Set-Mailbox -PublicFolder -IsExcludedFromServingHierarchy $false
Now, switch gears back to 2010 and run this command.
C:\> Set-OrganizationConfig -PublicFolderMigrationComplete:$true
And finally one last command back on the 2016 server.
C:\> Set-OrganizationConfig -PublicFoldersEnabled Local
All good?
You are done!
Once you are ready to remove the old Public Folder Databases check this article.
Recommended Reading
Here are some articles I thought you might like.
- Import & Export SSL Certificates in Exchange Server 2016
- Install Exchange 2016 in your lab (7-part series)
- Configure Kemp Load Balancer for Exchange 2016
- Create an IP-less DAG
- What Ignite taught us about Exchange 2016
Join the conversation on Twitter @SuperTekBoy.
Hello! please can you help me ?
I have 3 servers:
2 units 2010 (site a)&(site b)
1 unit 2016 (site b)
remark:
2010(a) have usermailboxes and PF don’t using.
2010(b) usermailboxes was migrated to 2016 server and have lastone PF database.
PF database stil on 2010 (site b) and have old data, i want to delete it. don’t need to migrate that 200Gb on server 2016 (site b).
Okay i can delete this data after migration, but now i can’t create new migration batch, i have an error:
MapiExceptionLogonFailed: Unable to make connection to the server. (hr=0x80040111, ec=-2147221231)
My PF database is mounted on 2010(site b) server. i can resolve it by command on 2016 server:
[PS] C:\PFMigration>Get-PublicFolderDatabase -Server ms02
Name Server
—- ——
PublicFolders MS02
and
[PS] C:\PFMigration>Get-Content “C:\PFMigration\mailboxmap.csv” -Encoding Byte
it’s ok for reading.
this is my question:
Can i migrate PF database on 2016, and leave 2010 (a) with users ?
Or i must migrate all 2010 (a) users to 2016 and after that continue my PFmigration ? and this error will be completing well ?
Hey Vlad,
If you move the public folders to 2016 but keep the users on Exchange 2010, those users will lose access to the public folders, as it’s not forward-compatible. Users on Exchange 2016 can continue to use 2010 public folders, though, so it is backward compatible.
Regarding the error, I suspect it’s a permissions issue on the public folder database itself. I recommend opening a Microsoft case on that error.
Hey Gareth. Hope you are still around for some assistance. When I do step #3 I get an error “cannot convert value “get-content” to type “system.byte[]…input string was not in correct format. Any help would be appreciated.
Hi Brian,
Sorry for the delay. Were you able to resolve? I am curious if you modified the CSV in any way prior to running step 3.
Hi Gareth,
The post is very useful!
The step by step approach with picture help lot of people accomplish their task.
Good job!
Hoping for similar post for Exchange 2016 migrate to Exchange 2019.
Hey Tsang,
Believe it or not, but it is as simple as doing a mailbox move request. Check out Microsoft’s documentation here – https://docs.microsoft.com/en-us/Exchange/collaboration/public-folders/migrate-from-exchange-2013?view=exchserver-2016
Thank you for the great article! Is there any way to perform user testing before we lock the old public folders? I have a need for a large amount of testing due to some custom macros and forms. It would be great if we could test them over a longer period of time.
Hey Scott,
You can migrate over a single user (or multiples) before transitioning the entire environment
Set-Mailbox -Identity user -DefaultPublicFolderMailbox pfmailboxname
Very nice article – thank you!
what do I do if I see all my public folders migrated as mailboxes under ‘public folder mailboxes’ but none shows under ‘Public Folders’ tab in EAC 2016? Had to rebuild the search index in the middle of the migration and now got completed with warnings on 2 out of 16 PF mailboxes.
Thanks
Thanks a lot.
Brilliant! Thank You.. Smooth sailing.. 20K items Migrated.
20,000 items is a great achievement. Well done!
We only have a public Calendar in our Public folders on exchange 2010, but we are wanting to migrate them over to “Rooms” in 2016. Does this migration process you have here incorporate this? Or do you have a good idea on how to do it?
This process would just migrate public folders from Exchange 2010 to Exchange 2016 and keep them in their current state.
It sounds like you are looking to convert your public folders to a number of room mailboxes going forward. I would recommend you convert these to room mailboxes on Exchange 2010 first, then move those room mailboxes to Exchange 2016.
Depending on how many public folders you have this could be as simple as dragging the calendar content from the public folder to the room mailbox in Outlook. If you have hundreds or even thousands of public folders you may want to look at a 3rd-party paid product to help you convert these from public folders to room mailboxes.
Great article Gareth.
I am just about to take the plunge and run my 2010/2016 PF migration and I have a couple of questions relating to this;
Some of our staff create links to their most used PFs in their Outlook “Favourites” folder, will these need to be recreated?
Also we use PF Contact folders and many users have “Show this folder as an Outlook Address Book” configured for these. Again will this need to be re-configured after the migration?
Many thanks
Good morning Ben,
I am actually not sure on either of those questions. Apologies it took so long to respond to your question. I suspect you may have now done this migration. If so, let us know what the experience ended up being for your users.
Great instructions!
One last issue to tackle. My test user was fine. And then ran the command to unlock the PFs for all users. Server returned the response that no change was made. After about 20 mins, some users started seeing the public folders, however after 48 hours, I still have many users who do not have access. If I explicity give them permission, it works, but why can’t I unlock for all users? Any thoughts?
Thanks!
Ran into an issue with what appears to be large items.
All send/receive/transport connectors had been set to 20MB. Increased to 2000MB and try to resume the migration job from the EAC but still get failures.
Restarted transport services on both old and new exchange and retried. Still have errors
1/15/2018 10:09:19 AM [exchange] Request processing started.
1/15/2018 10:09:19 AM [exchange] Cleared sync state for request 00000000-0000-0000-0000-000000000000 due to ‘CleanupOrphanedMailbox’.
1/15/2018 10:09:22 AM [exchange] Stage: CreatingFolderHierarchy. Percent complete: 10.
1/15/2018 10:09:22 AM [exchange] Initializing folder hierarchy from mailbox ”: 17 folders total.
1/15/2018 10:09:22 AM [exchange] Folder creation progress: 0 folders created in mailbox ‘2fa9f74a-e9ae-42f7-bad8-3095905d80a4’.
1/15/2018 10:09:23 AM [exchange] Folder hierarchy initialized for mailbox ‘2fa9f74a-e9ae-42f7-bad8-3095905d80a4’: 13 folders created.
1/15/2018 10:09:23 AM [exchange] Stage: CreatingFolderHierarchy. Percent complete: 10.
1/15/2018 10:09:23 AM [exchange] Stage: CreatingInitialSyncCheckpoint. Percent complete: 15.
1/15/2018 10:09:23 AM [exchange] Initial sync checkpoint progress: 0/17 folders processed. Currently processing mailbox ‘2fa9f74a-e9ae-42f7-bad8-3095905d80a4’.
1/15/2018 10:09:23 AM [exchange] Initial sync checkpoint completed: 13 folders processed.
1/15/2018 10:09:23 AM [exchange] Stage: LoadingMessages. Percent complete: 20.
1/15/2018 10:09:23 AM [exchange] Target Mailbox quota value is unlimited.
1/15/2018 10:09:23 AM [exchange] Stage: LoadingMessages. Percent complete: 20.
1/15/2018 10:09:32 AM [exchange] A large item was encountered: Item (IPM.Document.CompressedFolder) Subject:”B103106 07only.zip”, Size: 74.21 MB (77,810,256 bytes), Folder:”SAS”
1/15/2018 10:09:44 AM [exchange] Copying messages is complete. Copying rules and security descriptors.
1/15/2018 10:09:46 AM [exchange] Initial seeding completed, 932 items copied, total size 75.51 MB (79,175,279 bytes).
1/15/2018 10:09:47 AM [exchange] Stage: CopyingMessages. Percent complete: 95.
1/15/2018 10:09:47 AM [exchange] Copy progress: 932/932 messages, 75.51 MB (79,175,279 bytes)/75.51 MB (79,175,279 bytes), 13/17 folders completed.
1/15/2018 10:09:47 AM [exchange] Fatal error TooManyLargeItemsPermanentException has occurred.
Great article thanks but I have a slight issue.
All the Public folders are now available and look like they have the correct permissions but I cannot add new folders to the public folders, it gives a you don’t not have permission warning.
Hey Bob,
It sounds like you may be missing root permissions. In the Exchange Admin Center, go to the Public Folders > Public Folders tabs and click the three dots. You should have a drop down that says Root Permissions. Select that and you should be able to add root level permissions to your public folder environment.
Unfortunately, this failed at the last step to finalize. The 2016 server never said “completing” or “completed”, and stayed stuck at “Synced”. Went through the rollback process, and now I can’t see PF at all. What now?
Thanks for the article Gareth. This is my go-to for public folder migrations lately but I have a folder (only one folder under public folders on 2010) that is failing due to invalid characters. The fact is that the folder was abandoned and never used so I was able to just go ahead and delete it. Unfortunately, it’s still giving the error on the daily sync, even after I deleted the reference to it from PublicFolderStats.csv. Can I just go ahead and complete the batch or will this error prevent me from finishing?
Hey Andrew,
Often invalid characters are a result of a mail-enabled public folder and it’s the mail attributes of the public folder that is throwing the invalid character error. Aliases are typically the main culprit. For this error I typically recommend finding and correcting the invalid character. If that does not work then mail-disabling the public folder before you migrate it is the next step I typically take. Then mail-enable it once the migration is complete.
Unfortunately, I don’t know of a way to remove a single public folder from the migration batch once it’s started. The CSV mapping file is only used once when you create the migration batch with the New-MigrationBatch cmdlet. After that the CSV is not used again. So making changes to the CSV would only have effect if you used it for a brand new migration batch.
You can try and complete the batch but you may have to delete and recreate the batch (effectively restarting from Step 3). How many public folders do you have and how big is the public folder database?
Great arctile!
More precise and easy to go vs MS!!!
Thank you!
Hello, I am having trouble creating my migration batch, I have checked it is correct but when I try and run it I get:
[PS] C:\PFScripts>New-MigrationBatch -Name PFMigration -SourcePublicFolderDatabase (Get-PublicFolderDatabase -Server EXCH2010) -CSVData (Get-Content C:\PFScripts\FolderToMailbox.csv -Encoding Byte) -NotificationEmails email@domain.com
WARNING: An unexpected error has occurred and a Watson dump is being generated: The type initializer for ‘Microsoft.Exchange.ExchangeSystem.EnumValidator`1’ threw an exception.
The type initializer for ‘Microsoft.Exchange.ExchangeSystem.EnumValidator`1’ threw an exception.
+ CategoryInfo NotSpecified: (:) [New-MigrationBatch], TypeInitializationException
+ FullyQualifiedErrorId: System.TypeInitializationException,Microsoft.Exchange.Management.Migration.MigrationService.Batch.NewMigrationBatch
+ PSComputerName: EXCH2016.domain.com
Everything up until this has worked ok, any advice?
Hmm. I have not seen that one before. Any messages in the Event Viewer? With watson doing a bugcheck sounds like this issue may be bigger than Exchange itself (e.g. missing antivirus exclusions, bad hardware).
Nice Job ! I can add this remarks to accelerate complete migration : https://misstech.co.uk/2016/07/18/public-folder-migration-fail/
Great article. Thank you! Is there a way to enable interoperability or public folder coexistance?
This is great, but…I have a very small organization with only a handful of public folders (contacts and calendars). I exported them all to a PST as a backup before the migration. Is there a reason I wouldn’t manually create a public folder mailbox on the old server, connect to it with Outlook, then drag/drop the folders from my backup PST? Your process seems cumbersome for such a small number of folders.
Apologies, the third sentence should have read “Is there a reason I wouldn’t manually create a public folder mailbox on the NEW server”.
Hey Dave,
You can certainly do it that way. Keep in mind that a PST export/import will not retain any folder permissions or mail-enabled settings. So you will need to recreate those on the 2016 side.
You will also need to shut down 2010 from serving the old hierarchy when you are ready to do a final export to PST. Otherwise you might get a divergence in what is exported and what is on 2010 if users keep adding to Public Folders after you have exported. This command locks your users out of 2010. Also, be sure all your users own mailboxes are on 2016 before you do any of this.
Set-OrganizationConfig -PublicFoldersLockedForMigration:$true
Once all your users and public folders have been moved to 2016 you will need to run this on the 2010 side.
Set-OrganizationConfig -PublicFolderMigrationComplete:$true
Be sure to verify with Outlook through the Connection Status dialog that they are connecting to 2016 (and not 2010) for public folders before you decommission 2010.
You may want to double check the two above commands. It’s been a while since I did a PST Public Folder migration and I am going off memory. 🙂
What is the limitation of a PST migration of Public Folders. We currently have 20GBs of Public folders that we want to migrate over to Office 365. Do I need to worry about the auto-splitting or is it safe to move PF under 50 GBs through a PST migration?
Hey Kash,
If you only have 20 GB of public folders it should be okay to put into one public folder mailbox. However, how many users, servers and locations do you have in your environment? If you have a lot of client/user connections to your public folders it may by necessary to split the data between mailboxes/databases.
Thanks for the quick reply Gareth.
The client only has 12 users and one location which shouldn’t create too much of a load.
Yea, one public folder mailbox is more than enough.
Thanks for the great article, i am trying to follow it to move a very small PF structure over to a new Exch2016 server but i get the following message when i get to step 3……
MapiExceptionLogonFailed: Unable to make connection to the server. (hr=0x80040111, ec=-2147221231)
Any ideas?
I found out the solution to my own problem, it turns out i already removed and deleted all my mailbox databases from the old 2010 server, and apparently a mailbox db is still necessary on the 2010 server to perform this migration. I created a new empty mailbox Db on the 2010 server and then the command proceeded properly.
thanks!
Hey Andy. That will definitely do it. It needs to talk to a System Mailbox on the source server during the move process. Creating a temporary new DB on 2010 will fix it as you stated.
Great article, but I am running into a problem where I see the Public Folders listed in the EAC, permissions look fine, but I cannot see them in OWA or Outlook. I have not encountered any errors or issues along the way. Help!
Update – Was able to access the Public Folders from a machine running Outlook 2013. I was also able to figure out how you now have to access Public Folders from OWA. So, both of those are working. There seems to be a bug or something with Outlook 2016 where it cannot see the Public Folders on my Exchange 2016 server. My Outlook shows that it is fully updated. I’ll keep scouring to see if anyone has a fix/workaround for this.
Hmm. Haven’t seen this issue myself. What Exchange 2016 CU are you on? Let me know what you find.
F** this is the first comment i found in the internet telling the situation i’m facing and it is from 5 years ago and left without answer 🙁
Maybe anyone has face the same issue ? Migration not finalized i’m at step 8, when you have to do Set-Mailbox -Identity -DefaultPublicFolderMailbox .
I can see the public folder tree on EAC, and on OWA, but can’t see them on Outlook 2016 and Outlook 365.
Hey San,
When you say “migration not finalized” do you mean that the Complete-MigrationBatch command was run and the migration batch is not showing as complete yet? If so, what do you see if you look at the migration report?
If it is complete, and you ran the Set-Mailbox command, how many mailboxes have you tried that on? Are all having the same experience where OWA works but Outlook does not? If so, make sure you aren’t facing any DNS issues and there are no entries in the HOSTS file. I also recommend testing with a regular user account and not anything that would have admin rights. Lastly, does a new Outlook profile make a difference (note that public folders can take a few minutes to show up after a new profile is created). Also, from Outlook try running the Autodiscover test. In the XML file see if Autodiscover has discovered and is trying to return public folders to the client. If not, could be an Autodiscover issue.
Hey Gareth,
Great article on the 2010 to 2016 PF migration. I have one question though that I can’t quite get clarification on.
I work for an IT provider that hosts, among other things, email for our clients. We have about 14,000 users split up between about a dozen clients. We separate PF’s into the individual clients and lock down with permissions, so “Client A” can’t see “Client B’s” folders, and so forth. All PF’s are on one PF DB.
My question is, after I migrate “Client A’s” mailboxes over, it looks like, with batch migration I can migrate only “Client A’s” public folders over to 2016. Once I do that, can I lock just “Client A’s” public folders without effecting “Client B”? It sounds like locking is done at the Org level. Am I correct?
I need to keep this process as separate as possible. Thereby saying “Client A” is completely migrated over. Now on to “Client B” and so forth, and would rather not wait until all clients mailbox have been migrated over to start PF migration.
Hope this makes sense.
Russ
Great article!
I have one issues with permissions. Seems like when I moved my PF’s from 2010 to 1016, the permissions that allow all users to view the structure has not moved over. The subfolders look good. Top level/root have none. Is there a way to set permissions for all users to view the structure?
Looks like it took some time. I went back into the test user and the public folders appeared after about 15-20 minutes after the migration.
Also, need to migrate user mailboxes first before public folders! Ran into issues.
Hey Tom,
So the permissions are working now correct?
Correct, mailboxes on Exchange 2010 will not understand how to access modern public folders on 2013/2016. Always move mailboxes first.
Really great article! Very useful for my migration to Exchange 2016. Thanks for that.
But I get one problem. I can’t remove the Public Folder from Exchange 2010. I get this error: the public folder database contains folder replicas…
I checked the Public Folders and there are no replications anymore.
When I check Get-PublicFolderDatabase in PowerShell. The old Exchange 2010 server shows up:
Name Server
—- ——
Public Folders 2010 OLD-EXCHANGE-SERVER
Should it supposed to be empty?
Fixed, strange enough the Migration wasn’t finished
PublicFolderMigrationComplete : False
I’m pretty sure that I used: Set-OrganizationConfig -PublicFolderMigrationComplete:$true
But maybe on the wrong server…
Glad you got it working. Some of those commands can take some time to take effect and replicate throughout the organization (sometimes hours).
Hi, When starting the PF migration I get the following error.
Error: MigrationPermanentException: Cannot find a recipient that has mailbox GUID ’cfbbde32-590e-4891-baeb-326369de11c9’. –> Cannot find a recipient that has mailbox GUID ’cfbbde32-590e-4891-baeb-326369de11c9’.
Are you able to assist here? All articles on Internet say I need to stamp the mailbox before I can move it, thing is the PF isn’t a mailbox on 2010, its a database.
Thanks
Tony
Hey Tony. Under the EAC, navigate to Public Folders >> Public Folder Mailboxes. You may need to hit refresh. Are you seeing Public Folder Mailboxes created here? You should see as many as your map script output file contained.
Hi Gareth,
Thanks for the fast response. I see the Public Folder Mailbox created (Mailbox1) but no Public Folders created.
p.s. this time the error I got is
“The destination Active Directory forest isn’t up to date, which prevents the move from proceeding. Verify that Active Directory replication is working.” I know AD is up to date and replicating so its odd…
That’s an odd error to run into during a Public Folder move. I assume this is all within the same Active Directory Forest? Or are you doing a cross-forest migration? Found an a TechNet forum answer where someone reported that a teamed NIC on the Exchange server was causing the error.
I have checked and Domain FL is 2008 and Forest FL is 2003, so shouldnt be a problem.
There is only 1 NIC on the 2010 and 2013 servers.
I may have to speak to our friends at Microsoft!
Let us know what you find from Microsoft.
The other option is going through the roll back instructions and trying again as you are not that deep into the weeds yet.
To confirm, this is 2010 to 2013 migration? No 2016 in the environment. Just thought I’d confirm as 2016 requires forest functional to be 2008.
So running into an issue, when trying to complete the migrationbatch it says the public folders are not locked for migration, but the flag is set to True. I’ve not been able to get past this, by comparing articles some use new-publicfoldermigrationbatch compared to new-migrationbatch so not sure why those commands would not interchange.
Hey Joe. Great question. So the attribute will show as true immediately after you set it. It can take quite some time for that change to truly propagate through your environment. Give it a minimum of 15 minutes but know it could easily take 1 hour for that change to be apparent before the next command works. Try to complete the batch after an hour and it should go.
Good article(s) Gareth. Obviously you are aware of the new CU’s for both products now. Not sure if that changes anything, I doubt it. I read somewhere that you should only migrate your public folders off of Ex 10 after all of the mailboxes are moved off to the 2016 server , am I correct?
Hey Steve. Great question. Yes you want to make sure you move all users to 2016 (or 2013) first. Old legacy mailboxes on 2010 can not connect to modern public folders.
Correct. As of 2013 CU7 this is the preferred migration method.