![]() ![]() And without a doubt the most obvious was not checked. However, I was just curious to check what features were enabled on the license SKU. I was informed that the users were assigned correct license with Microsoft 365 Business Premium that should support Multi-session WVD office version and Office Shared Computer Activation. ![]() My last assumption was check the licenses. The Host pools Virtual Machines was also also behind strict firewall rule set, so I also verified that it could talk to the Microsoft Activation URL on 443. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration And I could confirm this by looking into the Registry was applied with the correct settings: So all the settings should be correct regarding Shared activation. The Image was using “ 20h2-evd-o365pp-g2″ from the Azure gallery image. To start with the Troubleshooting this was the only error that occurred for end user trying to activate. ![]() I was recently involved in troubleshooting shared computer activation with Office on a WVD hostpool image using the latest 20h2-evd-o365pp-g2 image sku and Microsoft 365 Business Premium for Office. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |