Use the Horizon Universal Console's General Settings page to modify settings that apply to your overall Horizon Cloud tenant environment.

As described in Tour of the Cloud-Based Horizon Universal Console for Administrative Tasks in Horizon Cloud, the console dynamically reflects the current state of your tenant environment. As a result, the sections you see and settings you can change in the General Settings page are only those that are relevant and appropriate for the current state of your tenant environment. For example, when your cloud-connected pods are all Horizon pods and no pods in Microsoft Azure, only the settings relevant to Horizon pods are provided in this page. When you have at least one pod deployed in Microsoft Azure, the General Settings page makes available settings relevant to that pod type.

To change a setting, use the pencil icon next to the section that contains the setting that you want to change. An edit window displays with that section's settings. Change the settings in that window and save your changes to the system.

Note: When changing any of the following settings, it can take up to 5 minutes for the update to take effect.

Default Domain

If you have only one Active Directory domain registered with your environment, the name of that domain appears here. If you have multiple Active Directory domains registered, this text box displays the name of that Active Directory domain that is specified as the default Active Directory domain, the one that appears first in the domain selection list in the Active Directory login page used when administrators log in to the administrative console.

This setting only governs which Active Directory domain appears first in the domain selection list on that Active Directory login page. As described in Log In to the Horizon Universal Console to Perform Management Tasks on Your Horizon Cloud Environment, when your environment has multiple Active Directory domains registered, the Active Directory login page has a domain selection list. You can use this Default Domain text box to specify one of the Active Directory domains as the default. That default Active Directory domain then appears first in the Active Directory login page's domain selection list. Click Edit to change the current setting.

My VMware Accounts

To give users the ability to log into Horizon Cloud, you add their My VMware accounts. After adding their My VMware information here, then assign their Active Directory user accounts the role that is appropriate for their job or business tasks. See Assign Roles to Active Directory Groups that Control Which Areas of the Horizon Universal Console are Activated for Individuals in Those Groups After They Authenticate to Your Horizon Cloud Tenant Environment.

Notification Recipients

To allow specific non-administrator users or groups to receive email notifications regarding your Horizon Cloud environment, you add their email addresses to the Notification Recipients list.

The preceding My VMware Accounts list can include various types of administrators. However, if you want non-administrator users or groups to receive email notifications, such as administrative and scheduled-maintenance email notifications, use the Notification Recipients section to add their email addresses.

All email notifications generated from Horizon Cloud are sent to all of the listed email addresses.

Session Timeout

These settings govern timeouts of connections to your Horizon Cloud environment:

  • The Admin Portal Timeout setting governs the amount time an administrator can be continuously logged in to the console. When that time has elapsed, the administrator's authenticated session ends and the administrator must log back in.

Deletion Protection

The Deletion Protection setting controls the number of desktop VMs that can be deleted per hour in each of your dedicated desktop assignments. Select one of the following options for Mass Delete Dedicated Desktop (per hour).

  • Unlimited - Unlimited desktop VMs can be deleted from dedicated desktop assignments.
  • None - No desktop VMs can be deleted from any dedicated desktop assignment unless you allow them for a particular assignment using the Max Desktop Deletions (see note below).
  • Custom - Number of desktop VMs that can be deleted from a dedicated desktop assignment per hour. If you select Custom, you must also enter a numerical value to the right of this drop-down menu. You can allow additional desktop VMs to be deleted from a particular assignment using the Max Desktop Deletions (see note below).
Note:

If you selected None or Custom, you can allow additional deletions for a particular assignment before this limit is invoked by editing the Max Desktop Deletions setting when you create or edit the assignment. If you have entered a value greater than 0 for the Max Desktop Deletions, then the system authorizes deletions of that number of VMs before counting them against the rate you set for Deletion Protection.

For example, you might set Max Desktop Deletions to Custom with a value of 10 and set Deletion Protection to Custom with a value of 1. In this case, after the first 10 VMs are deleted (no matter how long it takes for the count to reach 10), the system only allows 1 additional VM to be deleted per hour from that time forward.

If you select Unlimited for Deletion Protection, there is no need to use the Max Desktop Deletions setting.

For more information about the Max Desktop Deletions setting, see Create a Dedicated VDI Desktop Assignment.

