Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Network Requirements for VMM

Updated: March 11, 2010

Applies To: Virtual Machine Manager 2008, Virtual Machine Manager 2008 R2, Virtual Machine Manager 2008 R2 SP1

This topic describes network requirements and considerations for installing System Center Virtual Machine Manager (VMM) 2008 or VMM 2008 R2.

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. For VMM 2008 R2, you can install the VMM server in a Windows Server 2008, Windows Server 2008 R2, or Windows Server 2003 Active Directory domain. For VMM 2008, you can install the VMM server in a Windows Server 2008 or Windows Server 2003 Active Directory domain. The VMM server cannot be installed in a Windows 2000 Server Active Directory domain.

In a Windows Server 2003 domain, a Windows Server 2003 domain functional level is required. For information about features supported at the Windows Server 2003 functional level and guidance on raising the functional level, see Functional Levels Background Information (http://go.microsoft.com/fwlink/?LinkId=184527).

ImportantImportant
We recommend that you migrate your Active Directory infrastructure to Windows Server 2008 R2 or, for VMM 2008, to Windows Server 2008 as soon as possible. Microsoft extended support for Windows 2000 Server is to be retired on July 13, 2010. For help with planning your migration strategy from Windows 2000 Server to Windows 7, Windows Server 2003, Windows Server 2008, or Windows Server 2008 R2, see the Windows 2000 End-of-Support Solution Center (http://go.microsoft.com/fwlink/?LinkId=184536).

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 Windows Server-based 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. For more information about installing a VMM agent, see Installing a VMM Agent Locally on a Host.

For additional information about domain configurations that are supported for managed virtual machine hosts, see Adding Hosts (http://go.microsoft.com/fwlink/?LinkId=121818).

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. 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. For more information about ports used in VMM, see VMM Ports and Protocols (http://go.microsoft.com/fwlink/?LinkID=128912).

noteNote
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. 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. For more information about ports used in VMM, see VMM Ports and Protocols (http://go.microsoft.com/fwlink/?LinkID=128912).

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.

noteNote
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

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.