The RES Workspace Manager Agents
An important aspect of RES Workspace Manager 2011 is the architecture of each RES Workspace Manager Agent (i.e. each Terminal Server, workstation or laptop that runs RES Workspace Manager). The following illustration provides a schematic overview:
Configuration data received from the Datastore is cached locally. Each RES Workspace Manager Agent uses its cached data instead of connecting to the SQL database directly.
The data cache also stores user information (log files and monitoring data) that is collected by each RES Workspace Manager Agent. The RES Workspace Manager Agent Service sends this data from the local cache to the Datastore for centralized access from the Management Console.
Read more about the RES Workspace Manager Agent Service (res.exe) and about the communication processes to and from the Datastore in the chapter "The RES Workspace Manager communication architecture".
Each Agent Cache consists of:
- log files
- registry settings
The log files contain monitoring files, error logs and PowerTrace data from RES Workspace Manager end-user components. These files are stored in a dedicated cache folder:
%programfiles%\RES Software\Workspace Manager\Data\DBCache\Transactions
They are forwarded to the RES Workspace Manager Datastore by the RES Workspace Manager Agent Service.
The objects stored in the local cache are XML files containing part of the RES Workspace Manager configuration data, and various resources in different formats.
These files are stored in subfolders of
%programfiles%\RES Software\Workspace Manager\Data\DBCache:
- \Objects contains .xml files specifying application settings, PowerLaunch settings and other configuration settings.
- \IconCache contains icons for your programs and shortcuts.
- \Resources contains a number of subfolders that store your .ica files, .osd files, .adm files, files used as desktop images, and files used in your folder maintenance. The \Resources folder functions much like a distributed fileshare.
The RES Workspace Manager Agent Service forwards these objects from the RES Workspace Manager Datastore to the local cache.
The remainder of the RES Workspace Manager configuration data is implemented as Registry settings. The data is forwarded from the RES Workspace Manager Datastore to the agent cache by the RES Workspace Manager Agent Service, and is stored in the following registry key:
This concerns settings that have a restricted set of possible values, such as:
- MemoryShield > "Enabled": the value of the setting can only be "Yes" or "No".
- Maximum number of simultaneous logons: the value of the setting can only be a number.
You can define exceptions per user by customizing the registry key:
These exceptions can be implemented using the RES Workspace Manager Actions technology.