![]() ![]() So my plan is to move all mailboxes+public folder to Exchange 2013 and take over the Windows NLB IP to the new hardware load balancer when we decommission the Exchange 2007. ![]() According to Microsoft, procedure to import 2007 PST to 2016 is the same than if importing 20 PST files: Screenshot from Import email, contacts, and calendar from an Outlook. If automatic updates are paused or disabled, you'll have the. In the navigation pane, click 'Office Account.' 3. My question: do you foresee any issue if we still not touch Windows NLB at Exchange 2007 and use the new hardware load balancer on Exchange 2013? Importing an Outlook 2007 PST file to Outlook 2016 which is the current Outlook / Office version used by O365 should go without issues. Open Microsoft Outlook and the click 'File.' 2. Since the customer only has limited hardware, we will use half of the server that becomes Exchange 2016 as an interim solution to host Exchange 2013 and we need to replace Windows NLB with the hardware load balancer. This Exchange 2007 (CCR+SCR to DR) is using Windows 2003 with Microsoft NLB and I know both already EOL, but we still need to migrate them to Exchange 2016/2019 on-premise. So we need to move all mailboxes to Exchange 2013 (all exchange roles on the same box) then another move to Exchange 2016/2019 (all exchange roles on the same box). As my understanding there no direct path to migrate Exchange 2007 to the newer version Exchange 2016/2019 without any paid tools.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |