Otherwise, see this article for more information. This tool can be downloaded from Microsoft and upgraded in-place, in many instances.
The main thing you should do here is identify what you have now, what you are moving to, and where everything is going to live at the end of the day.Īzure Active Directory Connect: If you still have DirSync, you’ll need to upgrade it to Azure AD Connect. Before you begin: Prepare for the Upgrade Several of my clients have opted to move toward this configuration, until Microsoft figures out a way to get rid of Exchange servers on-prem for good, while still keeping Directory Synchronization (or maybe we’ll just move AD/DNS to the cloud too…). But guess what? It doesn’t need to do much–it’s basically just a management UI, and it can be installed onto any member server, or it can even be added to a Domain Controller (note: technically supported, but not necessarily recommended). I know, I know–that means you still need to keep an Exchange server around. Upgrade your legacy Exchange server to Exchange 2016. If that isn’t going to work for you, I have one more solution to offer:
HOW TO UPGRADE OFFICE 2010 TO 2016 PASSWORD
If all you care about is password sync, and you have less than 100 users in your organization, you might consider switching to the Windows Server Essentials Experience password synchronization feature, instead. So what are we to do? You have two choices. Other organizations want to keep Azure AD Connect for enabling true Single sign-on (SSO), pairing it with Active Directory Federated Services (ADFS). Because Azure AD Connect comes with so many cool features! For example, most SMB’s don’t want to lose the ability to synchronize local AD passwords and enable self-service password resets. Microsoft’s official stance regarding hybrid is this: If you remove the last legacy Exchange server from your domain in a hybrid environment, then you should also remove Azure Active Directory Connect (your ability to synchronize passwords to the cloud). You should verify that Office 2016 works fine on a new machine, so you can keep that as a final fallback for any machines that just fall apart with the update.One of the most common frustrations I hear from readers and clients alike is the requirement for keeping a hybrid Exchange server around, even well after all of your mailboxes have been moved to the cloud. And the reconfigures - as Office 2016 has to rebuild its licensing - are probably unavoidable.
MS just doesn't handle updating the executable without the installer also reconfiguring a bunch of other things along the way. It's also been observed that deleting the whole HKCU\Software\Microsoft\Office\15.0 (or 14.0) section in the desktop registry might help.īut we don't have a good, bulletproof way to make that major an Office upgrade. So if there's an equivalent Profiles\Outlook key under Office\14.0, deleting that might keep Outlook from panicking and uninstalling itself. HKCU\Software\Microsoft\Office\15.0\Outlook\Profiles\Outlook We had an old forum thread specifically about the Outlook uninstall problem when upgrading from 2013 to 2016, and it said to delete everything under this registry key in the desktop before switching layers: You can have Lync 2010, but it needs to be combined in the Office 2016 layer now. Are you sure there are no other Office 2010 components in any other layers? Office bits all need to be in the same layer together, so if you have a separate Lync 2010 layer, it can absolutely be causing problems with Office 2016. It's a possible problem for any software, but it's particularly difficult with Office.
HOW TO UPGRADE OFFICE 2010 TO 2016 SOFTWARE
The problem is that Office leaves a lot of stuff lying around which terribly confuses the new Office when the updated software wakes up in a substantially non-upgraded desktop.
That way the upgrader finds all the local 2010 stuff and handles the upgrade locally. Then switch the 2010 layer to the 2016 layer and check the Reinstall box.
Probably the safest (and most labor-intensive) way to do this is to upgrade 2010 to 2016 directly in the desktop. You can't just uninstall Office 2010, because that uninstall is remembered on the desktop and will conflict with some parts of Office 2016 trying to install.