The Host Group is not configured correctly
The information in this article applies to:
Visual Studio Team Foundation Server 2010
Visual Studio 2010 Lab Management
Windows Server 2003 and Windows Server 2008
Team Foundation Server Complete Health Check
Visual Studio Lab Management Health Check
The Best Practices Analyzer tool for Team Foundation Server checks the configuration of host groups and Hyper-V hosts defined for a team project collection. The tool logs the information that it gathers in the tree report under the Host Group Checks node**.** You can locate the Host Group Checks node by expanding Team Foundation Server Complete Health Check, expanding Team Foundation Server, expanding Team Project Collections, expanding a named project collection, and then expanding Lab Management.
In order to use Lab Management, you must resolve all errors. You do not have to resolve warnings.
In this topic
.gif "Information icon")
Information Messages.gif "Warning icon")
Warning Messages.gif "Error icon")
Error Messages
Information Messages
An information message appears if one of the following conditions is true:
Required software patch is installed on Hyper-V host
Unable to retrieve the status of Hyper-V host from Virtual Machine Manager
Warning Messages
A warning appears if one of the following conditions is detected:
Access Not Available Warnings
An error occurred while performing checks for the host group
An error occurred while performing for the Hyper-V host
Cannot access the Hyper-V host
Cannot determine if the required software patch is installed on the Hyper-V host
Cannot access Windows Management Instrumentation (WMI) on the Hyper-V Host
To resolve these warnings, check that the servers are operational and that the user who is running the scan has the necessary permissions to access the servers in the host group. For more information, see Access is not available.
System Requirement Warnings
Recommended reserve RAM is not present on the Hyper-V host
Recommended reserve hard disk space is not present on the Hyper-V host
Sufficient RAM is not present on the Hyper-V host
Sufficient hard disk capacity is not present on the Hyper-V host
To resolve these warnings, upgrade the specified host according to the "System Requirements" provided on the following Microsoft Web site: Configuring Lab Management for the First Time.
Software Requirement Errors and Warnings
Different versions of operating systems are installed on the servers in the host group
A best practice is to install the same version of operating system on all hosts in a host group. You may want to check the installed operating systems on the Hyper-V hosts and upgrade where indicated.
Required software patch is not installed on the Hyper-V Host
For each host that is running Windows Server 2008 SP2, download and install the hot fix from the Microsoft Web site: A Hyper-V differencing disk that you create in Windows Server 2008 R2 cannot be used in Windows Server 2008.
You must install this hot fix to enable certain kinds of virtual machines created on Windows Server 2008 R2 to be used on Windows Server 2008 SP2 hosts. For more information, see the section "Set Up and Configure Hyper-V Hosts" on the Microsoft Web site: Configuring Lab Management for the First Time.
Required software patches are not installed on the host
To correct this condition, click Start, point to All Programs, and click Windows Update.
Recommended Windows Remote Management settings are not configured on the host
To correct this condition, perform the tasks indicated in "Improve the Reliability of WinRM" on the following Microsoft Web site: How to: Change the Host Groups for Your Team Project Collections.
System Configuration Warnings
Host is not available for placement
Because the named host is not available for placement, virtual machines that are created by Lab Management will not be deployed on this host. You can make the host available for placement by changing the Host Properties in the SCVMM Administration Console. For more information, see the section "Set Up and Configure Hyper-V Hosts" on the Microsoft Web site: Configuring Lab Management for the First Time.
Multiple virtual machine paths are present on the Hyper-V Host for placement
When multiple virtual machine paths are present for placement on a Hyper-V host, Lab Management chooses the one with the maximum disk space, but does not use the sum total of free space on various paths to deploy virtual machines.
No host groups have been added to the team project collection
In order to support testing using the virtual lab for the named project collection, you must configure the collection with at least one host group. For more information, see the following Microsoft Web site: How to: Change the Host Groups for Your Team Project Collections.
No Hyper-V hosts have been added to the host group
In order to support testing using the named host group, you must configure the host group with at least one Hyper-V host. For more information, see There are no Hyper-V hosts present in the Host Group provided later in this topic.
The Hyper-V host with the largest drive is not configured as available for placement
A best practice is to configure the Hyper-V host with the largest drive as one of your placement paths. You can add the placement path of the named Hyper-V host from the Host Properties window in the SCVMM Administrators Console.
Unencrypted file transfers are not allowed for the Host Group
There are no Hyper-V hosts present in the Host Group
To resolve this warning, add at least one Hyper-V host to the host group that is named in the error message. You must add at least one Hyper-V host in a host group to deploy the virtual machines using Lab Management. For more information, see the following page on the Microsoft Web site: How to Add Hosts in an Active Directory Domain.
To add virtual machine hosts in a domain
Open Virtual Machine Manager Administrator Console.
Click Start, point to All programs, point to Microsoft System Center, point to Virtual Machine Manager 2008 R2, and then click Virtual Machine Manager Administrator Console.
In the Connect to Server dialog box, type localhost or the name of the VMM Server, and click Connect.
Add the HyperVHost machines to a host group in VMM. In any view in the VMM Administrator Console, in the Actions pane on the right side, click Add host. Click Next in all except the following pages of the wizard:
On the Select Host Location page, click Windows Server-based host on an Active Directory domain. To add hosts on a trusted domain, type the credentials for a domain account with administrative rights on all hosts you want to add. Click Next.
On the Select Host Servers page, in the Domain box, type the fully qualified domain name (FQDN) of the hosts you want to add.
In the Computer name box, type the NetBIOS name, the IP address, or the fully qualified domain name (FQDN) of a host in the specified domain.
To add a host in a different domain, change the value in the Domain box, and then enter the NetBIOS name.
If the host is in a disjointed namespace, use the host’s fully qualified domain name (FQDN) and select the Skip the Active Directory name verification check box.
On the Configuration Settings page, do the following:
In the Host group list, select a host group that will contain the hosts or host cluster, or accept the default host group, All Hosts, which is the parent host group of all hosts and host groups.
If one or more of the computers that you are adding is a host or a library server that is currently being managed by another VMM server, select the Reassociate host with this Virtual Machine Manager server check box to associate those hosts with the current VMM server.
On the Summary wizard page, click Add Hosts.
참고
It is recommended that you configure a separate host group for each team project collection. For example, if you plan to configure Lab Management in two project collections in Team Foundation Server, create two host groups in Virtual Machine Manager and allocate the hosts to each host group.
Unencrypted File Transfers are not allowed for the Host Group
To improve the performance of virtual machine transfers, you should allow unencrypted file transfers for the named host group configured for the named team project collection.
To resolve this warning, update the properties for the host group that is named in the error message. This allows unencrypted file transfers.
참고
If you allow unencrypted files, the protocol changes from https to http, which is less secure.
For more information, see the following topics on the Microsoft Web site:
For information about how to allow unencrypted file transfers, see the procedure "To improve performance of VM transfers" in the section "Install and Configure SCVMM" in the topic Configuring Lab Management for the First Time.
To allow unencrypted file transfers for Host Group
On the Application Tier, in the Virtual Machine Manager Administrator Console, do the following:
Click Start, point to All programs, point to Microsoft System Center, point to Virtual Machine Manager 2008 R2, and then click Virtual Machine Manager Administrator Console.
On the Connect to Server dialog box, type the name of the VMM Server, and click Connect.
In the Virtual Machine Manager Administrator Console, in the lower-left navigation window, select Hosts.
Right-click the name of the host that is specified in the error message in the Hosts tree, and then click Properties.
Select the check box Allow unencrypted file transfers.
Error Messages
When a host group is not configured correctly on the System Center VMM, one or more of the following errors might appear:
A host group is no longer configured in System Center Virtual Machine Manager (SCVMM)
The named host group no longer appears in the configuration of SCVMM. You might want to verify if it has been incorrectly deleted, and if it has been incorrectly deleted, re add it to the SCVMM. For more information, see " Configure SCVMM" on the Microsoft Web site: Configuring Lab Management for the First Time.
A host group is no longer configured in System Center Virtual Machine Manager (SCVMM)
An unsupported operating system is installed on the Hyper-V Host (Error)
Host is part of a non-trusted domain, a host cluster, or is on a perimeter network
To resolve these errors, you must make sure that the host is part of a trusted domain, is not part of a host cluster, and is not on a perimeter network. Lab Management does not support hosts that are in non-trusted domains, or are configured as part of a host cluster, or resides on a perimeter network.
Network Location for the Hyper-V host is not configured correctly
Hyper-V host status from System Center Virtual Machine Manager (SCVMM): %OverallState%
The status of the named Hyper-V host indicates that it might not be running for the named host group and project collection. You should make sure that the host is running correctly by opening the SCVMM Administrator Console.
The service account for Team Foundation Server does not have appropriate permissions on the Hyper-V host
Virtualization software is not updated on the Hyper-V host
To create and run virtual machines, you must resolve all errors for Lab Management.
An unsupported operating system is installed on the Hyper-V Host
To resolve this error, update the operating system where the Hyper-V Host is installed to a supported operating system. Only the following operating systems are supported on the Hyper-V Host:
Windows Server 2008 R2 operating system (Hyper-V 64-bit, Standard, Enterprise, and Datacenter Editions)
Windows Server 2008 R2 (Server Core installation, Standard, Enterprise, and Datacenter Editions)
Windows Server 2008 operating system (Hyper-V 64-bit, Standard, Enterprise, and Datacenter Editions with Service Pack 2)
Windows Server 2008 (Server Core installation, Standard, Enterprise, and Datacenter Editions with Service Pack 2)
To learn about the system requirements for Lab Management, see the section "System Requirements" on the following page on the Microsoft Web site: Configuring Lab Management for the First Time.
Host Group is not present in System Center Virtual Machine Manager (SCVMM) server
The Host Group that was added to a team project collection is not present in VMM server. This could occur for one of the following reasons:
The host group has been removed from the VMM Server.
The host group has been deleted and then re-added to the VMM Server.
Make sure that the host group that is named in the error message is correctly configured in your SCVMM Server. For more information, see the following topics on the Microsoft Web site: How to Create a Host Group and the section "Set Up and Configure Hyper-V Hosts" in Configuring Lab Management for the First Time.
Network Location for the Hyper-V host is not configured correctly
To correct this error, review the network location assigned to the host that is named in the error message. Make sure that the network location is the same for all hosts and that it is configured in the Team Foundation Server Application Tier for Lab Management. For more information, see "Set Up and Configure Hyper-V Hosts" on the Microsoft Web site Configuring Lab Management for the First Time.
To view or update the network location for a Hyper-V host
In the Virtual Machine Manager Administrator Console, in the lower-left navigation window, select Hosts.
For each host that you added to VMM, right-click the host name in the Hosts tree, and then click Properties.
In the Host Properties window, click the Hardware tab.
In the left navigation pane under Network Adapters, click the network adapter that is connected to the physical network. If multiple network adapters are connected to the physical network, select the one that is connected to the same network as VmmMachine.
For that network adapter, view the Network location in the right-side pane.
If the network location is empty, you might have selected the wrong adapter or your host might not have been set up correctly. To correct the configuration, see the following page on the Microsoft Web site: How to: Set Up and Configure Hyper-V Hosts.
참고
Make sure that the value entered in Network location is the same for all hosts that you added.
The network location should be the same as the network location that is specified for the configuration for the Application Tier for Lab Management.
The service account for Team Foundation Server does not have appropriate permissions on the Hyper-V host
To resolve this error, you must add the Team Foundation Server service account as a local administrator on the Hyper-V host. For more information, see "Set Up and Configure Hyper-V Hosts" on the Microsoft Web site Configuring Lab Management for the First Time.
To add the in Team Foundation Server service account as a local administrator
Click Start, point to Administrative Tools, and then click Computer Management.
In the Computer Management console, expand the Local Users and Groups node.
In the left pane, click Groups and in the right-side pane double-click Administrators.
In Administrators Properties dialog box, click Add.
In the Select Users, Computers, or Groups dialog box, in the Enter the object names to select text box:
Type the Team Foundation Server service account. This can be retrieved from the Team Foundation Administration Console under the Application Tier summary.
This account is required to give Team Foundation Server access to the physical host machine.
Click OK.
Click OK to close the Computer Management console.
Virtualization software is not updated on the Hyper-V host
To correct this error, connect to the VMM server named in the error message using the VMM Administrator Console and check the status of the host. You must use the VMM 2008R2 VMM Agent on Hyper-V host.
For information about how to install recommended updates and to verify that Hyper-V is installed correctly, see the following pages on the Microsoft Web site:
"Set Up and Configure Hyper-V Hosts" in Configuring Lab Management for the First Time.
In addition, you can use Windows Update to keep your Hyper-V host up-to-date.