Guided Consolidation requires that at least one host is managed through vSphere. It also requires that you provide credentials to the target physical systems.

Guided Consolidation can convert systems that are configured to any locale. Before you use the feature, ensure that the following prerequisites are met:

Guided Consolidation server must be installed on a host that meets the following system requirements:

Located within the company's network and have access to target systems for performance data collection.

The Guided Consolidation host must have a name that can be resolved from any machine on the network

The Guided Consolidation host must have a static IP address.

Located in a domain and can access the Active Directory server.

One of the following operating systems installed:

Windows 2003 Server SP2

Windows XP Professional SP3

Windows Server 2008 (Ensure that Computer Browser Windows Service is enabled)

Windows Vista (Ensure that Computer Browser Windows Service is enabled)

.NET Framework 3.0 SP1 installed

Windows Management Instrumentation (WMI) and Remote Registry installed, enabled, and running on host and all target systems

Minimum 1000MHz CPU

Minimum 1.8GB available RAM

3GB free disk space

Authorized and able to connect to all the servers to be analyzed and consolidated using the protocols and ports listed in the section below, Network Connections.

Access to general purpose ports that Windows uses for most of its communications for file/print sharing and authentication

The following operating systems on systems targeted for analysis are supported:

Windows 2000 Professional/Server/Advanced

Windows XP Professional (32 bit and 64 bit)

Windows Server 2003 Standard/Web/Enterprise (32 bit and 64 bit)

Windows Vista (32 bit and 64 bit)

Windows Server 2008 (32 and 64 bit)

Credentials with Log on as service privileges on the system where the Guided Consolidation server is installed must be provided at the time of installation. If Active Directory is deployed on your network, the provided credentials must also have sufficient privileges to query the Active Directory database.

File and Printer Sharing must be enabled on the system where Guided Consolidation is installed and enabled on all systems targeted for analysis. Windows XP Simple File Sharing is insufficient.

Guided Consolidation extension must be installed, enabled, and running on the vSphere Client.

At least one datacenter inventory object exists.

At least one host is registered with vCenter Server.

Guided Consolidation requires administrator access to the systems selected for analysis. Specifically, the vCenter Collector Service uses these credentials to connect to and retrieve configuration and performance data from the physical systems under analysis. Accounts must be fully-qualified and can be any of the following:

account of the target system.

account of the target system domain.

account of a trusted domain of the target system.

The Guided Consolidation server must have access to the ports listed in the Network Connections.

Network Connections





MS Windows




Microsoft DCE Locator service, also known as End-point Mapper.

DHCP Server

DNS Server

WINS Server




NetBIOS names service.

Firewall administrators frequently see larger numbers of incoming packets to port 137.

This is because of Windows servers that use NetBIOS (as well as DNS) to resolve IP addresses to names using the gethostbyaddr() function. As users behind the firewalls visit Windows-based Web sites, those servers frequently respond with NetBIOS lookups.

WINS Server

DNS Server




NetBIOS datagram

Used by Windows, as well as UNIX services (such as SAMBA).

Port 138 is used primarily by the SMB browser service that obtains Network Neighborhood information.




NetBIOS Session

Windows File and Printer sharing.




DNS Direct Hosting port.

In Windows 2000 and Windows XP, redirector and server components now support direct hosting for communicating with other computers running Windows 2000 or Windows XP.

Direct hosting does not use NetBIOS for name resolution. DNS is used for name resolution, and the Microsoft networking communication is sent directly over TCP without a NetBIOS header. Direct hosting over TCP/IP uses TCP and UDP port 445 instead of the NetBIOS session TCP port 139.

Active Directory