How to Add Hosts on a Perimeter Network
Updated: August 14, 2009
Applies To: Virtual Machine Manager 2008, Virtual Machine Manager 2008 R2, Virtual Machine Manager 2008 R2 SP1
Before you can add a host that is on a perimeter network (also known as a screened subnet) to Virtual Machine Manager (VMM), you must install an agent locally on the host. For information about installing a VMM agent locally, see Installing a VMM Agent Locally on a Host (http://go.microsoft.com/fwlink/?LinkId=121006).
When you install a VMM agent locally on a host, the Agent Setup Wizard prompts you for an encryption key and other information the VMM server needs to access and manage the host. The wizard uses the key you provided to encrypt the credentials and the other access information into a security file that you use when you add the host to VMM.
The wizard also creates a local agent service account that is named SCVMMxxxxxxxxxx (where xxxxxxxxxx is a sequence of random letters and numbers) and generates a random password. The VMM server uses this account to communicate with the host. After some time, depending on your Group Policy, the password might expire for this auto-generated account (or for another account that you might have used instead), and the VMM server will no longer be able to communicate with the host. When this occurs, in the VMM Administrator Console, in Hosts view, the host will have a Status of Needs Attention, and in Administration view, in Managed Computers, the host will have an Agent Status of Access Denied. To avoid or correct this, you must change the credentials for the agent on the Credentials tab of the Host Properties dialog box. For more information, see How to Set Credentials for Communicating with a Host.
Virtual machines that have been deployed on a host on a perimeter network cannot be migrated to hosts in the internal network or to other hosts on a perimeter network.