I do yearly Microsoft audits and need to know on any given computer if Visio 2013 or Project 2013 was activated by a MAK license or an MSDN license. Is there any way KACE1000 can pull this info and report back? I know this was able to be done in versions 2010 and below but I don't believe 2013 and up keep the activation key in the registry the same way, if at all. 
0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity


You can get the license status by running cscript ospp.vbs /dstatus. You can find ospp.vbs in the Office install folder but that will vary if you have a mixture of x86 and x64 machines in your environment. I would recommend using a script that detects the OS version and pipes the output of the file to a known location and pair that with a custom inventory rule to pull that into the inventory database.

While having the data in KACE is nice you might also want to look at the Volume Activation Management Tool. You can use it to query machines for both their Windows and Office activation keys and also change them if needed.

Answered 10/30/2015 by: chucksteel
Red Belt

  • Hey Chuck, I know this is an old post but am trying to check licenses on about a dozen win 7 devices and when attempting to run the script you suggest above, i get a runtime error. can you go into a little more detail on how to run this down, as i am a newbie to scripting and am sure i did something wrong. Thanks!
    • Do you get an error just running the script manually in a command prompt? What version of Office and Windows?
      • If i run it in command prompt as admin, i did get the same error. I then drilled down to the exact folder location for the ospp vbs and it ran correctly. Just my silly error not checking that.
        It does only show the last 5 digits of the key, is that normal?
        Also, if I do the same thing in the script and run it, i get a compilation error, not a runtime error.
        I am running windows 7 pro 64 bit with office 2013 h&b
      • I have only used this method with Office Professional Plus, so I'm not sure if there are differences there that might cause the problem.
Please log in to comment