This topic describes network requirements and considerations for installing System Center Virtual Machine Manager (VMM) 2008.
Network Connections
Because of the large size of virtual machine files, it is a best practice to connect all computers in a VMM configuration with at least a 100 MB Ethernet connection. Using a gigabit Ethernet connection and a more powerful processor for the VMM server than the recommended processor can further improve performance.
Domains
Before installing the VMM server, you must join the computer to a domain in Active Directory. All Windows Server-based virtual machine hosts must also be joined to Active Directory domains. A Windows Server-based host can be in a domain separate from the VMM server's domain and a host can be in a domain with a two-way trust with the VMM server’s domain or in a domain that does not have a two-way trust with the VMM server’s domain.
For hosts in perimeter networks, you must install a VMM agent locally on that host, configure the firewalls as discussed later in this topic, and then add the host to VMM.
Firewalls
Virtual machine hosts and library servers must have access to the VMM server on the ports specified during VMM server setup. This means that all firewalls, whether software-based or hardware-based, must be configured appropriately.
Computer firewalls
When you install the VMM server, you specify which ports the VMM server uses to communicate with the VMM Administrator Console, for communications with and file transfers between hosts and library servers. By default, these ports are 8100, 80, and 443, respectively. If you install the VMM server on a computer that is using Windows Firewall, the Setup Wizard automatically adds firewall port exceptions to Windows Firewall.
When you install the VMM Self-Service Portal, you specify which port the self-service users use to connect to the portal. By default, this port is 80.
When you add a computer that is using Windows Firewall as a host or a library server, VMM automatically adds firewall port exceptions to Windows Firewall on that computer. VMM adds firewall exceptions for the ports that were specified during the VMM server and the VMM Self-Service Portal installation.
 Note |
|---|
| The only firewall that VMM configures automatically is Windows Firewall. To configure any other firewall, refer to the instructions provided by the firewall's manufacturer. |
Network firewalls
To add a host that is located behind a network firewall, you must install a VMM agent locally on that host. When you install a VMM agent, you specify which ports the agent uses to connect to and transfer files between the VMM server and the host. The ports you specify for the agent must identically match the ports that you specified during the VMM server installation. By default, those ports are 8100, 80, and 443, respectively. If you install a VMM agent on a host that is using Windows Firewall, Setup automatically opens the specified ports in the Windows Firewall on the host.
Before you can add the host and use VMM to manage it across the network firewall, you need to manually open the specified ports in the network firewall to allow communication and file transfers between the VMM server and the host.
| Note |
|---|
| The only firewall that VMM configures automatically is Windows Firewall. To configure any other firewall, refer to the instructions provided by the firewall's manufacturer. |
See Also
For the most up-to-date Setup information, go to Virtual Machine Manager 2008 Deployment. To find additional Virtual Machine Manager 2008 documentation, go to the Virtual Machine Manager 2008 TechCenter Library.