Hyper-V Cluster Shared Vol. Disk Free

Hello,

which exact error do you get when you try adding the sensor? Or what exactly happens? Can you maybe upload some screenshots?

best regards.

I get this error when trying to add the sensor:

Sorry, the scan for available minitorin items has failed!

Error Message: Connecting to remote server failed with the following error message : The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: 'winrm quickconfig'. For more information, see the about_Remote_Troubleshooting Help topic.

Sensor Type: Hyper-V Cluster Shared Vol. Disk Free

Hi, I'm having the same issues. Did you solved it?

Also having the same issue.

just to check, is the Remote Registry Service running on the target?

See: https://www.paessler.com/manuals/prtg/hyper_v_cluster_shared_volume_disk_free_sensor.htm

Hi,

Yes, the remote registry is running on the Hyper-V hosts.

I have the same issue. We followed this guide to enable remote powershell: http://technet.microsoft.com/en-us/magazine/ff700227.aspx

We also have .NET 4 installed on the probe server and are using Windows 2008 R2 as the probe. Our Hyper-v cluster is built on Windows 2012. We have 2 CSV Volumes. The user that we currently use for monitoring is a domain admin and has full admin access to the target.

Please let me know if you need any other info.

Thanks, Andreas

Andreas, are the system that is running the PRTG probe and the target system in the same domain?
What Windows version is installed on both of those systems?
Did you run the "Enable-PSRemoting" with or without the -force parameter? We did encounter some problems with this sensor if you run command without the -force. We also would recommend using the WMI Volume sensor here, as the CSV-Sensor basically is designed to be an alternative if the WMI Volume sensor does not work. Both read the very same data.