You can edit general settings and upload certificates from the General Settings page.

Procedure

  1. Select Settings > General Settings.
  2. Click Edit.
  3. Make changes for these settings.
    Note:

    The Networks list shows a list of your currently used network(s). This list is not editable. Contact your service provider to edit or add Network(s).

    Option

    Description

    Default Domain

    Default domain that you are editing.

    Session Timeout

    • Client Heartbeat Interval - Controls the interval between Horizon Client heartbeats and connected state. These heartbeats report to the broker the amount of idle time that has passed. Idle time occurs when no interaction occurs with the end point device, as opposed to idle time in the desktop session. In large desktop deployments, setting the activity heartbeats at longer intervals might reduce network traffic and increase performance.

    • Client Idle User - Maximum time that a user can be idle while connected to the tenant. When this maximum is reached, the user is disconnected from all active Horizon Client Desktop sessions. The user must re-authenticate to re-access the Horizon Client.

      Note:

      Set the Client Idle User timeout to be at least double the Client Heartbeat Interval to avoid unexpected disconnects from desktops.

    • Client Broker Session - Maximum time that a Horizon Client instance can be connected to the tenant before its authentication expires. The timeout count starts each time you authenticate. When this timeout occurs, you can continue to work. If you perform an action that causes communication to the broker, such as changing settings, the system requires you to re-authenticate and log back in to the desktop.

      Note:

      The Client Broker Session timeout must be at least equal to the sum of the Client Heartbeat Interval and the Client Idle User timeout.

    • User Portal Timeout - How long you can be on the User Portal when you try to broker a connection before you need to log in again.

    Image Defaults Configuration

    Enter the Organization Unit within the Active Directory to store the Desktop Image resources. For example, OU=NestedOrgName, OU=RootOrgName, DC=DomainComponent, etc. If no value is entered, the default is CN=Computers.

    User Portal Configuration

    Enter the helpdesk email address, the trouble ticket system URL, and the external style sheet URL to allow for end-user portal configuration.

    IDM

    Settings for VMware Identity Manager. If more than one IDM is configured, a set of fields displays for each.

    • To add an IDM, click the Add IDM button and enter information for the new IDM:

      • IDM URL - URL of the IDM.

      • Timeout SSO Token - Timeout value in minutes.

      • Data Center - Name of data center. Select from drop-down list.

      • Tenant Address - Address of the tenant appliance.

    • For an existing IDM, you can edit the following fields:

      • IDM URL - URL of the IDM.

      • Timeout SSO Token - Timeout value in minutes.

      • Data Center - Name of data center. Select from drop-down list.

      • Tenant Address - Address of the tenant appliance.

      • Force Remote Users to vIDM - Enable to block remote user access except through IDM. Option only displays if IDM status is green.

      • Force Internal Users to vIDM - Enable to block internal user access except through IDM. Option only displays if IDM status is green.

    • To delete an IDM, click the "x" to the top right of the IDM to delete.

    Agent Pairing

    Sets a policy on the tenant which determines the access of legacy (pre-16.6.0) and 16.6.0 agents. Options are as follows:

    • 15.3 Compatibility Mode - Allows legacy and 16.6.0 agents to be paired with Desktop Manager. This is the default setting for upgraded setups.

    • 16.6 Upgrade Mode - Restricts legacy agents, but allows un-bootstrapped 16.6.0 agents on persistent desktops and bootstrapped 16.6.0 agents. This mode does not restrict desktops that are already paired using 15.3.x agents unless the desktop or agent service is restarted.

    • 16.6 Mode - Allows only bootstrapped 16.6.0 agents to be paired. This mode does not restrict desktops that are already paired using 15.3.x agents or un-bootstrapped 16.6.0 agents unless the desktop or DaaS agent service is restarted. This is the default setting for fresh installs.

    When to change this setting:

    • Change from 15.3 Compatibility Mode to 16.6 Upgrade Mode only when there are no longer any pre-16.6 agents in the system BUT there are some dedicated desktops from before the upgrade with their agents upgraded to 16.6.

    • Change from 15.3 Compatibility Mode to 16.6 Mode when there are no longer any pre-16.6 agents or 16.6 agents that are paired with legacy credentials. Once the 16.6 mode is enabled, only VMs creating using bootstrapped images will work.

    Contact Info

    Administrator contact information.

  4. Click Save.