Workspot Windows Client Release 3.0.1 (February 1, 2019)

Robert Plamondon -

Release Type

Workspot Windows Client Release 3.0.1 is a hotfix release featuring:

  • Support for Microsoft Conditional Access Tokens.
  • Bug fixes.

Who Should Update

Customers wishing to deploy (or evaluate) the Windows Client 3.0.1 features or bug fixes.

Note for Kiosk-Mode Customers

All pre-3.0 Kiosk-mode Clients must be reinstalled with the new “subdomain” parameter when upgrading to 3.0 and above. (Release 2.x Clients are not affected.) The value of “subdomain” is set by Workspot.

Look in Workspot Control under "Setup > Configuration > Registration and Authentication > Directory Services > Subdomain." If this field has a value, you can install Release 3.x Clients by using this parameter. Otherwise, contact Workspot.

For more on Kiosk-mode installation, see Running Workspot Windows Client in Kiosk Mode.

Download Location

Download the release from the download page at http://download.workspot.com. Both 32-bit and 64-bit versions are available.

Supported Platforms

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

New Feature: Azure AD Conditional Access

Azure AD conditional access is now supported. (Previously, the Windows Client used an Azure AD token type that did not support conditional access.)

With conditional access tokens, you can configure Client access rules in Azure that depend on a variety of conditions. For example,  a user in  a random location might be required to use multi-factor authentication to sign in to the Workspot Client, while the same user on the corporate network might be allowed to sign in without multi-factor authentication.

Bug Fixes

  • Mouse cursor display issue.
  • VPN Connections not working with Proxy PAC file configurations.
  • Client fails to authenticate against Cisco VPN.
  • “Invalid Input” error is shown on sign-in if the user uses a different username/password than was used originally.

Known issue

  • When 'Disable SSO' is enabled, the user is unable to sign into desktops or apps configured behind VPN. Workaround: Clear the ‘Disable SSO’ checkbox on the Client.

Related Documents

Have more questions? Submit a request

Comments

Powered by Zendesk