Chat now with support
Chat with Support

Foglight for VMware Horizon View 7.3.0 - User Guide

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

Prepare your VMware Horizon View environment for monitoring

Prior to creating VMware Horizon View agents, it is critical to configure the servers to be monitored. There are a few settings that must be made before the agents can successfully collect data. These steps should be done on each relevant host prior to running the Discover View Instances wizard or manually creating VMware Horizon View agents.

When using the Discover View Instances wizard to create VMware Horizon View monitoring agents, several agents are created:

•
A Connection Server agent is created to monitor the Connection Server.
•
A Host agent is created for each Connection, Security, and Transfer Server.
•
A Host agent is created for each physical machine (if any) available in your VMware Horizon View environment for checkout.
To prepare the VMware Horizon View environment for monitoring, execute the following tasks:
1
Domain task. Determine a domain user, Key Distribution Center, and event database password required for agent configuration. For more information, see Domain user and Key Distribution Center.
2
Agent Manager tasks. Verify whether the Agent Manager host is configured correctly. For more information, see Agent Manager configuration.
3
Connection Server tasks. Configure PowerShell execution policy. For more information, see Connection server PowerShell configuration.
4
Monitored Hosts tasks. Choose to monitor the environment using either WinRM (recommended) or DCOM, and configure the monitored hosts accordingly. These tasks apply to all Connection, Security, and Transfer Servers, as well as any physical hosts available for checkout. For more information, see Host configuration (WinRM) and Host configuration (DCOM).

For a list of problems that you might encounter while monitoring your environment using Foglight for VMware Horizon View, and solutions available to troubleshoot these problems, see Troubleshoot agent collection problems.

Domain user and Key Distribution Center

To correctly configure the view agent, the following information must be identified:

•
The domain user account to be used for monitoring. This user does not need any special domain privileges, but must be in the local administrators group of each Connection Server to be monitored.
The domain user also needs to be granted the Administrator (Read-only) role in the “View Administrator” console, which allows the view agent to collect information from the View environment. To grant this role to a domain user:
a
Create a domain user in Active Directory®.
b
Open the “View Administrator” console, navigate to View Configuration, and click Administrators.
c
Click Add User or Group and add the newly created domain user.
d
Select Administrators (Read only) role to this domain user.
e
Remote connect to the Connection Server. Using the Server Manager, click Configuration > Local Users and Groups > Groups > Administrators, and right click to open the Administrators Properties dialog box. Add the newly created domain user to the Administrators group.
•
The Key Distribution Center (KDC). If choosing to monitor the environment using WinRM (recommended), the Kerberos authentication is used. Kerberos is enabled by default in all Windows® domains, and all domain controllers act as KDCs. It is usually sufficient to specify just the domain in the agent settings, MyDomain.local, instead of the fully qualified domain name (FQDN) of a domain controller, MyDC.MyDomain.local. However, to ensure that the agent uses a specific domain controller as the KDC, use its FQDN.
* 
NOTE: For more information about KDC, see http://msdn.microsoft.com/en-us/library/windows/desktop/aa378170%28v=vs.85%29.aspx.
•
The Event Database password. The VMware Horizon View agent monitors the View Event Database. You must know the password for the Event Database to completely configure the VMware Horizon View agent. To confirm this password, go to View Configuration > Event Configuration in the VMware View Administrator instance.
The Event Database password is optional. The event database configuration, including the access password, is defined by the Event Database administrator during the event database installation and setup. For more information about this topic, refer to the VMware® documentation. The password should be the same as the password configured in the VMware View Administration, View Configuration > Event Configuration option.
* 
NOTE: When the password is specified in the view agent properties, it enables the event-based rules in the cartridge. When no password is specified, the alarms from the event database are not logged.

Agent Manager configuration

Before configuring a collection method, you must ensure that the Agent Manager machine on which the View Connection Server Agent resides can connect to the View Connection Server. Follow the configuration checks in this section to verify the connection.

Step 1: Verify the registry key

If running Agent Manager on a Windows® host and using WinRM (recommended), verify that the Kerberos is properly configured. Verify whether the following registry key exists and add it, if it does not exist.

Path: HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Lsa/Kerberos/Parameters

Value Name: allowTGTSessionKey

Value Type: REG_DWORD

Value: 1

Step 2: Verify the name resolution

Name resolution must work from the Agent Manager host to the View Connection Server.

To verify that the name resolution resolves:
1
Open a command prompt and verify that you can ping the View Connection Server using its fully-qualified domain name.
2
If this fails to resolve, contact your domain administrator or manually edit the hosts file on the Agent Manager host.
Step3: Verify the access port

The Agent Manager must be configured to access port 389 of the target Connection Server if not using SSL.

The Agent Manager must be configured to access port 636 of the target Connection Server if using SSL.

Connection server PowerShell configuration

The View Connection Server Agent must be able to execute PowerShell commands on the monitored Connection Servers.

Step 1: Set ExecutionPolicy
To set the execution policy:
1
Log in to the View Connection Server machine using an account with Administrator privileges.
2
Open a command prompt and type: powershell.exe
3
At the PowerShell prompt, type: Get-ExecutionPolicy
4
The message Unrestricted appears.
If this message does not appear, type: Set-ExecutionPolicy Unrestricted
5
When prompted, type y
The View Connection Server now has unrestricted access to run PowerShell commands.
Step 2: Verify the user account has sufficient privileges to run VMware Horizon View cmdlets

The View Connection Server Agent must have a user account with the correct credentials to run VMware Horizon View cmdlets on the Connection Server.

To verify the user account privileges:
1
Log into the View Connection Server using the same credentials as the View Connection Server Agent.
2
Open a command prompt and type: powershell.exe
3
Load the VMware Horizon View snapins. Type the following cmdlet:
C:\Program Files\VMware\VMware View\Server\extras\PowerShell\add-snapin.ps1
The Snapin.PS1 script adds the VMware Horizon View snapins. These snapins consist of all the cmdlets that are typically used in a VMware Horizon View environment.
4
Verify that the View Connection Server Agent can run the necessary VMware Horizon View cmdlets. To test, this, type one or more of the following cmdlets:
Get-ViewVC
Get-ConnectionBroker
Get-Monitor
Get-RemoteSession
Values specific to the issued cmdlet should be returned.
Step 3: Additional configuration

In addition to this Powershell configuration, the Connection Server must also be configured for either WinRM or DCOM as described in Host configuration (WinRM) and Host configuration (DCOM).

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating