We have followed the documentation on the website about the new way to monitor VMM using PowerShell. When I add a device (vmm server) and select the templates my VMM does not get discovered. The error in Auto Discovery Debug Log is.

25-4-2016 15:45:59: Autodiscovery Started; Device ID: 6930
25-4-2016 15:45:59: Device Templates; Device ID: 6930; Selected: 2
25-4-2016 15:45:59: Template Loaded; Device ID: 6930; Name: Hyper V Host Server
25-4-2016 15:46:00: Template Check; Device ID: 6930; Check ID: ping; FOUND
25-4-2016 15:46:02: Template Check; Device ID: 6930; Check ID: wmi; FOUND
25-4-2016 15:46:04: Template Check; Device ID: 6930; Check ID: wmihypervservercheck; NOT FOUND
25-4-2016 15:46:04: Template Assigned; Device ID: 6930; Name: Hyper V Host Server
25-4-2016 15:46:04: Template Loaded; Device ID: 6930; Name: Hyper-V Virtual Machines
25-4-2016 15:46:04: Template Assigned; Device ID: 6930; Name: Hyper-V Virtual Machines
25-4-2016 15:46:10: Template Create Meta Request; Device ID: 6930; Create ID: hyperv.virtualmachines; ERROR: 106
25-4-2016 15:46:16: Template Create Meta Request; Device ID: 6930; Create ID: hyperv.virtualhosts; ERROR: 106
25-4-2016 15:47:10: Autodiscovery Started; Device ID: 6930
25-4-2016 15:47:10: Device Templates; Device ID: 6930; Selected: 1
25-4-2016 15:47:10: Template Loaded; Device ID: 6930; Name: Hyper-V Virtual Machines
25-4-2016 15:47:11: Template Check; Device ID: 6930; Check ID: ping; FOUND
25-4-2016 15:47:11: Template Assigned; Device ID: 6930; Name: Hyper-V Virtual Machines
25-4-2016 15:47:17: Template Create Meta Request; Device ID: 6930; Create ID: hyperv.virtualmachines; ERROR: 106
25-4-2016 15:47:23: Template Create Meta Request; Device ID: 6930; Create ID: hyperv.virtualhosts; ERROR: 106

Any help would be appreciated.

Thank you.

Article Comments

When you execute the script like this: 

PRTG-HyperV.ps1 -metascanVM -Computername "%host" -userdomain "%windowsdomain" -username "%windowsuser" -password "%windowspassword"

...and replace the % placeholders accordingly - what output do you get then?


Apr, 2016 - Permalink

Hi Stephan,

Thank for your reply. I get a list of VM GUID ID's.

<item> <name>XXXXXXXX</name> <exefile>PRTG-HyperV.ps1</exefile> <params>-VM 57EE253E-DA1D-4A74-8D1D-9F6A3554C5E1 -ComputerName '%host' -Username '%windowsuser' -Password '%windowspassword' -userdomain '%windowsdomain'</params>


Apr, 2016 - Permalink

Okay, I think I know the cause of the problem. I'll report it to the developer. Until then, you can create a EXE/Script (advanced) sensor using the same script and parameters as in the params field for each VM.

The problem should be fixed within the next versions of PRTG :)


Apr, 2016 - Permalink

Hi Stephan,

Is this issue fixed?


Jul, 2016 - Permalink

Sorry, not yet :/
edit The bugfix has been merged into the latest canary :) So it should be available in the stable version soon.


Jul, 2016 - Permalink

Hi there,

Please download the latest version of the sensor (and replace all files). We finally fixed all the bugs so far and the sensor (including auto discovery) should now work with current PRTG version :)

Let me know if it worked out for you!


Aug, 2016 - Permalink