The following Workspace Control installation file, available for download at the downloads section of the Ivanti Community:

  • Ivanti Workspace Control Installer [version].exe - This is an installation package that contains the MSI files for the Workspace Control components.

Individual components can be extracted from the installer and are also available for download.

If you want to use the Relay Server, separate installation files are required. The installation of Relay Server requires Microsoft .NET Framework 4.7.2 or higher.

For further details about Relay Servers, see the document Getting Started with Workspace Control Relay Servers.

Software installed on Agent

  • A supported operating system. See the Compatibility Matrix.
  • Microsoft .NET Framework 4.7.2 or higher (4.6 or higher for Workspace Control 10.2.x and earlier).
  • Microsoft .NET Framework 4.7.2 Client Profile or higher when using User Setting caching (4.6 or higher for Workspace Control 10.2.x and earlier).


  • Each full installation of Workspace Control requires approximately 125 MB of hard disk space for the application files. This does not include the data stored in the local cache. The hard disk space required for cached data entirely depends on the configuration of your Workspace Control environment.
    Each Console-only installation of Workspace Control requires approximately 50 MB of hard disk space. These installations do not require any additional disk space for the local cache.
    Each Agent-only installation of Workspace Control requires approximately 82 MB of hard disk space.
  • The memory needed for the Workspace Control Agent depends on the configuration. For example, in an environment with applications enabled and 100 authorized files configured, the Agent needs around 27 MB of memory during a normal user session (applications are running, other applications are started and stopped again).
  • Each Agent requires drive space on the home drive for storing Workspace Control settings. As User Settings are stored in the same location, this amount increases if User Settings are available to the user. The required amount of space then depends on the size of the stored User Settings. All Workspace Control settings, including User Settings, are compressed when stored.


A supported database. See the Compatibility Matrix.


Database prerequisites

Microsoft SQL Server

  • Mixed Mode authentication (only when using SQL Server login for Authentication)
  • MDAC 2.6 or later on all Agents
  • A named SQL Server System Administrator login ID
  • If the Force protocol encryption option is enabled: Microsoft Native Client for SQL Server or Microsoft OLE DB driver for SQL Server

Microsoft SQL Azure

  • Microsoft Windows Azure credentials
  • Microsoft Native Client for SQL Server or Microsoft OLE DB driver for SQL Server on all Agents connecting directly to the Datastore


  • Oracle DBA credentials
  • Oracle database drivers on all Agents connecting directly to the Datastore

For Microsoft SQL Server and Microsoft SQL Azure:

  • If you have the option Fail-over Cluster Instances enabled (Active-Passive), if a fail-over to a secondary database happens, (global) objects in the Workspace Control Console are displayed with a blue icon with an “i” inside. This means the objects have read-only access to the Datastore at that moment. Restart the Console to reconnect to the Datastore.

  • Always-On Availability Groups are not supported. Based on the architecture of Workspace Control, high-availability can be made available through the use of Relay Servers. In addition, Workspace Control Agents always use the local cache. This means that the Agents will function without an active Datastore connection, using the cached data.

  • More information about the Microsoft OLE DB driver read the Microsoft OLE DB Driver for SQL Server article on Microsoft Learn website.

  • The registry setting useMSOLEDBSQL can configure the Workspace Control Console to not use the Microsoft OLE DB Driver for SQL Server when connecting to the Datastore. For more details, see useMSOLEDBSQL.