 This console makes use of the VMM PowerShell module to perform all of its tasks. It is purely a frontend for the VMM PowerShell module. VMM Management Server The management server is responsible for undertaking all actions. It is responsible for communicating with its agents on Hyper-V hosts, library servers, WSUS servers, and so on. VMM Library Server The library server contains all the physical files required for virtual and physical machines, including VHDX files, answer files, drivers for physical servers, application files, and so on. VMM Agent This is responsible for undertaking the required actions from the VMM Management Server. VMM PXE Server The PXE server is a Windows Deployment server that has the VMM agent server installed. It is solely used for bare metal deployment of Hyper-V hosts. VMM Update Server This is a WSUS server that has updates applicable to the servers under VMM's management. Chapter 1 The following diagram shows the components and where they would be installed: Virtual Machines Hyper-V Servers VMM Server Infrastructure Multiple WDS Multiple DHCP Servers Servers Highly Available VMM Multiple Domain WSUS Server Controllers Clustered File Server Clustered VMM Highly Available SQL Server (Failover cluster for VMM Library Management Server or AlwaysOn) VMM Console Installing Virtual Machine Manager VMM is capable of managing the alternative hypervisors: XenServer and VMware ESX/vSphere (via a VMware vCenter installation). For the smallest implementation, it is possible to install all of the components on a single server, including the VirtualManagerDB database. You have the option to make the installation of VMM highly available by using features such as SQL Server Failover Clustering, SQL Server AlwaysOn High Availability Groups, Failover Clustering for VMM Management Servers, Clustered File Servers for the VMM Library, and multiple Windows Deployment Servers. Deploying the required service accounts This recipe will provide you with the steps required to deploy the required service accoun