Workspot Mac Client Release 3.0 (January 11, 2019)

Robert Plamondon -

Introduction

The Workspot Mac Client 3.0 release introduces support for Azure Active Directory (Azure AD), Microphone and Webcam support, and other features.

System Requirements

The Workspot Mac Client 3.0 requires macOS 10.11 or higher.

Intended Use

Limited deployments to evaluate release 3.0 or full deployments when recommended for your organization by Workspot.

New Features and Enhancements

Azure AD Support

Azure AD (Azure Active Directory, also called 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 use of multi-factor authentication (MFA).
  • Microsoft’s conditional access feature is supported, allowing rules-based Azure AD authentication. See Microsoft’s What is conditional access in Azure Active Directory?
  • End-users log into the Workspot Client (only) 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.
  • The Workspot mode user PIN is not supported when Azure AD is enabled.
  • Azure AD capability is disabled by default. Contact Workspot if you are interested in enabling it.

Webcams and Microphones

Webcams and microphones on Client devices are now supported.

  • 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 Client’s use of the Webcam with the Client’s “Settings > RDP > Devices > Use Webcam” and “Use Microphone” checkboxes. 
  • For Webcam support, the remote desktop must be running Windows 10 release 1803 or higher.
  • Webcam support for the Mac Client requires that you install Webcam support software on the remote desktop. (For Windows clients, this software is required only for Skype video support.) Contact Workspot for more information.

Installation/Update

System Requirements

  • This release requires macOS 10.11 or higher.

Download Location

TBD

Installation Procedure

TBD

Bug Fixes

  • “No desktops available in pool” error not being logged by Workspot Control.
  • Workspot Client freezes when microphone is used by remote desktop.
  • Client cached credentials when told not to by Workspot Control.
  • Display artifacts with Task Manager ‘Always on Top’ option.
  • Client displays spurious “New configuration available” messages.
  • Cannot use second App in full screen mode on the Mac Client while first App is launched.

Known Limitations

  • In macOS 10.14 (Mojave) in Dark Mode, the Workspot Client screens are hard to read and button sizes seem inconsistent.
  • On some Client systems, an echo may be heard when using Skype for Business on some Work-spot desktops.
  • With multi-factor authentication, if the user does not respond to the MFA challenge, the login attempt times out after five minutes with the message “The credentials you entered are incorrect,” rather than the correct cause of the error.
  • On a Mac using a British keyboard layout, the (“) and (@) keys are swapped on the remote desktop/app due to differences between Microsoft and Apple British keyboard layouts. Workaround: Contact Workspot for details.
  • A duplicate desktop icon is created on Client if a new end-user accepts the “New configuration available” option and then launches a desktop while the desktop pool is being resized.
  • If an end-user launches a full-screen desktop and then a full-screen app, the desktop may become inaccessible until the app is closed.
  • Within Workspot apps, trying to move a dialog box or other window may be jumpy rather than smooth.
  • If there is a mismatch between the authentication method (AD vs. Azure AD) specified in the RD Gateway and Workspot Control, the error message on the Client is “The credentials you entered are incorrect. Please try again,” when the real problem is the configuration mismatch.

Related Documentation

Have more questions? Submit a request

Comments

Powered by Zendesk