If any of these ESU key not found, then report as non-compliant. Note: The PowerShell script that I have used in the baseline will check if the device activated with 1 year or 2 year or 3 year ESU key and report as compliant. You will need to do this task twice because there are 2 baseline files available 1) for windows 7 and 2) for server 2008/R2. Go to your configuration manager, configuration baseline, right-click, and import configuration data. After you download, you need to extract it to get. This is a ZIP file which contains 2 baseline policies. Download the configuration baseline file ( SCCM Baseline for ESU Activation.zip) from Github. You can use this guide to create the collections.Ģ. Create a collection for all windows 7 and windows server 2008/R2. I am not doing step by step guide in this post on how to create the compliance item and compliance baseline then deploy to the collection but I will give you the steps and also the exported baseline configuration for you to import the settings into your configuration manager and deploy it.ġ. What other options do we have without bloating the database? A simple and easier method is compliance settings. The above command will generate a lot of data that is not required for us. Get-WmiObject -query "select * from softwarelicensingproduct" I DO NOT recommended option 1) because SoftwareLicensingProduct class contains a lot of data that will be collected from all devices along with activation information which will bloat your database.Ī simple example is, on your Windows 7, open PowerShell command and run the following syntax to see the data that is available in SoftwareLicensingProduct ![]() ![]() So to check the activation status, we can use 1) Enable the Software_licensing_product in client inventory settings (hardware inventory) 2) Use compliance settings to detect the ESU activation status and 3) script If you know where does the ESU information stored in WMI, it would be easier for us to use configuration manager to gather data for further analysis.īy default, SCCM clients do not send the information about this class SoftwareLicensingProduct hence if you try to create a collection or query database using this class, you get empty results. If you have installed the ESU key on the windows device, the information gets stored in WMI class called ‘ SoftwareLicensingProduct’ This monitoring will help you take action on the missing ESU devices to avoid the possible threats. In this blog post, we will see how to check the activation status of ESU on windows 7 and server 2008/R2. ![]() There are multiple posts on the internet on how to install ESU. For more information about how to purchase the ESU, refer to this blog.Īfter you have purchased the ESU, you can install and activate window 7 or server 2008/R2 devices using Configuration Manager task sequence or scripting or by other means. Please remember to mark the replies as answers if they help and unmark them if they provide no help.As you already know that, Windows 7 and windows server 2008/R2 has reached their end of support lifecycle on January 14, 2020, however you can purchase the extended security updates (ESU) for windows 7 and server 2008/R2 through volume licensing to make sure these devices are protected. ![]() If there is anything else regarding this issue, please feel free to post back. $null = $KMSservice.RefreshLicenseStatus()Īuto-activate a non-domain joined Windows OS using Powershell and a domain KMS host $null = $KMSservice.InstallProductKey($key) $KMSservice = Get-WMIObject -query "select * from SoftwareLicensingService" The script below can install the appropriate KMS client key for the detected OS: $OSversion = (Get-WmiObject -class Win32_OperatingSystem).Caption If you want to activate Windows via powershell script, please check the WMI class SoftwareLicensingService. Please note you can also use the cmd "slmgr" in Windows Powershell.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |