![office 2016 vs office 365 windows 10 vm office 2016 vs office 365 windows 10 vm](https://www.codetwo.com/admins-blog/wp-content/uploads/2016/07/Hyper-V_01.png)
![office 2016 vs office 365 windows 10 vm office 2016 vs office 365 windows 10 vm](https://i.ytimg.com/vi/eb8JXKmT1fY/maxresdefault.jpg)
The user can then click Ok and continue to use Office applications without further prompts or any notification that the product is not activated until they sign in and are placed on a different RD Session Host server. To continue using this product, please sign in with your Office 365 account. "Sorry, we cannot verify the license currently installed for this product. However, when a user logs in to RDS, if they are put on a different RD Session Host server than the last one they were sign in to then they receive the following prompt when opening an Office application. Users are able to sign in to activate Office without any issues.
#Office 2016 vs office 365 windows 10 vm password#
Our Office 365 tenancy is setup with Azure AD Connect with password hash sync. I have also tried the Current version 16.7070.2033 32-bit and the same behaviour persists. I've recently updated the RD Session Hosts to Office 365 ProPlus 2016 from Office ProPlus 2013 using the Office Deployment Tool C2R with the option SharedComputerLicensing set to 1 and I have confirmed that this is definitely set in the registry. User Profile Disks are used for the profiles with no exceptions, which means the users entire profile follows them when they get load balanced to different servers as they sign in. I have a Windows Server 2012 R2 Remote Desktop Services environment with 4 RD Session Hosts.