In this article, we shall discuss how to Integrate Hyper-V [SCVMM] with Veeam Recovery Orchestrator. Please see how to install Veeam Recovery Orchestrator and Agents to VBR and VEM, and how to Create local Backup Repository and Add HyperV to VBR Inventory. System Center Virtual Machine Manager (VMM) centralizes and simplifies datacenter management by providing a single platform to configure, monitor, and control virtualization hosts, networking, storage, and deployment resources. Thereby, enabling administrators to efficiently provision and manage virtual machines and services across private clouds.

Note: A Hyper-V cluster can be added to the Veeam infrastructure and is ready to serve as a source and target for backups, replication, and other operations. Note that adding SCVMM servers to Veeam Backup & Replication is not required. You can read more about SCVMM support by Veeam from here.

VMM also integrates with hybrid environments via Azure Arc. This allows organizations to extend governance, automation, and security to cloud-managed workloads while maintaining full control of their on-prem infrastructure.

Please see How to upgrade Trellix ePolicy Orchestrator, Why you should not Upgrade Windows on an ePO Server, and Trellix ePolicy Orchestrator Installation on Windows Server.

Adding Microsoft Hyper-V or Cluster to VRO

To allow Orchestrator to connect to an SCVMM server, you must first install the SCVMM console on the machine that runs Orchestrator as described in Microsoft Docs. Keep in mind that the SCVMM version of the console must match the System Center version of the server. If you do not do this, you will not be able to integrate SCVMM with VRO.

Note: If the SCVMM server or standalone cluster that you want to connect to Orchestrator is added to a backup server, you must first upgrade the server or cluster to Veeam Backup & Replication version 12.3. Otherwise, the server or cluster will no longer be able to connect to the backup server, which may affect data protection. Also, see Upgrade Path and In-Place Upgrade for VBR v13 and Known Fixes.

But for Veeam Recovery Orchestrator, to collect data about Microsoft Hyper-V infrastructure objects. You must configure connections either to Microsoft System Center Virtual Machine Manager (SCVMM) servers or standalone clusters.

Note: Before adding a connection, ensure all Microsoft Hyper-V infrastructure objects are online. If you activate them afterward, Veeam Recovery Orchestrator may take up to 2 hours to synchronize and collect their data

Since I do not currently have a cluster, I have decided to “Integrate Hyper-V: Install System Center Virtual Machine Manager“.

To do this, navigate to the Administration page. Under Infrastructure, select Microsoft and click on Add as shown below.

Please see How to determine Windows Version or Edition and Build, how to Allow Password change for specific users in Exchange Server, and Concept of Ansible on Windows using Cygwin.

SCVMM Connection details

Enter the SCVMM connection details. Here you can use the DNS or IP address and then specify the credentials. Do not forget to click on Save.

As you can see, we have missed an important prerequisite that requires the installation of the VMM console on VRO.

Please see how to Periodic Scanning: How to schedule Windows Defender Antivirus to scan on Windows, how to Check if Windows Updates were installed, and Editions of MSSQL Server: What are the differences between various Editions of Microsoft SQL Server.

Install Virtual Machine Manager Console

To do this, I will access the TDASCVMM server from the TDAVRO server using the Run dialog (Win + R) . Then connect via the administrative share, for example: \\TDASCVMM\\c$ or \\192.168.2.29\\c$

I will copy the setup to the downloads folder

Will click on Install to proceed with the installation.

As you can see below, we are prompted with an error “To install the VMM management server. You must be logged on under a domain account that has administrative credentials on the local computer”.

Please see how to “Migrate Windows Servers from Hyper-V to Proxmox Correctly”, how to Add Synology NFS Storage to Proxmox VE for VMs and Backups., and how to Resize or Expand Proxmox Hard Drive.

You must be logged on to install VMM Server

To put just the SCVMM console on your non‑domain VRO server. You have to bypass the GUI and run setup in client mode from the command line, which does not require the machine to be domain‑joined.

Run the Installer with Domain Credentials

You can also try to run the Installer with Domain Credentials (run as a different user) as shown below.

Enter your domain credential and click on OK.

This method is similar to using the “runas” command via the command line as shown below

runas /user:DOMAIN\username setup.exe

Install the console from the command prompt

I employed this approach as it is very straight forward unlike the “runas” command above. To do this, open an elevated Command Prompt and change to the root of the setup file or ISO.

Then run the command below to install the VMM console. More information about the command can be found here.

setup.exe /client /i /IACCEPTSCEULA

As you can see, the command completed without errors.

Please, see Unable to connect to MSSQL Server after changing Server name, how to configure Windows server update services and Remote Desktop Services Setup on Windows Server.

Connect to the VMM Console

Since the VMM management server is not stored locally. We have to change from localhost to the remote server FQDN or IP Address, and then specify the credentials.

Please, see Handy Shutdown commands available in Windows, Office Configuration Analyser Tool (OFFCAT): Now Microsoft Support and Recovery Wizard, and

Re-attempt SCVMM integration with Veeam Recovery Orchestrator

Enter the SCVMM connection details. Here you can use the DNS or IP address and then specify the credentials. Do not forget to click on Save.

As you can see below, I have entered a local administrative credential. I will proceed and ensure I enter the right credential with the necessary privilege.

Note: For an account to be displayed in the Credentials list, it must be added to the configuration database as described in section

Have entered a domain credential to access and connect to VRO, and click Save.

As you can see, the status is currently pending.

Note that after you configure a connection to a standalone cluster or perform any infrastructure configuration changes, the changes may not appear in the Orchestrator UI immediately. The data synchronization process may take up to 15 minutes to complete.

From the image below, you can see that we have successfully added.

Next, I will show you how to create a recovery location in Veeam Recovery Orchestrator. With the infrastructure already configured, it is now ready to serve as a recovery location for orchestrated tasks.

I hope you found this article on how to integrate Hyper-V [SCVMM] with Veeam Recovery Orchestrator very useful. Please, feel free to leave a comment below.