Running Workspot Windows Client in Kiosk Mode

Robert Plamondon -

Kiosk mode allows multiple users to share a Workspot client installation. You would use kiosk mode on shared devices; for example, in clinic examination rooms. Users log onto the Workspot Client at the start of each session. Once logged in, they are presented with the same desktops and applications they would see on their own Workspot-enabled devices. The normal on-boarding process, which dedicates the Client permanently to a single user, is skipped.

The Workspot Client runs in Workspot mode by default. Kiosk mode requires that you set command-line switches when launching the Workspot Client .msi file.

Once installed, kiosk mode and the other command-line parameters will be retained across updates. Switching from kiosk mode to Workspot mode, or vice versa, requires that you uninstall and reinstall the Workspot Client.


  • Workspot Enterprise Connector
  • Active Directory (AD) or Azure Active Direcotry (Azure AD) Integration
  • The latest Workspot Client in .msi format
  • A client system running a supported Windows OS.


Kiosk mode is currently supported in the Windows 32-bit and 64-bit Client only.

Using Kiosk Mode

From the end-user's point of view, kiosk mode is almost identical to Workspot mode. Users see their own Workspot desktops and applications, just as they would with dedicated devices.

The differences revolve around logon and logoff procedures:

  • Kiosk mode does not use a PIN: You must log in at the start of each session.
  • Release 2.4.6 and up: If the autologoff option is specified on installation, closing your desktops or applications also logs you out. (This happens when you close all open desktops or apps. For example, if you have two desktops open, you must close both of them before you are logged out.) The login screen is then displayed, allowing another user to log on.

Installing Kiosk Mode

1. Download the Windows Client for your Windows OS (32-bit or 64-bit):

Workspot Windows Client
Workspot Windows Client

2. Run the Workspot Client .msi file with the appropriate switches. These are described in Installer Switches, below. Switches may change from release to release.

  • For the release 3.0 Workspot Client, use the following format:

msiexec /i WorkspotClientSetup64.msi mode=kiosk subdomain=customerstring allusers=1 /l* %temp%\WorkspotInstall.log

where subdomain=customerstring uses the subdomain identifier of your company, as set up by Workspot (usually your company name in lower case, such as "acme").

The subdomain=customerstring mapping is set manually by Workspot on request, and can be seen in Workspot Control under "Setup > Configuration > Registration and Authentication > Directory Services > Subdomain."


  • For the release 2.4.x Workspot Client, use the following format:

msiexec /i WorkspotClientSetup64.msi mode=kiosk allusers=1 /l* %temp%\WorkspotInstall.log

where is your Active Directory domain.

3. The installation process begins. Follow the instructions on the installation screens.


4. Launch the Workspot Client and log in as a Workspot user. Your desktops and applications will appear.



Command-Line Switches

Use Microsoft's built-in command msiexec to install the Workspot Client.

Msiexec Task Summary

  • Basic msiexec command format
    • msiexec /option required_parameters optional_parameters
  • Install a product
    • msiexec /i productname.msi optional_parameters
  • Install or configure a product
    • msiexec /a productname.msi optional_parameters
  • Administrative installation over the network
    • msiexec /j[u|m] productname.msi optional_parameters
    • where u = install for current user, m=all users
  • Uninstall
    • msiexec /x productname.msi product_code

Standard Msiexec Options

Note: Standard msiexec options start with a slash ('/') character, but Workspot options (in the next section) do not.

  • /l* filename
    • Send detailed logging information to filename.
  •  /quiet
    • Run the installation silently.

Workspot Client Options

Note: Unlike standard msiexec options, Workspot-specific options do not start with the slash ('/') character.


  • if mode=kiosk, the Workspot Client is run in kiosk mode, allowing the same Client instance to be shared among users. mode=kiosk requires that the domain or subdomain switch be used (depending on the Client release). In this mode, users enter their domain or Azure AD credentials to login to Workspot.
  • If mode=workspot (default), the Workspot Client is run in Workspot mode, which allows only one Workspot user per Windows user profile. To share a Windows device between multiple users in Workspot mode, each user must logon to Windows using a different user profile.


  • Releases 2.4.6 and up. Kiosk mode only. If set, the current user session will be logged off when the user closes the last open desktop or application. This simplifies the sharing of kiosk-mode devices and minimizes the number of sessions accidentally left active.

CloseButton={close, disable,minimize}

  • Sets the behavior of the Close (X) button on the Workspot Windows client. Only applicable when mode=kiosk.If this switch is not included or specified as "close" (default), the button functions normally. If “disable” is selected, the button is greyed out and does nothing. If “minimize” is selected, when the button is hit, the Workspot Client is minimized to the taskbar.


  • When the client device is on the corporate network (determined by the Location Detector settings in Workspot Control), the Remote Desktop (RD) Gateway is bypassed by default, and the Workspot Client connects directly to the desktop or application through your corporate network or VPN. If this is not desired and you prefer to use the RD Gateways configure in Workspot Control, add the names of the desired RD Gateways here.
  • If there are spaces in the gateway name, use quotes (“rdgateway one, rdgateway two“). To bypass all RD gateways, use an asterisk: "NoRdgatewayBypassList=*".


  • Install the Workspot Client in the Program Files directory for all users. When using this option, the command must be run from an elevated command prompt or via a software distribution tool. If this option is not selected (default), the application will be installed in the current user's folder.


  • Sets the "Use all monitors for Remote Desktop" when Workspot starts the first time. This is most useful for Kiosk mode, where this is not a persistent setting when set by the user.


  • Disables Remote Desktop Protocol's auto-reconnect for remote desktops and applications. Useful for environments where auto-reconnect triggers unwanted multi-factor authentication challenges.[,]

  • Releases before 3.0. Used with Kiosk Mode, where it is mandatory. Specifies the fully qualified active directory domain (, not org), or comma-separated list of such domains, used for this installation. In kiosk mode, the dialog box will show the list to the user on the login screen.


  • Release 3.0 and up. Used with Kiosk Mode, where it is mandatory. Specifies a string representing your customer name, typically the same string you use for your public Web site. For example, if your company is Acme Industries and your Web site is a, your Subdomain will be acme. This string is assigned by Workspot.


  • Release 3.0.2 and Up. Used with Kiosk Mode, where it is optional. Specifies the fully qualified active directory domain (, not org), to be listed first in the Client's drop-down domain list. If the preferreddomain doesn't match a domain listed in Workspot Control, it is ignored.


  • Remembers the most recent username and uses it as the default for the kiosk mode login dialog.

Special Flags

These switches are not recommended for ordinary installations (consult your Workspot representative).


  • Specifies that all RDP authentication is via a smartcard.


  • Allow the Workspot Client to be installed on machines that are still running deprecated versions of RDP (v8.0 or lower).



Have more questions? Submit a request


Powered by Zendesk