New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


Querying the Registry VIA get-wmiobject

Votes:

0

Your Vote:

Up

Down

I have a local PoSh script scheduled task that queries a particular computer setting and either writes a "1" or a "0" to a custom registry key. I then have a PoSh script tied to a custom EXE/XML sensor that queries the registry via WMI. Files can not be shared between these two computers, but the WMI ports are open.

Script:
$regkey = 2147483650
$regclass = Get-WmiObject -Namespace "root\default" -list "StdRegProv" -computername "servername"
$key = "SOFTWARE\option-check\check"
$value = "option"
$return = $regclass.GetStringValue($regkey,$key,$value).svalue

if ($return -match 1) { 
Write-Host @"
<prtg>
<result>
<channel>Option</channel>
<value>1</value>
</result>
</prtg>
"@
} else {
Write-Host @"
<prtg>
<result>
<channel>Option</channel>
<value>0</value>
</result>
</prtg>
"@
}

When I run the script on the PRTG Prode with my Domain Admin account, my results of the query are as such:

$regclass.GetStringValue($regkey,$key,$value)

__GENUS          : 2
__CLASS          : __PARAMETERS
__SUPERCLASS     :
__DYNASTY        : __PARAMETERS
__RELPATH        :
__PROPERTY_COUNT : 2
__DERIVATION     : {}
__SERVER         :
__NAMESPACE      :
__PATH           :
ReturnValue      : 0
sValue           : 1
PSComputerName   :

However when the script is tied to a sensor and ran with the context of the account running the probe service I get a different result:

$regclass.GetStringValue($regkey,$key,$value)

__GENUS          : 2
__CLASS          : __PARAMETERS
__SUPERCLASS     : 
__DYNASTY        : __PARAMETERS
__RELPATH        : 
__PROPERTY_COUNT : 2
__DERIVATION     : {}
__SERVER         : 
__NAMESPACE      : 
__PATH           : 
ReturnValue      : 2
sValue           : 

the account is a local admin of the probe and the machine being probed. It is also a member of the Distributed COM Users, and Performance Log Users and the machine being probed.

The PRTG WMI tester can query root\cimV2 on the remote machine just fine, so it isn't an issue of creds to WMI.

thanks for insight.

exexml powershell wmi

Created on Jan 26, 2017 3:34:53 PM by  stephensmall_it (0) 1

Last change on Jan 26, 2017 4:05:18 PM by  Torsten Lindner [Paessler Support]



1 Reply

Votes:

0

Your Vote:

Up

Down

Created on Jan 27, 2017 8:13:39 AM by  Stephan Linke [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.