Download Hyper-V Private Cloud Monitoring
Sealed SCOM Management Packs for Hyper-V private cloud infrastructure. The release contains 13 product packs: four always-required packs plus nine independently selectable capability packs. The primary deployment ZIP upgrades all 12 non-PureStorage solution packs together. Pure Storage remains separately selectable because it requires the vendor Management Pack.
Read the prerequisites first
The Microsoft and vendor Management Packs each capability requires are not redistributed here, and a missing one is the most common cause of a failed import. Work through the prerequisites before downloading anything.
Current release: 1.3.8.0 — Private Cloud Powered by Hyper-V: A 360° View
1.3.8.0 is the current production release. Every one of the 13 sealed product MPs has version 1.3.8.0, delivering the full 360° Private Cloud Distributed Application service model. This includes complete fabric modeling across physical server chassis/hardware, top-of-rack data switches, out-of-band management switches, perimeter firewalls, Opengear out-of-band console servers, DHCP/IPAM, management domain services (Active Directory, DNS resolution, and PXE/WDS bare-metal deployment), central deep-troubleshooting operator tasks, and the streamlined 2-pack override model. All 13 product Management Packs are sealed with the permanent public key token 54d0fb1159995c86, verified by Microsoft VSAE, strong-name checked, and covered by the published SHA-256 manifest. The release catalog contains 13 sealed Management Packs and 2 canonical override packs: 171 unit monitors, 149 dependency roll-ups, 80 rules, 23 discoveries, 124 views, 74 operator tasks, and generated day-2 support for all 522 supported elements across host, VM, Failover Clustering, CSV, Storage Spaces Direct, SAN (Fibre Channel, iSCSI, MPIO), SMB/SOFS, Network ATC, physical networking, SDN host binding, VMM and Pure Storage. Cluster-wide facts are evaluated once per cluster, host-wide facts once per host, and one probe run per host feeds every per-VM, per-LUN, per-session, per-port and per-intent monitor.
Version 1.3.8.0 adds generated day-2 references and completes source-defined root health paths for all 159 enabled product unit monitors. It preserves the correct Availability, Performance, Configuration, and Security aspects; fixes cluster failure-episode evidence; and completes VMM, File Services, Storage, SAN, Network ATC, S2D, Pure Storage, Security, and host-participation relationships. Validation did not install a guest SCOM agent. The sealed package passed VSAE/SDK, strong-name, package-content, and checksum validation. The exact 1.3.8.0 sealed upgrade and runtime soak have not yet been run and are not claimed as passed.
Management Packs are named for the product — HyperVPrivateCloud.Library, HyperVPrivateCloud.Capability.Cluster, and so on. Publisher attribution is carried in the sealed pack Company and Copyright metadata rather than in the pack ID.
Download now
- Download the 12-pack solution upgrade — all four core packs plus Cluster, Storage, S2D, File Services, Network ATC, Physical Network, SDN, and VMM, all at
1.3.8.0. It contains no override MPs. - Download the complete package — archive containing all available product packs and optional starter templates; do not bulk-import its contents.
- Download the core-only bundle — Library, Discovery, Monitoring, and Presentation for deployments that intentionally use no optional capabilities.
- Download canonical override templates — Discovery and Monitoring override templates; select and review one Discovery/Monitoring pair only.
- Download SHA-256 checksums
- View the release manifest
- View the public asset manifest
Verify what you downloaded
SHA256SUMS.txt covers every file published alongside it, including the two manifests. Verify before importing:
Get-Content SHA256SUMS.txt | ForEach-Object {
$expected, $name = $_ -split '\s+', 2
$name = $name.Trim()
$actual = (Get-FileHash $name -Algorithm SHA256).Hash
'{0,-8} {1}' -f $(if ($actual -eq $expected.ToUpper()) { 'OK' } else { 'MISMATCH' }), $name
}The checksum file is written by the Windows release packager and carries CRLF line endings, so on Linux or macOS strip them first: tr -d '\r' < SHA256SUMS.txt | sha256sum -c -.
The immutable versioned files are also retained under 1.3.8.0. The latest directory serves the same exact bytes and changes only when a newer validated version is published. Previous releases remain under 1.3.7.0, 1.3.6.0, 1.3.5.0, 1.3.4.0, and 1.3.3.0.
Apply a tuning profile in one command
After the core and capability packs are in, apply one deployment profile's tuning tier without digging through the zip:
iwr https://labs.hybridsolutions.cloud/hybrid-health-monitoring/downloads/hyper-v-private-cloud/tools/Install-HyperVPrivateCloudOverrides.ps1 -OutFile Install-HyperVPrivateCloudOverrides.ps1
./Install-HyperVPrivateCloudOverrides.ps1 -DeploymentProfile ClusteredSAN -TuningTier Standard -ImportRun it as a file (not pasted line-by-line). Pick the profile matching the capability packs you imported; import exactly one Discovery + Monitoring pair per management group. Standard is the coded defaults made explicit; Lab is forgiving; Strict is tight.
Deployment-profile bundles
Use a profile bundle when you want only the sealed MPs and six starter override files for one topology. Import exactly one override tier's Discovery and Monitoring pair after reviewing it.
| Profile | Download |
|---|---|
| Standalone | Download |
| Clustered SAN | Download |
| Clustered Pure Storage | Download |
| Clustered S2D | Download |
| Hybrid SAN and S2D | Download |
| Hybrid Pure and S2D | Download |
| Hyper-V over SMB | Download |
| Network ATC | Download |
| SDN enabled | Download |
| VMM managed | Download |
| Complete private cloud | Download |
Before import
The HCS ZIPs do not redistribute Microsoft, VMM, or Pure Storage prerequisite Management Packs. Install only the capability adapters your environment uses, and satisfy their publisher-owned dependencies first. Review the administration guide for the dependency matrix and import order.
SCOM runtime validation is intentionally performed after download and installation in the operator's isolated management group. Use the included diagnostics and the repository's certification collector to record that evidence; any verified defect is corrected in a version-increased release.