craigcamacho Posted October 28, 2016 Posted October 28, 2016 Hi Guys, Over the past couple of weeks I've been preparing to deploy Office 2016 and everything seems to be going ok except one little thing that is niggling away at me although it might be something and nothing. I have added the KMS key for Office 2016 from our agreement into VAMT 3.1 on our server which is running Server 2012 R2 and everything seemed fine when adding it. When I deploy Office 2016 to a bunch of machines initially when you launch one of the apps it comes up saying it isn't activated but then after a while it appears to talk to the KMS server and activates which is what I would expect it to do. However when I look in VAMT 3.1 under the Office products I can see all my clients in there and under "License Status" they all say "Licensed" however under "Genuine Status" they all seem to say "Not Available". Is this something I should be worried about or will it auto correct itself? 1
FN-GM Posted October 28, 2016 Posted October 28, 2016 (edited) Im confused why you would use VMAT if you have a KMS server? What is the output for Office 16 when you run cscript slmgr.vbs /dlv all on the KMS server? Also before you deployed your image did you rearm office? This is like a mini sysprep specifically for office activation. Edited October 28, 2016 by FN-GM
craigcamacho Posted October 28, 2016 Author Posted October 28, 2016 I'm new to licensing so am trying to get my head round how it "should" be done. When I run that cmd on the server I get the below followed by all my products each of which list licensed with a large number next to it and unlicensed with 0 next to it. Like I say I'm new to this and trying to figure out how licensing\KMS\MAK works and the best practices. Would you say that for KMS I can just add it in from cmd line using slmgr and that VAMT would only be used with MAK keys so you can keep track of remaining seats etc? This license is not in use. License Status: Unlicensed Remaining Windows rearm count: 998 Remaining SKU rearm count: -1 Trusted time: 28/10/2016 12:46:53 Key Management Service is enabled on this machine Current count: 50 Listening on Port: 1688 DNS publishing enabled KMS priority: Normal Key Management Service cumulative requests received from clients Total requests received: 17214 Failed requests received: 759 Requests with License Status Unlicensed: 0 Requests with License Status Licensed: 14421 Requests with License Status Initial grace period: 2007 Requests with License Status License expired or Hardware out of tolerance: 1 2 Requests with License Status Non-genuine grace period: 0 Requests with License Status Notification: 15
FN-GM Posted October 28, 2016 Posted October 28, 2016 It looks like the KMS key has been installed on the KMS but not activated. What OS is this on? Server 2012 R2 and 2016 have a GUI wizard you can use to activate it. VMAT is for MAK really yes. With KMS you set it up and the machines automatically activate.
3s-gtech Posted October 28, 2016 Posted October 28, 2016 VAMT is very handy with a KMS server, as it lets you check on the status of clients, push KMS keys to clients that may be on MAK (and vice-versa for some machines where they won't activate via KMS due to invalid SLIC tables) and also give clients a prod when they're being slow activating. I don't use ours often, but it can be very handy when doing large deployments. 1
craigcamacho Posted October 28, 2016 Author Posted October 28, 2016 My server is running Server 2012 R2. How do I launch the GUI? I installed the KMS host using the kms_host.vbs script at which point it launched a GUI where I entered my information. Is this the GUI you mean?
FN-GM Posted October 28, 2016 Posted October 28, 2016 If you search on the start screen for "Volume Activation Tools" thats the one you need. On the activation type select KMS and enter your KMS server name.
craigcamacho Posted October 28, 2016 Author Posted October 28, 2016 Ah yes I've launched that before and been through that process of putting my KMS key and activating it. When I re run it now and put my KMS key the activation bit is greyed out which I'm assuming is because I already activated it. The thing is I've deployed Office 2016 and they all say activated when I check so can I assume they are going to stay this way? If I had installed my KMS key using the GUI you mentioned or via Slmgr from cmd line I wouldn't have known about the "Genuine Status" column issue in VAMT. Is VAMT perhaps giving me this message because I've used a KMS key and this message is normal?
HendersonsRelish Posted March 16, 2017 Posted March 16, 2017 Folks This thread answers info about KMS and MAK Doesn't really answer the genuine status question. Any further thoughts / knowledge on this? Hendos
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now