/build/static/layout/Breadcrumb_cap_w.png

Systems Management Question


KACE SMA - Windows 7 Extended Security Updates (ESU) MAK Deployment

03/05/2020 355 views

Hi All,  

We are tasked with deploying over 1,000 Win 7 ESU MAK Licenses within our organization.  So far the deployment has been smooth but we are finding the occasional client PC that does not have the new MAK Lic installed.  

At this point, we are looking for a way to determine exactly how many Win Devices have the new MAK applied.  Does anyone know how to search or report using the KACE SMA against the MAK Lic File that the Windows command  slmgr /dlv  provides?  THE Windows Script Host provides Information such as Name:  Windows(R) 7, Client-ESU-Year1 add-on-for, Description, Activation ID, Extended PID, partial product Key, etc.  

Thank you!


Answer Summary:
5 Comments   [ + ] Show comments

Comments

  • Thanks for your reply. I took your advice and was able to create a Custom Inventory Rule as you suggested by doing the following:

    1. Go to Inventory | Software |New
    2. Fill out all fields.
    3. Under Custom Inventory Rule enter the following:

    shellcommandtextreturn(c:\windows\system32\cscript c:\windows\System32\slmgr.vbs /dli)

    I now have this applied to 635 of my Win 7 machines! Although I didn't expect this to run on all devices since I did not Assign a Label and there is no field to add specific devices. I would be curious to see what your experience was in regards to deployment. I was hoping to only deploy this to a specific group of devices but maybe that's not an option with the Custom Inventory Rule?
  • CIR are not label related.
    They use a standard functionality for inventory.
    By default during inventory all software is checked and counted:
    Since you built a CIR for a "FAKE" Software it is handling it as it were a real software and runs it on all "supported" OS. Sometimes it makes sense to limit the software item to OS but usually it is not nessesary)
  • Ok, thanks for that info. We did limit the software to Win 7 only and that seemed to work. Any advice for reporting against the Partial Product key that is now reporting under the Custom inventory Field? Thanks again for your help with this!
  • if you open the reporting wizard you have now a field with the name of your CIR, so you simply can do a report with the filter "CIR FIELD" "containts" "your serial"
  • Works great!! Thanks again.

Answer Chosen by the Author

0

use a Custom Inventory Rule (or many in that case) which runs slmgr and greps the output for the nessesary info.

As an example I check if the system is licensed or not.

ShellCommandTextReturn(cmd /c c:\windows\system32\cscript.exe c:\windows\system32\slmgr.vbs -dlv|findstr status)
You can modify it for the output you want and then you can report against your CIRs
Answered 03/06/2020 by: Nico_K
Red Belt

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