Veeam Management Pack 13 for Microsoft System Center Release Notes

This document provides last-minute information about version 13.1 of Veeam Management Pack for Microsoft System Center, including system requirements, installation and upgrade procedures, as well as relevant information on technical support, documentation, and online resources.

The release of v13.1 of Veeam Management Pack for Microsoft System Center is available for download at: https://www.veeam.com/vmware-microsoft-esx-monitoring-download.html starting from 26th October, 2026.

What’s New

Veeam Management Pack for System Center Operations Manager (SCOM) has been updated to v13 to match the other products in the Veeam Data Platform.

Highlights of the many new features and improvements are below. For further details see the user guides

• Brand-new configuration UI, with new overview dashboard and improved workflows.
• Support has been added for the latest versions of VMware vSphere, Microsoft Hyper-V and Windows Server.
• Support for Veeam Backup & Replication v13.x has been added with a new ‘Data Collector service for Veeam Backup’.

Changes from previous v9.x

• Security is improved with support for group-managed service accounts (gMSA) for the connection to SCOM server to gather Hyper-V host data.
• Data Collector auto-deploy MSIs have been removed from the standard MP deployment. These MPs are still available in the MP Resource Kit.
• Veeam MP PowerShell module has been replaced with a REST API.

System Requirements

Microsoft System Center

• Microsoft System Center Operations Manager (SCOM) 2025
• Microsoft System Center Operations Manager 2022
• Microsoft System Center Operations Manager 2019
• Microsoft System Center Virtual Machine Manager (SCVMM) 2025 (optional)
• Microsoft System Center Virtual Machine Manager 2022 (optional)
• Microsoft System Center Virtual Machine Manager 2019 (optional)

SCOM agents must be installed on every Hyper-V host. For the system requirements for SCOM agents, see Microsoft Docs.

If you add a SCVMM server to the Veeam Backup & Replication infrastructure, you must connect this SCVMM server with SCOM to ensure proper discovery of monitored objects. For more information on how to connect SCVMM with SCOM, see Microsoft Docs.

Hardware

• Hard disk space: variable storage size (OpsMgr database)

Additional Software

• Microsoft SQL Server 2025 Reporting Services
• Microsoft SQL Server 2022 Reporting Services
• Microsoft SQL Server 2019 Reporting Services
• Microsoft SQL Server 2017 Reporting Services

VMware Infrastructure

Servers

• vCenter 9.x
• vCenter 8.x
• vCenter 7.x

Hosts

• vSphere ESXi 9.x
• vSphere ESXi 8.x
• vSphere ESXi 7.x

Software

• vCenter Server 9.x
• vCenter Server 8.x
• vCenter Server 7.x

Microsoft Infrastructure

Servers

• Windows Server 2025
• Windows Server 2022
• Windows Server 2019

Hosts

• Windows Server Hyper-V 2025
• Windows Server Hyper-V 2022
• Windows Server Hyper-V 2019

Veeam Infrastructure

Servers

• Veeam Backup & Replication 12.0 and later

Agents

• Veeam Agent for Windows 6.0 and later

Veeam Virtualization Extensions Service & UI (VES)

Hardware

• Hard disk space: minimum 2 GB — required for .NET Framework installation, binaries and log files.
• Memory and processor: processor architecture must be x64.

OS

64-bit versions of:

• Microsoft Windows Server 2025
• Microsoft Windows Server 2022
• Microsoft Windows Server 2019

Software

VE Service:

• Operations Manager Management Server or Gateway Server.
• Windows Remote Management must be enabled for the Management Server.

Web UI:

• Microsoft Internet Information Services 7.0 or later (IIS is installed and configured during VES installation).
• Microsoft Edge (latest version), Mozilla Firefox (latest version), Google Chrome (latest version).

Veeam Data Collector for VMware vSphere & Veeam Data Collector for Veeam Backup

• The Veeam Data Collector for VMware vSphere is only required for gathering monitoring data from VMware vCenter environments.
• The Veeam Data Collector for Veeam Backup is only required for gathering monitoring data from Veeam Backup & Replication servers.

Hardware

• Processor: 4 x 2GHz minimum
• Memory: 4 GB minimum. To achieve maximum scalability and performance, x64 OS with 6 GB RAM is recommended
• Hard disk space: 2 GB minimum — required for .NET Framework installation, binaries, and log files

OS

64-bit versions of:

• Microsoft Windows Server 2025
• Microsoft Windows Server 2022
• Microsoft Windows Server 2019

Known Issues

General

