Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Powershell Monitor to get Windows license/activation state

I try to deploy my first own Component Monitor. there I added the Windows Powershell Monitor and this script

        $ActivationStatus = Get-CimInstance SoftwareLicensingProduct -Filter "Name like 'Windows%'" | Where-Object { $_.PartialProductKey } | Select-Object LicenseStatus       

        $LicenseResult = switch($ActivationStatus.LicenseStatus){
          0	{"Unlicensed"}
          1	{"Licensed"}
          2	{"OOBGrace"}
          3	{"OOTGrace"}
          4	{"NonGenuineGrace"}
          5	{"Not Activated"}
          6	{"ExtendedGrace"}
          default {"unknown"}
        }
 $LicenseResult

I did not specify any other values.

The goal is to run this script on a node over the (passive) agent, get back the license status and get a warning if its not "Licensed". The script above works find when executed directly on a Win 2919 server.

The reason why I need Orion for that: RPC/WMI is blocked for most VLANs, so I need to find a way around that and want to use Orion for that.

I set a test server, Execution mode to locally and got this error: "Unable to schedule job on agent node 11 - required APM plugin is missing or not installed properly."

I googled that and found that net 4.8 is missing. If I'm not mistaken 4.8 is already installed on Windows server 2019? If not, I only need to install it on the Orion server?

So i changed the Execution Mode to Remote Host. The output is fine, but it tells me "Test failed with unknown status"

"COMPONENT TEST RESULT DETAILS

Output: ==============================================
Licensed"

But for that the Monitor tells me it uses wsman on port 5985, which i fear will be blocked also. Is there no way to run the script locally on the node to test?

So before I go on I would like to ask for help here, if my idea would even work and if I'm on the correct path. Maybe there is a easier solution or it will not ven work, maybe i need parameters ( i dont think so) or specify the output of the script (i dont know how).

I read the manual (Use case: Create a SAM template that uses the Windows PowerShell Monitor to detect possible dictionary attacks (solarwinds.com)), but it forks and forks until I really had no idea anymore.I guess there are examples of powershell monitors and I'm for sure not the only one who wants to get activation/license information from their servers, so I would be grateful if someone can put me in the right direction.

The next /much more complex) script (with several parameters as a result) would gather information about open Windows Updates. The script is already done, but since it also uses WIM/RPC i can't use it and must utilize Orion for it.

Find more posts tagged with

component monitor

PowerShell

Accepted answers

JoachimT

For everyone with the same problem, i post my finished script as well as a script skeleton that you can use to develop own scripts. I hope this helps the next seeker of wisdom

# This scripts gets Windows License and Activation status

$ErrorActionPreference = "silentlycontinue";
$ActivationNumber = 3 # if the command below fails, we set this variable to "critical". Otherwise the variable is later filled with the proper values (0 = ok, 1 = down, 2 = warning, 3 = critical)

 $ActivationStatus = Get-CimInstance SoftwareLicensingProduct -Filter "Name like 'Windows%'" | Where-Object { $_.PartialProductKey } | Select-Object LicenseStatus       
 $LicenseStatus = $ActivationStatus.LicenseStatus

        $LicenseResult = switch($LicenseStatus){
          0	{"Unlicensed"}
          1	{"Licensed"}
          2	{"OOBGrace"}
          3	{"OOTGrace"}
          4	{"NonGenuineGrace"}
          5	{"Not Activated"}
          6	{"ExtendedGrace"}
          default {"unknown"}
        }

        $ActivationNumber = switch($LicenseStatus){
          0	{3}
          1	{0}
          2	{2}
          3	{2}
          4	{3}
          5	{3}
          6	{2}
          default {3}     
        }   

 write-host "Message.ATSWindowsActivation: $LicenseResult"
 Write-Host "Statistic.ATSWindowsActivation: $ActivationNumber"
 Exit $ActivationNumber;

# Descritpion, what the script does

$ErrorActionPreference = "silentlycontinue";

CODE HERE

# Generate Message and Statistics here. These are necessary for every script!
Write-host "Message.UniqueMessageDescription: $MessageText"
Write-Host "Statistic.UniqueStatisticDescription: $Statistic Number" # this statistics you can check and set warning or critical

# Send the exit code for the script. 0 =ok, 1 = 1 down, 2 = 2 warning, 3 = 3 critical
Exit $ExitCoder;

