Workspot Windows Client Release 3.0 (December 14, 2018)

Robert Plamondon -

Release Type

Workspot Windows Client Release 3.0 is a new-feature release.

Note: This release is recommended for limited evaluation deployments. Please discuss a broader deployment with the Workspot Customer Success team before rolling it out to all your end-users.


Download Location

The release is provided as .MSI files at

There are two binaries: one for 32-bit and one for 64-bit Windows:

New Features and Enhancements

  • Azure AD login (Azure Active Directory or Microsoft login) is supported in both Kiosk and Workspot mode. Users can sign in to the Workspot Client using Azure AD authentication.
    • Azure AD authentication is most commonly chosen for its flexible multi-factor authentication (MFA).
    • End-users log into the Workspot Client using Azure AD. They log into their Workspot desktops and applications as before, typically using an Active Directory login.
    • Once Azure AD is enabled, all end-users must use Azure AD-capable Workspot Clients, such as the Workspot Windows Client 3.0 or the Workspot HTML5 Client.
    • The Workstation Client PIN is not supported when Azure AD is enabled.
    • When Azure AD is first enabled, users will be asked to re-enroll using Azure AD credentials.
    • Azure AD capability is disabled by default. Contact Workspot if you are interested in enabling it.
    • For more information, see Configuring Azure Active Directory in Workspot Control.
  • Webcams on Client devices are now supported.
    • The remote desktop or app can access the end-user’s Webcam, if enabled.
    • In Workspot Control, this feature is controlled by the “Allow Audio Redirection” checkbox under “Policies > Security Policy Name > Utility Rules.”
    • In the Workspot Client, the user controls the use of the Webcam with the Client’s “Settings > RDP > Devices > Use Webcam” checkbox. 
    • Both the remote desktop and the Client device must be running Windows 10 release 1803 or higher.
    • Additional software must be added to the remote desktop to allow Webcam support for Skype.
  • Drive mapping has changed slightly in the Workspot Client. If allowed by the Security Policy configuration in Workspot Control, users can choose to share (or not share) any of their local drives with the remote desktop, and to share drives mounted during the session.
    • In Workspot Control, this feature is controlled by the “Allow local drive sharing” and “All drives user plugs in while in session” checkboxes under “Policies > Security Policy Name > Utility Rules.”
    • In the Workspot Client, the user controls which drives are mounted with the Workspot Client’s “Settings > RDP > Drives” checkboxes. The Client-side default is to share all drives. 
  • Network status is provided with a popup menu just below the title bar, indicating presence/absence of connections to the network, Internet, Workspot Control, LAN, and VPN. 
  • The built-in secure browser has been updated. Web-based apps should give fewer warnings.
  • Error messages are clearer and include more details.
  • TLS 1.0. In keeping with security best practices, the Workspot Client no longer supports TLS 1.0 VPN connections. Customers using Juniper or other VPNs supporting TLS 1.0 need to upgrade to a newer version of their VPN software.

Bug Fixes

  • In multi-monitor configurations, disabling and re-enabling the rightmost monitor resulted in a blurry display in the Workspot Client.
  • In multi-monitor configurations, a slight vertical misalignment was seen when all monitors but the rightmost were enabled.

Known Issues

  • Copy/paste and drag-and-drop transfers between the Workspot Client and a remote desktop are limited to 2 GB. Larger files can be transferred using mapped drives.
  • File transfers between client system and remote desktop sometime hang at around 1GB.
  • When going through the First-time user login, if you select one account on the first (email address screen), then select “Use another account” on the Azure AD login screen and attempt to sign in with a different account, you get an “Invalid input” error. Workaround: use the same account throughout the process.
  • Users relying on a Web proxy configuration on the Client device and also use a VPN may  not be able to connect to remote applications that rely upon the Secure Browser.
  • Connections to VPNs that still support TLS 1.0 will be rejected by the Client. Please upgrade to a newer version of your VPN software.

New and Updated Documentation


Have more questions? Submit a request


Powered by Zendesk