Support for virtualization environments with Configuration Manager
Applies to: Configuration Manager (current branch)
Configuration Manager supports installing the client and site system roles on supported operating systems that run as a virtual machine in the virtualization environments in this article. This support exists even when the virtual machine host (virtualization environment) isn't supported as a client or site server.
For example, you use Microsoft Hyper-V Server 2012 to host a virtual machine that runs Windows Server 2012. You can install the client or site system roles on the virtual machine running Windows Server 2012. You can't install the client on the host running Microsoft Hyper-V Server 2012.
- Windows Server 2019
- Windows Server 2016 Note 1
- Microsoft Hyper-V Server 2016 Note 1
- Windows Server 2012 R2
- Microsoft Hyper-V Server 2012
- Windows Server 2012
- Microsoft Hyper-V Server 2008 R2
- Windows Server 2008 R2
Note 1: Nested virtualization
Configuration Manager doesn't support nested virtualization, which is new with Windows Server 2016.
Virtualization environment support
Each virtual computer needs the same or greater hardware and software requirements that you would use for a physical Configuration Manager computer.
To validate that your virtualization environment is supported for Configuration Manager, use the Server Virtualization Validation Program. It includes an online Virtualization Program Support Policy Wizard. For more information, see Windows Server Virtualization Validation Program.
Configuration Manager doesn't support Virtual PC or Virtual Server guest operating systems that run on Mac computers.
Configuration Manager can't manage virtual machines if they're offline. An offline virtual machine image can't be updated nor can inventory be collected by using the Configuration Manager client on the host computer.
No special consideration is given to virtual machines. For example, Configuration Manager might not determine whether an update has to be reapplied to a virtual machine image if the virtual machine has been stopped and restarted without saving the state of the virtual machine to which the update was applied.
Microsoft Azure virtual machines
Configuration Manager can run on virtual machines in Azure just as it runs on-premises within your data center. Use Configuration Manager with Azure virtual machines in the following scenarios:
Scenario 1: Run Configuration Manager on an Azure virtual machine. Use it to manage clients on other Azure virtual machines.
Scenario 2: Run Configuration Manager on an Azure virtual machine. Use it to manage clients that aren't running on Azure.
Scenario 3: Run different Configuration Manager site system roles on Azure virtual machines. Run other roles in your on-premises data center, properly connected to Azure.
The same Configuration Manager requirements for networks, supported configurations, and hardware requirements that apply to installing it on-premises also apply to installation on Azure virtual machines.
For more information, see Configuration Manager on Azure.
Configuration Manager sites and clients that run on Azure virtual machines are subject to the same license requirements as on-premises installations.