![]() ![]() ![]() ![]() Locking the public folders for final migration (this requires an outage, usually of at least an hour, but longer for very large environments).Starting the migration, and waiting for initial synchronization to complete.Creating public folder mailboxes in Exchange 2016 databases.Generating CSV files using the Microsoft scripts.Preparing the organization for public folder migration.To migrate legacy public folders from Exchange 2010, a procedure called a batch migration is performed. If you later have a need for public folders, you can create modern public folders in Exchange 2016 at that time. Keep in mind that if your organization has no need for legacy public folder data, you can simply remove your legacy public folders completely, instead of migrating them. If you are migrating legacy public folders from Exchange 2010, then the process is more complicated.If you are migrating modern public folders from Exchange 2013 to Exchange 2016, you can simply move the public folder mailboxes just as you would migrate any other mailbox.For an Exchange 2016 migration, the public folder migration options depend on which version of Exchange you’re migrating from: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |