How do we get this to work on Server 2012 R2 SCVMM?

I've installed a remote probe on my SCVMM box and tell it to use the custom discovery like the guide above says. Finds 0.

When I try to run the PRTG-SCVMM-HyperV.ps1 from the machine with the probe I get (regardless of PowerShell running as Administrator or not):

**[NAME.DOMAIN.COM] Connecting to remote server NAME.DOMAIN.COM failed with the following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic.
    + CategoryInfo          : OpenError: (NAME.DOMAIN.COM:String) [], PSRemotingTransportException
    + FullyQualifiedErrorId : AccessDenied,PSSessionStateBroken**

If I run the PS1 from my PRTG server to the SCVMM server NAME.DOMAIN.COM it works. I get a list of HyperVs back.

It looks like as long as I'm not localhost the PS1 file will work.

How can I make this work in PRTG?

This is probably due to remote powershell not being properly enabled. Please check this for further instructions. Make sure to download the latest version of the sensor from the initial reply as I posted a new version :)

Hi Team,

The sensor is succesfully seeing my SCVMM, however i am getting this error when running the script

3/07/2017 12:16:40 AM]      error      Could not create sensor for SYDAWSDC01.
[3/07/2017 12:16:40 AM]   information   Starting sensor creation for AWSMELDC01 (GUID: 70d40a8d-4dd4-476d-9b50-e9c6783f5be3)
[3/07/2017 12:16:40 AM]      error      Could not create sensor for AWSMELDC01.
[3/07/2017 12:16:40 AM]   information   Starting sensor creation for MMOSRVAPP02 (GUID: 6a812734-e453-4c7f-9c0e-ea37b5dd23c7)
[3/07/2017 12:16:40 AM]      error      Could not create sensor for MMOSRVAPP02.
[3/07/2017 12:16:40 AM]   information   Starting sensor creation for SYDSRVHUB01 (GUID: 64c9431b-a628-4afc-be0a-ead1b10fad21)
[3/07/2017 12:16:40 AM]      error      Could not create sensor for SYDSRVHUB01.
[3/07/2017 12:16:40 AM]   information   Starting sensor creation for MRN-CAS2 (GUID: cb3f169a-383a-4a06-ba54-ec283343d1fa)
[3/07/2017 12:16:40 AM]      error      Could not create sensor for MRN-CAS2.
[3/07/2017 12:16:40 AM]   information   Starting sensor creation for GuestWifiTestVM (GUID: 7d65b3ac-7108-491a-91ab-f2f30fd91a91)
[3/07/2017 12:16:40 AM]      error      Could not create sensor for GuestWifiTestVM.
[3/07/2017 12:16:40 AM]   information   Starting sensor creation for Boot (GUID: 5856c590-6cf1-4afc-9750-facb68271205)
[3/07/2017 12:16:40 AM]      error      Could not create sensor for Boot.
[3/07/2017 12:16:40 AM]   information   Starting sensor creation for AUSSRVMON01 (GUID: fbf1e27f-fbd5-4b17-bc62-fbd724622360)
[3/07/2017 12:16:40 AM]      error      Could not create sensor for AUSSRVMON01.
[3/07/2017 12:16:40 AM]   information   Starting sensor creation for MELSRVDC01 (GUID: caa3b009-3451-43f1-8420-fcdc60c0bcf9)
[3/07/2017 12:16:40 AM]      error      Could not create sensor for MELSRVDC01.
[3/07/2017 12:16:40 AM]   information   Starting sensor creation for AWSSRVAPP01 (GUID: 574d52cd-3c89-4f4b-b339-fff0e8fe8118)
[3/07/2017 12:16:40 AM]      error      Could not create sensor for AWSSRVAPP01.
[3/07/2017 12:16:40 AM]   information   0 new Virtual Machines have been added to PRTG.
[3/07/2017 12:18:20 AM]      error      Couldn't push the data to the configured PRTG server using the specified token (57be3832-f68c-478d-888f-162b2f546c03).
[3/07/2017 12:20:00 AM]      error      Couldn't push the data to the configured PRTG server using the specified token (84e73668-f434-4930-8481-5664321f6220).
[3/07/2017 12:20:02 AM]      error      Couldn't push the data to the configured PRTG server using the specified token (da74ed95-0c77-4081-9461-86bef65dbf2e).
[3/07/2017 12:20:03 AM]      error      Couldn't push the data to the configured PRTG server using the specified token (e81b1ddd-3b73-4284-aaa4-c2341d2423d1).
[3/07/2017 12:20:04 AM]      error      Couldn't push the data to the configured PRTG server using the specified token (f47a588e-e547-4728-99bc-d7b22b4bd280).
[3/07/2017 12:20:05 AM]      error      Couldn't push the data to the configured PRTG server using the specified token (bd83524c-e46f-45f2-807c-0fa2147d6f90).
[3/07/2017 12:20:06 AM]      error      Couldn't push the data to the configured PRTG server using the specified token (df53ed60-4561-432f-827c-53273045b3ef).
[3/07/2017 12:20:07 AM]      error      Couldn't push the data to the configured PRTG server using the specified token (c314a559-7d30-47b2-bcdb-9249fa7877a5).
[3/07/2017 12:20:08 AM]      error      Couldn't push the data to the configured PRTG server using the specified token (0ac01dca-ebcd-40a0-a53e-a335f5a7c75e).
[3/07/2017 12:20:18 AM]      error      Couldn't push the data to the configured PRTG server using the specified token (dcff2afb-fbea-4ead-b6bb-04951f111e0d).
[3/07/2017 12:20:19 AM]      error      Couldn't push the data to the configured PRTG server using the specified token (b3aedd08-81a9-4a16-a1d8-0509d717114a).
[3/07/2017 12:20:20 AM]      error      Couldn't push the data to the configured PRTG server using the specified token (43708edf-6b88-4090-80ff-0a263c1e97b5).
[3/07/2017 12:20:21 AM]      error      Couldn't push the data to the configured PRTG server using the specified token (2c286efa-c241-4db3-a1da-0cd0d22891d2).
[3/07/2017 12:20:22 AM]      error      Couldn't push the data to the configured PRTG server using the specified token (73eefe2d-8bbc-4689-9f33-0cf4db718913).
[3/07/2017 12:20:23 AM]      error      Couldn't push the data to the configured PRTG server using the specified token (dabe90f5-4c55-40c6-b052-11e363cdac3c).
[3/07/2017 12:20:24 AM]      error      Couldn't push the data to the configured PRTG server using the specified token (13b00809-d765-4252-a41e-153dfd857b1e).

I am running SCVMM 2016, however looks more like an issue getting the data into PRTG.

Any ideas or tips would be great.

Cheers Matt

Dear MacquarieMedia

Did you manually create the HTTP Push Data Advanced sensor before you ran the script?

This seems overly complicated. PRTG has always allowed me to quickly monitor simple and complicated things in an "easier to setup" way then other monitoring applications. This is why I recommend PRTG to other users. But this is not simple.

The instructions could use some more detailed, "example based" instructions for setting up the parameters for the script. This custom sensor should be reworked so that is select-able with the parameters in the web gui vs doing it this way. This would mimic the previous sensor, but require the powershell modules. I recognize that VMWare is probably easier to monitor. Sensors for HyperV and System Center Virtual Machine Manager should be something that PRTG makes easier to setup and monitor then the other monitoring companies.

Thanks for a great product and for listening. DB

Dear davbujn17

Yes, this custom sensor solution is rather complicated. But custom sensors cannot be made select-able in the web gui. We don't want to re-add this sensor to the web gui as we deprecated it just last years because of its little overall usage.

It surely appears counter-intuitive how we make the software better if we remove existing features. The idea is two-fold: One, we keep PRTG simple. Second, we reduce the source code, making it easier to rework and easier for new developers to get into it. That means, that we try to not implement little-used features in the first place, and last year we even removed existing, but little-used sensors.

While SCVMM monitoring is now admittedly more complex, we used our development resources to make other things better.

We've got more than 8000 VM's in Hyper-V and I'm very pro-PRTG, so I've tried to sell PRTG in our organization. Because of this issue they've decided to not buy the unlimited license.

While the script was tested with around 300 VMs, this surely is over the top and we cannot test this with such large environments :( It's rather possible that the script will take a loooong time to retrieve the host servers and virtual machines, running into Windows' 20 minute child process timeout rather than working correctly.

For environments that large, you're probably better off with Microsoft SCOM :)

Kind regards,
Stephan Linke, Tech Support Team

Hello Stephan,

We've got an environment with more than 8000 vm's. We're currently monitoring using PRTG the yper-V hosts only. We would like to buy the unlimited sensor suite of PRTG, but only if PRTG can measure VM's in Hyper-V cluster aware, and directly on the Hyper-V node without SCVMM.

Are you basically saying that PRTG is not a good product for our sizing when it comes to live migrating VM's in Hyper-V?

In that case, I'd recommend against it, yes. The HTTP Push Sensors used in this approach are putting less strain on either system (target host and PRTG). It's unfortunately a chicken and the egg case. We can't monitor moving VMs moving on HyperV clusters; even if we could, it would be 8,000 WMI queries against the systems. The script approach above is querying Hyper-V directly, querying all VMs and hosts at once. However, it has not been tested with that amount of VMs - the most we had were about 400, and it took quite a bit to get the values (took about 2-3 minutes to get them).

PRTG Scheduler | PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team

Hi. I'm trying to set up this custom sensor to monitor two SCVMM machines, one SCVMM 2012r2 and one SCVMM 2016. I don't why, but i cannot seem to get the parameters correct on the sensor settings.

I feel like i have tried all possible combinations to get it to work. Can anyone please give me an example on the correct syntax to use for the parameters when creating the sensor?

Sorry that this took a while, as I was on vacation :( What does your log look like and what parameters do you use, exactly? Did you create the SCVMM device on a remote probe by any chance?

Hi Stephan. I have been on vacation also, so no worries there. :)

What logs would you like? Can i PM them in some way? The parameters i entered are anonymized but here is the exact string entered on the parameters field on the sensor settings.

-prtgHostName=https://fqdn.prtgserver.com -prtgPort=443 [email protected] -prtgPassHash=********** -prtgPushPort=5050 -prtgScvmmDeviceId=%deviceid -prtgTemplateSensor=7284 -Userdomain=%windowsdomain -Username=%windowsuser -Password=%windowspassword -Verbose=$true

Right now the sensor says "Monitoring 0 objects. Last scan took 0 seconds and added 0 objects."

The device is created on a probe yes. I have installed the hyper-v script package on both the probe and the main PRTG server.

Oh well - nice! :) If it's one a probe, please use this version instead:
https://gist.github.com/stephanlinke/3cf39a40dea862171e383fc9553899b1

It has an additional parameter -prtgProbeAddress, allowing you to pass the FQDN/IP of the Remote Probe. It should work with that one. Otherwise, execute the script on the PowerShell command line with the same parameters, including -Verbose (=$true is not necessary, as it's a switch) and post it here with !NO PUBLISH. Then I can check it without others seeing it :)

PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team

Is Remote PowerShell enabled on the SCVMM Server, as disclosed on HowToGeek? The script complains that it cannot connect to the target host :)

PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team

Issue remains that the script cannot connect to the target host :( Try the domain without .local in the userdomain instead.

PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team

Sorry, no luck there. Still unable to connect. I have also tried to use the FQDN for bbvmm.

Executing Get-Command -Module hyper-v | Out-GridView on the target host will give you a comprehensive list of installed Hyper-V modules. Get-VMHost and Get-VM should be included there. Is that the case?

PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team

Hi. Sorry for the late answer. Yes. Get-VM and Get-VMHost is in the list on all hosts. I also checked our SCVMM servers. Both have the Powershell modules for Hyper-V management. Still not getting anything.

I'll drop you a mail later as this is seemingly something different I'm not seeing yet. I'll be in touch.

PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team

I've made a small modification to this script as my SC-VMM also has ESXi hosts in there as we're using the SCVMM tools to migrate away from VMware. I don't want PRTG to be monitoring ESX hosts and vSphere clusters via SCVMM so I've changed lines 423 and 424 from

$hosts = (Get-VMHost); $vms = (Get-VM);

to

$hosts = (Get-VMHost | Where-Object {$_.OperatingSystem -match "Windows"}); $vms = (Get-VM | Where-Object {$_.VirtualizationPlatform -match "HyperV"});

That way, it only returns Hyper-V hosts and VMs.

Nice one! :)

PRTG Scheduler | PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team

Hello Team,

I have created the sensor for the VM monitoring as described in the manual. Unfortunately, the VMs are created twice and in -guidfile.dat no entry is made.

How can I solve this problem?

Best Regards Nils

This likely means that the script can't connect to your SCVMM host and read the hosts/VMs. What's the output of the script when running the script within ISE, configuring the parameters directly in the script?

The script says that no connection can be made. But in PRTG, VM sensors are created. Unfortunately, I do not have all access data and permissions for the SCVMM server, these are only stored in PRTG. Is it possible to display the output of the script via PRTG?

Are you using these Sensors on a Remote Probe by any chance?

PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team

No, i use the sensors on the local probe under the SCVMM device

Strange. Could you check if it makes a difference when disabling the IE first run wizard on a system level, according to https://stackoverflow.com/a/43496639 - simply create the registry entry and let the script run again. Do you get the same error?

PRTGapi | Feature Requests | WMI Issues | SNMP Issues

Kind regards,
Stephan Linke, Tech Support Team

Hi Stephan,

The registry entry has brought no change. I have run the script once with the correct access data directly on the core sample. There were three error messages. The VMs were successfully read and created in PRTG as a sensor, but these sensors do not provide any values. In addition, duplicate sensors with the same GuID will continue to be created

Method invocation failed because [System.Diagnostics.Stopwatch] does not contain a method named 'new'.
At C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXE\PRTG-SCVMM-HyperV.ps1:126 char:1
+ $Stopwatch = [system.diagnostics.stopwatch]::new()
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : MethodNotFound
 


You cannot call a method on a null-valued expression.
At C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXE\PRTG-SCVMM-HyperV.ps1:530 char:1
+ $Stopwatch.Start();
+ ~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : InvokeMethodOnNull



You cannot call a method on a null-valued expression.
At C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXE\PRTG-SCVMM-HyperV.ps1:531 char:23
+ This-GetSCVMMObjects; $Stopwatch.Stop();
+                       ~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : InvokeMethodOnNull

Are the latest PowerShell version (5.1) and .NET installed on the PRTG Server? Please also try the updated script version available at github. Thanks!

Today i begun to configure the scvmm monitoring, but it seems that i stuck in problems. If i try to test the script manually, i will get following message:

PS C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXE> .\PRTG-SCVMM-HyperV.ps1 -prtgHostName=https://server.ddcmgm.local -prtgPushPort=443 [email protected] -prtgPassHash=*** -prtgPushPort=5050 -prtgTemplateSensor=5173 -prtgScvmmDeviceID=5170 -Userdomain=%windowsdomain -Username=%windowsuser -Password=%windowspassword -Verbose=$true
[29.12.2020 15:04:01]   information   GUID file path: C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXE\-guidfile.dat
[29.12.2020 15:04:01]   information   Retrieving HyperV hosts and VMs...
[29.12.2020 15:04:01]      error      Couldn't connect to the server or execute the given commands. Please check if WinRM is enabled and allowed.
Cannot index into a null array.
At C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXE\PRTG-SCVMM-HyperV.ps1:483 char:5
+     $VMHosts   = $objects[0];
+     ~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : NullArray

Cannot index into a null array.
At C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXE\PRTG-SCVMM-HyperV.ps1:484 char:5
+     $VMs       = $objects[1];
+     ~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : NullArray

[29.12.2020 15:04:01]     success     0 HyperV hosts have been found.
[29.12.2020 15:04:01]     success     0 Virtual Machines have been found.
[29.12.2020 15:04:01]   information   0 new HyperV Hosts have been added to PRTG.
[29.12.2020 15:04:01]   information   0 new Virtual Machines have been added to PRTG.
[29.12.2020 15:04:01]   information   Elapsed Time: 00:00:00.2575762
0:Monitoring 0 objects. Last scan took 0 seconds and added 0 objects.
PS C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXE> Enter-PSSession -ComputerName ddcmgmscvmm10.ddcmgm.local
[ddcmgmscvmm10.ddcmgm.local]: PS C:\Users\svc.scvmm\Documents>

As you see - we can connect over powershell to the remote system.

What is the problem here? How can we get this sensors up and working?

I assume that you actually used credentials instead of the % placeholders and are using single quotes to surround them? Is the account you're using a member of the Hyper-V administrators?

I assume that you actually used credentials instead of the % placeholders and are using single quotes to surround them? Is the account you're using a member of the Hyper-V administrators?

I am having an issue when the scvmm sensor is on a remote probe. I have entered the $prtgProbeAddress to the script on the remote probe but I receive this error when the script runs on the remote probe, "Couldn't push the data to the configured PRTG server using the specified token".

It seems roever above had the same issue but I do not see any resolution to his/her issue.

Is the URL to the Sensor (to where the script is pushing the data) actually opening with a browser on the probe? The script uses Invoke-WebRequest, which may be stopped by the First Run Wizard. Once disabled, it may already work :)

I've made a couple more modifications to this script which help me a little.

The first is with the display names of the sensors. When the script creates its sensors, it just names it after the VM which is great but when you have hundreds of VMs spread across multiple clusters, it makes it a little hard to keep track of what is where. Naming conventions are all very well and good, but aren't always followed. So therefore I've changed line 348 from

if(This-AddHTTPPushSensors -sensorName $object.name -Token $object.id)

to

if(This-AddHTTPPushSensors -sensorName $(if ($object.ObjectType -eq "VM") {"$($(Get-Cluster -Name $object.VMHost).name) - $($object.name)"} else {$object.name}) -Token $object.id)

That gets the name of the cluster that the host node is a member of and uses it as a prefix to the sensor name. The sensors now display the name of the cluster, followed by the name of the VM.

I've also added a metric to be measured to the VM sensor, I've added a line at line 523ish which says:

"Memory Available" = @($VM.MemoryAvailablePercentage,"Percent",0,0,0,0);

I like this script, and I can see myself adapting it for use for other things outside of SCVMM.

Cool update! Indeed, better naming conventions are crucial for large environments. I'll add your post to the first one if anybody else needs it and doesn't want to dig the whole thread :)