Workspot Windows Client Release 3.5 (September 27 2019)

Robert Plamondon -


Release Type

Release 3.5 is a new-feature and bug-fix release.

Who Should Update

Customers requiring the new features of release 3.5.

Download Location

Note: If you are currently running a beta release, uninstall it before updating.

Supported Platforms

Windows 32-bit and 64-bit Windows 7, 8, 10 and Windows 10 IoT.

Note: Windows 7 is nearing end of support.

End of Life/End of Support

New Features

  • Multiple monitors. in systems with two or more monitors, you can specify that only one monitor be used for the remote desktop, that all monitors be used, and that all except one monitor be used. The last option is new. See Changes in Multi-Monitor Support.
  • RD Gateway capacity scaling and redundancy. When more than one RD Gateway is specified in Workspot Control for a Workspot desktop pool or app, the Client selects one from this list, rather than being limited to a single gateway. See Capacity Scaling and Redundancy in RD Gateways.
  • Multiple workspaces. If a user has two or more Workspot accounts, these can be accessed through multiple workspaces on the same system. These workspaces are kept separate and are accessed and encrypted separately. See Multiple Workspaces.
  • Credentials:
    • The user no longer needs to enter the domain name if this is not required by Workspot Control. See Optional Use of Domain Name.
    • The user now has the option to reset the Client passcode from the lock screen.
    • Credential caching follows the settings in Workspot Control more exactly.
    • When “Disable SSO” is selected on the Client, no credentials are saved, not even for the duration of the current session.
  • Secure browser update. The built-in secure browser has been updated.
  • App names. Hovering the mouse over an app will reveal the full app name, if truncated.

Changes in Multi-Monitor Support


You can now set the Workspot Client to use all monitors but one, increasing the number of options to three: All monitors, one monitor, and all monitors except one.

Your Workspot desktop will create as many virtual monitors as these settings allow. For example, if you have three local monitors and choose to use all monitors except one, the remote Workspot desktop will create virtual displays for two monitors. If you choose to use all monitors, the Workspot desktop will create three virtual displays.

Note: This feature is currently supported on Windows 10 version 1809 and 1903 only. On unsupported releases, the “Use subset of monitors” option is not shown.

This is set on the Client’s “Settings > RDP > Display” section. The “Use subset of monitors” checkbox tells the Client to leave one display free for the local system. This checkbox is only available if “Use multiple monitors” is set.

Up to three monitors are supported in a T or horizontal row (set in your local system in “Settings > Display Settings”). With four or more monitors, the Client does not currently support rectangular arrays of monitors.

When “Use subset of monitors” is selected, the rightmost or bottommost monitor is reserved for local use, and the others are used for your Workspot desktop.

If “Use multiple monitors” is set, desktops will automatically open in full-screen mode. If you use switch to windowed mode, your Workspot desktop will go into single-monitor mode, will all its open windows migrating into the surviving desktop window.

Capacity Scaling and Redundancy in RD Gateways

The Workspot Windows Client now supports multiple RD Gateways for capacity scaling and high availability.

This is done through a simple mechanism: in Workspot Control, you can now select more than one RD Gateway as part of the pool definition. This list of Gateways is sent to the Client. When the Client needs to make a connection to a desktop, it selects a gateway at random from the list for that pool. If the connection fails, this process repeats.

Clearly, capacity scales roughly linearly with the number of Gateway. Redundancy and failover are inherent whenever two or more gateways are selected.

For existing pools, the list of RD Gateways is in Control at “Resources > VDI Pools > poolname > Actions > Edit.” The Gateway field is now a pull-down menu that allows you to select as many gateways as you like.

Workspot supports multiple gateways per pool only when the Gateways are all in the same region.

If you need more gateways to achieve redundancy, contact Workspot.

Multiple Workspaces

Sometimes users need access to more than one Workspot environment; for example, when a user has accounts at different operation units of the same Workspot-enabled organization or even at two different organizations. The new multiple workspaces feature allows a user to have two  or more independent Workspot Windows Client configurations on the same Client system. These use the same binaries but have independent logins and encrypted credential storage.

How it Works

The “account” command-line option has been added to the Workspot Windows Client. This specifies an arbitrary alphanumeric string to identify the second (or subsequent) Client account. The first time the option is used, a new Client configuration is created, prompting the user to go through the first-time user process as usual. Later uses of the same command line launch the Client using this configuration.

Once the second configuration is configured, the user can run both configurations at once. The configurations are independent: no configuration data or credentials are shared between the two instances.

Creating a Second Workspace

Run the Workspot Client (WorkspotClient.exe) with the “--account AccountLabel” option:

path\WorkspotClient.exe --account AccountLabel

For example:

“C:\Users\Robert\AppData\Local\Programs\Workspot\Workspot Client\WorkspotClient.exe” --account ExampleAccountLabel

Since creating the new workspace and invoking it later use the same command, putting the command in a batch file is convenient.

Installation proceeds as usual. When complete the user’s Workspot main windows shows the account label.


The original workspace is invoked if the client is launched without the “--account” option.

The two workspaces can be used simultaneously.

Optional Use of Domain Name

Starting with Release 3.5.0, the Workspot Windows Client supports an optional default domain specified in Workspot Control for the “Single Sign On using username and password” Login Type for Workspot apps and desktops. When selected, the default domain is used by the Client if the user does not include a domain name.

If your Workspot app or desktop does not use a domain for login, you can select this option and leave the “Login Domain” field blank.

This default is overridden when the user enters “domain\username.”

The default login domain is specified in Workspot Control when creating a new app or pool or by editing an existing app or pool. For example, for a desktop pool, go to “Resources > VDI Pools > poolname > Actions > Edit” and editing the “Login Type” and “Login Domain” fields.


Support for PingOne Authentication

PingOne authentication is now supported as a selective feature. Its operation is similar to Workspot Azure AD authentication. The feature set of PingOne, such as multifactor authentication (MFA) are supported, since they are handled directly by the PingOne service, not Workspot.

Contact Workspot if you are interested in PingOne authentication.

Fixed Bugs

  • When the security policy used by an app has “Cache credentials” set to “No,” the app sometimes came up as a blank screen.
  • When the login type was changed in Control to not require a domain, this was not reflected immediately in the Client.
  • VPN access to pools is no longer prevented by the “Disable SSO” option.
  • In full-screen mode, typing Alt+Windows locked the Windows key on.
  • When Control declares the domain as optional, the Client honors this.

Known Issues


  • Connections where a VPN is present but not used (typically when users are on their organization’s LAN) are logged on Control as if they had gone through the VPN.
  • On Windows 7, if you launch the Client, then connect a second monitor, then check and uncheck the "Use all monitors" Client option, then launch and close a desktop or app, the Client will crash.
  • If a user cancels the launch of a desktop or app, this event is logged twice in Control.
  • Canceling a Ping login leaves an empty display dialog box on the screen. Workaround: Close the empty dialog box.
  • When the Client has an RD App open and the user opens a different RD App from the same pool without closing the first one, the Client may misreport the new app to Control, which logs this in an Event message.
  • If the network is lost during a Ping authentication, the login process hangs on the Ping error message even after the network is restored. Workaround: Close the application window and try again.
  • If you leave a desktop or app open when you upgrade the Client, you will have to re-enter the desktop/app’s credentials after the upgrade.
  • If the user unchecks the “Use subset of monitors” box while the remote desktop displays are minimized, the additional monitor will not be used.
  • On lower-resolution displays, the final characters in the username box may be clipped.
  • In a Web app, if the user double-clicks on a control that creates popup windows, the Client can hang after it goes through a lock-screen/unlock sequence. Workaround: Kill the Client process in Task Manager.
  • After uploading logs, the “Uploading Logs” popup appears every time the user unlocks the Client, even though the logs are fully uploaded. Workaround: Exit and restart the Client.
  • RD Apps do not use stored credentials with “Disable SSO” is enabled.
  • The icons for Minimize, Maximize, and Close on the Client main window vary in size according to the screen resolution.
  • RD Apps may not open if closed and then immediately relaunched.
  • The Workspot Client will hang on systems whose time is set far enough in the future that new access tokens or certificates seem to have expired.


End of Life/End of Support

When the Workspot Windows Client 3.5 is released for production, versions before 3.0 will no longer be supported, in line with our lifecycle support policy (see link below).

Windows 7 will not be supported after January 2020 (see link below).

Related Documents


Have more questions? Submit a request


Powered by Zendesk