After you have the script, choose any node for "Get Script Output" an no (or the correct) credentials. This generates the output the monitor needs to understand. Save and TEST. It should work now.

All comments

JoachimT

Since I read that to execute a script through the agent it must be set to "Execution Mode: Local Host" i tried again and now I did NOT get the "Unable to schedule job on agent node 11 - required APM plugin is missing or not installed properly." error I got before, but I got the

"Test failed with unknown status"

"COMPONENT TEST RESULT DETAILS

Output: ==============================================
Licensed"

So I just need to figure out how to pass the $LicenseResult (which is "Licensed" in the Test Result Details") to the monitor.

christopher.t.jones123

@JoachimT, for script monitors you need to define a Statistic at a minimum, this value must be an integer. That's probably why your script is returning "Test failed with unknown status" to ensure that what it is just add in a statistic. You can read these for more guidance

The Basics of PowerShell (part 1)

The Basics of PowerShell (part 2)

The Basics of PowerShell (part 3)

JoachimT

I followed your links (mostly 3) and i think i have all things necessary in the script and also get the correct output, but still got the "Test failed with unknown status".

What i missed: I did not choose a server for "Get Script Output" an no credentials.When i did that, the output was generated and the test afterwards worked.

So obviously you need to set a test server one time in "Get Script Output" to get the results and the monitor then reads them. This is a one time thing and I did not find any documentation about that, while it's the crucial step to make the output and test work.

 $ActivationStatus = Get-CimInstance SoftwareLicensingProduct -Filter "Name like 'Windows%'" | Where-Object { $_.PartialProductKey } | Select-Object LicenseStatus       
 $LicenseStatus = $ActivationStatus.LicenseStatus

        $LicenseResult = switch($LicenseStatus){
          0	{"Unlicensed"}
          1	{"Licensed"}
          2	{"OOBGrace"}
          3	{"OOTGrace"}
          4	{"NonGenuineGrace"}
          5	{"Not Activated"}
          6	{"ExtendedGrace"}
          default {"unknown"}
        }

        $ActivationNumber = switch($LicenseStatus){
          0	{"3"}
          1	{"0"}
          2	{"2"}
          3	{"2"}
          4	{"3"}
          5	{"3"}
          6	{"2"}
          default {"3"}     
        }   

 write-host "Message: $LicenseResult"
 Write-Host "Statistic: $LicenseStatus"
 Exit $ActivationNumber;

JoachimT

For everyone with the same problem, i post my finished script as well as a script skeleton that you can use to develop own scripts. I hope this helps the next seeker of wisdom

# This scripts gets Windows License and Activation status

$ErrorActionPreference = "silentlycontinue";
$ActivationNumber = 3 # if the command below fails, we set this variable to "critical". Otherwise the variable is later filled with the proper values (0 = ok, 1 = down, 2 = warning, 3 = critical)

 $ActivationStatus = Get-CimInstance SoftwareLicensingProduct -Filter "Name like 'Windows%'" | Where-Object { $_.PartialProductKey } | Select-Object LicenseStatus       
 $LicenseStatus = $ActivationStatus.LicenseStatus

        $LicenseResult = switch($LicenseStatus){
          0	{"Unlicensed"}
          1	{"Licensed"}
          2	{"OOBGrace"}
          3	{"OOTGrace"}
          4	{"NonGenuineGrace"}
          5	{"Not Activated"}
          6	{"ExtendedGrace"}
          default {"unknown"}
        }

        $ActivationNumber = switch($LicenseStatus){
          0	{3}
          1	{0}
          2	{2}
          3	{2}
          4	{3}
          5	{3}
          6	{2}
          default {3}     
        }   

 write-host "Message.ATSWindowsActivation: $LicenseResult"
 Write-Host "Statistic.ATSWindowsActivation: $ActivationNumber"
 Exit $ActivationNumber;

# Descritpion, what the script does

$ErrorActionPreference = "silentlycontinue";

CODE HERE

# Generate Message and Statistics here. These are necessary for every script!
Write-host "Message.UniqueMessageDescription: $MessageText"
Write-Host "Statistic.UniqueStatisticDescription: $Statistic Number" # this statistics you can check and set warning or critical

# Send the exit code for the script. 0 =ok, 1 = 1 down, 2 = 2 warning, 3 = 3 critical
Exit $ExitCoder;

After you have the script, choose any node for "Get Script Output" an no (or the correct) credentials. This generates the output the monitor needs to understand. Save and TEST. It should work now.