Connection from the Relay Server to the Datastore can be immediately or with a predefined schedule, this is especially very useful if the Datastore is in another site with reduced bandwidth. Each Relay Server caches the content of the Datastore with the configuration data and the usage tracking information of the Agents. Basically the Relay Server acts as a proxy between the Datastore and the Agents. In RES Workspace Manager 2012 a new component was introduced: the Relay Server. The machine starts the Workspace Manager Agent and, since there is Datastore to contact, it will present the users workspace with the configuration without the important security update. When a machine starts up the RES Workspace Manager retrieves the latest version from the Datastore and stores this in the local database cache.īut what happens when the database server fails and the Datastore becomes unavailable? Because the machines are non-persistent they will revert to the initial state of April 1st. On April 21 st an Administrator changes a configuration, for the sake of the argument this is an important security policy, which is stored in the Datastore. The image of the non-persistent machines is created on April 1 st, the database cache stores the configuration of this date. In an environment with a normal setup (where Agents connect directly to the Datastore ) the situation can be as followed. RES Workspace Manager normal architecture New changes cannot be configured of course. When the Datastore is unavailable due to a failure this does not impact the users workspace, all the latest (security or policy) changes are applied as configured. To continue running when the datastore is not available, for instance on a laptop that is not connected to the network, each Agent has a database cache stored locally on the machine. Each machine that runs RES Workspace Manager has an agent that connects to the Datastore to receive the configuration. Administrators connect the console directly to the database to see and edit the configuration. RES Workspace Manager stores all the configuration and state data in a database (the RES Workspace Manager Datastore ). This has a lot of benefits but comes with some challenges. When a machine is non-persistent the machine reverts to the state it was before (also called stateless) as it is stored in the “golden image”. Virtual desktop machines are either persistent or non-persistent. UEM products like RES Workspace Manager are common in virtual desktop environments like SBC or VDI (I don’t like the term VDI) because they simplify management and improve consistency between all the machines. RES Workspace Manager is a user environment manager (UEM) that enables you to centrally manage the user workspace (RES term for the users desktop, start menu and all user related settings) for both virtual and physical machines.
0 Comments
Leave a Reply. |