To prevent all VM deletions in a dedicated desktop assignment, use the Prevent Deletions setting on the Assignments page. See Prevent Deletions or Allow Deletions for a Dedicated Desktop Assignment.

RDSH Farm

You can provide a message that Horizon Cloud displays to end users when their logged-in Windows session with their session desktop or remote application has reached the farm's configured maximum session time. The system will forcibly log out the user from their logged-in Windows session after the grace period time expires.

In the Grace Period text box, you can provide a time for which the system waits before forcibly logging out the user, after the reminder message has been sent.

Desktop Assignment Options

Use this setting to configure the displayed virtual desktops' names seen by your end users when they access their assigned virtual desktops using their end-user clients. This setting applies only to virtual desktops provisioned by a dedicated VDI desktop assignment provisioned from pods in Microsoft Azure. For information about desktop assignments in Horizon Cloud, see A Brief Introduction to Your Tenant's Desktop Assignments Based on Horizon Cloud Pods in Microsoft Azure.

Initially, when an end user logs in to their end-user client and sees a desktop newly provisioned from a dedicated VDI desktop assignment, the client displays the name of the dedicated VDI desktop assignment. At this point in time, a specific desktop virtual machine (VM) is not yet assigned to that end user as their dedicated desktop VM. When that end user takes the step to launch the virtual desktop for the first time, at that point, the system dedicates that specific desktop VM to that user as a result of that initial launch. Then for subsequent desktop launches, the name for that desktop that appears in that end user's client depends on the setting you choose here.

Important:
  • Enabling the Enable Dedicated Desktop Assignment Name setting applies to pods at pod manifest version 1900 and later. When the pod is at a manifest version lower than 1900, the legacy behavior stays in effect for virtual desktops provisioned from that pod, regardless of the toggle setting.
  • When you change the setting, it can take up to 5 minutes for the update to take effect.
  • This option does not apply to end-user connections using Workspace ONE Access. When an end user uses Workspace ONE Access to access a desktop entitled to them from a dedicated VDI desktop assignment, Workspace ONE Access displays the assignment name and the user's Horizon Client and HTML Access portal displays the VM name for subsequent desktop launches.
  • When the toggle Enable Dedicated Desktop Assignment Name is deactivated, the end-users clients display the name of the virtual desktop's underlying VM. Displaying the VM name is the legacy behavior.
  • When the toggle Enable Dedicated Desktop Assignment Name is enabled, the end-user clients continue to display the name of the dedicated VDI desktop assignment that provisions the virtual desktop, even for subsequent desktop launches.

Agent Updates

The Failure Threshold setting indicates the number of VMs for which automated agent updates for dedicated desktop assignments in pods on Microsoft Azure are allowed to fail before the update process is stopped. This prevents mass failures from occurring. The default value is 30. For more information, see Updating Agent-Related Software Used by Horizon Cloud.

Image Management Settings

These settings are displayed when your tenant's pod fleet includes at least one Horizon pod. These settings apply to the Image Management Service (IMS) features for Horizon pods. Use these settings to optimize the image replication process. For all of the information about the Image Management Service, see the document Managing Horizon Images from the Cloud and its subtopics.

Domain Security Settings

Use these settings to prevent the communication of Active Directory domain names to unauthenticated users using the various Horizon clients to connect to the pods in Microsoft Azure. These settings govern whether the Active Directory domain information is sent to the client and, if sent, how it is displayed in the end-user clients' login pages. For details, see Horizon Cloud - Domain Security Settings on General Settings Page.

Important:
  • These settings are applied to all of your environment's pods that are deployed in Microsoft Azure, the ones that are under the same Horizon Cloud customer account (tenant).
  • The combination of options selected here changes the user experience in the clients. Certain combinations can set requirements for how end users enter the domain information on the client login page, especially when using older clients, command-line clients, and when your environment has multiple Active Directory domains. How these settings affect the client user experience depends on the client. You might need to balance your desired end-user experience according to your organization's security policies. For more information, see Horizon Cloud - Domain Security Settings on General Settings Page.
  • The General Settings page does not display this Domain Security Settings section when your Horizon Cloud environment has any pods in Microsoft Azure that are not yet updated to pod manifest version 1273 or later. To get access to these controls, update all your pods in Microsoft Azure to this release.
  • Until all your pods are updated to pod manifest version 1273 or later, your environment is configured by default to provide the same behavior as it was in the previous Horizon Cloud release. Until all your pods are at this release level, the system sends the Active Directory domain names to the end-user clients and the clients have the legacy behavior that displays the Active Directory domain drop-down menu.

    Then when all your pods' manifests are at version 1273 or later, these settings are displayed in the General Settings page. At that point, the displayed settings reflect the legacy behavior (both controls set to No), and you can change them to control the communication of domain information to the clients.

