Foglight for VMware Horizon View 7.3.0

Domain user and Key Distribution Center Agent Manager configuration Connection server PowerShell configuration Host configuration (WinRM) Host configuration (DCOM) Troubleshoot agent collection problems

Explore administrative tasks

Tasks area Agents view Manually add View instances Discover View instances Add Host Agents Managing certificates

Use the VMware View Environment dashboard

Details tab Administration tab Navigating between View server instances

Explore the VMware View Environment Details tab

Work with tiles Use the Quick View Explore user sessions Explore desktops Explore Horizon Pools

Use the VMware Explorer

Virtual Infrastructure view VMware Explorer View

Accessing VMware® actions and tasks

Reference

Views

Add Host Agents

This workflow allows you to add Infrastructure (IC) agents to monitor your VMware Horizon View environment. An IC agent collects data such as CPU, disk, memory, services, and other network metrics for the VMware Horizon View components in your environment. This data appears on the Details tab of the VMware View Environment dashboard.

To add an Infrastructure agent:

In the VMware View Environment dashboard > Administration tab > Agents view, select a View agent instance from the list, then click Add Host Agents.

The Add Host Agents wizard appears, showing the Select Agent Manager Host page. The information listed on this page is from the Agent Host dashboard (Administration > Agents > Agent Hosts).

Select the Foglight Agent Manager Host to be used for the new Infrastructure agent instance, then click Next.

The Select Server(s) page appears. This page lists the terminal servers, security servers, and connection servers that are in the VMware View infrastructure.

Select those servers for which you want to create an Infrastructure (IC) Agent, then click Next. The agent will monitor the selected servers.

The Credential Verification - Windows page appears. Credentials are security data that provide the Infrastructure agents with the permission to monitor system resources, such as a host or a range of hosts.

Select one of the following options:

•

Do not configure a credential. Select this option if you want to configure the credential for this resource at a later time. Local credentials for Windows® and UNIX® are set up by default when Foglight for Infrastructure is installed. Click Next and continue with Step 7.

•

Add host(s) to a new credential. Select this option if you want to add the host to a new credential. This option is suitable if none of the existing credentials have the connection details needed to access the new host. Click Next and continue with Step 5.

•

Add host(s) to an existing credential. Select this option if you want to add the host to an existing credential. This option is suitable if an existing credential has the security data needed to access the new host, but you need to edit its resource mappings to include this host. Click Next and continue with Step 6.

Create a new credential.

On the Credential Type page that appears, select the credential type from the available options.

Click Next.

The Credential Properties page appears. The level of required information depends on the selected credential type. For example, the User Name and Password type needs a user name and a password, while the Challenge Response type needs a user name along with a question/response pair.

On the Credential Properties page, type the required properties, and click Next.

The Credential Name and Lockbox page appears.

On the Credential Name and Lockbox page, provide a name to identify the credential, and select a lockbox in which you want to keep the credential. A lockbox can be used to group credentials for access and/or security. In smaller Foglight installations, using the default System lockbox should be sufficient.


	NOTE: If a lockbox is password protected and is not released to the target Foglight Agent Manager, you can provide the lockbox password on the last page of the wizard.

Click Next.

The Resource Mapping page appears.

On the Resource Mapping page, indicate which hosts you want to associate with this credential. You can either select the host that you are about to start monitoring, all monitored hosts, or hosts whose name contains a specific text string.

Click Next.

The Policies page appears.

Optional. On the Policies page, define one or more policies for this credential. A policy defines the number of times a credential can be used, the number of allowed authentication failures, the time range during which the credential is valid, or the length of time the credential data can be cached on the client. For example, you can specify the number of times the credential can be used, or the time period during which it can be used. For complete information about the available credential policies, see the Foglight Administration and Configuration Help.

Click Next.

The Summary page appears.

Continue with Step 7.

Use an existing credential.

On the Credential page that appears, select an existing credential to contain this host.

Click Next.

The Resource Mapping page appears.

Click Next.

The Summary page appears.

Continue with Step 7.

On the Summary page that appears, review the information provided about the host and the monitoring agent.

Click Finish.

The new host is added to the Hosts dashboard after a short delay. The monitoring agent is created.

If the operation is successful, the Result For Agent(s) Creation dialog box appears. Review the information and close the dialog box.

The agent instance created to monitor the new host appear on the Administration > Agents > Agent Status dashboard.

Managing certificates

Syntax Conventions

In order to successfully make use of the Foglight commands in your monitoring environment, review the syntax conventions before getting started. The syntax conventions are as follows:

•

Generic examples follow the UNIX path structure that uses forward slashes '/' to separate directories.

•

Platform-specific examples follow standard platform conventions. For example, UNIX-specific examples use forward slashes ‘/’ as directory delimiters, while Windows examples use backslashes ‘\’.

•

<foglight_home> is a placeholder that represents the path to the Foglight Management Server installation.

•

<foglight_agent_mgr_home> is a placeholder that represents the path to the Foglight Agent Manager installation. This can be the location of the Foglight Agent Manager installation on a monitored host, or the home directory of the Foglight Agent Manager that comes embedded with the Foglight Management Server. For example:

Path to the Foglight Agent Manager installation on a monitored host (Windows):

C:\Quest\Foglight_Agent_Manager

Path to the embedded Foglight Agent Manager installation (Windows):

C:\Quest\Foglight\fglam

•

Unless otherwise specified, Foglight commands are case-sensitive.

Managing certificates for FglAM

Foglight Evolve agents use Foglight Agent Manager (FglAM) to manage certificates for SSL encryption connection.

Prerequisite

All the certificate-related command line options require that FglAM be up and running.

Add a certificate

bin/fglam --add-certificate "user alias 1"=/path/to/certificate/file

•

Validate the certificate and ensure the following:

•

It is not expired.

•

It is an X.509 format.

•

FglAM requires the Base64 format. To verify if the certificate file is encoded with Base64, open the certificate with a notepad and the certificate should be similar to the following example:
-----BEGIN CERTIFICATE-----
XXXXXXXX=
-----END CERTIFICATE-----


	NOTE: If the certificate is not Base64 format, use openssl command to convert the certificate file into a Base64 file. Use either of the following commands depending on the source form: openssl x509 -inform DER -in xxx.cer -out xxx.crt or openssl x509 -inform PEM -in xxx.cer -out xxx.crt