It requires Exchange 2013 be on Cumulative Update 7 or later. ![]() Works with 2013: This process also works with migrations to Exchange 2013 (from 2007 SP3 RU15 or 2010 SP3 RU8). On a high level, it is the process of moving all data out of a database and into a special mailbox. This makes the migration process vastly different. And with that, all the benefits of Windows Failover Clustering. With Public Folders stored as a mailbox, that mailbox can now be part of a Database Availability Group (DAG). And hello are the new Public Folder Mailboxes. The old architecture is now known as Legacy Public Folders. This new architecture is referred to as Modern Public Folders. Plus, it is vastly different than any previous migration process.īeginning with Exchange 2013–and continued with 2016–public folders underwent a major architectural change. If you are not comfortable with PowerShell it may seem a bit overwhelming. So many scripts. So many PowerShell commands. If you are in the planning stages for migration from Exchange 2010 to Exchange 2016, then you have probably seen this TechNet article.
0 Comments
Leave a Reply. |