To see your pods' current manifest versions, use the Capacity page. For this release's pod manifest version, see the Release Notes page linked from the Horizon Cloud Documentation page.

Monitoring

The Horizon Cloud Cloud Monitoring Service (CMS) collects and stores session, application, and desktop data from connected pods for monitoring and reporting purposes. When your environment is configured for Horizon Infrastructure Monitoring, the CMS also collects metrics about the pods' infrastructure components. The CMS is one of the central services provided in Horizon Cloud. For an introduction to the CMS, see Introducing the Cloud Monitoring Service's Unified Visibility and Insights, Health Monitoring, and Help Desk Features Provided in the Horizon Universal Console. The information collected by the CMS is used in charts on the Dashboard page and reports on the Reports page. See Horizon Cloud Dashboard - Health Visibility and Insights into Your Pod Fleet and Tenant Environment, Reports Page in the Horizon Universal Console, and Horizon Infrastructure Monitoring and the Pods in Your Horizon Cloud Environment.

  • Use the Cloud Monitoring Service toggle to enable or deactivate the Horizon Cloud cloud monitoring service. It is enabled by default.

    When this setting is deactivated, the Session Data setting below does not appear.

  • When the cloud monitoring service is enabled, you can use the Session Data toggle to opt in or opt out of tracking user information related to your end users' sessions. Information collected includes times they logged in, session durations, and average session length per user.

    When you opt in to the collection of user data, Horizon Cloud collects this information and maintains it for the duration of your use of Horizon Cloud. You can delete the collected data by turning off the Session Data toggle.

    When you opt out of the collection of user data but leave the CMS enabled, Horizon Cloud collects session data for a limited period and hashes the user name to allow real-time administration while deactivating historical and aggregated viewing of information. As a result, some reports, such as the User Usage report, are not available. In this case the system also continues to collect other data related to applications and desktops in connected pods.

Cloud Service Provider

This section indicates whether the tenant environment is onboarded to the VMware Cloud Service Engagement Platform. Onboarding to that platform is a prerequisite to activating the Horizon Infrastructure Monitoring feature on this environment's cloud-connected pods. For information about onboarding to the VMware Cloud Service Engagement Platform, see Onboard Your Horizon Cloud Tenant to VMware Cloud Services Engagement Platform and VMware Cloud Services Using the Horizon Universal Console.

Horizon Infrastructure Monitoring

The Horizon Infrastructure Monitoring feature collects metrics about the health of a pod's infrastructure components and sends those metrics to the CMS. The feature must be activated on a per-pod basis. Onboarding the tenant environment to the VMware Cloud Service Engagement Platform is a prerequisite to activating this Horizon Infrastructure Monitoring feature on a pod.

When a participating pod experiences an issue, the CMS reports the information on the Dashboard page. For information, see Horizon Infrastructure Monitoring and the Pods in Your Horizon Cloud Environment.

Activate Horizon Infrastructure Monitoring on a specific pod by clicking the pencil icon and following the on-screen prompts.

Pendo Analytics and Guides

The console displays this section only when you have logged in to your Horizon Cloud tenant using the VMware Cloud Services login method. If you have logged in using the My VMware credentials method in the Horizon Cloud login screen, the console does not display this section.

This section indicates the current enablement state of the Workspace ONE service feature based on Pendo analytics and guides. When you log in to your tenant using the VMware Cloud Services login method, the Pendo-related features are enabled by default.

To read about these Pendo-related features and optionally change the current settings, click the edit (pencil icon). Upon clicking the icon, the console redirects you to the Workspace ONE console's Cookie Usage page which provides information about these Pendo-related features and displays toggles for changing the settings.

To reflect the changes you make in the Workspace ONE console's Cookie Usage page in the Horizon Universal Console General Settings page, refresh the General Settings page.