Communication Model

Workspace Control stores all configuration data and resources in an Oracle or SQL-based database: the Workspace Control Datastore. You can set all your Terminal Servers, workstations, virtual desktops, and laptops to use a single database or you can use replication to set up multiple databases.

The first time a connection between an Agent and the Datastore is established, for example directly after the installation of the Agent, the Datastore will transfer all its configuration settings to the local data cache on the Agent. After this, downstream data traffic will consist of Datastore changes only; never the full contents of the Datastore. If the Datastore is busy or unavailable, the request is deferred until the Datastore is able to process it. Because of this selective synchronization, the data packages that are transferred are very small, which reduces network traffic significantly. This greatly increases the scalability of Workspace Control with regards to the number of devices that can use a single database.

Workspace Control Communication Model

Process Overview

The Workspace Control Console communicates directly with the Datastore. All Workspace Control Agents receive a local cache containing configuration data from the Datastore (optionally through a Relay Server). Each Agent uses its cached data instead of connecting to the SQL database directly.

The local cache also stores user information (log files and monitoring data) that is collected by each Agent. The Workspace Control Agent Service, which runs on each Agent, sends this data from the local cache to the Datastore directly or via a Relay Server.

Local caches are updated through selective synchronization: the Workspace Control Agent Service retrieves only changed information from the Datastore to place in the local data cache. This reduces the load on the central database significantly. This downstream communication is asynchronous: if the Datastore or the Relay Server are busy or unavailable, the request is deferred until they can process it.

The Workspace Composer logs all actions that a user carries out in his workspace. Some user actions are also recorded as Usage Tracking data. These log files and Usage Tracking data are cached locally on the Agent. Because all communication between the Datastore and Agent caches is asynchronous, Agents do not upload log information to the Datastore first before proceeding with other tasks: As soon as the log data has been stored in the local cache, the Agent will continue operations.

When the user starts a session on an Agent, the Workspace Composer uses the data in the local data cache to build the user workspace. The main elements that are responsible for the contents of the user workspace are:

  • The Workspace Control Agent Service

  • The Agent cache

Port Utilization



<vendor default>

Datastore connection

The following components connect to the Datastore:

  • Workspace Control Console

  • Internet Information Services -- IIS (Management Portal)

The following components optionally connect to the Datastore:

  • Relay Servers

  • Workspace Control Agents

1942 TCP/UDP

Used by the Workspace Control Agent Service for communication between the Workspace Control Console and Workspace Control Agents (for example: when triggering Force Cache Updates from within the Workspace Control Console). The port cannot be changed (this port is hardcoded).

When a Relay Server is installed on a computer that contains an Ivanti Workspace Control Agent Service, port 1942 is not available as the listening port for the Relay Server. If you try to configure with port 1942, you will get an error message that mentions the port is already in use.

80 TCP

443 TCP

IIS connection:

  • Management Portal

Workspace Control Console connection:

  • Automation Dispatcher

  • Identity Director Catalog Services

139 TCP



Active Directory

139 TCP


Network shared drives