Highlights
Note: Starting with Release 18.2, you will have to know your Company Identifier to sign in, either by using a Control URL that includes it or by typing it into the “Company Identifier” field on the first Control sign-in screen.
Support for Non-Persistent Global Desktop Pools on the Microsoft Azure Cloud.
Support for both multiple Control instances and enhanced Control sign-in security through changes to Control Administrator sign-in process.
Support for Entra ID, NPS, and IdP authentication for Workspot Managed Gateways on the Amazon Workspaces Core and Amazon EC2 Clouds.
Provisioning desktops in AWS Workspaces Core now takes place during pool creation rather than desktop assignment, speeding up the time to launch the desktop for the first time.
Control’s “Groups” page now has a “Domain” column that lists the domain associated with the Group, if any.
Changes to Control’s SAML Configuration page.
Workspot's Splunk output includes two new fields: "clientExternalpAddress" and "clientInternalIpAddress." See Workspot Configuration Guide for Splunk.
When creating a desktop pool using a Cloud and plan that require sole-tenant nodes (STN), you are notified that STNs will be used. If you have a choice of STN sizes or types, this will appear on the page as a “Sole-Tenant Node Type” pull-down menu.
Known Issues
New Known Issues
When using Entra ID (Azure AD) as your SAML provider, the usual logout URL provided by Azure AD may result in an error message when signing out of Control. Workaround: Configure SAML in Control ("Setup > SAML > Signout Service URL") to use the folllowing URL instead: “https://login.microsoftonline.com/common/wsfederation?wa=wsignout1.0”