VAMT\KMS Office 2016

[Firefox]

Anyone using the GUI of VAMT and managed to key the office 2016 key added?

 

I keep being told that the Key isn't valid and that I may need to upgrade VAMT - this is despite running on version 10.0.10240.0 (which I believe to be the latest)

 

I have run the Office 2016 Volume license pack, but unlike previous installs this never asked for the key to be added. So I ran the slmgr /ipk (office 2016 KMS key) and this came back as successful.

 

I have KB3058168 installed already, and I did find an article about moving a pkconfig file from this article to C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\VAMT3\pkconfig which I have also tried to no avail.

[Boredguy]

Have you downloaded the Office Professional Plus 2016 Key Management Service Host from the VLCS that upgrades the KMS host to support it?

[Firefox]

I believe I ran the correct kms_host script file. It did say it was successful, the eula from the download does say MICROSOFT OFFICE 2016 VOLUME LICENSE PACK

[Boredguy]

When you run the script that was in the download, it should have launched the VAMT tool for you to enter your KMS key

[Firefox]

It does indeed (although the screen looks very different to normal, I only normally get a small box to enter the key) I fill out the relevant details and it all appears to work. However I still cannot see\add the key into the VAMT gui

[Firefox]

 

This is where I'm trying to add the key

[bwilkerson]

[ATTACH=CONFIG]33011[/ATTACH]

 

 

 

This is where I'm trying to add the key

 

How funny I was trying to do the same thing today. I did discover a machine with Office 2016 and I tried to activated by installing a key and using the Automatically select a KMS client Key and that was successful because I installed the key to the server using the KMS host script.

 

If I try to activate against that key it says my count is insufficient so based on that I think it is working but the VAMT 3.1 just won't accept the Office 2016 KMS Key in the list of keys.

[glenharrison8]

Yep, I have the same problem

 

If I run slmgr.vbs /dlv all - then I can see Office 2016 VLK is licenced, but nothing is showing up in VAMT (version 10). When trying to add it, it says it's an invalid key

[Firefox]

Well I'm pleased to hear it's not just me it's not working for lol At least it appears to be working, just means I'll have to alter my documentation for other people to follow

[TheITGuy83]

Has anyone tried the following link?

I am having the same problems with Office 2016, I am trying this to see if it solves the issue. I shall let you know.

 

[sOLVED] When Using A Volume Activation Management Tool ( VAMT ) 3.1: The Specified KMS Product Key Is Invalid, Of Is Unsupported By This Version Of VAMT. An Update To Support Additional Products May Be Available Online. When Adding Windows 10 Produc

[TheITGuy83]

This did not work unfortunately. I am running VAMT version 10.1.10586.0

I have not yet tested this on a machine, but from what I see in this thread the KMS key is still installed and activated you just can't see it in the GUI.

 

 

 

Has anyone tried the following link?

I am having the same problems with Office 2016, I am trying this to see if it solves the issue. I shall let you know.

 

[sOLVED] When Using A Volume Activation Management Tool ( VAMT ) 3.1: The Specified KMS Product Key Is Invalid, Of Is Unsupported By This Version Of VAMT. An Update To Support Additional Products May Be Available Online. When Adding Windows 10 Produc

[perak]

Having the same issue here, did anyone manage to solve it yet?

[C3dy]

Hey there folks

 

Also having the same issue here.

 

I have tried to install the Office 2016 KMS Host via Script. After running the script and waiting several seconds, the volume activation assistant opens. First it asks me to wether use Active Directory Activation or choose a kms host. Active Directory is not an option for me, because i am running two 2008 r2 AD Servers and dont want to update anything ther yet. So I chose the option KMS host. I also don't have a KMS host, so I typed in the VAMT server itself and clicked next. It successfully accepts the kms host. In the next step ist wants me to install a KMS-Host key. I copied the Office 2016 key and clicked next, then an error message appears.

 

It tells me like: "An error occured, solve the error and repeat the step. Description: The software licensing service detected an invalid key"

 

I did search the internet yesterday for a few hours for finding a solution to solve this problem. Every Thread I found had some good advices, but at the end it run into nothingness...

 

Anybody having some more ideas yet?

 

Best regards,

 

C3dy

[3s-gtech]

