Chat now with support
Chat with Support

Foglight for VMware Horizon View 5.7.7 - User and Reference Guide

Manage desktops in virtual environments Interact with Foglight for VMware Horizon View dashboards Reference

Host configuration (WinRM)

When using this collection method to obtain information from remote hosts, Foglight for VMware Horizon View relies on WinRM to expose the data.

This section includes some specific information related to configuring WinRM to remotely access the monitored hosts. It should not be used as a complete reference for this Windows® component.

For complete information about configuring the WinRM service, refer to the WinRM documentation. To quickly access the WinRM help, type WinRM at the command prompt.

When the WinRM configuration is complete, ensure that the Windows® Remote Management service is started:

Check the existing configuration. Open a command prompt as administrator. Type:

Choose either to allow non-encrypted (HTTP) communication or to require encryption (HTTPS). This choice corresponds to the Use SSL (True/False) section during agent configuration. When choosing to require encryption, you must have your certificate thumbprint. See your domain administrator for details.

Type: winrm set winrm/config/service @{AllowUnencrypted="true"}
Type: winrm create winrm/config/listener?Address=*+Transport=HTTPS @{CertificateThumbprint="PASTE_CERTIFICATE_THUMBPRINT_HERE"}

The port returned by the command below is used in the WS-Man Communication Port field during agent configuration. The WS-Man Communication Port is set to 5985 by default. Most Windows® versions use 5985/5986; however, some versions are known to use other port values, such as 80/443.

From a command prompt, type: winrm enumerate winrm/config/listener

Host configuration (DCOM)

When using this collection method to collect process information from remote hosts, Foglight for VMware Horizon View relies on DCOM to access the Windows® Management Instrumentation (WMI) infrastructure on the remote hosts, to connect to virtual and physical machine hosts and collect their metrics.

The following information must be taken into consideration when using this collection method with Foglight for VMware Horizon View:

When using DCOM to collect metrics through a firewall, configure the firewall manually, then create and run a configuration script (as shown in Configure firewall settings using a script).

64-bit systems only. Create a rule that allows all incoming traffic for the file: %systemroot%\SysWOW64\dllhost.exe

Use the following process to bypass the access restrictions that prohibit the View Connection Server Agent from collecting data from a monitored system.

Click OK to close the Advanced Security Settings dialog box.
On the target machine create the file firewall-config.ps1 containing the following script.

Troubleshoot agent collection problems

This section provides information about problems that you might encounter while monitoring your environment using Foglight for VMware Horizon View, and describes the solutions available to troubleshoot these problems.


Data collected by the VMware Horizon View agent by PowerShell command-lets through WinRM may exceed the default envelope size of WinRM when the scale of VMware Horizon View is large enough.

The maximum envelope size for the connection server and for the VMware Horizon View agent may be different. For the connection server, the default value of MaxEnvelopeSizekb is 150. For the Client (VMware Horizon View agent), the default value of MaxEnvelopeSizekb is 15,360,000 (about 15,000 * 1024, which is 100 times bigger than the default value on Server side).


If NEW_LARGER_VALUE is less than 15,000, the problem is resolved. Otherwise, continue with Step 2.
<FGL_INSTALL_PATH>\state\default\config\baseline.jvmargs.config (for Foglight for Virtualization, Enterprise Edition 7.0 or later)
<FGL_INSTALL_PATH>\state\default\config\vm.config (for Foglight for Virtualization, Enterprise Edition versions prior to 7.0)


By default, SSL is not enabled for Active Directory® Lightweight Directory Services (AD LDS), previously named Active Directory Application Mode (ADAM). VMware Horizon View monitoring fails in this case.


The certificate should issue to the FQDN of the server name.
The certificate should contain the Server Authentication purpose.
In order to use the certificate for authentication, the service account running the AD LDS should have Read access of the private key. By default, the service account is NETWORK SERVICE. If you use another account to run the service, you must grant the permission to that account.
Click Start, right-click Command Prompt, and then click Run as administrator.
Type mmc to open Microsoft® Management Console (MMC).
Click File, click Add/Remove Snap-in, select the Certificates snap-in in Available snap-ins, and then click Add.
In Add or Remove Snap-ins, select Computer account to view the certificates, and then click Next.
In Add or Remove Snap-ins, select Local computer, and then click Finish.
In the console tree, expand Certificates(Local Computer), expand Personal, and then expand Certificates.
Right click a certificate, select All Tasks, and then click Manage Private Keys.
Select and expand the target AD server, right click Reverse Lookup Zones, and select New Zone from the menu.


Explore administrative tasks

The Administration tab of the VMware View Environment dashboard contains links to agent administration tasks that you can use to manage or create agent instances. From this tab, you can choose to either detect the agent instance information during creation or enter the information manually. Both methods create a View Connection Server Agent.

This tab consists of the Tasks area and the Agents view. Additional administrative tasks include:

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating