Updating changes to exchange2016
See here for more information: Check that your clients are supported.Windows clients need Outlook 2010 with KB2965295, Outlook 2013 or Outlook 2016.
This command needs to be run on a single line and run from a Power Shell window with elevated privileges.Have a read and make sure that you meet these requirements. This ensures that you have enough RAM, CPU and storage resources available for your server to perform correctly.Essentially, Exchange 2016 is sized the same as an Exchange 2013 multirole server but requires additional compute resources.In the next post, we’ll install an SSL certificate on Exchange 2016 and configure Exchange 2013 – 2016 coexistence which prepares us for the mailbox migration. Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Search for updating changes to exchange2016:
sadly it has no answer though I have come across same issue while doing migration to Exchange 2013 requiring to replace SSL cert on Exchange 2010 and configure OA to enable proxying through Exchange 2013.