Which Office 2016 key did you type? Unless it is specifically a KMS host key (which you have to apply for) it won't work.

[C3dy]

Has anyone tried the following link?

I am having the same problems with Office 2016, I am trying this to see if it solves the issue. I shall let you know.

 

[sOLVED] When Using A Volume Activation Management Tool ( VAMT ) 3.1: The Specified KMS Product Key Is Invalid, Of Is Unsupported By This Version Of VAMT. An Update To Support Additional Products May Be Available Online. When Adding Windows 10 Produc

 

Hey all together

 

I did actually type a MAK key, which should be right for VAMT.

 

Anyway, I could solve the problem with the solution above from ThelTGuy83. With Version 10, the key has been accepted without problems.

 

 

Thanx to everyone working that solution out.

 

 

:::Edit:::

 

Unfortunately, Windows and Office both loose the activation after a reboot... I have to activate it again. Is there a solution to this?

 

Thanx

Edited May 2, 2016 by C3dy

[3s-gtech]

Why are you putting a MAK key into your KMS? It needs to be a specified KMS key which MS generate on request for you. I'm amazed it took it, but not amazed that you're having further issues.

[ColinP]

Hi im using VAMT 10.0.10240.0

 

AD Based authentication seems to be working fine with our windows 10/office2016 machines, however im not able to add the key to a normal KMS type authentication for windows 7/office 2016 under keys?

 

I get the same error as the screen shot above.

 

Cheers

[C3dy]

Why are you putting a MAK key into your KMS? It needs to be a specified KMS key which MS generate on request for you. I'm amazed it took it, but not amazed that you're having further issues.

 

Hey 3s-gtech

 

Thats exactly the reason why I use the VAMT, because regarding Microsoft articles VAMT is used with MAK keys! I don't want to set up a KMS Host, though we don't have enough clients for this, that's why I want to use only MAK keys.

 

VAMT console took both, server 2012 r2 MAK and Office 2016 MAK key.

 

Activation is working fine, and Server 2012 r2 activate themselves after reboot. Only office wont automatically activate after reboot, but if I do it manually, it works.

 

I also noticed in our VLA Center, that counts of activations increase everytime I reboot the servers... Is this normal?

 

Thanks

[3s-gtech]

Not normal at all - the MAK keys should just go in and stick. Once activated once, that's it - it's not the same as KMS where they 'check in' frequently to carry on working. There are some oddities that can cause these issues, such as the permissions of the user which you're running KMS as - can you try activating it with a domain admin account if you're not doing so already?

[C3dy]

Hey 3s-gtech

 

Thanks for your reply.

 

I think the reason why the activations get lost is that we are using citrix provisioning services. Means that vDisks created with a master server are streamed to several targets. when rebooting the targets, the system looses all the settings and changes, except whats saved in user profiles.

 

We spoke to our citrix professional, still no solution there for this problem. We are thinking about getting rid off provisioning services.

 

Best regards

[LeMarchand]

I know this is an old 'un, but did anyone solve this? 2008 R2, VAMT 3.1 is activating Office 2016: I have a couple of clients that I want to swap to KMS activation but, because I cant input the key into the GUI, VAMT won't let me do it. I could track down the machines and do it manually, but if there's a solution that doesn't involve that...

[Firefox]

From memory you add this key via the toolkit, but it never actually appears in the VAMT gui. On our estate it does still license correctly, and from the gui when we do an update license status it does report correct

[LeMarchand]

From memory you add this key via the toolkit, but it never actually appears in the VAMT gui. On our estate it does still license correctly, and from the gui when we do an update license status it does report correct

 

It does, but unfortunately doesn't help if you want to change a key type.

 

I should probably learn how to do it in Powershell...

[LeMarchand]

I know this is an old 'un, but did anyone solve this? 2008 R2, VAMT 3.1 is activating Office 2016: I have a couple of clients that I want to swap to KMS activation but, because I cant input the key into the GUI, VAMT won't let me do it. I could track down the machines and do it manually, but if there's a solution that doesn't involve that...

 

Turns out it was as simple as downloading the most recent ADK and installing the VAMT component from it. it overwrote the existing installation but retained all data and allowed me to add the O2016 key and push it out to the clients that needed changing from MAK without leaving my desk.