How To Run Workplace As A Service


This article will cover how to set up your Workplace agent to run as a service on a Windows PC. Please note that the user you want it to sign in as needs to be an team adminstrator.


  • A Workplace customer
  • The credentials for the team administrator account
  • Internet Explorer or Edge browser
  • Workplace agent installed

The Process

  • Launch Internet Explorer or Edge browser
  • Type awp:run_service in the address bar
  • Select to run either as LocalSystem or as the Windows user under which Workplace Desktop is running

The LocalSystem will enable Workplace Desktop to run as a background process even when the user is not logged in. It may not, however, have sufficient permissions to the data set to sync; the LocalSystem account requires full permissions to the data set in order for syncing to function properly. The Windows User account is more likely to have the necessary permissions to the data set, but must be part of the Admin group and listed in the “Log on as a service” policy in the Local Security Policy.

Run Workplace Desktop in Multiple Windows User Accounts

Workplace Desktop for Windows 5.2 or later can be run on multiple user accounts, even when running in service mode.

This is useful in scenarios in which multiple Workplace accounts must be synced with a file server, typically a multi-tenant setup hosted on a single file server. Previously, this would have required a separate machine (virtual or real) to host each instance of Workplace Desktop. As of the Workplace Desktop 5.2 for Windows release, a different Windows user account can be used for each instance, and each instance can be run in service mode. This means that each instance will automatically start after a reboot or an update to Workplace Desktop.

To use this feature, do the following:

  • Launch and configure Workplace Desktop within each Windows user account.
  • Run as Service as described above