Frequently Asked Questions (FAQs) About Workspot

Prev Next

Multi-Factor Authentication (MFA)

Q: How does Workspot provide Multi-Factor Authentication (MFA) single sign-on to Microsoft Office 365 for NON-domain authenticated users?

A: MFA can be configured for remote access on your Microsoft RD Gateway by using RD Gateway's industry-standard RADIUS support to connect to your MFA resources. Workspot users login to the network resources via your Microsoft RD Gateway.

Single Sign-On (SSO)

Q: How does Workspot provide seamless single sign-on to Microsoft Office 365 for domain authenticated users?

A: For administrators, Workspot allows Security Assertion Markup Language (SAML) based login to Office365/Azure Active Directory (AD). However, your federated identity management system must be previously set up using Microsoft Azure AD to provide single access to multiple systems across different enterprises. 

Workspot Agent

Q: Why is the Workspot Agent mandatory?

A: Workspot wants to provide much more information and control for IT Admins during the lifecycle of Virtual Desktops and RDSH Servers. To achieve this, Workspot will need to have more visibility into the state of the virtual resource. This can be achieved by installing our secure Agent into persistent and non-persistent pool templates. When the template is deployed it will report to Control and allow for greater visibility in control by the IT Admin.

Workspot Control

Q: I updated a user's Active Directory (AD) record to have a new or updated email address, and now the user has two Workspot Desktops in the same pool. How do I fix this?

A: This only affects non-persistent desktop pools, and only when the user happens to be logged into a Workspot desktop when the AD record is updated. Workaround: Reboot the user's longest-running desktop.