Workspot Control Setup Menu

This article summarizes Workspot Control’s “Setup” menu tree and provides links to the individual setup pages.

“Setup > Dashboard”

The Dashboard page is the first page you see after signing into Control. It can also be reached by clicking the Workspot Control logo at the top left of the screen.

The page gives a pie chart with the breakdown of Workspot Client usage by device type, useful links, and a summary of the Workspot licenses and rate plans in effect.

Setup

The Setup menu is used to configure your overall Workspot deployment.

“Setup > Cloud”

“Cloud” in this context means a specific subscription to a commercial Cloud provider (and the virtual machines you create and manage within that subscription), or a connection to the virtual machine management software that controls an on-premises datacenter. Control uses the Cloud subscription and the Cloud API to manage your Workspot resources.

You can declare as many Clouds as you need.

Public Cloud

A Public Cloud is a major commercial Cloud provider like Amazon AWS, Google GCP, or Microsoft Azure. Workspot Control signs into these Clouds on your behalf to perform management functions such as creating and monitoring Workspot Gateways, Application Servers, and Desktops. Most Workspot customers use at least one Public Cloud. See Step 4 of Getting Started with Workspot.

Private Cloud

A Private Cloud is generally an on-premises datacenter using virtual machine management software such as Microsoft Hyper-V or Nutanix Prism Element. Workspot Control manages such deployments with functionality that is roughly comparable to Public Clouds. See Step 4 of Getting Started with Workspot.

Custom Cloud

A Custom Cloud is not strictly a Cloud at all, and makes no use of virtual machine management software. Instead, it is an ad hoc collection of virtual or physical devices that you create and update by other means, while Control manages the monitoring and day-to-day operation of the Desktops and Application Servers. See Custom Clouds and Custom Cloud Pools.

Secure Cloud Proxy (Optional)

TBD

“Setup > Gateways”

“Gateway” generally refers to a Remote Desktop Gateway, though VPNs are also included in this menu. End-users access their Workspot Desktops and Applications through the Workspot Client via a Remote Desktop Gateway, since the users and their Desktops/Applications are usually not in the same location. However, if they can reach their Workspot resources directly or through a VPN, a Remote Desktop Gateway is optional.

Public Cloud Gateway Clusters

Public Cloud Gateway Clusters (also called Managed Gateways) are Remote Desktop Gateways that are created and managed by Workspot Control in one of the Public Clouds you have defined. These Gateways allow end-users to access their Workspot Desktops and Applications in that Cloud. They are called “Clusters” because they support up to five Gateways with identical configuration.  See Step 5 of Getting Started with Workspot and Managed Gateways (Gateway Clusters).

Physical Gateway Clusters

A Physical Gateway Cluster uses the same concept as a Private Cloud: you create the Windows Servers that are used for the Remote Desktop Gateways, but Control monitors and manages them. These can be physical or virtual servers. See Step 5 of Getting Started with Workspot and Managed Gateways (Gateway Clusters).

Private Cloud Gateways

A Private Cloud Gateway is one that you create and maintain yourself and that Workspot Control cannot manage or monitor; it does not run the Workspot Gateway Agent. These are often the existing Remote Desktop Gateways in your datacenters. See Step 5 of Getting Started with Workspot.

Private Cloud VPNs

These are the VPNs you wish to use with the clientless VPN software built into the Workspot Client.

“Setup > Configuration”

This is the main Configuration page for your Workspot Deployment. See Control Setup: Configuration Page.

“Setup > Client Software”

The Client Software page shows the currently recommended Workspot Windows Client production release (the “Stable Ring”), the current beta release (the “Preview Ring”), and versions you choose yourself (“Custom Rings”). Your end-users’ Windows Clients are optionally updated to match one of these versions according to their Group Policy settings. See Workspot Windows Client: Automatic Updates via Deployment Rings.

“Setup > Certificates”

TBD.

“Setup > Splunk”

The Splunk page lets you enable Splunk monitoring of Workspot control and provides a Workspot Splunk plugin. See Workspot Splunk/SIEM API User Guide and Workspot Configuration Guide for Splunk.

“Setup > API”

The API page lets you enable access to the Control API, which supports most management tasks. See Using the Workspot Control API.

“Setup > GUIDE”

This page provides the integration token that connects your Workspot GUIDE deployment to Workspot Control. The token is regenerated before use. It expires in fifteen minutes, so click the “Regenerate Token” button just before copying it and pasting it into the GUIDE Portal. See Using the GUIDE Portal.

“Setup > Identity Provider”

The Identity Providers page is used to declare third-party Identity Providers used to authenticate Workspot Client users. See Control: Third-Party Identity Providers (IDP).

“Setup > Advanced Features”

“Advanced Features” means “Workspot Trends and Workspot Watch” in this context. This page lets you manage which users have access to Watch and Trends. See Administering Workspot Watch and Trends in Control.