The Office KMS key you need is not listed in your licensing portal as a "host" key. To enable KMS with office, you remove any installed keys (in my case i had to remove my MAK keys) Office doesnt require a second key for KMS like your OS might. A direct link to the Office 2016 Pack can be found here: These can be found in the URL listed above for ADBA. The Office Volume License Pack needs to be installed on the server hosting volume activation services (Note: you dont actually need the VAMT tool, though it can be helpful) What ultimately solved our issue as a whole was deploying Volume Activation Services on a server, configuring it for Active Directory Based Activation (ADBA), and leveraging our KMS keys. SDK documentation and download i believe can be found here: These changes require the installation of Citrix SDK on a machine in the environment. If you're going to proceed with MAK keys on the OS, there are a few tweaks you may need to make outlined in this article: So if you're going to auto-activate Office, you're going to need a KMS deployment. While it may work for the OS, it definitely did not work for our Office deployment. MAK - I didnt get to fully test this on the OS. So i think we finally have things working. I'll post the final solution in a few because there were some additional details that might be a bit confusing for others. So i kind of shifted gears into setting up the ADBA deployment with KMS. I may have had some luck on the OS side but i wasnt able to continue testing because i finally was able to locate our KMS host keys with the help of MS support. MAK does not appear to work for Office activations. In any event, it appears MCS handles the cloning process a bit differently. All subsequent clones when provisioned through PVS were activated. Office on the other hand continued to work fine with a MAK license activated on the gold image. Post windows 10, we definitely needed KMS for the OS. But that could also have to do with how Microsoft handled their licensing. I can only speak from personal experience, but prior to Windows 10 we didnt need to leverage KMS for activations with PVS (Windows XP or Windows 7). We have always needed KMS or ADBA to handle your scenario I doubt Citrix did any work with MAK and Office - likely just windows. But it doesnt mention Office i dont think. So is ADBA and KMS the only way to now license both windows and office installations deployed with Citrix? There's no way to utilize MAK for both Windows and Office with a non-persistent DaaS MCS deployed VM? The article above mentions a possible registry adjustment for windows activation, i havent tested this yet. After the non-persistent desktops rebooted, they just went back to their default unlicensed state. It doesnt appear to be able to utilize MAK keys.Ĭan confirm. How will this work for non-persistent desktops? Even if i activate a device in the database, once it reboots, wont it just forget everything i just did?ĪDBA looks like it requires the KMS host key which im still trying to locate. I recently tried installing VAMT as an attempt to manage both windows and office activations but the thought occured to me. Have been having quite a time with this one trying to locate our KMS "host" keys.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |