Skip to main content

Hyper-V Replication Integration Alert

Purpose​

This solution is built to audit and alert for the Hyper-V Integration and Replication failure. It also helps to create an audit result by storing the Integration and Replication state.

Associated Content​

ContentTypeFunction
cPVAL Hyper-V Integration Service StatusCustom fieldThis custom field stores the Hyper-V integration service status fetched by the Script - Hyper-V Integration Service Audit.
cPVAL Hyper-V Replication StatusCustom fieldThis custom field stores the Hyper-V replication status detail fetched from the Script - Hyper-V Replication Audit.
Hyper-V Integration Service AuditScriptThis script queries all Hyper-V virtual machines and looks for any VM where the IntegrationServicesState is Update required. 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.
Hyper-V Replication AuditScriptThis script validates that it is running on a Hyper-V host using the vmms service. If not a Hyper-V host, it exits cleanly. If Hyper-V is present, it checks replication health and flags Critical or Warning states.
Hyper-V Integration Service Status AlertCompound ConditionThis compound condition is built to create the ticket if the Hyper-V Integration service state is out of date.
Hyper-V Replication State AlertCompound ConditionThis compound condition is built to create the ticket if the Hyper-V replicate state is unhealthy.

Implementation​

Changelog​

2026-05-11​

  • Initial version of the document