--- title: "Add a hypervisor node" description: "Add a VMware ESXi or other hypervisor for agentless scanning." product: "Guardian" edition: "Classic" type: "workflow" url: "https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/add-a-single-node/agentless/hypervisor-node/" --- # Add a hypervisor node Add a VMware ESXi or other hypervisor for agentless scanning. Guardian supports multiple types of Hypervisor nodes. For example, you can add VMware ESXi 5.1 nodes, ESXi 6.5 nodes, ESXi 8.0 nodes, and more. Applies to: `Guardian Classic` ## Add a Hypervisor node Adding a Hypervisor node to your Guardian instance lets you monitor and track the configuration of a virtualization host. !!! warning The following process assumes that you already have a Windows Connection Manager configured within your Guardian instance. For more information, see [Windows Connection Manager](https://docs.cloudhouse.com/guardian/classic/inventory/connection-managers/connection-managers/windows/windows-connection-manager/index.md). To add a Hypervisor node for Agentless scanning, complete the following steps: 1. In the Guardian web application, navigate to the **Add Nodes** tab (**Inventory** > **Add Nodes**). The **Add Nodes** page is displayed. ![Add nodes tab](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/add-nodes/single-nodes/add-nodes-tab.png) 2. Type the name of the Hypervisor node you want to add in the search bar. 3. Select the node type you want to add and click the **Go Agentless** button to proceed. The **Connect Agentlessly to [Node Type]** page is displayed. ![Go agentless hypervisor](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/add-nodes/single-nodes/go-agentless-hypervisor.png) 4. Here, complete the following options: ![Connect agentlessly hypervisor](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/add-nodes/single-nodes/connect-agentlessly-hypervisor.png) **Connection Method** drop-down list : The connection protocol to be used. This is automatically set to 'WinRM' for this node type. !!! note This option is only displayed if you have the **SSH** feature enabled. If not, 'WinRM' is set by default. This is an optional feature that must be enabled. **Connection Manager group** drop-down list : The Connection Manager group that is responsible for scanning your node. Select a Connection Manager group from the drop-down list. **Node Name** field : The name of the node. The value you enter here will be used as the display name in Guardian. **Hostname / IP Address** field : The hostname or IP address of your node. !!! note Typically, this is the fully qualified domain name (**FQDN**). However, it could also be the IP address. **Port (Optional)** field : The port number for the HTTP or HTTPS connection. By default, port 80 is used for unsecured connections (HTTP) and port 443 for secured connections (HTTPS). You can specify a different port if needed. **Guardian Credentials Vault** radio button : Option to use credentials stored in the Guardian vault. Select this option to display the **Credentials** drop-down list, then choose the credentials you want to use. Additionally, you can select 'Add New Credential' to display the **Create Credential** dialog if you anticipate using these same credentials for other nodes or integrations. For more information, see [Create Credential](https://docs.cloudhouse.com/guardian/classic/inventory/credentials/credentials/index.md#create-credential). !!! note The **Credentials** tab was introduced in V4.3.46.0 of Guardian. For more information, see [July 2024 Quarterly Release](https://docs.cloudhouse.com/guardian/classic/what-s-new/3-archive/2024/quarterly-releases/q2/july-feature-2024/index.md). !!! warning This option is only displayed if you have the **Credentials** feature enabled. If you don't, the **Username** and **Password** fields are displayed instead, as described below. **Secret Server** radio button : Option to use credentials stored in Secret Server. Select this option to display the **Secret Server Items** drop-down list, then choose the credentials you want to use. The credentials displayed are defined by the Secret Server integration. For more information, see [Secret Server Integration](https://docs.cloudhouse.com/guardian/classic/control/integrations/secret-server-integration/index.md). !!! note The Secret Server feature was introduced in V4.3.54.0 of Guardian. For more information, see [April 2025 Quarterly Release](https://docs.cloudhouse.com/guardian/classic/what-s-new/2-previous-release/2025/quarterly/q2/april-2025/index.md). !!! warning This option is only displayed if you have the Secret Server feature enabled. If you don't, the **Username** and **Password** fields are displayed instead, as described below. **Username** and **Password** field : The username and password of the user account configured to use WinRM. !!! note This option is only displayed if the **Credentials** or Secret Server feature are not enabled. **CredSSP** checkbox : Select to enable an encrypted Transport Layer Security (**TLS**) protocol when authenticating the username and password of the service account. If selected, the authentication process is encrypted during transmission ensuring that login credentials are protected from being intercepted or compromised by unauthorised parties. 5. Once you've completed the above options click **Scan Node** to add the node to your Guardian instance. Now, Guardian performs an initial scan of the node. You can wait on this page for the scan to finish, at which point you will see a **View Scan** button. To view the results of this initial scan, click **View Scan**. However, you can also navigate elsewhere while Guardian performs its initial scan of the node. You can then view the status of the scan on the [**Job History**](https://docs.cloudhouse.com/guardian/classic/control/job-history/job-history/index.md) page (**Inventory** > **Job History**). For more information on what to do next after adding a node, see below. ## Where next - [*Read* **Node Scan Results** What every scan of a node collected.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/nodes/node-scan-results/index.md) - [*Organise* **Node groups** Group nodes by type, location and more.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/node-groups/node-groups/index.md) - [*Tune* **Scan options** Choose what each scan collects.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/scan-options/scan-options/index.md) - [*Compare* **Configuration differencing** Compare nodes, groups and scans.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/configuration-differencing/configuration-differencing/index.md) - [*Govern* **Policies** Define the configuration you expect.](https://docs.cloudhouse.com/guardian/classic/control/policies/policies/index.md) - [*Connect* **Integrations** Sync nodes and act on events.](https://docs.cloudhouse.com/guardian/classic/control/integrations/integrations/index.md)