![]() ![]() To prevent each Agent from communicating with the Datastore (or Relay Server) via a WAN connection a Relay Server can be placed in each remote site. This (of course) does not mean less license are needed, each agent still requires a license. When Agents are configured to communicate with the Relay Server the number of connections to the Datastore is decreased to two per Relay Server, regardless of the number of Agents. When the Datastore is stored on an Oracle server this limit is “100s of thousands”. With each Agent having two connections (one for the configuration database and one for the logging database) a Microsoft SQL server could reach its User Connection limit of 32.767 (see Maximum Capacity Specification for SQL Server). In a large environment the server hosting the Datastore could reach its connection limit. This could led to challenging situations because either the Datastore needs be replicated to multiple sites or each Agent communicates via a WAN connection to a remote Datastore. This requires that the Agents are able to communicate to the Datastore, even when they are in different locations. When administering RES Workspace Manager the Console always communicates directly with the Datastore, never via a Relay Server.īy default Agents connect directly to the Datastore. This makes the Datastore a critical component in a RES Workspace Manager infrastructure. RES Workspace Manager stores all the configuration, logging and usage tracking data in a RES Workspace Manager Datastore. Just like the Relay Server the RES WM Agent will poll the Relay Server every x time (default: 5 seconds) and update its local cache after x time (default: immediately) Since this location is on the system drive (by default) it will monitor the available free disk space to prevent resource depletion (see other facts). The Relay Server stores the entire RES Workspace Manger Datastore in its cache location: %ProgramData%\RES\Relay Server, this location can be changed. The Relay Server polls for changes every x time (default 5 seconds) and updates its local cache after x time (default: immediately). While the name suggest the Relay Server relays the traffic between a RES WM Agent and the RES WM DataStore it actually doesn’t, instead it acts as intermediate storage. It is a Windows Service that can be installed on a Windows operating system and by default listens on TCP port 1942 (registered at IANA), the same port that’s used by the RES WM Agent (see other facts). The Relay Server is an intermediate component between the RES WM Agent and the Workspace Manager Datastore, if required Agents can still connect directly to a Datastore. The Relay Server was introduced with RES Workspace Manager 2012 as an optional component. In this article I’ll explain what the Relay Server is, how it can help you in your Workspace Manager (WM) environment and reveal some of its mysteries. ![]() This service runs under the local system account, which may not be changed.With the release of RES Workspace Manager 2012 a new component was introduced: the Relay Server. On the Agent, also the driver service Workspace Control PE ( respesvc64.exe) runs. ![]() Pwrcache /upload (checks the Agent for transactions that need to be processed by the Datastore).Pwrcache /download (checks the Datastore for changes that should be downloaded to the Agent).The Workspace Control Agent Service contains the following sub processes: Handle License requests (session and application).Unlocking and locking the user Registry.The tasks of the Workspace Control Agent Service ( Res.exe) consist of: The following information is stored at HKLM\Software\RES\Workspace Manager / HKLM\Software\Wow6432Node\RES\Workspace Manager: Key Res.exe and its sub processes have only one instance per device. The Workspace Control Agent Service is named Res.exe. These transactions are stored in the central database by the agent service whenever it can access the central database As someone works in their User Workspace, information is collected by the Workspace Composer in transactions. The Workspace Composer running on the Windows desktop will use this local information and the context of the user to compose and secure (parts of) the User Workspace. The Workspace Control Agent Service and its subprocessesĮach desktop that has the Ivanti Workspace Composer installed, has an agent service that retrieves the information from the database and stores it locally.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |