anagement HTTPS 443 (maximum value: This port is changed server to in-guest 32768) using BITS. agent (VMM to virtual machine data channel) VMM management HTTPS 443 (maximum value: This port is changed server to VMM agent on 32768) using BITS. Windows server-based host (data channel for file transfers) VMM management server to remote Microsoft SQL Server database Console connections This port is changed (RDP) to virtual using the VMM machines through console. Hyper-V hosts (VMConnect) Remote Desktop to This port is changed on virtual machines the virtual machine. VMM management WS-Management This port is changed server to VMM agent on when the VMM is set Windows server-based host (control channel) VMM management WS-Management server to in-guest agent (VMM to virtual machine control channel) VMM management WS-Management server to VMM agent on Windows server-based host (control channel- VMM console to VMM This port is changed management server when the VMM is set Planning the Virtual Machine Manager Purpose Protocol Port number(s) Where to change VMM console to VMM This port is changed management server when the VMM is set (HTTPS) Windows PE agent to This port is changed VMM management when the VMM is set server (control channel) VMM console to VMM This port is changed management server when the VMM is set (NET.TCP) WDS provider to VMM This port is changed management server when the VMM is set VMM console to VMM This port is changed management server when VMM is set up. (HTTP) Windows PE agent to This port is changed VMM management when the VMM is set server (time sync) VMM management PowerShell server to Cluster PowerShell interface The most critical elements in these tables are the networking layouts. For Hyper-V Network Virtualization, you need to ensure the VLANs and subnets in use are large enough to cope with the required workloads for your environment. It is absolutely critical that all the information is collated and the scope and purpose of the installation is formalized and agreed upon. This ensures that a