![]() ![]() To Disable Activation UI, write the registry key: “DisableActivationUI”, value: “1” (DWORD) to “HKLM\Software\Microsoft\Office\16.0\Common\Licensing” path or “HKLM\Software\Wow6432Node\Microsoft\Office\16.0\Common\Licensing” if you are installing 32bit Office on 64bit Windows.Now that the license is installed we still need to suppress those popups… Here are some of the registry edits suggested in the tweet: Open an elevated PowerShell window, change your directory to the Office installation folder.Ĭlick to enlarge: If your 5-days runs out, then you can run a command to get another 5-days.This can be done using the following steps: ![]() First we need to load the new license after Office has been installed. So, let’s use the information from the tweet to see if we can use Office with automation. …and if you tried to script the virtual user to escape these popups, you finally get to the application, in a very locked down form that you can’t do anything with.Ĭlick to enlarge: Scripting the Virtual User only gives you a locked-down version If I’m using automation this is already trouble.Ĭlick to enlarge: Popups appear when the application fires up, as the user has not activated yet After it deploys, it’s ready to use for the most part, except that if you try to use an Office application, you’re very limited.įirst, when the application fires up, you get a lot of popups because the user has not activated yet. I’ve just setup a new instance in Azure and have chosen the “Windows 10 Enterprise multi-session, Version 2004 Microsoft 365 Apps” image. ![]() I thought I’d give it a try on a new system… so follow along and see how it works… It has just about everything you need to enable a machine to do the testing you need – a license key, a way to inject that license key, and some helpful registry edits to suppress popups that get in the way of automation. It’s also been the biggest driver of load on a system when using Login VSI or Login Enterprise.Ĭlick to enlarge: Pieter Wigleven Tweeted a license key for Microsoft 365 Apps In my latest WVD testing I am using a set of users that were already registered, but we aren’t all that lucky and have a real need to test with 365 Apps because it is what a majority of production enterprise users use on a daily basis. It can be pretty costly to license non-production users for the purposes of testing and in the past there were volume keys from MSDN that could be used to enable larger scale testing that uses Microsoft Office products This is great news for our customers because this happens to be one of the most requested help topics from them. (NOTE: when we tested this new key, it only gave us 5 days to start, but you have an option to run a ‘rearm’ 1 time). It enables a 10-day subscription on machines that you might want to perform some automated testing on. One of our favorite WVD product managers at Microsoft posted a license key for Microsoft 365 Apps (formerly called Microsoft Office 365). I don’t know if you noticed the BIG news in a little tweet a couple weeks ago, but we certainly did here at Login VSI. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |