System Center VMM 2025 on Hyper-V with Veeam v13

This is a full walkthrough of standing up a System Center 2025 Virtual Machine Manager environment on a Windows Server 2025 Hyper-V cluster, then integrating Veeam Backup and Replication v13 for backup jobs and replica protection. Every step was run on real production hardware. Screenshots are included where they add value. The tone is engineer to engineer. No fluff.

What We Are Building

The target architecture is a standalone SCVMM 2025 management server running as a VM on the same Hyper-V cluster it manages. SQL Server 2022 runs on a separate VM, also on the cluster. Veeam Backup and Replication v13 connects through the SCVMM server to discover and protect the Hyper-V fabric.

Support Matrix

All of these are validated combinations. Microsoft explicitly supports VMM 2025 on Windows Server 2025 with SQL Server 2022 as the backend. The VMM server can run as a VM, but it must not have the Hyper-V role installed in the guest OS.

Part 1: SQL Server 2022 VM Build

The SQL VM is the foundation. Build it first, validate it, and move on. Do not try to install VMM until SQL is rock solid.

Recommended VM Baseline

SQL Build Steps

1. 1Deploy the SQL VM on the cluster. Assign a static IP, join it to the domain, confirm forward and reverse DNS registration.
2. 2Patch Windows Server 2025 completely. Reboot until there is no pending restart.
3. 3Install SQL Server 2022 Database Engine Services. A default instance is the simplest path for a new VMM deployment.
4. 4Use Windows authentication. Mixed mode is fine if your security standard requires it, but it adds nothing for a VMM-only database.
5. 5Enable TCP/IP in SQL Server Configuration Manager. Restart SQL services after the change.
6. 6If using the default port, confirm TCP 1433 is reachable from the future VMM server. If you use a non-default port, write it down and use it during VMM setup.
7. 7Grant the VMM install account the sysadmin server role on the SQL instance. This is required for the VMM installer to create the database.
8. 8Record the SQL server name, instance name (default or named), and the database name VMM will use. You will need all three during VMM setup.

Part 2: VMM 2025 VM Preparation

The VMM VM needs several prerequisites installed before you run the SCVMM setup wizard. Miss any of these and the installer will block you or produce warnings.

VM Baseline

Microsoft documents 4 GB as the minimum RAM for the VMM management server, but recommends 16 GB. The prerequisite checker flags a warning if the VM has less than 16 GB. The install will proceed either way, but you should not deploy a production VMM server with less than 16 GB.

Preparation Steps

1. 1Deploy the VMM VM on the cluster. Assign a static IP, join to domain, verify DNS.
2. 2Patch Windows Server 2025 fully. Reboot until clean. No pending restarts.
3. 3Install Windows ADK for Windows 11 and Windows Server 2025.
4. 4Install the Windows PE add-on for the same ADK version.
5. 5Confirm PowerShell 5.1 is present (ships with Server 2025).
6. 6Install the SQL Server Command Line Utilities (version 15 or later). Microsoft documents these as "not required for VMM installation," but the prerequisite checker flags a warning if they are missing. Install them to clear the warning and because sqlcmd is useful for post-install database validation.
7. 7Install the Microsoft ODBC Driver 17 or 18 for SQL Server. This is a dependency of the SQL Server Command Line Utilities, not a direct VMM prerequisite. If you installed the SQL CMD utilities, you likely need this for them to function.
8. 8Confirm network reachability from the VMM VM to the SQL VM on port 1433, and to all Hyper-V nodes over standard Windows management channels (WMI, WinRM, SMB).

Part 3: SCVMM 2025 Installation

Mount the System Center 2025 VMM media on the VMM VM and run setup.exe as Administrator.

Feature Selection

Select VMM management server. The VMM console is installed automatically with it. If you only need a remote console on a separate workstation, you can install the console alone on that machine later.

Prerequisite Warnings

The prerequisite checker will flag anything missing. In this build, three warnings appeared: insufficient memory (15998 MB vs 16000 MB recommended), SQL Server Command Line Utilities not installed, and a pending restart from the ADK installation.

The resolution: reboot to clear the pending restart, then install the SQL Server Command Line Utilities 15 from Microsoft. After both are resolved, click "Check prerequisites again" and the warnings drop to just the memory advisory. That one is safe to ignore.

Database Configuration

Point the installer at your remote SQL Server. Enter the SQL VM hostname, port 1433 (default), and credentials with sysadmin rights. Select "New database" and leave the name as VirtualManagerDB unless you have a reason to change it.

Service Account and Distributed Key Management

Choose the VMM service account carefully. Microsoft states that the identity of the VMM service account cannot be changed after installation without a full uninstall and reinstall. Your options are Local System, a domain account, or a Group Managed Service Account (gMSA). For production, gMSA is the recommended choice.

If using a traditional domain account, it needs Log on as a service and Replace a process level token rights on the VMM server. If using gMSA, enter the identity in YOURDOMAIN\gMSAAccount$ format and make sure the VMM VM has permission to retrieve the gMSA password.

Distributed Key Management (DKM) stores encryption keys in Active Directory. For a standalone VMM server, local storage is acceptable. For HA designs, DKM in AD is required.

Port Configuration

Accept the defaults unless your security team requires different ports. The default ports are well documented and expected by every integration that talks to VMM.

Library Configuration

The VMM library share holds ISO images, VM templates, hardware profiles, guest OS profiles, and scripts. The default share name is MSSCVMMLibrary at C:\ProgramData\Virtual Machine Manager Library Files. Accept the default or point it at a larger volume if you plan to store many ISOs.

Installation Summary and Install

Review the summary carefully. Every decision on this page is final or painful to change. Confirm the database target, the service account identity, the port assignments, and the library path.

Installation takes 10 to 20 minutes depending on storage performance. The wizard installs the VMM management server first, then the console.

Part 4: Post-Install Validation

Before you add a single host, validate the base VMM installation.

Connect to the VMM Console

After setup completes, check "Open the VMM console when this wizard closes" and click Close. On the Connect to Server dialog, the default is localhost:8100. Use current Windows session identity for the first connection.

Validation Checks

Part 5: Onboarding the Hyper-V Cluster

The existing Windows Server 2025 Hyper-V cluster was already built and validated in Failover Cluster Manager before VMM entered the picture. All nodes were online, CSVs were healthy, and the cluster quorum was stable. If your cluster is not in that state, stop here and fix it before involving VMM.

Add Hyper-V Hosts and Clusters

In the VMM console, navigate to Fabric. Click Add Resources and select Hyper-V Hosts and Clusters.

Resource Location

Select "Windows Server computers in a trusted Active Directory domain." This is the standard path for domain-joined Hyper-V hosts.

Credentials

Provide credentials with local administrator rights on all Hyper-V hosts. You can use a Run As account (which persists in VMM for future management) or enter credentials manually (one-time use during onboarding).

Discovery Scope

Enter the FQDNs of your Hyper-V hosts, one per line. You can also enter the cluster name or a single node and let VMM discover the cluster relationship, but providing all host FQDNs explicitly is the most reliable method.

Target Resources and Host Settings

After discovery completes, VMM presents the discovered computers. You will see the Hyper-V hosts and the cluster object itself, all showing Windows Server 2025 Datacenter and Hyper-V as the hypervisor. Select all of them.

On the Host Settings page, assign the cluster to a host group. "All Hosts" is acceptable for initial setup. You can create a more structured host group hierarchy later (for example, All Hosts > Production > HyperV-2025) for placement and delegation.

Click Next, review the summary, and finish the wizard. Wait for the jobs to complete. Verify all nodes, CSVs, and hosted VMs appear in the VMM fabric view.

Part 6: Day-1 Fabric Configuration

Once the cluster is onboarded, complete these initial fabric tasks before handing the platform over to workload teams.

1. 1Create the permanent host group structure for placement and delegation.
2. 2Review cluster reserve settings so the placement engine reflects your node-failure tolerance policy.
3. 3Define logical networks for management, live migration, cluster, storage, and workload networks.
4. 4Define VM networks, VLAN mappings, IP pools, and MAC pools.
5. 5Populate the library with ISO images, VM templates, hardware profiles, and guest OS profiles.
6. 6Set host reserves and placement settings to prevent overcommit.
7. 7If update remediation will be used later, integrate WSUS only after the core VMM fabric is stable.

Part 7: Veeam Backup and Replication v13 Integration

With the Hyper-V cluster onboarded into VMM and the fabric validated, the next step is connecting Veeam Backup and Replication v13. Veeam supports two paths for Hyper-V infrastructure: adding the SCVMM server so Veeam discovers everything through VMM, or adding the cluster directly. Since you just built SCVMM and your fabric is already managed through it, the VMM path is the natural choice. Veeam will enumerate the entire VMM fabric and discover all managed clusters and VMs automatically.

Adding SCVMM to Veeam

1. 1Open the Veeam Backup and Replication console. Navigate to Backup Infrastructure > Managed Servers.
2. 2Click Add Server and select Microsoft Hyper-V. At the server type step, select Microsoft System Center Virtual Machine Manager.
3. 3Enter the VMM server FQDN or hostname.
4. 4Provide credentials with administrative rights on the VMM server. Veeam needs to query the VMM fabric for host and VM inventory. If some Hyper-V hosts use different credentials, you can specify per-host credentials after onboarding.
5. 5Veeam will connect to VMM, enumerate all managed Hyper-V clusters and hosts, and deploy its agent components to each host automatically. Let this complete without interruption.
6. 6After the VMM server appears in Managed Servers, expand it to verify all cluster nodes show as online and all VMs are visible in the inventory.

The SCVMM path has a practical advantage: if you add or remove hosts from the VMM fabric later, Veeam picks up the changes automatically. You do not have to manually update the Veeam server list every time the cluster membership changes. It also gives you VMM-aware placement during restore and replica operations.