• The Traffic Lights widget does not show the Path property. Even if you configure the widget to display the Path property, dashboards will still show no data for it.
• If you use a non-default SQL collation that is not supported by SCOM, after installation of Veeam MP you may receive errors such as: ‘Cannot resolve the collation conflict between ’SQL collation’, ’SQL_Latin1_General_CP1_CI_AS’ and ’Latin1_General_CI_AS’ in the equal to operation’.
• Virtual machines. UptimeStatistics and Veeam State Details reports may show ‘No relevant data’ if the end date of the reporting period is more than one month away from the current date.
• Kerberos-only authentication between Veeam MP components is not supported.
• Predefined report templates may fail during deployment with the following error: “Uploading or saving files with .ManagementPackHistory extension is not allowed. Contact your administrator if you have any questions”. To resolve it, register the required extension for the SQL Server Reporting Services (SSRS) manually as described in Microsoft Docs.

VMware vSphere

General

• If the VES is installed on an SCOM agent-managed machine that communicates with the Management Server through a gateway server, the Management Server will be unaware of vSphere hosts that were placed in the Maintenance Mode.

  To work around the issue, after you put a host in the Maintenance Mode in vCenter, do the same in the SCOM console.

• The Veeam Relationship History, Storage vMotions History and vMotions History reports may take a long time to generate. The OperationsManagerDW database may accumulate huge amounts of discovered objects and relationships.

  To resolve the issue, ensure that appropriate database grooming processes are in place.

• The VMCluster-memory and memoryUsedMB metrics may report incorrect values if you choose to split host clusters into multiple monitoring jobs to allow more flexible load-balancing.

  To resolve the issue, disable the SplitClusters option and try redistributing the monitoring load across Collectors.

• For thin-provisioned VMs, vSphere may report that used space is higher than the actual allocated space. For such VMs, the Datastores. Overprovisioned Storage report may show negative overprovisioning values. This is a known limitation of the vSphere API.
• If you configure multiple monitoring jobs for one vCenter Server and assign these jobs to different Veeam Data Collectors, duplicate vCenter events and monitor triggers may be generated in SCOM.
• Under certain circumstances, when the environment has multiple Veeam Collectors, SCOM may show vSphere datastore GUIDs instead of datastore names during the discovery period. This issue will be resolved automatically within 4–24 hours when discoveries from all Collectors have completed.
• If a vSphere host NIC is not connected to any vSwitch or Distributed vSwitch, Veeam MP for VMware will not monitor its state. Monitoring will only start when the NIC is added to a switch.
• The default 5-minute setting for statistics collection should not be changed in a vCenter Server. This interval is required for gathering VMware data.
• The Host Security Profile report may not display all expected audit events when you drill down to a specific change. This can occur due to synchronization issues around discovery and update of the Host Security Profile object. All discrepancies should be resolved within 24 hours after automated discovery rules update the objects.

  To view all host security profile audit events, click the Total number of changes link under the hostname. This link will always display all security events captured during the reporting period.

• After Veeam MP for VMware is installed, the Veeam VMware Collector: Health Service recommended configuration monitor checks the configuration of the Microsoft Monitoring Agent service and will generate a warning if the optimal configuration is not present. Run the Recovery Task in the monitor to update the service configuration. The task will automatically restart the service if installed on an agent; for a SCOM Management Server, the service must be restarted manually when convenient.

  To resolve the warning, run the recovery action, and if required restart the Microsoft Monitoring Agent service manually.

• On the SCOM Management Server, the Maintenance Mode synchronization script may fail with the following error: ‘MaintenanceMode.ps1 : SCOM Shell Module or Snap-in not found.’

  To resolve the issue, install PowerShell 5.0 or later and reboot the server. If this does not resolve the issue, install the Operations Console on the Management Server.

• During the normal Veeam MP for VMware discovery process, some vSphere objects may be temporarily shown as unmanaged and their management will reside on an Operations Manager Management Server. When trying to run Veeam workflows for such objects, the Management Server will attempt to open the Veeam VMware Event log. If there is no Veeam Data Collector for vSphere installed on the Management Server, the following error will be observed: ‘The Windows Event Log Provider is still unable to open the Veeam VMware Event log on computer ’<SCOM Manager Server Name>’.’

  When the Veeam MP for VMware discovery process is finished, all vSphere objects will have been ‘claimed’ for management by a Collector and the errors on the MS should no longer appear.

• After you upgrade Veeam MP for VMware, monitoring of vCenter Servers stops until you trust the vCenter Server certificates.

  To resolve the issue, edit each vCenter connection and accept the certificate.

Unknown files analysis

The Veeam VMware: Datastore Unknown Files Analysis monitor tracks space taken on datastores by files which are ‘unknown’, i.e. not a part of vCenter’s known configuration, such as ISOs stored on a datastore. Note the following issues:

