VAMT 3.0

[Joanne]

OH EM GEE...

 

Right I've got me a Server 2012 R2. Activated with KMS Server and Windows 10 key thing. KMS seems to be working, getting hits when I run slmgr /dlv

 

ok, so I want to see MOAR INFORMATION! So I install VAMT.

 

It wants an SQL database. So I install SQL server express. That wants .net framework, so I'm just installing that now.

 

Is this right? It doesn't feel right. ARGH .net framework feature keeps failing too!!

[sted]

OH EM GEE...

 

Right I've got me a Server 2012 R2. Activated with KMS Server and Windows 10 key thing. KMS seems to be working, getting hits when I run slmgr /dlv

 

ok, so I want to see MOAR INFORMATION! So I install VAMT.

 

It wants an SQL database. So I install SQL server express. That wants .net framework, so I'm just installing that now.

 

Is this right? It doesn't feel right. ARGH .net framework feature keeps failing too!!

 

yes but my experience is that the sql install fails about 2/3 of the time if its on a dc i just use scripts usually depends how much info you want/need

 

cscript.exe C:\Windows\System32\slmgr.vbs /dlv > "c:\Users\me\Desktop\kms.txt"

 

& office 2013

 

cscript.exe C:\Windows\System32\slmgr.vbs /dlv 2E28138A-847F-42BC-9752-61B03FFF33CD > "c:\Users\me\Desktop\kms office2013.txt"

[timbo343]

I prefer to use the command line stuff instead of VAMT. So much simplar to use and dont have to install a database

[Joanne]

Cool. So I get this:

Name: Windows®, ServerStandard edition

Description: Windows® Operating System, VOLUME_KMS_2012-R2_WIN10 channel

Activation ID: 20e938bb-df44-45ee-bde1-4e4fe7477f37

Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f

Extended PID: 06401-00206-405-338768-03-2057-9600.0000-0812016

Product Key Channel: Volume:CSVLK

Installation ID: 019854899471652030147965845070885461688670513084489836

Use License URL: https://activation-v2.sls.microsoft.com/SLActivateProduct/SLActivateProduct.asmx?configextension=Retail

Validation URL: https://validation-v2.sls.microsoft.com/SLWGA/slwga.asmx

Partial Product Key: K6CYM

License Status: Licensed

Remaining Windows rearm count: 1000

Remaining SKU rearm count: 1001

Trusted time: 30/03/2016 13:43:25

 

Key Management Service is enabled on this machine

Current count: 3

Listening on Port: 1688

DNS publishing enabled

KMS priority: Normal

 

Key Management Service cumulative requests received from clients

Total requests received: 1025

Failed requests received: 191

Requests with License Status Unlicensed: 0

Requests with License Status Licensed: 21

Requests with License Status Initial grace period: 276

Requests with License Status License expired or Hardware out of tolerance: 0

Requests with License Status Non-genuine grace period: 0

Requests with License Status Notification: 537

 

Which is good... then I'm assuming I need more hits for the office to start activating?

 

Name: Office 16, Office16KMSHostVL_KMS_Host edition

Description: Office 16, VOLUME_KMS channel

Activation ID: 98ebfe73-2084-4c97-932c-c0cd1643bea7

Application ID: 0ff1ce15-a989-479d-af46-f275c6370663

Extended PID:

Product Key Channel:

Installation ID:

Use License URL: https://activation.sls.microsoft.com/SLActivateProduct/SLActivateProduct.asmx?configextension=o14

Validation URL: http://go.microsoft.com/fwlink/?LinkID=187557

This license is not in use.

License Status: Unlicensed

Remaining App rearm count: -1

Remaining SKU rearm count: -1

Trusted time: 30/03/2016 13:43:31

[sted]

windows yes you need 25 before it does much. Office 2013 probably i seem to remember -1 meaning it wasnt working but i could be mistaken (it might just mean nothing has tried to activate yet)

for reference heres what my server says now you are missing a bunch of stuff from the bottom. (you have to install a specific program for office 2013 to activate and it looks odd and asks some badly worded questions

 

Software licensing service version: 6.2.9200.16693

 

Name: Office 15, OfficeKMSHostVL_KMS_Host edition

Description: Office 15, VOLUME_KMS channel

Activation ID: 2e28138a-847f-42bc-9752-61b03fff33cd

Application ID: 0ff1ce15-a989-479d-af46-f275c6370663

Extended PID:

Installation ID:

Use License URL: https://activation.sls.microsoft.com/SLActivateProduct/SLActivateProduct.asmx?configextension=o14

Validation URL: http://go.microsoft.com/fwlink/?LinkID=187557

Partial Product Key: keyab

License Status: Licensed

Remaining Windows rearm count: 1000

Trusted time: 30/03/2016 13:44:27

 

Key Management Service is enabled on this machine

Current count: 10

Listening on Port: 1688

DNS publishing enabled

KMS priority: Normal

 

Key Management Service cumulative requests received from clients

Total requests received: 223

Failed requests received: 0

Requests with License Status Unlicensed: 0

Requests with License Status Licensed: 136

Requests with License Status Initial grace period: 61

Requests with License Status License expired or Hardware out of tolerance: 1

Requests with License Status Non-genuine grace period: 0

Requests with License Status Notification: 25

 

[Joanne]

Right. I've got 2013 activating on my old KMS on a windows 7 VM. I always had to run a script to get it to activate though!

 

I'll look into the -1. Importing the key with the 2016 tool all seemed WRONG. But might be that I'm just used to command line importing and then it says successful! I installed the VA role on the server so it does it all through that.

[timbo343]

Just a note, we had to rearm 25 machines as we pushed out the same image via ghost which didn't generate different installation IDs. We are hoping this year is going to be different... fingers crossed.

[Joanne]

My image should be golden, sysprepped through WDS and all that.

[timbo343]

My image should be golden, sysprepped through WDS and all that.

 

, you should be ok. We syspreped the original image, took an image via ghost and deployed it and it did nothing but complain. I wonder if WDS/MDT is slightly different.

[sted]

, you should be ok. We syspreped the original image, took an image via ghost and deployed it and it did nothing but complain. I wonder if WDS/MDT is slightly different.

 

did you have office as part of the base image if so did you rearm that before sysprep as its a separate command to rearming windows?

[timbo343]

Narh, we didnt though we have changed things this year to do this .

[sted]

you want this download run it and do what it says https://www.microsoft.com/en-us/download/details.aspx?id=35584 though the link on there appears borked