45 docs tagged with "Hyper-V"

This document outlines the procedure for alerting the ProVal support team when a VM in a Hyper-V environment contains a checkpoint that is older than 24 hours. It includes an example log of the agent procedure and details on the dependencies and process involved in generating the alert.

Retrieves detailed Hyper-V VHD/VHDX information and stores it as an HTML table in a NinjaRMM Custom Field. "cPVAL Hyper-V Vhdx Details".

A group tailored for Windows Servers that have the Hyper-V Cluster role installed

A group tailored for Windows Servers that have the Hyper-V role installed

This custom field stores the Hyper-V integration service status fetched by the [Script - Hyper-V Integration Service Audit](/docs/1c8cf2c3-d470-4616-bc27-35e69f274202)

This custom field stores the Hyper-V replication status detail fetched from the [Script - HyperV Replication Audit](/docs/d3e74048-d274-4fe7-8501-c826822707b2)

Stores an HTML-formatted inventory of Hyper-V Virtual Hard Disks (VHD/VHDX). Data is populated via the "Audit Hyper-V VHDX" automation script and includes disk paths, allocation types (Dynamic/Fixed), current file size, and fragmentation percentage.

This document provides a script for creating a checkpoint of a virtual machine hosted on a Hyper-V Host Server. It includes details on intended targets, variable descriptions, user parameters, and sample runs to help users effectively utilize the script.

This will get information about the current number of Hyper-V checkpoints on a given machine. A threshold in days can be specified for reporting, and this threshold can also be obtained from an integer custom field.

This creates ticket if the hyper-v checkpoint detected older than the provided threshold days

This document describes a script that enables the management of virtual machines on a Hyper-V host, allowing users to start or shut down VMs based on previous executions of the script, ultimately saving time in the process.

This will get information about the current number of Hyper-V checkpoints there are on a given machine and based on it if detected older checkpoint then it creates ticket

This document provides a detailed report of the Hyper-V disk records from the custom table pvl_disk_record, including information on client names, locations, computer names, operating systems, and various disk attributes such as total size, free size, and status.

This script queries all Hyper-V virtual machines and looks for any VM where the IntegrationServicesState is `UpdateRequired` / `Update required`/ `NotPresent`, or `Unknown`. If any such VM is found, the script stores the VM details in the NinjaOne custom field `cpvalHyperVIntegrationServiceStatus` and exits with code 1. If no VMs require Integration Services updates, the script stores `UpToDate` and exits successfully with code 0.

This compound condition is built to create the ticket if the Hyper-V Integration service state is out of date.

If the system is not a Hyper-V host, the script records `NotAHyperVHost` and exits successfully. If Hyper-V is present, the script evaluates replication status for all VMs where replication is enabled. The script flags VMs that have replication states indicating issues, specifically `Critical` or `Warning`. If any VM is found in an unhealthy replication state, the script reports the affected VMs and sets a failure exit code. If all replication-enabled VMs are healthy, it reports `Healthy`.

This solution is built to audit and alert for the Hyper-V Integration and Replication failure.

This compound condition is built to create the ticket if the Hyper-V replicate state is unhealthy.

This document outlines a monitor set designed to detect Hyper-V hosts with problematic replication status for virtual machines. It provides insights into the replication state of virtual machines, troubleshooting steps, and details for ticketing when issues arise.

This document provides a comprehensive overview of dataview audit snapshots for virtual machines hosted on the Hyper-V Server, detailing the various columns and their descriptions for better understanding and management of virtual environments.

Executes "Audit Hyper-V VHDX" script once per day against Hyper-V Hosts.

Retrieves detailed Hyper-V VHD/VHDX information and stores it as an HTML table in a NinjaRMM Custom Field.

This document provides a comprehensive overview of the auditing information related to Hyper-V virtual machines, including details about their state, status, and configuration settings.

This monitor generates alerts for HyperV host virtual machines with failing Integration Services.

This solution outlines how to detect and monitor HyperV Host servers for Integration Service health issues from CW RMM.

This monitor generates alerts for HyperV host virtual machines with replication states of Warning or Critical.

This solution outlines how to detect and monitor HyperV Host servers for replication state issues from CW RMM.

This document outlines the implementation of a remote monitor that alerts on Hyper-V host snapshots that are 3 days old or older. It provides detailed instructions for alert configuration, ticketing, and monitoring to ensure efficient management of VM snapshots.

This monitor will generate alerts for HyperV host snapshots that have turned 3 days old in the past hour.

This solution outlines the process for detecting and monitoring Hyper‑V Host servers that store snapshots older than 3 days from CW RMM.

Group of HyperV Host servers where integration service monitoring is turned on.

Group of HyperV Host servers where replication state monitoring is turned on.

Check this box to enable alerts for HyperV Host servers that have snapshots older than 3 days.

Group of HyperV Host servers where monitoring for snapshots older than 3 days is turned on.

Check this box to enable alerts for HyperV Host servers with Integration Service health issues by enabling HyperVIntegrationSvcMonitoring.

Check this box to enable alerts for HyperV Host servers with replication state issues by enabling HyperVReplicationStateMonitoring.

This document outlines the implementation steps for monitoring Hyper-V snapshot age using a SQL query. It provides a detailed SQL command to insert monitoring agents and instructions for applying the alert template in the ConnectWise Automate environment.

This document provides details on a monitor that checks for the Hyper-V integration service and generates tickets if it is out of date. It includes setup instructions, dependencies, and implementation guidance.

This document provides an overview of the audit report for disk space on Hyper-V cluster servers, including details on cluster volumes and their respective sizes, free space, and usage statistics.

This document describes a script that schedules a reboot for the next applicable day at a specified time on a target machine. For Hyper-V hosts, it also creates a ticket indicating that the reboot has been scheduled, ensuring that the support team is informed.

This document describes a script designed to check for Hyper-V machines that exceed their NUMA node limits, helping to identify misconfigured virtual machines and optimize resource allocation.

Documentation for the Set-VMGuestState command to start or stop all running VMs on the Hyper-V host, with special handling for domain controllers.

This document provides a comprehensive solution for monitoring Windows Cluster Shared volumes, creating tickets when space falls below 10%, and auditing to maintain a report of cluster disk spaces on Hyper-V Cluster servers. It includes details on scripts, remote monitors, and implementation steps for effective management.

This document outlines a script designed to place virtual machines hosted on a Hyper-V Host into Maintenance mode for a duration of 60 minutes. During this period, alerts will be suppressed, and script execution will be limited on the affected virtual machines, ensuring a smooth maintenance process.

This document provides a detailed overview of the cluster disk space audit report generated from the pvl_cluster_volumes table. It includes information on the client, location, computer, operating system, and various metrics related to cluster volume sizes and usage, as well as dependencies on the relevant CWA script.