• For datastores with no registered VMs, the UnknownFilesGB metric value is returned as ‘0’.
• During the VM migration process, the UnknownFilesGB metric may show inaccurate values and the Veeam VMware: Datastore Unknown Files Analysis alerts may trigger. The issue will be resolved after vMotion completes and Veeam MP discovery processes the change.
• Some 3rd-party solutions can replicate, backup, or copy VM files without registering them in the vCenter Server.
• This monitor is disabled by default for Virtual Volumes, vSAN datastores and NFS datastores.

Microsoft Hyper-V

• Hyper-V Integration Services should be installed on all VMs to allow full-featured monitoring.
• Storage migration to another volume halts the storage performance data collection. The following performance metrics are affected: Storage IOPS, Storage KB Total/sec, Storage Flush Count and Storage Error Count. Note that this issue does not affect migration between hosts.

  To resolve the issue, restart the SCOM agent after storage migration.

• CSVs and cluster disks must not contain apostrophes in their names. Otherwise, Veeam MP will not be able to discover them.
• Microsoft Windows and Microsoft Hyper-V containers are not supported.
• If you set an override for a Veeam MP performance metric in a way that the specified data collection time interval exceeds the SCOM time range configured to collect dependent metrics, the corresponding Veeam MP monitor will not be able to work correctly and all dependent metrics will return zero values.
• In case a virtual machine uses the VHDs (VHD Set) type of virtual hard disk, SCOM will not be able to collect disk metric values for the VHDs and the Used Storage GB metric will return zero values because the Hyper-V API does not expose per-VM disk usage for VHDs attached to a specific VM.
• The Configuration Change Tracking and Alert Correlation report displays ‘GUID to VM name’ events as changes.
• The VM Net and Disk Traffic Analysis dashboard does not show Net Used and Disk Time statistics.
• Importing the Hyper-V Task Manager VMM plug-in may require a restart of the Operations Manager console.
• The Last Successful Backup property of Microsoft Hyper-V VMs with crash-consistent backups enabled is always empty.
• The Veeam Hyper-V: VM Integration Services Status monitor may generate errors in the SCOM log if a heavily loaded virtual machine has not been able to respond in a timely manner.
• After a VM is renamed, a VM reboot is required for Hyper-V to start collecting the new name and related performance metrics.
• When the Hyper-V host does not correctly process a command that the guest VM OS sent to the iSCSI device, it will increase the Error Count metric value although the command is valid and not necessarily an error.
• During initial discovery, VMs may be temporarily represented with GUIDs instead of VM names.
• During initial discovery, if VMs are removed from Hyper-V Manager inventory while the storage remains offline, the VMs will have GUIDs shown instead of VM names.
• If two or more VMs residing on a Hyper-V host have the same VM name, the Hyper-V Task Manager may show inaccurate performance statistics data for such VMs.
• For VMs with static memory, Hyper-V will not send memory usage data to the PerfMon classes. As a result, such VMs will have zero memory usage in SCOM.
• When all VMs on a Hyper-V host are stopped, events 10103 is written to the event log on the Hyper-V host: ‘In PerfDataSource, could not resolve counter instance [CounterName]. The module will not be unloaded. One or more workflows were affected by this.’ When all VMs are stopped, the Hyper-V server unloads all PerfMon classes, and the SCOM PerfMon module cannot access data.
• Local disks and volumes on Hyper-V hosts will be discovered only if there are VMs residing on these volumes.
• NFS storage is not supported.
• The size of the pass-through disks is not taken into account when the Used Storage metric value for a VM is calculated.
• The Virtual Machine. Idle VMs report output tables show ‘n/a’ values in the Down Time (%) column.
• After installation or upgrade, the Traffic Light and Top N dashboard widgets will show no data until performance statistics are aggregated in the OperationsManagerDW database. Usually, the initial data aggregation takes about 4 hours.
• If a VM is migrated from a volume that has several mount paths, the Used Storage property for the VM may be reported incorrectly.
• If a Clustered Shared Volume is unavailable (failed status), the Used Storage GB metric will be reported as zero.
• If the Run As account configured for the Veeam Hyper-V MP VMM Connection Account (Read-only) profile does not have sufficient permissions, ‘Unauthorized Access’ exceptions will be written to the event log on the Management Server.
• The “Veeam Hyper-V: VM Storage Errors” monitor can generate false-positive alerts if this metric is missing from Performance Manager for the virtual machine’s disk.

Veeam Backup & Replication

• Standalone Agent jobs may still be visible in the SCOM console after the agent was moved under the control of the Veeam Backup & Replication server.
• If a Veeam Backup & Replication server runs a large number of jobs, data collection process may consume a high amount of CPU resources and sometimes cause a significant load on the backup server. To minimize the load, you can disable the following rules: Veeam Job Processing Rate MBps, Veeam Job Backup Size GB, Veeam Job Processed Size GB, Veeam Job Duration, Veeam Job Deduplication Ratio %, Veeam Job Transferred Size GB and Veeam Job Compression Ratio %.
• The Backup Job RPO compliance monitor does not support SureBackup jobs and Backup Copy (Immediate Copy) jobs.
• The VM Backup Status report incorrectly displays some backup job statuses for jobs in the in-Progress state. The in-Progress job state may indicate poor performance of the Veeam Backup configuration database or other performance issues on the backup server.
• The Veeam Backup: Job RPO Compliance monitor tracks job history only for restore points successfully created during the previous 3 months.
• Job sessions that failed before VM enumeration are excluded from Veeam Backup & Replication reports.
• vCenter Servers must be added to the VES UI using the same unique address as in the Veeam Backup & Replication console. Otherwise, the Protected VMs report may show incorrect data.
• The _Total Instance value of the CPU Used % metric for a backup proxy may exceed 100% if the backup proxy is overloaded.
• If a VM has a large volume (more than 2TB) and the volume is distributed among several VMDK files, the VM Configuration Assessment report may incorrectly show this volume as having a potential backup issue.
• Some configuration data from Veeam Agent for Microsoft Windows in Agent Management mode and being managed by the backup server is not collected. All relevant job data is collected when jobs are managed by Veeam Backup servers.
• SQL Transaction Log and Oracle Archived Log backup jobs are not collected for all agents.
• The Veeam Backup: Job RPO Compliance monitor (disabled by default) ignores agent backup jobs managed by the backup server that contain more than one machine.
• The Backup Repository Maintenance Mode and Repository Seal Mode tracking monitors support only Performance Tier extents of scale-out backup repositories.
• The Backup Copy Job Overview report may show backup copy job sessions under the same backup job object if the sessions belong to different backup copy jobs having the same names and running on different backup servers.
• The Repository Details report only shows the latest repository used in the file share backup job.

Installing Veeam Management Pack for Microsoft System Center

For more information, refer to the Veeam Management Pack for Microsoft System Center installation guides, sections Installing Veeam MP for VMware, Installing Veeam MP for Hyper-V and Installing MP for Veeam Backup & Replication.

Uninstalling Veeam Management Pack for Microsoft System Center

For more information, refer to the Veeam Management Pack for Microsoft System Center installation guides, sections Uninstalling Veeam MP for VMware, Uninstalling Veeam MP for Hyper-V and Uninstalling MP for Veeam Backup & Replication.

Upgrading Veeam Management Pack for Microsoft System Center

Upgrade to v13.1 of Veeam Management Pack for Microsoft System Center is only supported from the prior version 9.1. The version was updated to 13.1 in this release to match the Veeam Data Platform overall versioning.

For more information, refer to the Veeam Management Pack for Microsoft System Center installation guides, sections Upgrading Veeam MP for VMware, Upgrading Veeam MP for Hyper-V and Upgrading MP for Veeam Backup & Replication.

Licensing

Veeam Management Pack for Microsoft System Center is licensed per CPU socket. A CPU socket is defined as a single physical processor chip on a vSphere host in the monitored environment. The Veeam Management Pack for Microsoft System Center solution does not take into account the number of cores on a physical CPU. For more information, refer to the Veeam Management Pack for Microsoft System Center pricing page.

A trial license key is sent to you automatically after downloading the product. The trial license is valid for 30 days and includes Basic technical support. When the trial ends, the monitoring features for Veeam Backup & Replication environment remain active, giving you the free edition of Veeam Management Pack for Veeam Backup.

To obtain a full license key, please refer to veeam.com/products/management-pack/pricing.html.

The perpetual license includes a one-year maintenance plan with Basic support. To renew or upgrade your maintenance plan, please contact Veeam Renewals at veeam.com/renewal.html.

Technical Documentation References

If you have any questions about Veeam Management Pack for Microsoft System Center, you may use the following resources:

• Product web page
• User guides
• Community forums

Technical Support

Veeam offers email and phone technical support for customers on maintenance and during the official evaluation period. For a better experience, please provide the following when contacting Veeam Customer Support:

• Version information for the product and its components.
• Error message and/or accurate description of the problem you are having.
• Log files.

To submit your support ticket or obtain additional information, please visit the Veeam Customer Support Portal.

Contacting Veeam Software

At Veeam Software, we pay close attention to comments from our customers — we make it our mission to listen to your input, and to build our products with your suggestions in mind. We encourage all customers to join Veeam R&D Forums and share their feedback directly with the R&D team.

Should you have a technical or licensing issue or question, please feel free to contact our Customer Support organization directly. We have qualified technical and customer support staff available 24/7 who will help you with any inquiry that you may have.

Customer Support

For the most up-to-date information about our support practices, business hours and contact details, please visit the Veeam Customer Support Portal.

Company Contacts

For the most up-to-date information about company contacts and office locations, please visit the Veeam Contacts Webpage.