Configuring a Backup Job for Hyper-V

Veeam Hyper-V backup jobs use a different processing model than VMware jobs. Hyper-V backups run on-host by default, meaning the Veeam agent on each Hyper-V node processes the VMs locally and sends data directly to the repository. Off-host mode is available if you want to redirect processing through a dedicated backup proxy, but on-host is the default and performs well for most environments. One sizing detail to plan for: each running backup task (one task per virtual disk) consumes up to 2 GB of RAM on the Hyper-V host. If the host runs out of available memory during the backup window, it will start paging and everything slows down. Factor this into your concurrent task limits per host.

1. 1In the Veeam console, go to Home > Backup Job > Microsoft Hyper-V.
2. 2Name the job. Use a naming convention that makes it obvious what cluster and workload type the job covers.
3. 3Add VMs. You can add individual VMs, host groups, or entire clusters. Adding at the cluster level ensures new VMs are automatically protected.
4. 4Select the backup repository. Confirm the repository has enough capacity for the retention policy you plan to set.
5. 5Set the retention policy. For production workloads, 14 restore points is a reasonable starting point.
6. 6On the Guest Processing page, enable application-aware processing if the VMs run applications with VSS writers (SQL Server, Exchange, Active Directory). Provide guest OS credentials for the in-guest processing agent.
7. 7Schedule the job. Run it once manually to validate the full backup chain before relying on the schedule.

Configuring a Replica Job for Hyper-V

Veeam replication for Hyper-V creates a VM replica on a target Hyper-V host or cluster. The replica is a near real-time copy that can be started manually or through an automated failover plan. This is not Hyper-V Replica (the built-in Windows feature). This is Veeam-managed replication with its own change tracking, seeding, and failover orchestration.

1. 1In the Veeam console, go to Home > Replication Job > Microsoft Hyper-V.
2. 2Name the job. Include "Replica" in the name so it is not confused with a backup job in the job list.
3. 3Add the source VMs. Same selection model as backup jobs: individual VMs, host groups, or clusters.
4. 4Select the target Hyper-V host or cluster. This is where the replica VMs will be created. For DR, the target should be in a different failure domain from the source.
5. 5Map the target datastore. Select the CSV or local volume where replica VHDX files will land on the target hosts.
6. 6Set restore points. Each restore point is a point-in-time you can failover to. More points mean more storage consumption on the target.
7. 7Configure network mapping if the source and target are on different network segments. This tells Veeam which virtual switch and VLAN to attach the replica NICs to during failover.
8. 8Enable replica seeding if you have a large initial dataset and want to pre-stage the first sync using a backup file or portable media. This avoids pushing the full initial copy across the network.
9. 9Schedule the job. Replica jobs typically run more frequently than backup jobs. Every 15 minutes to every hour is common depending on RPO requirements.

Part 8: Common Errors and How to Fix Them

Error 10421: User account is the same as the VMM service account

This error fires when you try to add hosts using the same credential that VMM runs under. The fix is simple: use a different administrative account for host onboarding. Create a Run As account in VMM that maps to a domain admin or a dedicated VMM host management account.

Error 23008: Live migration failed due to credential issues

This appears when VMM attempts a live migration and the credential delegation chain breaks. The Virtual Machine Management Service cannot establish a connection for migration because no credentials are available in the security package. Common causes: constrained delegation (Kerberos) is not configured between the Hyper-V hosts, or the VMM service account does not have delegation rights. Fix: configure constrained delegation for the Hyper-V hosts in Active Directory, specifically for the Microsoft Virtual System Migration Service and CIFS SPNs.

Discovery finds no computers

If the Add Resource Wizard returns "There were no computers discovered based on your inputs," check these items in order: the VMM service account has read access to the target AD domain, WinRM is enabled and reachable on the target hosts (Test-WSMan from the VMM server), the hostnames or FQDNs you entered are correct and resolve in DNS, and the credential you provided has local admin rights on the target machines.

Prerequisite: SQL Server Command Line Utilities not found

The VMM prerequisite checker warns if the SQL Server Command Line Utilities (sqlcmd) are not installed. This is a warning, not a blocker. The install will proceed without them. But the warning will persist until you install the SQL Server 2019 or 2022 Command Line Utilities package from Microsoft. Version 15.x or later satisfies the check. The ODBC Driver for SQL Server is a dependency of the CMD utilities and must be installed first.

VMM database pointed at the wrong server

If you accidentally enter the VMM server hostname instead of the SQL server during database configuration, the installer will either fail to connect or create a local database on a SQL instance you did not intend to use. There is no way to change the database target post-install without reinstalling VMM. Double-check the Server name field before clicking Next.

VMware Tools on Hyper-V VMs

If you are migrating a Veeam server or other workloads from a VMware environment to Hyper-V, VMware Tools will fail to run on Hyper-V guests. Uninstall VMware Tools before or after the migration. The Veeam Mount Service and other Veeam components do not depend on VMware Tools for Hyper-V operations.

---