By Max Ranzau

Are you new to Virtual Workspaces, Dynamic Desktops, Automation Management and Reverse Seamless windows? Too many new buzzwords flying around to come to grips with after the 5 ringed Circus RES rode into town? :*) No worries, many people are in the very same situation these days. When you need to figure what Workspace Manager, VDX and Automation Manager are all about, first thing is to scale that brick wall of buzzwords so you know what the story is when somebody talks about Workspace Containers, Engines, and Custom Resources etc.

The RESpedia below, is a massive ongoing work in progress by yours truly. For that reason, you will likely encounter items which have not been described completely yet. These are marked as work in progress () If you would like to contribute with some relevant terminology, just comment on this article below and I’ll move it into the article. Some final notes: The RESpedia is ordered alphabetically and organized across all RES Software products. Not all terms in this glossary are official RES terminology, but may come from engineering jargon in the field or similar sources. Since the original inception, RES Marketing has added a light glossary to the corp site, courtesy of You can find it here.

To make it easier to recognize to which product or part of the RESverse the term applies, I’ve added relevant tags to the terms in the RESpedia. Here is an overview of them:

  • [W] RES Workspace Manager (formerly known as PowerFuse)
  • [A] RES Automation Manager (formerly known as Wisdom)
  • [V] RES VDX related
  • [O] Service Orchestration Module (formerly known as Orchestration Pack for Wisdom)
  • [H] RES HyperDrive related
  • [B]usiness stuff
  • [T]raining related.

Where you see links in Italics, it refers to a jump link to another item covered in the RESpedia. Links which are not in italics, refer to external resources, such as other RESguru articles, Wikipedia, etc. Below is an alphabetical jump index of the entire RESpedia:





Access Balancing [W] – A performance subsystem found in the RES Workspace Manager product, which acts as a session throttle. It works really well to prevent overloaded servers in peak load periods. The log of Access Balancing can also help you analyze your logon-time SLA. See this article for info on how to do just that.

Access Control [W] – The ability to control to who and where a configuration or security object is available. Access Control is a tab found on most Workspace Manager objects, where you can configure one or more Access Principals to configure the identity of the user. Multiple access principals can either be combined with a logical AND or a logical OR. The access principal can optionally be combined with a Location and Devices setting, describing where/what the computer is. The logical relationship between the Identity and Location elements of an Access Control configuration is always a logical AND.

Access Principal [W] – This term references the methods with which you can apply Access Control to almost any object in Workspace Manager. Examples of simple access principals are groups, ou’s and individual users. More advanced access principals exists, such as Language Selection, Orchestration Services (only available when Automation Manager/Service Orchestrationtion is configured and enabled). You are also able to use exclusions. Note that while you can mix and match access principals on regular objects, you can currently (per Workspace Manager only select one access principal on applications.

Action [O] – This is an activity which moves a Service Orchestration workflow from one step to the next after completion. An example could be asking somebody, like a manager, for permission to add a given new Finance employee access to the payroll system.

Action [W] – Within the context of the RES Workspace Manager, actions are task items that can be assigned a managed application to execute upon launch. Examples of actions are: Merge registry settings into HKCU, execute a command, run an Automation Manager task, modify contents of home directory, and much more.

Actor [O] – Person to whom a service workflow action applies. This can be the subscriber to the service, the requester of the service, a person determined by a smart rule or someone who has been directly assigned to the action. An example of an actor is someone who has to approve a workflow. They have to act in order for things to continue, hence they are referred to as an actor.

Adaptive Security Module [W] –

ADDTOWORKSPACE [W] – One of the public MSI attributes for the RES Workspace Manager installation. This parameter, used as ADDTOWORKSPACE=”NameOfYourWorkSpaceContainer”, will automatically add the installed Workspace Manager agent to the Computer Control tab of the given workspace container.

$Adinfo() [W] – A function in Workspace Manager which will allow you to reference any Active Directory Service attribute from within configuration items available in Workspace Manager. For example, you could use $adinfo(title) as part of an Email Template signature for Outlook or perhaps generate user initials for Office. See the $Substring() function for a combined example of this. Note: $Adinfo can also return some attributes from other directory services, such as NDS if anybody out there still uses that. Basic stuff like $adinfo(title), $adinfo(office), $adinfo(department), $adinfo(homephone), $adinfo(fax) should work there, however if a call to $Adinfo returns blank it’s most likely the specified attribute doesn’t exist.

Administrative Note [W,A] – Formerly known as Annotations. You will find these fields many places in both Workspace Manager and Automation Manager and it’s your job as a responsible console operator to put some sensible information into them. Don’t enter information here just for the sake of entering info. Put in good comments that will help yourself and your colleagues 6 months down the road to figure out why you did any particular configuration in the first place.

Administrative Roles [W, A] – Formerly known as Security Roles. Adminstrative Roles are used to delegate what part of the consoles (both Workspace Manager and Automation Manager) can be used by whom. This is a brilliant method for slicing out the console for different parts of the IT organization. For example you may only wish to give access to Workspace Analysis and User Sessions for firstline supporters, while 2nd and 3rd line support get more privileges. On the other hand, the CIO may request a pure read-only role to the console, so he can keep up to speed on what’s going on, without wanting to change anything. In Workspace Manager you can in addition combine Administrative Roles with Scope Control. If a user does not belong to any administrative roles, he/she will be refused access to the console.

Advanced Admininstration [W] – Obsolete name for one of the featureodules available for RES Workspace Manager. This feature module is now know as the Delegation and Compliance Module.  See also the other current feature modules: Dynamic Configuration and Adaptive Security

Advanced Mode [W] – New feature in Workspace Manager 2012 SR3, which reveals the more advanced settings of User Settings on a Managed application. The User Settings tab now has an Advanced button at the bottom which reveals additional settings, although nothing new from SR2 to SR3. See also Basic Mode.

Agent [W,A] – A term used for both Workspace Manager and Automation Manager. Both are regular NT services which run in the background and talk with respectively the Workspace Manager and Automation Manager datastores. The Automation Manager agent’s purpose is to execute the jobs, which are scheduled to it. The Workspace Manager agent’s (see RES Service) primary function is to ensure that the DBcache folder is synchronized with the central datastore. Agents are uniquely indentified by either a unique GUID or WUID, the MAC address of the first NIC, or the combination of domain+computername.

AI_DESKTOP_SH [W] – One of the public MSI attributes for the RES Workspace Manager installation. This parameter, used as AI_DESKTOP=<0|1> determines if an icon for the Workspace Manager Console is placed on the AllUsers Desktop during installation. Default is 1, meaning icon is created. If you set it to 0, it’s great to use for StealthMode deployment of Workspace Manager. See also AI_STARTMENU_SH.

AI_STARTMENU_SH [W] – One of the public MSI attributes for the RES Workspace Manager installation. This parameter, used as AI_STARTMENU=<0|1> determines if an icon for the Workspace Manager Console is placed on the AllUsers Start Menu during installation. Default is 1, meaning icon is created. If you set it to 0, it’s great to use for StealthMode deployment of Workspace Manager. See also AI_DESKTOP_SH.

Alerting [W,A] – A feature in both Workspace Manager and Automation Manager, by which administrative staff can be alerted to many different events. For WM you can trigger for example an alert if  application fails to launch, something went wrong during login, an unauthorized executable was attempted launched, licensing and about 20 other items. These can be found under Setup | Integration | Alerting in the WM console. For AM, you can trigger an alert for jobs which are Failed, Canceled, Aborted, Completed or Completed. These are configured under Infrastructure | Datastore | Global Settings | Job Notifications. For either product alerts can be either emails or SNMP alerts. For Workspace Manager you can additionally launch a commandline within the user’s session or shedule an AM job to run.

Alligator [B] – An obsolete expression used once upon a time by RES Software developers in NL, to denounce a bug or unexpected behavior, as in “Whoa! We’ve got an alligator here!”. The origins of the expression is rumored to have come from the initial introduction where new developers were explained: “You’re here to kill an alligator, not to drain the swamp”. In short it was a way of saying don’t persue an overly complex solution to a simple problem. To keep it in mind, we once had big alligator pooltoys hanging from the ceiling in R&D :-)

AM [A] – Non-official (but often seen) acronym for the RES Automation Manager

AMC [A] Non-official acronym for the Automation Manager Console. Not to be mistaken for the Citrix Access Management Console. This console used to be known as the WMC or Wisdom Management Console, which happens still to be the name of the binary.

Annotation [W,A] – Obsolete name for Administrative notes. Found in products prior to PowerFuse 2010.

AppGuard [W] – AKA Application Security. This is a security subsystem in Workspace Manager. Appguard prevents unauthorized processes from running. This is done by way of a kernel filter driver which intercepts all calls to the OS to spawn new process names. If the processes do not match processname+authorized path to the executable, the process will be barred from executing. When enabled, it can be run in either Blocking Mode or Learning Mode.

AppID [W] – AKA Application ID. This is an unique-value integer, which is assigned to every managed application in RES Workspace Manager. When you start with a blank  environment, your first managed app will be assigned AppID 16, as the 15 first are reserved for internal use (see this article for details). AppID’s for your own managed apps can be inspected if you open the Workspace Manager Management Console and go to Composition | Applications | Managed Applications and click on the Application List tab. In the ID column, you will see the AppID’s for every application. The AppID is used by PWRGATE.exe to invoke the right actions when a managed application is launched by a user. Note, there are some reserved application ID’s in Workspace Manager for internal applications such as the Workspace Preferences and Printing Preferences. There is an article on this specific topic right here.

Application List [W] – An alphabetical list view of all Managed Applications within RES Workspace Manager. This view is found on the Application List tab, located under Composition|Applications. The application list view has a hidden Instant Search feature: just start typing any part of any application name and the list will jump toward the correct entry as you are typing.

Audit Trail [P,W,O]- AKA Audit Log. A function in Workspace Manager and Automation Manager which will allow you to see which console operator modified a given setting in the Workspace Manager console. An audit trail is usually available per object, such as an application or for example a drive letter mapping. In the products there is also a global audit trail which will show you what’s been going on across all objects. Audit Logs can be protected from deletion with a separate password.

$AutoCount() [W] – A function within RES Workspace Manager which returns a cyclic value. For example $AutoCount(1-4) will return one of the numbers 1, 2, 3, 4, 1, 2, 3… each time it’s called.  This function is very useful if you have to generate unique, sequential and non-repeating number. One use case from back in the day was LUN numbers to connect some types of terminals to their hosts. Also you can use it to rotate through a list of predefined wallpapers, by using Autocount to generate a filename for the %DESKPIC% variable. See the online Functions help for an example.

Autolink [A] – A feature in RES Automation Manager where project parameters or runbook parameters can automatically be linked to the parameters inside. Only prerequisite for this to happen is that you have used the same names for the parameters in the modules/projects that you are linking to. For example, if you have a project parameter called DomainName, a module parameter in an embedded module must use the same name for the AutoLink feature to work.

Automation Manager [A] – See RES Automation Manager.

Automation Manager Integration [W] – RES Workspace Manager has the ability to interface with it’s sister-product RES Automation Manager. In effect this integration allows you to execute Automation Manager projects and modules either when a user logs on, or when a certain application is launched. This effectively gives you install-on-demand capability, without having to sacrifice security. The beauty of this integration is that Automation Manager executes the job using the Automation Manager agent, which runs in the context of LocalSystem per default. Effectively there is no hassle with the UAC, or having to elevate the user’s rights in the user session one way or another.

Automation Manager Console [A] – AKA AMC. The application used to manage RES Automation Manager with. The AMC connects directly to the Automation Manager datastore. The console is protected by Administrative Roles, where you can specify who can do what in the console. There are also several interesting commandlines to be used with the console executable. See article RG017 for further details.

Azure [W] – A new cloud based SQL Database offered by Microsoft, which Workspace Manager 2010 now supports natively as it’s datastore. See this article for more information.



Baseline Desktop Analyzer [W] -Aka BDA. This is a FREE service from RES Software (Available publicly from July 1st 2011) The BDA will allow organizations to gather an overview of what’s going on in their user environments before starting any kind of project affecting the users desktops. It allows you to start down the path of truely organized Desktop Transformation. The Baseline Desktop Analyzer is an native Azure based cloud app, which analyzes data collected by the Desktop Sampler. For more information see technote RG03B and watch a Citrix TV demo here.

Basic Mode [W] – New feature in Workspace Manager 2012 SR3, which only displays the the most simple and readily available configuration items of the User Settings tab on a Managed application. The User Settings tab now has an Basic/Advanced button at the bottom which reveals/hides additional settings, although nothing new from SR2 to SR3. See also Advanced Mode.

Blocking Mode [W] – Refers to a state which a security subsystem is currently operating in. Note: There is no such term as Blocking Mode in the Workspace Manager Console, this is just a term commonly being used by field engineers. Blocking Mode is said to be active when the given subsystem is set to enabled.

Building Block [W,A]Term applies to both Workspace Manager and Automation Manager. A Building Block is a block of configuration data for either product which is stored in XML format. Any binary payload is placed in a .XBB file. A Building Block allows you as an integrator to re-use configuration from one customer site to another, thereby being more efficient. As a Console Operator it allows you to backup/restore individual parts of the system and re-use them elsewhere. To create a buildingblock, either rightclick in the console tree and select the required buildingblock operation from the context menu. Alternatively look for the building block button () within most nodes in the consoles. An example of a valuable Automation Manager building block could be one which installs a Citrix server from scratch. Building Blocks can be imported and deleted in Workspace Manager using command line parameters.

Bronze [W] – One of the editions which RES Workspace Manager 2011 is available in. This is the smallest retail edition available. Note: You still have the seperate Express edition, however since it’s free it’s not regarded as part of the regular retail editions, besides Express is a seperate download. Anyway, the Bronze edition of WM only includes the Personalization and Configuration module. See also Silver, Gold and Enterprise editions.



Capture once, track further [W] – This is the new third Zero Profile mode available from Workspace Manager 2010 SR2 , which allows you to use the best of immediate mode and Capture Targeted mode to further ease migration scenarios. What happens is that you start with specifying a given setting which you want to pick up. For example, this setting could be the Outlook .N2K file which caches all the email addresses the user has typed until now. The setting will be picked up in Capture Targeted mode the first time, without the user having to make any changes to it. This could be arranged by a Stealthmode Workspace Manager deployment to the existing environment. As soon as the setting has been picked up, the zero profile mode will be flipped to immediate mode and all changes to the setting will be tracked in realtime by Workspace Manager from there and onwards.

Capture Targeted mode [W] – AKA Specified mode AKA legacy mode. This is one of the 3 Zero Profile modes available for user settings in Workspace Manager 2011, which is compatible with the old User Preferences feature in Workspace Manager 2008. Contrary to Immediate mode, which captures anything a given target does, specified only grabs specifically what you tell it to grab. This is very useful for picking up known settings such as the custom dictionary file for office, favorites for IE, etc.

Catalog [O] – This is essentially a list of Service Orchestration Module Services which may be made available to users or 3rd party applications.

Catalog Services [O] – This is a NT service, part of the Service Orchstration Module for RES Automation Manager, which is installed in your datacenter. The purpose of the catalog services is to publish sets of available Orchestration services. May be used by the Orchestration Clients, Console and/or 3rd party applications.

Category [O] – Logical classification of a group of people in the Service Orchstration Module for RES Automation Manager. A category may be pretty much anything, for example: Department, Education, Shoesize, etc – whatever you need to distinguish people on in order to orchestrate services for them in your organization. You can then filter Qualification uppon these categories.

Classification [O] – A relationship between people and a category. Example needed.

%CLIENTIPADDRESS% [W] – An environment variable which is made available in RES Workspace Manager at logon. If the user is logged in on a workstation/laptop, the variable will contain the IP address of that computer. If the user is logged into a TS/Citrix/VDI environment, the variable will contain the IP address of the client computer or thin client device. See also %FULLUSERNAME%.

Composition [W] – A main node of the new Workspace Manager 2010 console. It includes access to Managed Applications, User Installed Applications, Files and Folders, Data sources and User Settings. In short, the composition covers every type of item the users might receive in their managed workspace.

Computer Control [W] – A tab found on the properties of every Workspace Container in the Workspace Manager console. This is a list of computers – not computer names – referenced by the Workspace Manager agent’s identification method. This means that if you for example are using MAC address identification, you can rename the computer as you want and it will still remain a member of this WorkSpace container. Remember that Computer Control can be combined with regular Access Control within the Workspace Container. If this happens, all items are treated with logical AND’s. This means if a Workspace Container’s computer control tab contains ComputerX, and has UserY and LocationZ defined on the Access Control tab, all three items must test positive before the Workspace container is active.

Computer Function [A] – One of the Conditions which RES Automation Manager offers when processing tasks. With computer function you can add task logic on if the target computer is a SQL server, Domain controller (both DC’s and legacy PDC/BDC’s are supported), running the Timesource service, is an Apple File Protocol server, is a Lan Manager 2.x domain member, is sharing a print queue, running dial-in service, supports Microsoft File and Print for NetWare, Running a browser service as backup, running the master Browser service, running the domain master Browser or is a Terminal Server.

Condition [A] – This is one of the features of Automation Manager which gives it significant value when added to other automation such as SCCM and Citrix Workflow Studio. Conditions in RES Automation Manager allow you to control whether a given task is executed, skipped or failed. You can also optionally choose to skip all following tasks. Criterias for conditions can be Computer Function, Date and Time, value of a (system) Environment Variable, Version of an executable/dll, full or partial FQDN, OS bit version, OS suite, OS type, OS version/servicepack level, Module parameters, Processor Architecture (x86/x64), Registry setting (HKLM, HKCR, HKU) and State of previously executed task (completed/failed)

Configuration.XML [V] – This file is used by VDX to configure many advanced options. The file’s default location is %programfiles%\RES Software\VDX Engine\. The file should be edited with the VDX Editor.

Connection String [W] – A feature of Workspace Manager 2010, which allows you to import/export an encrypted string, contains all the information to connect a Workspace Manager agent to it’s datastore. As an added bonus you can put the connection string into a DHCP option, so a new agent automatically will initialize it’s connection. See this article on how to set it up.

Connector [A] – A feature of RES Automation Manager which allows you access to extended functionality in the product. The way it works is that if you don’t use the functionality, you don’t pay for it. There are several connectors, and when you enable one, it charges a given amount of licenses from your Automation Manager licensepool. You can read more about the connectors in this technote article.

Console Operator [P,W,O] – This is not official terminology. However, as RES Software products offer the ability to permit non-adminitrative users to run the administrative console, via Administrative Roles. Thus using the term ‘administrator’, may leave room for misunderstanding, it may be better to refer to such users as Console Operators.

Consultancy Reward Program [B] – This is a program designed to reward currently non-partnering consultants and/or integrators for bringing business to RES Software. Contact your local RES Software representative for more information on the CRP program.

Context [W] – A main node of the new Workspace Manager 2010 console. It includes access to Locations and Devices, Directory Services, Administrative Roles, Connection State, Languages and Workspace Containers. Context generally refers to items that describe identity (who the user is), the users physical location (subnets, etc.) type of device being used (workstation, terminalserver, laptop, etc.) and even time of day, although this is only a property of the individual applications currently.

Context, Workspace Designer [W] – Inside the Workspace Designer wizard, we also refer to Context. Although it essentially means the same as above, it is important to distinguish that in the wizard it refers to any selection of known groups, defined locations which together matches the data that was picked up by the Desktop Sampler. In other words, in the Workspace Designer wizard you would choose one or more contexts that would make sense to assign a rule to, where you get maximum coverage and minimum slack or missed users.

Control Center [O] – Former name during the early interim days, for the Service Orchestration Console

Coverage [W] – A name of a tab and a term used in the Workspace Designer wizard in Workspace Manager. Let’s say you are using the workspace designer to create rules for Drive and Portmappings. Going through the wizard, you will pick one or more contexts to assign the mapping to. The Coverage percentage tells you how many users had the mapping before and would keep it using the selected context(s). Ideally your coverage should always be 100%. If you have less than 100% coverage you have missed users. See also slack.

CPU Optimization [W] – Formerly known as CPUshield. One of the performance enhancement subsystems in Workspace Manager. CPU Optimization works by actively repriortizing any user process which misbehaves. As default if an app is using more than 70% cpu time for more than 5 secs, CPU Optimization slams the process’ priority down to Idle. Once the process starts behaving nicely again, (keeps under 10% for 30 secs), the original process priority is restored. This system is so simple yet incredibly effective that was it enabled per default up until Workspace Manager 2010, where everything is switched off in the default Workspace Model.

CPU Shield [W] – Old name, pre Workspace Manager 2010. See CPU Optimization.

CRP [B] – Acronym for the Consultancy Reward Program

Custom Resources [W] – This is a place in the RES console where you can store files which automatically should be replicated out onto each machine running Workspace Manager. The files are stored in the Workspace Manager datastore. The replication is done by the RES Workspace Manager agent service, which is a part of any Workspace Manager installation. There is a variable %rescustomresources%, which inside a Workspace Manager session will point to the folder the resources are replicated to. Default path is: %RESPFDIR%\data\DBcache\Resources\custom_resources\. Examples of usage for custom resources: Ensuring a certain graphic logo is replicated out to all computers, so an HTML outlook signature will work with it (example here) Another good use case is to store a mandatory profile here, to eliminate network traffic. There is a nice article on that here.



Datastore[P,W,O] Reference to the database of either Workspace Manager or Automation Manager. Supported database systems are: MS SQL 2000 and up, Oracle 8.1 and up, IBM DB II, MySQL 5.0 and up and Microsoft Azure (from Workspace Manager 2010). Note that the Service Orchestration Module shares the datastore of Automation Manager.

Data Link [O] – This is a type of link that maps information from external data sources to information in Service Orchestration. You can use People Data Links, Category Data Links and Classification Data Links.

Data Model [O] – formerly known as the Identity Warehouse in the IT Service Store (also formerly known as Service Orchestration)

Data Reader [O] – A component you can configure in the Identity Warehouse node of the Service Orchestration console. The purpose of a Data Reader is to retrieve data originating from external data sources such as a Human Resources system, which can be used for automated input of employee and organizational information. You can retrieve data from Microsoft Active Directory, .CSV files and external databases through ODBC data sources.

Data Sources [W] – Formerly known as Instant Datasources. A configuration item in Workspace Manager, which will enable you to create ODBC connections on the fly. Workspace Manager stores the ODBC configuration once created. All you need to do is to attach it to an application. Upon launch of the app, Workspace Manager creates the datasource as a User DSN. If access is withdrawn from a user to an app with an associated Instant Datasource, the User DSN will be cleaned out at logout. Note, you can also configure datasources to be created at logon, which is useful if you’ve got multiple apps sharing one data source.

DBcache[W] This is the folder where Workspace Manager stores it’s cached copy of the central configuration datastore. The default path is %RESPFDIR%\data\DBcache.

DDS [B] – Non-official acronym for the Dynamic Desktop Studio.

Delegation and Compliance [W] – One of the FeatureModules available in RES Workspace Manager. This featuremodule was previously known as Advanced Administration.

Dependancy [O] – Delivered orchestration service that is a prerequisite for another service

%DESKPIC% [W] – An environment variable which can optionally be created within RES Workspace Manager to control what wallpaper/logo file is being used for a given user/location context.  In the RES Console you must: 1) Go to Composition | Desktop | Background. 2) Mark the checkbox “Use %deskpic% environment variable to determine picture file name” The variable should just contain the filename (no path) of the image you wish to use. 3) Go to Composition | Actions by Type | Environment variables. 4) Create two or more instances of the DESKPIC variable (percent signs are not necessary here). Each variables should just contain the filenames (no path) of the image you wish to use. 5) Set access control as necessary on each environment variable

Desktop Extender [B] – See Virtual Desktop Extender aka VDX.

Desktop Sampler [W] – This is a standalone component in Workspace Manager 2010, which can be deployed into any existing Windows environment to pick up current settings. The net result is like sticking your head into every users session out there. The desktop sampler currently records stuff like: Current applications in startmenu, Location information, Domain, Datasources, Drive and Port Mappings, Subst’s and network Printers. All this stuff is stored in an encrypted .DTS file, which then can be processed in the Workspace Designer. The Desktop sampler can be pushed out with an MSI file and have preconfigured an expiry date and a path to save sample files. It is launched per default via HKLM\…\Windows\Run. Desktop sampler can be downloaded separately from the RES Portal, or you can find it’s MSI file in %programfiles\RES Powerfuse\ when you have installed the full package somewhere.

Desktop Transformation [W] – A unique solution offered by RES Workspace Manager 2010, which allows for a gradual transition from a traditional scripted/unmanaged environment, into a fully managed User Workspace. You start by recording data about the existing environment with the Desktop Sampler. After a while you can import the resulting DTS files into the Workspace Designer, where you create the necessary rules which can create the required items such as Managed Applications, Drive and Port mappings, ODBC Datasources, printer mappings, and much more. Once the rules are created, they can be organized into one or more Workspace Models which will allow you to switch things on at the pace you are comfortable with. There are two nice videos to explain the concept here and here.

Diagnostics [W] – One of the main nodes in RES Workspace Manager. Here you can monitor current activity in User Sessions, perform detailed Workspace Analysis of a user, monitor the Audit Log, Usage Tracking and much more.

Directory maintainance [W] This part of Workspace Manager will let you wrangle the contetns of the users home directories and profile directories. It revolves around a Model Directory where you store all the stuff you need to deploy to someone. The files etc. are deployed according to rules which can be copy always, copy only if newer, delete, or edit values in .ini file. The last part is really cool, as it will allow you to use variables too.

Directory Services [W] – The RES Workspace Manager supports enumerating multiple directory services including Multipe Active Directories, Legacy NT domains, Local computer accounts and Novell E-Directory. All these can be configured and prioritized in the Workspace Manager console below the Context main node. The way directory services are enumerated is as follows: Given the priority numbers in the right-most columb (number 1 = highest priority) the directory services are read one-by-one. Workspace manager stops at the first match found. Note1: While multiple AD’s with multiple mount points can be defined, only one Novell directory service can be defined. Note2: RES Workspace Manager does not make any kind of schema mod, or any other modification to any of your directory services. Note3: You can add access control and workspace container control to a directory service. The purpose of this is to ensure optimal performance in a large scale geographical deployment. For example in a multinational environment, you probably want to ensure that US employes are not enumerated against European domains as that would likely slow things down.

Discovery Wizard [W] – New feature in Workspace Manager 2012 SR3, which makes it very easy to create new User Settings templates for unknown applications. The feature is described in more detail in this article.

Dispatcher [A] – A part of the RES Automation Manager architecture. The function of a Dispatcher is to broker communication between Automation Manager Agents and the Automation Manager datastore. Also the dispatcher will cache resources being used, thereby minimizing network traffic. In short the Dispatcher is the keystone in Automation Manager’s ability to operate concurrently on literally thousands of computers without killing the central datastore. While back in Automation Manager 2009, the Dispatcher had a limit of 150 concurrent Agent connections, this has been increased 10x in the Dispatcher+ in AM 2012. RES Workspace Manager has a similar, but optional component, known as the Relay Server.

Dispatcher Plus [A] – Aka Dispatcher+. This is a new version of the Dispatcher in Automation Manager 2012, written in C# which drastically increases the number of concurrent agent connections from 150 to 1500 concurrent agent connections. The Dispatcher+ requires the full .Net 4 framework package installed on the target computer. For more information see Technote RG043. Even if you’re still worried about 1500 concurrent Agent connections, this isn’t really a limitation though: For example, if you schedule a AM job to a site with 4500 live AM agents, the job will indeed execute on all 4500 agents, but only on 1500 at a time. You can add more dispatchers to make the job more concurrent and the environment more fault tolerant. The 1500 concurrent agent limitation is a boundary set by the registry and by practical trials on IOps consumption. While you can indeed override it, it’s not recommended.

Drive and Portmappings [W] – The ability to manage network drives and/or legacy LPT: and COM: port mappings from within RES Workspace Manager. Within this node, located below Composition | Files and Folders in the Workspace Manager Console you can map and unmap the above mentioned devices, but also assign Friendly Names, hide/unhide drives, specify credentials and much more. Note that the usage of WebDAV (the ability to map a network drive to a http(s) url, is fully supported. For offline usage, it is recommended that you use Drive Substitutes.

Drive Substitutes [W] – A feature in Workspace Manager, found under the Composition | Files and Folders | Drive Substitute node. This feature will allow you to emulate the old DOS subst command, which will map a local path to a virtual drive letter. As an example, it’s extremely useful for providing a home directory / homedrive on a laptop, when it’s offline – that is, if you’re not a big fan of Windows Offline Folders…

DSbrowse – A really cool utility from RES Software. It was formerly known as Tim the Toolman. The utility helps customers time different responses from their AD. In other words, if your domain controller is performing badly, DSbrowse will let you know about it by timing different operations, such as enumerating AD objects. These are the same procedures that Workspace Manager employs. DSbrowse is unfortunately not available from the download portal, so you have to ask around. More info here

DTS file [W] – Files with this extension are produced by the Workspace Manager 2010 Desktop Sampler component. The files are typically around 256kb in size and are named as username@computername.dts. The DTS file contains a snapshot of non-application specific settings present in the users current environment. This covers items such as applications in the start menu, mapped network drives and printers, ODBC settings, domain membership, network/subnet information. All this information is encrypted. One or more DTS files can be imported through the WorkSpace Designer in the Workspace Manager console.

Dynamic Configuration Module [W] – New name as of Workspace Manager 2012 SR3 for the feature module formerly known as Personalization and Composition. This module is available in all the retail editions of Workspace Manager 2011. This excludes the Express edition though. The Dynamic Config module covers features that deal with replacing user policies, login scripts and user profiles in general. See composition and user settings for feature highlights. For description of the other modules, see Advanced Administration, Security and Performance and VDX modules

Dynamic Desktop Studio [B] – See RES Dynamic Desktop Studio.

Dynamic Privledges [W] – A feature within Workspace Manager 2012 and up, which allows a console operator to elevate or restrict rights for managed applications while maintaining default privileges for the user. This allows you to grant administrative privileges to specific applications that need these privileges (such as proprietary applications, Control Panel applets (using rundll32.exe or control.exe) and applications that allow changes to be made to hardware settings) without granting the user full rights as an administrator. Reducing user privileges may be useful for granting a user that is an administrator an application that should not be run as an administrator, such as a command prompt.



EAP [B] – Acronym for Early Adopter Program.

Early Adopter Program [B ] – This is RES Software‘s program for existing customers and partners, who are willing to go the extra mile to help us try out and give suggestions on our upcoming releases. This program is by invitation only. Where the EAP program differs from a regular Beta program, is that Interim releases made available to early adopters are completely supported. The caveat is that due to support capacity, RES Software only takes in a certain number of EAP members and each applicant is reviewed individually. If you have received an invitation, you will be required to fill out this form and send it back to your commercial point of contact within RES Software.

Edition [W] – A set of features available when you purchase the RES Workspace Manager 2011 product. There are currently 4 retail editions of WM2011: Bronze, Silver, Gold and Enterprise. Besides the retail edition, there is the seperate free Express edition, but it’s a seperate download. The 4 retail editions are cumulative, so Enterprise includes Gold, Gold include Silver and Silver includes all features of Bronze edition.  An edition gives access to one or more feature modules.  See article RG032 for detailed information on this topic. Important update: From Workspace Manager 2012 the silver editions contens can be swapped with the contens of Gold. This is done through the licensing node in the WM console.

Elevation [W] – See Dynamic Privledges.

E-mail Templates [W] – Formerly known as Instant Mail. Allows you to setup email MAPI profiles for many of the most popular communications suites. The emphasis is on Outlook 2000 and up, but Email Templates also supports configuring a bunch of other messaging components. It works similar to Datasources: You create one and attach it to an application. For Outlook especially, it will also allow you to create a dynamic email signature which picks up it’s elements, such as title, name and phone etc, from Active Directory or other Directory Services

$EndString() [W] – A string manipulation function in RES Workspace Manager, which allows you return the last x number of characters from a string. For example, $EndString(RESguru,4) would return ‘guru’. See also $SubString().

Engine [A] – A new node in the RES Automation Manager 2011 console. This node was previously called Dispatchers. However with the emergence of the Service Orchestration Module, it is now possible to view the status of Catalog Services and Transaction Engines from within the Engines node as well.

Enterprise [W] – One of the 4 retail editions of RES Workspace Manager. The Enterprise edition is the top-level/tier edition which includes the cumulative offerings of Gold, Silver and Bronze editions, plus it gives you access to VDX. This means effectively that you get all 4 feature modules; Personalization & Composition, Advanced Administration, Security & Performance and VDX.

Exclusive Filter [W] – This is an optional checkbox which you can set on Workspace Manager filters. It will configure the filter to show only settings which have explicitly have been given only to the users/workspace containers/locations as specified by the filter.

Execute Command [W,A] – Formerly known as External Task. The ability to run a command of your choice within the framework of either Workspace Manager or Automation Manager. Note that currently within Workspace Manager 2010 SR1, the command is executed with the credentials of the user who’s currently logged in.

Express [W] – Express is a free edition of Workspace Manager, which is limited at 100 users and only includes the basic personalization items, such as the ability to map drives, change registry settings etc. Since the product is free, there is no SA to pay on it either. Therefore all support calls on Express Edition are charged per incident.

External Task [W] – Old name, pre Workspace Manager 2010. See Execute Command.



Feature Module [W] – A grouping of features in RES Workspace Manager which are licensed together. As of Workspace Manager 2012 SR3 the available feature modules are Dynamic Configuration, Delegation and Compliance and Adaptive Security. The Express version of Workspace Manager is per definition also a feature module.

File and Folder security [W] – One of the security subsystems in Workspace Manager. With F&F Security you can block access to certain filetypes (such as .MP3 .torrent, etc) and also to specified folders. The latter is extremely useful if you for example want to restrict some users from placing anything on the desktop – except shortcuts. There is an article on this topic right here. The important thing to note about File and Folder security is that contrary to the other security subsystems, this one is the only one that allows you to directly blacklist specific items.

File Server [H] – This is the Hyperdrive terminology for what we normally would think of as a regular share. A HyperDrive File Server can either be private (ie only accessible to the user himself) or shared, so a user can invite others to collaborate on the contens. A private fileserver can always be converted to a shared fileserver

File Types [W] – Formerly known as Instant Filetype Associations. This feature of Workspace Manager lets you take very granular control with any type of file associations, both very simple yourapp.exe %1 to very complex DDE filetype configurations. With File Types you can import existing associations for an app, as well as create new ones. This includes building context (rightclick) menu’s which can do all sorts of nice things for your users.

Filter [W] – A method to see only the stuff you need to work with in Workspace Manager. In the lower left hand corner you’ll find a funnel icon. By right clicking it you can define for who, what or where you want to see in the righthand side of the console. An example would be that one day a console operator only wants to work with the applications available to the Finance department. See also Scope Control. Note: When a filter is active, the mentioned funnel icon turns blue. Also, you will notice the word [filtered] in the titlebar of the console applicaiton.

Folder Synchronization [W] – A feature of RES Workspace Manager 2010, which utilizes Microsoft’s .Net synchronisation framework. You may already be familiar with this technology through utilities such as SyncToy. Problem with SyncToy specifically is that it was part of the PowerToys from Microsoft, thus never supported. Using Workspace Manager you get a fully centralized GUI for managing any kind of file sync in your user’s sessions. This is especially useful for synchronizing the users’ network homedirectory to a laptop so they can work offline. Synchronization can be configured to happen on login/logout/refresh/reconnect, per timed interval and of course when you launch an application. This last option is useful for creating a Sync-My-Stuff-Now button for example. Microsoft .NET Framework 2.0 and Microsoft Sync Framework 1.0 must be installed on all agents running user sessions in which folders are to be synchronized. Microsoft .NET Framework 2.0 must be installed separately; Microsoft Sync Framework 1.0 is automatically installed during installation of RES Workspace Manager.

Fox Pro [B] – The flatfile database format used by PowerFuse 7.03 and earlier legacy versions of the RES Workspace Manager. Fox Pro was the predecessor to MS Access and wasn’t considered a relational database since it had no transaction processing capability. This was however not required by the legacy RES products, as all the “brains” was and still are in the RES Agents and not in the datastore.

Friendly Name [W] – An attribute which you can set when configuring Drive and Port Mappings in RES Workspace Manager. Normally when you just map a network drive, the user will see ” on ” as the descriptive text next to a network drive icon in their explorer. By specifying a friendly name you can specify something nicer such as “Finance” or even use variables and/or functions. You could for example put in “$adinfo(firstname)’s computer” or perhaps the good old “%username% on %computername%”.

%FULLUSERNAME% [W] – An environment variable which has been in RES Workspace Manager since the dawn of time. This variable is initialized at logon with the user’s full name / displayname from Active Directory or other available Directory Service. See also %CLIENTIPADDRESS%. Note: Although you could use $adinfo(firstname) $adinfo(lastname) to produce the same result, using this legacy variable is just easier and it’s here to stay anyway.

Function [W] – In Workspace Manager, there are several functions available for multiple purposes: String manipulation (such as $SubString, $EndString, $LowerCase, $UpperCase), Information retrieval ($Adinfo and $UserShellFolder) and speciality functions such as $AutoCount. These functions can be inserted most places where text can be specified, such as registry values, environment variables and email signatures. Note that functions can be nested within each other. The entry for $Substring has an example of this.



GA [B] – Acronym for General Availability. When a given software product is available to the general public for eval/purchase.

Gareth Kitson [B] – A very sad induhvidual who seems to have a hard time with RES Software, LiquidWare and all the other kids in the schoolyard, who actually can get along. Exhibit A.

Global Authorized Files [W] – A node found in the console of RES Workspace Manager. The list found here shows what files and executables have been authorized either through AppGuard, Read-Only Blanketing or File and Folder security.

Global Model [W] – A part of the Workspace Model found under the main node Setup in Workspace Manager. The Global Model contains the master settings for what parts of Workspace Manager is turned on/off per default. In a freshly created Workspace Manager 2010 datastore everything in the global settings is turned off per default. If you have upgraded a Workspace Manager 2008 installation, everything will be turned ON per default, as it was difficult to turn things off individually back in the 2008 version. See article RG027 for further information on this topic. When turning on/off individual settings, you can use the Teleport Button to jump directly to the affected nodes to configure additional options.

Global Settings [W] – An obsolete name for the Global Model, found in the Workspace Model node of Workspace Manager 2011 and up. Global settings may however still refer to the registry settings found under HKLM\SOFTWARE\Policies\RES\PowerFuse\Settings. See this posting for further info on the RES policy registry settings.

Global Variables [A] – A feature in Automation Manager, which allows you to specify values that follows teams or agents. The difference between module parameters and Global Values is, that the latter are evaluated at execution of a job, rather than at scheduling. Technote RG042 explains the concept in detail.

Gold [W] – One of the retail editions of RES Workspace Manager. In addition to it’s own feature set, Gold includes the cumulative features of Silver and Bronze editions. This effectively gives you the following modules: Personalization & CompositionAdvanced Administration and Security & Performance Note: Gold does not include VDX. You need the Enterprise edition for that, or purchase VDX seperately.

GUID [W,A] – Acronym for Global Unique IDentifier. Within Workspace Manager and Automation Manager, each configuration item is assigned an internal GUID which enables the replication subsystems to distinctly identify the changes in the datastore and replicate those changes to where they need to go.



Home Directory [W] – A crucial part of any Workspace Manager installation. As individual workspace preferences and user settings are stored here per default, it is important that every user has a home directory. Unlike other products which store these things in their datastore, there is significant performance and reliability to be obtained by having user’s settings and preferences readily available where the user is. Note that workspace preferences and user settings can alternative be placed somewhere else than the user’s homedirectory, as long as it’s a drive unique to each user. Using the File Synchronization feature of Workspace Manager, you can easily replicate the users own documents, workspace preferences and user settings so they follow the user offline.

Hybrid Profiles [W] – While this is not RES terminology, it deserves mention. Back in the late nineties, CCS (Citrix Consulting Services) were credited with figuring out an innovative way of combining the best of Roaming and Mandatory profiles. To be fair, the delivery was somewhat a cludgy scripting hack, but the operating principle is what most, if not all software products that do anything with profile data, are based uppon. The principle was simple: At logoff fire up a script that would dump selected keys from the user’s HKCU and selected files and folders from %userprofile% to a user-unique location, typical the user’s own home directory. At login, load everything back in again. While vastly more granular and easier to configure, the User Settings feature of RES Workspace Manager employs basically the same operating principle, although it’s not limited to just loading profile data at login/out.

Hyperdrive [H] – A product released in 2012 by RES Software. The HyperDrive platform is a secure way to deliver follow me data and file-sharing with the enterprise-class security of on-premises technology. Available on pretty much any current mobile platform it includes enpoint encryption, remote-kill and office integration to name a few highlights. For more info and a cool video, go to the product page here.



Identification Method [P, W] – Both Workspace Manager and Automation Manager Agents can be identified by either MAC, GUID/WUID or Domain+Computername. Which ID method you select will depend on the environment you use. For example you probably will not use GUID/WUID identification if you use cloning a lot in your environment, as you would start to see duplicate Agent entries in your consoles. In a VDI environment, it depends on how you spawn new instances of your images. If your MAC addresses are generated dynamically, you probably want to use the domain+computername or the Unique ID option.

Identity Warehouse [O] – The menu-item in the Console for the Service Orchstration Module, where you can configure People Identifiers and People Attributes, Data Readers, Data Links and SmartRules.

Immediate Mode [W] – Aka. Realtime mode AKA Track Settings Immediately. This one of the three zero profile modes available in RES Workspace Manager. In immediate mode RES Workspace Manager will pick up any profile change done by a target object (this is typically a managed application) and store it as a upr2 file if it is a registry setting in HKCU or as a upf2 file if it’s a file in the user’s profile. See also Capture Targeted mode.

Instant Datasources [W] – Obsolete name, pre Workspace Manager 2010. See Data Sources for details.

Instant File Associations [W] – Obsolete name, pre Workspace Manager 2010. See File Types for details.

Instant Logoff [W] A technology in RES Workspace Manager, which was developed a couple of year sbefore Microsoft released their UPHclean utility. Instant Logoff does two things. Not only does it close any open file- and registry handles when a logoff is initiated. Second, if it’s running inside a ICA/RDP or VDI session, it can optionally disconnect the session. The resulting impression is a logoff that is fast as lightning, although it’s smoke, mirrors and a timely disconnect which does the job.

Instant Mail [W] – Obsolete name, pre Workspace Manager 2010. See Email Templates for details.

Instant Report [W] A nifty way to generate system configuration documentation. Workspace Manager will allow you to generate PDF based reports for every configuration screen in the console. This also is the case for the Workspace Analysis view of a given user. You can either click on the Instant Report button () for a given item you wish to document, or you can right click in the console and choose “Select items for instant report.”

Interim Release [B] – An early release of any RES Software product. These releases are strictly personal and only available to RES Software’s Early Adopter Program partners. Interim software releases are fully supported by RES.

IP Security [W] – See NetGuard.

IR [W,B] – Acronym, either for Interim Release or Instant Report.

ITaaS [B] – Acronym for IT as a Service. Although it is a buzzword which has been hyped tremendously throughout the year, you can effectively configure and deliver ITaaS by using the Service Orchestration Module for Automation Manager. There is a great video available here, which demonstrates the concept and the actual product in action

ITS [O] – Often seen used acronym for the RES IT Store.

IT Store [O] – Per December 2012, this is the new name for the RES Service Orchestration Module. The RES IT  Store also includes new enhancements as it includes a new web-client/interface.  This client resembles what users know from other stores such as iTunes and Google Play.

IT Store Client [O] – AKA IT Store Notification Client. This is a component that installs into the system tray. It looks like a small shopping cart. It’s purpose is to optionally notify the user on messages waiting inside the IT Store Webinterface, but it’s also this components job to trigger a refresh in Workspace Manager, if this specified as an action in a ITS workflow.

IUL [B] – Acronym for Internal Use Licenses.



Job [A] – A job is the common term used for something you schedule in RES Automation Manager. It can be a module, project or a run book, the latter containing multiple job schedulings. Either of these job types can be scheduled to one or more agents or teams.



Learning Mode [W] – The different security Subsystems in Workspace Manager have a learning mode. This mode will allow anything through the filters, but a log entry will be created on anything that has not been authorized and would have been prevented in Blocking Mode. Learning modes for all subsystems writes to the log table stored in the Workspace Manager datastore. Note: Unchecked and enabled globally, logs can become very large, so I urge you to excercise caution when enabling in a live environment. See this RESguru article for further info on how to work with learningmode.

Licensing, Activation [W, A] – Activating evaluation or purchased RES product licenses can be done in 3 different ways: Online (SSL/443), Email or via file import/export. The last option is great if the installation is on a secure net without internet access. Regardless of method chosen, you will be asked if you are activating this as an end-user customer, or if you are doing it on behalf of said customer as a consultant/partner. You will then be prompted to fill in your details. At the end a license request will be generated. As soon as it has been reviewed by RES Software, a license activation file will be sent back to the email-address(es) you specified during your activation request. These are then imported into the products console and you’re done. Note: the activation request review takes place in central european business hours which is 8am-5pm CET+1. That would be 11pm-8am PST or 2am-11am EST, so plan accordingly. See this article for an illustrated guide to license activation.

Licensing, Automation Manager [A] RES Automation Manager is licensed differently from the RES Workspace Manager as Automation Manager deals with the machine and not the user session on it. Therefore Automation Manager is licensed per device and device type. This means that one regular windows workstation or laptop takes 1 license, a server (print/file/etc) takes 4 licenses, and a server with Terminal Services configured in Application Server mode, requires 8 licenses. If you use Service Orchstration, a charge of 0,5 Automation Manager licenses are applied to each serviced user. Finally, you have the option to add additional functionality by configuring so-called connectors. See the Automation Manager Licensing 101 article for further information.

Licensing, Evaluation [B] – Prospective and existing customers as well as partners of RES Software can request evaluation licences for any current RES product. Mind you, these are not to be mistaken for the built-in trial licenses. An evaluation license can contain any number of licenses, however it is always time limited. When you contact your local RES representatives for such, they will obviously ask some questions about your organization and project and will grant you a license. The licenses will arrive shortly after in an email, where you save the attached .XML based license files and import them into your RES product. The evaluation license may require activation.

Licensing, managed applications [W] Workspace Manager has the ability to not only monitor but also enforce the licensing of applications provided to the user. There are currently 5 licensing models supported: Company wide license, per Server, per named user, Per seat and Concurrent users. Note in order for Workspace Manager to enforce licensing on an application it must be a managed application, launched through pwrgate.exe.

Licensing, IUL [B] – AKA Internal Use Licenses. These licenses are available at a discount to signed and certified partners only. IUL’s serve the purpose when a partner wishes to deploy RES products in an internal production environment. Like NFR licenses, IUL’s are not for resale, however the IUL’s can be ordered in any quantity.

Licensing, NFR [B] – AKA Not-For-Resale license. A license typically provided only to certified and signed RES Software partners, being reseller, training and distribution partners. The NFR license is typically a low-count license file which will allow the partner to keep a long-term lab environment running without having to worry about license expiry. If the partner additionally wishes to deploy a RES product for internal use, IUL license are available. Note: NFR licenses are exclusively issued at the discretion of RES Software.

Licensing, Workspace Manager [W]Workspace Manager is licensed per concurrent users, depending on the device where the user is logging in. If an ACPI compliant battery is detected in the device, Workspace Manager assumes it’s a laptop and a license is bound to the ID of the Workspace Manager agent running on that machine. This is, however, not permanent. If a laptop is lost, all you have to do is delete the Workspace Manager agent from the Workspace Manager console and the license is returned to the pool.

Licensing, Trial [W,A] – These are the built-in fully functional time-limited licenses which RES Workspace Manager and RES Automation Manager come with out of the box. When you install RES Workspace Manager, 25 trial licenses will be available for 2 months / 60 days. RES Automation Manager comes with 75 licenses that likewise will run for 2 months.

Linked Applications [W] – See User Settings Linking

Linked Resource [A] – Another kind of Automation Manager resource. A linked resource is basically a pointer to a file residing on an existing fileshare somewhere. This is useful when a customer already has a fileshare based installation file repository somewhere on the network. When employing the RES Automation Manager, there are however several advantages of converting fileshare based resources to either regular Automation Manager resources, or resource packages. See resources for more information on this topic.

Linking [A] – See parameter linking or user settings linking.

Locations and Devices [W] – Aka. Zones, aka. Location. Formerly known as PowerZones. A container object in Workspace Manager which describes a computers’ geography and/or geometry. Geography means where the computer is physically. This can be determined by so called Zone Rules, defining things such as IP subnets, ranges, computer name masks, etc. All this is of course ultimately determined by the availability of such data from the underlying infrastructure. There is an interesting article related to this topic here. By geometry, a Location can trigger on the contents of the computer. A few examples: Screen resolution, CPU speed, DVD burner present, reported chassis type and much more. A Zone with or without Zone Rules doesn’t do anything by itself, but almost any kind of configuration item can be attached to it, through the Access Control tab of almost any object within WM.

Lockdown and Behavior [W] – A subsystem in RES Workspace Manager which offers a large collection of checkbox options. These determine the operation of the product. As the name indicates, the section serves two purposes. The lockdown part describes items that are restrictive to the users abilities within the workspace. Hiding the Recycle Bin or disabling drag&drop on the startmenu, are good examples of these. The purpose of many of the lockdown items is to free you from having to configure the corresponding settings through Windows policies, but goes beyond what policies can offer. All lockdown items are marked with a padlock (padlock-enabled) icon. No lockdown items are processed as long as the Lockdown and Behavior system is disabled. The other purpose this node serves is Behavior items. These are not restrictive per say, but aimed towards, well.. how WM behaves. Things like when to refresh, when to notify are a couple of examples of Behavior items, which are marked with a gear (gear) icon. Important: Behavior items are always processed, regardless if the Lockdown and Behavior subsystem is disabled. You can have multiple sets of Lockdown and Behavior configuration sets by using Workspace Models. There is an article that explain that right here.

$LowerCase [W] – A string manipulation function within RES Workspace Manager which converts an input string to lowercase. See also $UpperCase. This function here is especially useful if you are creating email addresses, where it’s considered good form to keep all letters in lowercase. Here is an example that will generate a full email address from the users name and the current domain from a system variable: $lowercase($substring($adinfo(firstname),1,1).$adinfo(lastname)@%USERDNSDOMAIN%)



MAC [W,A] – Media Access Control number. This is the physical 6-segment hex number (for example 00-1D-BC-65-1E-45) assigned to your network adaptors. One of the Identification Methods available for both Workspace Manager and Automation Manager. If there are more than one nic in the computer, the MAC chosen is the one from the primary network card. Note that the MAC can usually be changed via the driver software.

Main Node [W] – Not official terminology. With the release of Workspace Manager 2010, the console was changed to make it more accessible. Before then it was a evergrowing tree of nodes and something had to be done about it. RES Software redesigned the console with 5 main nodes in the bottom left corner, resembeling the Mail, Calendar, Tasks etc nodes we know from MS Outlook. Workspace Manager 2010 comes with 5 main nodes which are Context, Composition, Security, Diagnostics and Setup.

Major release [P, W] – In Workspace Manager and Automation Manager, a new major version is released every second year or so. Workspace Manager 2010, Workspace Manager 2008 and Workspace Manager 7, 6 and 5 were major release versions. Where Workspace Manager runs with even release years, RES Automation Manager runs on even years. Automation Manager 2011, 2009, 2007 etc are major release versions of Automation Manager.

Managed Application [W] – A Managed application is a record in RES Workspace Manager that exactly defines how a given application should be configured, exposed and handled by Workspace Manager. On the properties of the Managed Application node, you can configure the behavior of managed apps, if they should replace all existing shortcuts, merge with existing or do nothing. On each individual managed application it is possible to configure general properties and settings, licensing, notifications, publishing, access control, time– and location/device restrictions, actions, filetypes, email templates, ODBC datasources, user settings to be retained, and security authorizations on the application.

Memory Optimization [W] – This feature set of Workspace Manager contains multiple ways of helping you control memory consumption. This is obviously most valuable on a multiuser system. By linking what’s going on in the workspace with what’s being swapped to disk, Workspace Manager ensures memory is freed up exactly when it is not needed anymore. Second, Memory Optimization allows you to set limits, either per number of apps or per amount of MB’s allocated, before a user is allowed to launch new apps.

Memory Shield [W] – Old name, pre Workspace Manager 2010. See Memory Optimization for details.

Merge Mode [W] – One of the ways Workspace Manager can handle the user’s startmenu. In Merge Mode, the user’s originally start menu is left intact but new [RES] managed shortcuts can be injected. If you already have a shortcut for, say Microsoft Word 2013 and you have created a shortcut for this, you have the ability to override whatever current shortcut is in the startmenu. Alternatively to merge mode, you can chose replace mode.

Missed [W] – A name of a tab and a term used in the Workspace Designer wizard in Workspace Manager to describe the situation in details, when you have less than 100% coverage. Let’s say you are using the workspace designer to create rules for Drive and Portmappings. Going through the wizard, you pick one or more contexts to assign the mapping to, the Missed percentage tells you how many users had the mapping before and would lose it using the selected context(s). Ideally your missed percentage should always be zero. The workspace designer has the ability to automatically remove both missed users and slack by choosing the “Add any missing and remove slack” checkmark. Missing users are simply added explicitly to the access control on the rule being generated by the wizard.

Model Directory [W] – A place in the Workspace Manager Console where you can create templates of what your home directory and your profile folder should contain. See home directory maintenance

Module [A] – An Automation Manager object, which can contain multiple Automation Manager Tasks. The module is essentially a list of items to process plus associated module parameters and conditions and Automation Manager modules can be scheduled on their own or organized into Automation Manager Run Books and Projects.

Module [W] – AKA Feature Module. In the context of Workspace Manager 2011, a Module is a grouping of product features which are available in certain editions of Workspace Manager. Currently there are four feature modules. Personalization and Composition, Advanced Administration, Security and Performance and VDX. The modules are NOT cumulative nor overlapping.

Module Parameter [A] – These objects will allow you to make Automation Manager modules generic and flexible, by allowing you to enter input during import and/or execution of the module. For example if you create a module to enter a computer into the domain, it’s a good idea to make a parameter for the domain credentials, as they probably will change over time. By asking for them when a module is scheduled you avoid having to re-edit the module. Overall this offers you the possibility to build black-box tools for use by for first-line support personel, for example. They don’t have to know how the modules work. As long as they can answer the right questions, you can set it up so they can run, but not edit modules of your choice.

Mount Point [W] – An attribute of the RES Workspace Manager‘s directory services configuration. Using a mount point you can specify from which OU and downwards you want enumerate user’s and groups. This is very useful when you are partially implementing Workspace Mananger for a large organization, this could be a pilot project for example. So, if there are +170 OU’s and 78.000 users in the AD, you may chose to focus only on the 6.000 users in a certain part of the AD to begin with. Note that you are allowed to create multiple Directory service entries for the same Domain with multiple mount points. This is great for gradual adaption to a managed workspace.



NetGuard [W] – AKA. Network Security AKA. IP Security. This is a security subsystem of RES Workspace Manager which will let you control which hosts are reachable from a given executable. Managing layer 3 IP traffic is useful, for example, for limiting a telnet client from reaching certain hosts in the datacenter. This is great for limiting external contractor’s access. Traffic can be controlled on port number, direction, transport (udp/tcp) and target IP address which supports wildcards. Note that Netguard can be configured also per application, so you can have two instances of a TN3270 app, given to two seperate usergroups, where they respectively only can hit two seperate hosts, i.e. no possibility of crossing over. For even more granular URL centric security, see website security.

NFR [B] – Acronym for Not For Resale. See Licensing, NFR for details.

Node [P,W,O] – This term usually describes a location in one of the consoles below one of the main nodes. The term is used for both root nodes such as the Context, Composition, Security, Diagnostics and Setup in the Workspace Manager console, as well as for leaf nodes such as Composition | Desktop | Lockdown and Behavior.

Notification [W] – A property of Workspace Manager managed applications, which will allow you to define separate messages the user will receive, for when a) the application is disabled and/or b) when the user launches the application. A flag can be set so the notification message is only shown once per user per app. The messages can contain rich text (fonts, colors, etc) and the notification box also supports all environment variables and the $adinfo() function. Another cool way to utilize the notification, is to create a Message of the Day app.



Orchestration [O] – Aka Project Orchestra, Orchestration Pack for Wisdom. Also refers to the act of providing orchestated services to your users. See Service Orchestration Module.

Orchestration Client [O] – See Service Orchestration Client.

OS Suite [A] – One of the conditions available in RES Automation Manager for conditional executions of modules, projects, etc. It is also one of the conditions available for Team Rules. OS Suite will allow you to detect if Backoffice components are installed, if this is a Windows Home edition, Windows Server Compute Cluster edition, Windows Server Datacenter edition, Windows Server Enterprise edition, Windows Server Web edition, Windows Small Business Server, Windows Storage Server, or Windows XP Embedded.

OTAP [B] – A Dutch abreviation to describe multi-tier environments. Specifically it’s short for Ontwikkel (Development), Test, Acceptatie (Acceptance) and Productie (Production).



Parameter Linking [A] – This is a very powerful feature of RES Automation Manager. For example, you can link a project parameter to module parameters in modules which are included in a project. Let’s say that you have a project that uses two or more modules, which both require domain credentials. Instead of having to supply the credentials two or more times, you would create a project parameter of type Credentials. Using the Add button on the Project Parameters | Links tab, you would connect the Project parameter to the Credentials module parameter in the two modules. The great thing is that this can happen automatically using the Autolink button.

Partially Managed Workstations [W] – Obsolete name, pre Workspace Manager 2010. Refer to User Installed Applications instead.

Partner Portal [B] – See RES Portals.

Pass-thru Publishing [W] – A very nifty feature of Workspace Manager which will enable you to automatically connect to a published application in a farm when the given application is not available on the server you are on. Pass-though publishing will automatically generate the required ICA or RDP file to create a session to the server(s) which offer the managed application. This works with both Terminal Services 2008’s remoteapps and also with Citrix Xenapp. It requires that Workspace Manager is installed on every server to participate in the scheme.

Pattern Matching [P,W,O] – The ability to use advanced wildcards in RES Products. Pattern Matching enables you to use the following operators: ? matches any single char, * matches zero or more characters, # matches any digit 0..9, [c-h] matches any single character between c and h (case sensitive, ![k-p] is an inverse character list, that matches any single character NOT between k and p in this example. Look for a button or a Pattern Maching button wherever there is possibility to enter a partial string. Be be sure to check this article on advanced use of pattern matching as well.

People [O] – AKA Service Orchestration Person. Somebody who can log on to a Service Orchestration environment

People Attribute [O] – Service Orchestration placeholder for additional information about a person, such as address, place of birth, telephone number, etc. The people attributes are different from the People identifiers in the way that attributes are NOT necessarily unique. For example more people can share the same birthday and/or birthplace.

People Identifier [O] – Identification method, with which people can be uniquely identified in a Service Orchestration environment. Also used for authentication purposes for clients. For those of you familiar with DBMS terminology, this is equivalent of a primary key. Although you are free to define more, there are 3 built-in people identifiers in Service Orchestration is Windows logon name, primary email address and Apple Device ID.

Personal Settings [W] – A folder created in the root of the user’s homedrive by Workspace Manager 2012. Personal Settings is the new name for the old pwrmenu folder created by WM 2011 and earlier to store User Settings and other personalization related files, such as pwruser.ini

Personalization and Composition [W] – Obsolete name for the Dynamic Configuration feature module of RES Workspace Manager. While the contents is the same, the name became obsolete per the 2012 SR3 release.

PF20xx [W] – Often used in writing, not particular official acronyms for RES PowerFuse 2010 or RES PowerFuse 2008.

PFGII.exe [W] – Process name for the PowerFuse Generic Isolation Integration component. This executable is inserted by different means into other non App-V application virtualization bubbles. Examples of supported environments is VMware Thinstall, Citrix Streaming server and others. The procedure for this is described in the Workspace Manager online help, accessible through F1 in the Workspace Manager Management Console

PFWSMGR.exe [W] – Main process for the RES Workspace Manager‘s Workspace Composer. Due to the name of the process executable, the composer was actually formerly known as the PowerFuse WorkSpace Manager, which can potentially be a bit confusing since Workspace Manager was the new name for RES PowerFuse as per Oct. 5th 2010.

Placeholder App [W] – Field engineer jargon for an empty application (that doesn’t have a commandline) in RES Workspace Manager. The only purpose of such an app is to store a set of configuration items such as security rules. See this article for further information.

Platinum Edition [W,A] – This is essentially a bundled license of RES Workspace Manager, Enterprise Edition and RES Automation Manager, where you essentially get both products cheaper than if you bought them separately. For more information and pricing, your local RES Software representative. See also: Standard, My Workspace and Express editions.

PlusMenu [W] – This is an integral part of the Workspace Manager 2010 console. It is used to specify global options for specific users/locations/workspace containers. You will notice it on console nodes which normally define global settings. An example is CPU Optimization. You will see a menu appearing as at the top of the node you’re in. If you click on it, you will be able to add one or more Workspace Containers. You can then specify a different set of CPU Optimization rules for that workspace container. If one or more plus menu’s are inserted, they will be processed from left to right. You can re-arrange them and/or disable them individually by right clicking. See this article for further information.

PMWS [W] – Obsolete acronym for Partially Managed WorkStations. From Workspace Manager 2010, see User Installed Applications instead.

Portal [B] – See RES Portals.

Portal Admin [B] – When you register a Site ID for the first time, the user who does it will automatically become a portal admin for the company if no portal admin has been registered before. The portal admin has the capability to create new users for the company that owns the Site ID. See this article on how to register. If your portal admin has been hit by a train or a better offer, contact RES Support to have the portal admin changed for your company.

PowerFuse [B] – Obsolete name, prior to October 5th 2010 for the RES Workspace Manager.

PowerHelp [W] – An information utility for the user, which can be found in the start menu of a Workspace Manager controlled user session. PowerHelp will allow the user to see an overview of available managed applications, what they do and where to find them, even though the user might not currently have access to them yet. Think of PowerHelp as a service catalog. PowerHelp can be disabled, or applications can individually be hidden from view in PowerHelp. Note with the advent of the Orchestration Module for Automation Manager, this feature is mostly obsolete.

PowerHours [W] Obsolete name, pre Workspace Manager 2010. See Time Restrictions

PowerLaunch [W] Obsolete name. This was a term used in the older releases of Workspace Manager, prior to 2010. The term was commonly used for items such as Environment variables, Drive and port mappings, Drive Substitutes, Network printer mappings, user registry settings, home directory/profile folder management, external tasks and Automation Manager integration. There are two places in Workspace Manager 2008 where PowerLaunch settings were configured. The global PowerLaunch settings, which are found under Configuration Management | PowerLaunch, and then underneath every single application defintion, under the Configuration | Power Launch tab. The difference between the two is that the global PowerLaunch items are mostly processed only at logon (there are certain exceptions to this), while the application PowerLaunch settings are processed when an application is started. All this is still the case in Workspace Manager 2010, although the old menu of PowerLaunch items have been broken up and put other places in the console. See the Workspace Manager help for details.Today PowerLaunch settings are refered to as composition items instead.

PowerMenu 2000 [W] The very first commercially available (and now obsolete and unsupported) product from RES Software, launched in 1999, which is a precursor to the RES Workspace Manager. For a trip down memory lane and learn about the humble origins of RES Software, see this article.

PowerPanel [W] Obsolete name, pre Workspace Manager 2010. See WorkSpace Preferences

PowerPack [W] – Obsolete name, Pre Workspace Manager 2010 for a RES Workspace Manager Service Pack

PowerPrint[W] Obsolete name, pre Workspace Manager 2010. See Printing Preferences

PowerTrace [W] – Obsolete name, pre Workspace Manager 2010. See Usage Tracking

PowerZone [W] – Obsolete name, pre Workspace Manager 2010. See Locations and Devices. These days most people just refer to these objects as Zones.

Prefetch [W] – A feature introduced in Workspace Manager 2011. Essentially prefetching is “trickle-loading” of User Settings for managed applications. The advantage is that instead of holding up the login process, loading a ton of settings for different apps, prefetching spawns a background thread loading the settings for a given app asyncronously with the desktop itself. If the setting is not ready (rarely happens unless it’s a honking big pile) the user will be notified that this particular app isn’t ready for use. If that mode of operation isn’t desireable by the admin, one can alternatively chose to postpone settings load until the user launches the app. The advantage is that login is still speedy and no funky messages are shown to the use. The downside is that the app may take a few seconds longer to load. This behavior can be configured globally or per app.

Printers.lst [W] – This is a special file which can be distributed to users via Directory Maintainance or Custom Resources. The file will allow users much more intuitively to chose printers from a tree of well known geographical/physical locations instead of just the names of print servers. See this article for more information and examples.

Printing Preferences [W] Formerly known as PowerPrint. This is a utility similar to WorkSpace Preferences. Printing Preferences in it’s simplest form merely allows a user to choose their default printer. An advanced button is available per default, letting the user configure a default printer which will be remembered per device. This is very useful for users who frequently roam back and forth between two or more locations and don’t want to be bothered with setting up printers every time they move.

Primary Team [A] – Within Automation Manager you can create groups of agents, called teams. You can also specify settings, such as bandwith limitations on either a global level or each agent individually. A primary team is a team which will override all global settings for a given agent. An agent can be member of one or more teams, but only one team can be a Primary Team for that agent. Settings which have been configured on the agent is also overridden by the primary team.

Project [A] – A project is a Automation Manager container object which is designed to hold two or more Automation Manager Modules. The idea with using a project is that you can group a bunch of modules together. An example module would be building a Citrix server. Here you would have different modules which would be installing different prerequisite components such as Java, .Net framework etc. A Project can have Project Parameters which then can be linked to the modules inside.

Project Parameter [A] – Similar in nature to module parameters and run book parameters. The advantage is that a project parameter can be linked to module parameters in different modules via parameter linking.

Process Elevation [W] – See Dynamic Privledges

Process Intercept [W] – A feature from Workspace Manager 2012, which uses filter drivers to intercept and temporarily halt user process launches and inject personalization and composition items into the users profile, before the process is allowed to continue. This allows the elimination of the classic managed application and allows WM to interact with an app, no matter how the user launches it, be it from Start|Run or from within another program.

Process Security [W] – The security subsystem in Workspace Manager responsible for preemtively blocking execution of unauthorized executables. This section needs more detail.

PWRGATE.exe [W] -This process is responsible for launching all Managed Applications. When the Workspace Composer renders a shortcut in the users Start Menu, QuickLaunch or Desktop, the commandline of those Managed App icons will always be PWRGATE.EXE <AppID>. This will ensure that Workspace Manager runs any Actions that are associated with the managed application before the real executable of the application is launched. Note that PwrGate.exe can launch several internal Workspace Manager apps and functions. Article RG024 explains all that. Note that pwrgate.exe per Workspace Manager 2012 is no longer required to launch managed apps, as it employs a new feature called Process Intercept.

PWRGRID.exe [W] -This is a special process that like PFGII.exe is used for integration with application virtualization. This one is however dedicated to Microsoft App-V (formerly SoftGrid). The reason why there is a seperate integration piece for App-V is that this came way before all the others app virtualization contenders, so RES Software made some especially smooth integration with the App-V platform.

PWRHELP.exe [W] – The executable which launches Power Help. Located in %programfiles%\RES PowerFuse\

PWRTECH.exe [W] – The executable which launches the Workspace Manager Management Console. See this article for commandline options.

Pwrmenu [W] Obsolete Name. The name of a folder – prior to the 2012 release of Workspace Manager – created in the root of every managed user’s homedrive. Useless fact of the day: This folder is a reference to the very first incarnation of Workspace Manager back in the late 1990’s: PowerMenu 2000 (!) Anyway, go see Personal Settings for more information.

PWRUSER.INI [W] A file created by Workspace Manager in the Personal Settings folder the users homedrive. The file stores information about the users choices in the Workspace Preferences tool.



Qualification[O] – Set of rules that define which people qualify for a service. Example, you must be in the Engineering department in order to quailify to request AutoCad as an application on your workstation.

Query [A] – A query is one of the two types of basic task you can use within RES Automation Manager. With a query you can ask about something across one or multiple computers or teams. The other type of object is tasks. A query is a very usefull item in most automation manager usage scenarios, as you can combine them with Query Evaluators.

Query Evaluator [A] – A feature which is available from Automation Manager 2011. Query evaluators will allow you to make decisions upon the outcome of a query. An example of this is to do a query on diskspace. Based on available space (specified either in size or percent free) you can then execute other tasks to deal with it.

Quick Edit [W] – A feature of RES Workspace Manager 2012 and up, which allows you to batch-change settings for Access Control, Process Intercept and Publishing on Managed Applications. This feature as of WM 2012 SR2 does however not work on PowerLaunch objects. Activate quickedit by either rightclicking on a folder in the Application tree in the Managed Application node, or selecting multiple apps in the Application List tab. Then chose quickedit and follow the wizard. It’s pretty much self explanatory.



RALC [T] – Acronym for RES Authorized Learning Center.

RAMBC [T] – Acronym for RES Automation Manager Basic Course. There are 3 variants of this course. See this posting for details on these courses.

RC [B] – Acronym for Release Candidate.

RCP [T] – Acronym for RES Certified Professional.

RCT [T] – Acronym for RES Certified Trainer.

Read-Only Blanketing [W] – One of the five security subsystems of RES Workspace Manager. The easiest way to understand RoB is to imagine that you put a clear piece of plastic over the filesystem, and user processes are then only able to read the file system. There are of course default exceptions such as the Recycle Bin folder, Spool directory, the user’s profile directory and the Temp directory, where Read-Only Blanketing is disabled per default. Note: RoB only works on local drives, for your fileshares you should use your NTFS/Share permissions on your fileserver. Read-Only blanketing is not hard to set up as all necessary permissions can be picked up by running either the entire environment or a specific application in Learning Mode.

RegGuard [W] One of the kernel drivers in RES Workspace Manager. Unlike Appguard this driver is not a blocking driver, but more responsible for everything to do with picking up changes to the registry. Features such as User Settings and Registry Tracing depend on RegGuard. Note that neither RegGuard or AppGuard are installed with a Console-Only WM installer.

Registry Tracing [W] – This is a feature intruduced back in PowerFuse 2010, which allows the Workspace Manager console operator to follow real-time what changes are made in HKCU by a given application – very much like the old Sysinternals Regmon/Processmon. However, in addition to logging changes, the WM console offers the operator to convert the trace into a Workspace Manager registry setting to be applied either every time or on a run-once basis, when a user either logs in or starts a given managed application. Note: This feature has nothing to do with the User Settings feature.

Real Enterprise Manager [W] – Obsolete (more like ancient) name for the Workspace Manager Management Console. This name was used back in the version 6.x days and before.

Refresh [W] – The process of reinitializing the user’s Workspace Manager session with new settings. A refresh is a non-destructive event, i.e. the user will not lose any data or be forced to close apps. It is important to know that only some settings are processed during a refresh. There is a detailed article availble on this topic here. From Workspace Manager 2010 two major changes have been made to the refresh: 1) If a refresh is triggered by the user or an admin while in a session, the screen is not blanked anymore. A progress indicator is shown just above the system tray area and the user can continue working while this happens. 2) The refresh can now be performed completely silent.

Relay Server [W] – A component of the 2012 release of RES Workspace Manager. The Relay Server is essentially the equivalent of the Automation Manager’s Dispatcher, but for Workspace Manager instead. The relay server may be deployed on any Windows OS, XP and higher, For more information and details, see this article.

Release Candidate [B] AKA RC – A pre GA release version of a given RES product. A Release Candidate is not to be mistaken with an Interim Release. An RC is provided via the RES Portal for all SA customers only. The purpose of the release candidate software is for existing customers to be able try out and plan for he upcoming major release of a RES Software product.

Reliability [W] – One of the nodes found under the Setup main node in the RES Workspace Manager console. Here you can configure the behavior of Access Balancing, CPU Optimization, Instant Logoff and Memory Optimization.

Removable Disk Security [W] – Aka. USB Security. RES Workspace Manager offers two ways of managing security around USB removeable drives. A) You can set security on the drives, so for example you can only read data IN from a drive, but not write data OUT to a drive. This is governed by the kernal filter driver built into Workspace Manager. B) Another posibility is to use said USB device as a security token. Workspace Manager is able to read the serial number and manufacturer off almost any USB drive, enabling you to detect ranges of USB devices. Combine an app with the prompt for password setting and you’ve got two-factor authentications on your apps! See this article for an example on how to use Removable Drive security.

Replace mode [W] – One of the ways that Workspace Manager can handle shortcuts on the user’s start menu. In this mode the existing startmenu is completely blown away and you only see the apps you have access to. Alternatively you can disable the shortcuts all together or run in merge mode. If you disable replacement mode, the original startmenu will be restored.

Reporting Services [W] – A separate add-on open Web service for RES Workspace Manager, which allows you via SOAP messages to retrieve Usage Tracking data from the Datastore as this is encoded in binary fields in the RES Datastore. Stay tuned for a future article on this. In the meantime, have a look at the documentation here.

Requester [O] – Person who requested the delivery or return of a Service Orchestration service.

RES [B] – Acronym for Real Enterprise Solutions. The original company name, under which RES Software was founded.

RES Authorized Learning Center [T] – AKA RALC. A training company or partner with adequate facilities and a RCT on staff able to provide official certification training with RES Software courseware. To find a RALC in your area, contact

RES Automation Manager [B] – The new name per october 5th for the product formerly known as RES Wisdom. The RES Automation Manager is a small-footprint, yet highly scaleable infrastructure management platform that allows you to make changes to any kind of Windows server or computer, without having to create a single script or policy. Automation Manager (abreviated AM) is driven by a userfriendly and easy-to-use management console, that allows for massive parallel operation: Multiple admins can schedule multiple jobs on multiple AM agents all at the same time. While retaining the ability to interface with Active Directory for the purpose of managing AD objects, RES Automation Manager itself does not need AD as a prereqisite to run. This means you can manage machines even outside of your own domain. AM supports multiple administrative roles, which will allow you to securely define exactly who can create or run jobs on what target computers. You can add the Service Orchestration Module to AM, which will allow you to deliver IT as a Service.

RES Certified Professional [T] – AKA RCP. A certification awarded to those who pass the prometric exam for a given RES Product.

RES Certified Trainer [T] – AKA RCT. The certification awarded to those who a) hold current RCP certifications in all RES Products and b) have participated in a T3 class. While a RALC can provide the prerequisites, only RES Software can certify new trainers.

%RESCUSTOMRESOURCES% [W] – Environment variable which points to the location of Workspace Manager’s Custom resources.

RES Dynamic Desktop Studio [B] – This is the new name per October 5th 2010 for the suite of all RES products together. The Dynamic Desktop Studio consists of RES Workspace Manager, RES Automation Manager, the Service Automation Module and the Virtual Desktop Extender AKA VDX.

RESguru [B] – Multiple meanings: A) Reference to this site or B) An individual demonstrating practical knowledge of RES products AND a determination to share that knowledge by any means possible. The site was originally founded by Max Ranzau in early 2009. You can find the current list of RESguru writers here.

%RESPFDIR% [W] – A system environment variable set by the installation of RES Workspace Manager, which points to the location of the installed software. This variable is important if you mixed environments of Pre-WM2011 and WM2011, such as the case may be if you are midstream in an upgrade. This variable is necessary if you need to refer items in the dbcache. For products prior to Workspace Manager 2011, the default path was %programfiles%\res powerfuse\data\DBcache. In new WM2011 installations the default location is %programfiles%\res software\workspace manager\data\DBcache. Note that directory names are shortened in the variable so it usually looks something like C:\PROGRA~1\RESSOF~1\WORKSP~1.

RES Portals [B] – There are actually two RES portal sites today: 1) The Support portal is for all current SA customers and partners alike. This is where you can log in to retreive the latest released software, access the knowledge base, request remote control, start support tickets and much more. 2) The other portal is the Partner Portal. Here reseller and distribution partners can download collateral and other things. Access to the support portal is governed internally by a Portal Admin within your company. See this video for a great tutorial and introduction to the RES Partner Portal. Also check out this article on how to register.

RES PowerFuse [B] – Former name, pre October 5th 2010 for the RES Workspace Manager

RES Screensaver [W] – See Static Screensaver.

RES Service [W] – Aka. RES Workspace Manager Agent Service. A part of the Workspace Manager installation package. The job of the RES Service is to connect to the Workspace Manager datastore and ensure replication of downstream configuration data and upstream logging and Usage Tracking information. The short name of the service is RES and the binary image is C:\PROGRA~1\RESPOW~1\svc\res.exe. The service runs with local system credentials. This is fine as long as you use SQL authentication. If you want to use Windows Authentication on your SQLserver, you may need to change the credentials on the RES Service.

RES Software [B] – The place where all the magic happens! RES Software has produced user workspace management solutions since 1996 with a broad adaptation in over 18 countries. The two main products are RES Workspace Manager , RES Automation Manager and VDX. For more information, visit the corp. website here.

RES User Group [B] – Originally founded by Yuri Haak, The RES Software User Group (RESUG) is a community formed with the intention of representing a worldwide association of people who share a common interest in the development, deployment and exploitation of RES Software’s products. The usergroup is a seperate legal entity from RES Software and has a blog here and is also home to an active forum with many participants.

RESverse [B] – Okay, okay, so I totally made that one up.. :-) The ‘RESverse’ is my humble reference to the realm of all things RES Software related: The RES Universe! (cue rimshot)

RES Workspace Manager [W] – The new name, per October 5th 2010 for the product formerly known as RES PowerFuse. Before that date, the term Workspace Manager was an early name for the Workspace Composer. The RES Workspace Manager has been the flagship product of RES Software for +10 years and is the market leading solution for user workspace management. For the technical crowd this is the ultimate SuperTool for managing configuration, profile contents, security, reliability, alerting, performance, documentation and much much more. The architecture of Workspace Manager is a highly scaleable, lightweight cached client-server job, where a local RES Service caches the configuration data from the central Workspace Manager datastore and a separate process, the Workspace Composer renders the users workspace contents (apps, data, printers, settings, etc.) according to the user’s context (user identity, location, devicetype and time of day), while maintaing kernal level security for processes, file systems, removable drives and network. For further reference, see the product page on the corp site here.

Resource [A]- An Automation Manager object which can contain any kind of file or collection of files, which is to be used by a Automation Manager task. A resource can be anything filebased: A hostfile, a MSI file or a printer driver, consisting of multiple files. A resource can be stored in the Automation Manager datastore or you can point to an existing fileshare using a linked resource, where you might have an existing installation library. A regular AM resource only contains one file. For multiple files you’ll use a Resource Package . Note that both regular resources and resource packages are stored in the Automation Manager datastore. They are however not stored as BLOB’s but stored within actual AM table data. The advantages of using database table based resources is that Automation Manager then can both offer 2-tier bandwidth control and direct firewall traversal. These are not possible using the linked resource type as the agent will access the linked ressource directly when needed. Also note that you can convert back and forth between linked resources and regular resources. Just rightclick on an existing resource and select convert.

Resource Package [A] – Another type of resource for the RES Automation Manager. A resource package is essentially just a compressed container object, in which you can store multiple files. This is ideal for software deployment, where the install package consists of multiple files. This is typically the case with printer drivers for example. To use a resource package, just create a new resource within the Automation Manager console, under the Repository node. When selecting resource type, select Resource Package from the drop-down there. See also linked resource.

RES Shell [W] – AKA Classic Shell AKA RES Workspace Manager Shell. This is the original replacement shell which the Workspace Manager offered prior to the emergence of the Windows Explorer interface in NT4 and newer. Back in the heyday of Citrix Winframe, the users had grown fond of the startmenu on the Windows 9x local operating systems and only had the ancient Program Manager interface at their disposal in Winframe desktop sessions. Enter PowerMenu 2000, circa 1999 which gave the users a shell that looked very Win9x’ish and had all sorts of configuration bells and whistles attached. The funny thing about this shell, still available in WM today is that it divides up our customers in two groups, those who love it and those who hate it. There is no inbetween aparently. Those who love it, do so because it’s not explorer with it’s inherent management and security challenges. Those who oppose using it, usually do so from a look-n-feel or functionality standpoint. The RES Shell is by no means meant to replace Explorer or newer interfaces, but to provide an alternative. Successful use cases include kiosk environments such as libraries. For more info read this article.

Restriction [O] – Delivered service orchestration service that disqualifies a person for a specific other service. For example two apps could be mutually exclusive due to corporate policies.

RESug [B] – Acronym and domain name for the RES UserGroup.

Return [O] – What you do with a service when you don’t need it anymore. Think of it like returning a book to the library. A practical example; you’ve used MS Visio for your project which has been completed. You can then opt to return the Visio service. This could then practically result in the icon being removed from your Workspace Manager rendered Dynamic Desktop, and the software automatically being removed from your computer, utilizing Automation Manager.

Reverse Seamless Windows [W] – Seamless Windows by itself, was a client display concept implemented by Citrix in the late ’90’s in the MetaFrame product. The technology made it possible to spoof the desktop into displaying a remote application as if it is part of the local desktop on a client PC. Reverse Seamless Windows does, as the name indicates, the exact opposite. Here we take a local application (such as an app that won’t run well or at all on a SBC server) and make it look like it’s actually part of the remote desktop being served up on the server farm. Reverse Seamless Windows is offered (and patented) by RES Software by way of the Workspace Extender, now known as the Virtual Desktop Extender abreviated VDX.

ROB [W] – Acronym for Read-Only-Blanketing. A security subsystem in Workspace Manager. (Also the firstname of a kickass trainer at RES.NL ;)

Rule [W] – Rules are the basic components of Zones in RES Workspace Manager. A zone is defined by one or more rules. The current 25+ available rules in general describe the geography and/or geometry of the session/computer where the user is logged in to a RES managed workspace.

Run Book [A] – A runbook, in Automation Manager terminology is an object which can contain parings between modules and/or projects, – and agents and/or teams. What this means in plain english is that you can store job schedulings for different tasks to be run on different computers, all within one container. This will enable you to automate jobs which has dependancy across multiple computers. An example would be to build the components of a Citrix Xenapp farm: First build the DC, then the SQL, and then finally deploy XenApp to the terminal servers. Each of these tasks need to happen on different computers, but in sequence as the build contains dependancies.

Run Book Automation [A] – See Run Book

RunBookWho [A] – A parameter in RES Automation Manager which allows you to specify during scheduling which agents will be executing the runbook. This is very useful in scenarios involving Service Orchestration.

Run Book Parameter [A] – This is similar to module parameters and project parameters. A runbook parameter allows you to specify values which then via parameter linking can be used in the projects and modules within the run book. The run book is a self contained object which may operate across multiple computers, yet with a run book parameter, you can specify values or variables which can determine the operation of the run book. For example, schedulings within a run book can be determined by conditions.

Run-Once [W,A,O] – An option which can be configured in several RES products to ensure that a given setting is only applied once. Note that there are several flavors of run-once, depending on the setting. For example a user registry configuration setting can be chosen to be run only once, making the setting voluntary for the user, yet other configuration items – such as a Automation Manager job scheduling – can be chosen to be either run once per user, per computer or per user per computer.

RWMBC [T] – Acronym for RES Workspace Manager Basic Course. There are 3 seperate course outlines for Workspace Manager, although it’s recommended to combine them all into once couse. See this posting for further info.



SA [B] – Acronym for Solution Assurance.

Sampling Mode [W] – Is a subfeature introduced in the Workspace Manager 2010 User Settings. This feature is NOT related to the Desktop Sampler. It allows you to capture what’s going on for a cross section of the user population to which you are planning to implement User Settings. You can configure a ratio so that you, for example, only record sample data for, say 1 out of 10 users. Unlike User Settings and the desktop sampler’s DTS files, the sampled data is stored in the Workspace Manager datastore. This is however only temporary until you get a fix on what settings you want to preserve or ignore. After that you are free to dump the sampledata. Sampling mode records HKCU registry changes and file changes in %userprofile%. The changes can be recorded globally or per application.

Scheduling [A] – The act of preparing jobs to execute in RES Automation Manager. Jobs can be scheduled immediatly, recuring, scheduled to execute later, after next boot, after every boot and when a new agent registers. Job scheduling can also be invoked from within a user session managed by RES Workspace Manager, using Automation Manager Integration. Finally it is also possible to schedule AM jobs through the command line options of the AMC.

Scope Control [W] – This describes the ability to limit a given Administrative Role to a certain subset of users identities, locations and devices and/or workspace containers. The idea is that you can run several departments (or perhaps even companies for that matter) under the same umbrella. Using scope control, you can then configure that AdminX for DepartmentX can only manage settings which are exclusive to the users of DepartmentX. Settings which are shared among different scopes will be read-only to the Administrative Roles that share them.

Secure Envelope [W] – This was an old demo concept to show off the capabilities of Removable drive security. The secure envelope is configured around a “secure” app, where the prereqiusites are: a) Two factor authentication and b) Certain other communication apps such as IE, MSN, Outlook must not be allowed to run while the envelope is active. More information on this novel approach can be found in this article

Security [W] – A main node in the Workspace Manager 2010 console. Here you can configure the 7 built-in security subsystems of Workspace Manager: Applications, Websites (from WM2011 and up), Removable Drives, File and Folder security, Read-Only Blanketing, Sessions and Network.

Security Context [A] – A set of fields in the RES Automation Manager console which can store a username and a password. The security context can also be stored in a Module parameter of the Credentials type. An example use for a security context is storing domain admin credentials for creating a user in AD.

Security & Performance [W] – Obsolete name for the Adaptive Security Module, one of the feature modules in RES Workspace Manager. This name became obsolete per the 2012 SR3 release. See also the Dynamic Configuration and Delegation and Compliance feature modules.

Security Roles [W,A] – Obsolete name, pre Workspace Manager 2010. See Administrative Roles.

Service [O] – Predefined capability that can be requested by the organization and can be delivered by the IT department to a specific person. An example could be a new employee to HR, or a new app to an employee, or ordering a cellphone could be requested as a service.

Service Attribute [O] – Specific information that applies to the subscriber of a delivered service. Example needed.

Serviced User [A,O] – A Serviced User is a name for a user to whom one or more services have been delivered through Service Orchestration, but not yet returned. This name is being used in the context of Automation Manager for licensing purposes. As long as a user is considered serviced, 0,5 licenses is charged from the Automation Manager license pool. In the context of Service Orchestration, a user who has requested a given service is known as a subscriber.

Service Orchestration Client [O] – This is the user interface of the Service Orchestration Module for Automation Manager. There are currently 3 Orchestration clients available. One is a windows client, which sits nicely in the system tray, the other is a webclient which looks nice on most cell phones. Third, a native orchestration client is now available for the iPhone/iPad in the AppStore and on iTunes. The Service Orchestration Clients allow the user to request services, or partake in a workflow, by adding input, approving something, etc.

Service Orchestration Module for Automation Manager [O] – This is the RES Software product launched in 2010, which allows you to implement people processes and business flows, which tie into IT automation, in a swift and efficient manner. This software is an add-on to the RES Automation Manager. Formerly known as Project Orchestra and Orchestration Pack for Wisdom, this component introduces the ability for IT admins to invoke task automation and resource provisioning based on services and business rules. As of December 2010, the service orchestration module is available for download and evaluation through the evaluation download page at RES. For a nice demo of the product, go have a look at the video here.

Service Orchestration Console [O] – The central console for the Service Orchestration Module for Automation Manager. This console is the first item that you typically will install. It requires .Net Framework 4.

Service Orchestration Person [O] – See people.

ServicePack AKA Service Release [W] – New name for RES Workspace Manager PowerPacks. The servicepacks are quarterly released sets of fixes and enhancements, which include a rollup of all the updatepacks which has been released since the previous servicepack or major release. See version numbers for further details. Service Releases are usually referred to as SRn, where n is the Service Release number.

SessionGuard [W] – Old name, pre Workspace Manager 2010. See Sessions.

Sessions [W] – AKA Session Security. Formerly known as SessionGuard. This is a node within Workspace Manager to allow the console operator to control the behavior of user sessions when the user roams physically from one device to another. If a user moves from one device (PC or thin client) then Workspace Manager can prompt the user for what he wants to do (log off the other session, disconnect, etc). Session security also offers the option to show users the applications running on the computer they left behind. This system can help you improve overall security if you have problems with users not logging off properly.

SETPRINT.exe [W] – This is a component of Workspace Manager. The executable that launches Printing Preferences. Located in %programfiles%\RES Software\Workspace Manager. Note Printing Preferences and other internal Workspace Manager apps can be launched using pwrgate.exe

SetShell [W] – Aka. SETSHELL.exe This utility is almost obsolete. See end of this paragraph. SetShell is a free utility from RES Software designed to switch the shell of either the local or a remote computer between native Windows (means Workspace Manager 2008 or earlier switched off), Workspace Manager enabled, or RES Subscriber enabled. SetShell can only configure one computer at a time. If you need to change the shell on more than one computer simultaneously, there is a Task in Automation Manager to do just this, or you can do it in the Workspace Manager 2010 Agent view. The SetShell used to be freely available for download from the main RES site, but they have moved it onto the portal, so you need a username and password to get it. Note: With the release of Workspace Manager 2010, SetShell has become largely obsolete as you can now set the shell on all agents centrally from the RES console. See this article. Note however that if you are using the Subscriber, currently (March ’10) Setshell is the only RES utility that can set that for you, unless you want to modify the registry yourself.

Setup [W] – One of the main nodes of the RES Workspace Manager console. Here you can configure most of the set&forget type of settings such as datastore connectivity, licensing, workspace models, usage tracking, reliability and much more.

Shell [W]The interface you’re presented with. When Workspace Manager is controlling a user session’s shell, there are two options available. Either use the built-in Windows shell, managed by Workspace Manager or use a small RES-built desktop called PowerMenu. There are advantages and caveats of each, which may be covered in another article sometime. Note however that you can configure exeptions for the shell so you can have different users running different shells.

Silver [W] – One of the 4 editions of the RES Workspace Manager 2011. In addition to it’s own features, the silver edition cumulatively contains the features of the Bronze edition. This effectively gives you the Personalization & Composition and Advanced Administration feature modules. See also Gold and Enterprise editions. Update: From Workspace Manager 2012, the contens of silver can be determined by the customer. In other words, if a customer is only prepared to purchase Personalization and Composition, while needing security and none of the Advanced Admin items, this can be specified under the licensing node.

Site ID [W, A] – A site ID is a unique SID-like identification string which is generated when you initialize a new datastore for either RES Workspace Manager or RES Automation Manager. The Site ID is needed when you register for a portal account with RES Software. You will find the Site ID in the top of the Licensing node found in the consoles. Note: The site ID must be activated before you can register for a portal account. See this aticle on license activation.

SLA [B] – Acronym for Service Level Agreement. See wiki article here on this topic. Access Balancing can help you monitor your login time if you have a SLA on it.

Slack [W] – A name of a tab and a term used in the Workspace Designer wizard in RES Workspace Manager. Let’s say you are using the workspace designer to create rules for Drive and Portmappings, based on data you’ve picked up with the Desktop Sampler. Going through the wizard, you pick one or more contexts to assign the mapping to, and the Slack percentage tells you how many users which didn’t have the mapping before and would now all of a sudden get it, if you decide to use the selected context(s). Ideally your slack percentage should always be zero. The workspace designer has the ability to automatically remove both slack and missed users by chosing the “Add any missing and remove slack” checkmark. Slack is removed by adding explit no-access entries for the slack users to the access control on the rule being generated by the wizard. In plain english, the checkmark add rules that prohibit access to those who shouldn’t have it.

Solution Assurance [B] – AKA SA, Software Assurance, Subscription Advantage, etc. This is the annual fee you would pay as a RES Software customer to ensure eligibility and continual access to the latest releases of the software you’ve purchased. A typical SA would be something like 20% of the purchase price. When you purchase your RES product, one year of SA is included per default. Note: SA does not per default entitle you for EAP status as that program is per invitation only.

Smart Cache [W] – A new feature introduced in Workspace Manager 2012. This feature allows for better handeling of User Settings in mobile (laptop) environments, where access to the user’s homedrive isn’t always accessible. The short explanation of Smart Cache is that User Settings uppon change are stored in the DBcache of the local computer and then uploaded to the users homedirectory when there is an online connection.

Smart Rule [O] – Smart rules allow Service Orchestration to determine to whom a certain workflow action applies, based on criteria. An example of a smartrule is when a given person is unavailable to give permission to a service. A smartrule will allow you to configure alternative people to approve if the first one does not respond.

Specified Mode [W] – Aka. legacy mode. This is one of the Zero Profile modes available in Workspace Manager 2010, which is compatible with the User Preferences feature in Workspace Manager 2008. Contrary to Immediate mode, which captures anything a given target does, specified only grabs specifically what you tell it to grab. This is very useful for picking up known settings.

Splash Screen [W] – The graphic loader screen with a progress indicator, being shown while the Workspace Composer renders the user workspace at logon. In Workspace Manager 2010 you can switch off the splash screen completely in the Composition|Desktop|Lockdown & Behavior node. Note: switching off the splash screen is a global setting, it is not possible to show it to some users, but not to others. This is due to the fact that when the user is identified the windows for deciding to show a splash screen would have passed.

SO [O] – Acronym for Service Orchestration.

Static Screensaver [W] – AKA RES Screensaver. This is the default built-in screensaver which can be enabled in RES Workspace Manager. The concept of a static screensaver dates back to the 1990’s in the days of CRT monitors and ISDN dial-on-demand routers. (Yeah, go ahead and make me feel old, okay!) Anyway, the theory was that a static (i.e. non-moving) image presented on a WHITE background would wear the monitor less and since there is no movement, there would be no screen (ICA/RDP) traffic to keep the ISDN lines open. Today it’s hardly ever used as most customers prefer some other screensaver. There is an article here that shows you how to configure a custom screensaver in Workspace Manager.

Stealth Mode [W] – This is as of yet still an unofficial term, used to describe the situation when you install Workspace Manager 2010 onto an existing unmanaged computer and switch off all the management functions in the Workspace Model to begin with. The user will not notice the shell has been switched to Workspace Manager if the splashscreen is disabled at the same time. The cool thing about stealthmode is that you can then gradually start to take managed ownership over different parts of the existing estate. You could also use this mode of operation in preperation for a migration to a new operating system. In that case, you would use User Settings in Capture Targeted mode to pick up existing settings in the existing environment. Second, you might only want to start with taking over the network drive mappings, thereby eliminating a big chunk of the existing loginscript. See article RG02A on Stealthmode deployment.

Subscriber [O] – In the IT Service Store, this is a person to which a service has been delivered, that has not yet been returned. Example; you have requested and aproved for usage of MS Visio. As long as you are eligeble for that app and haven’t returned it, you are said to be subscribing to that service. Note: Service Orchestration Module will charge 0,5 licenses from the Automation Manager license pool until all services are returned by a given subscriber. In the context of licencing, the subscriber is known as a serviced user.

Subscriber[W] – In the realm of RES Workspace Manager This is a variation of the Workspace Extender. This component will allow you to convert any regular PC into a thin-client, though preserving it’s ability to launch local applications. The Subscriber is set as an alternative shell, which in turn either can display a local simple menu, or suck the user straight into a loadbalanced, published, central desktop (where Workspace Manager must be running in order for the Subscriber and Workspace Extender to work). Tip: run subscriber.exe /config to access the configuration panel of the application. See article RG011 on how to set it up.

$SubString() [W] A string manipulation function within RES Workspace Manager. This function will carve out a substring from another string starting from the left. The format is $Substring(sourcestring,startchar,length). For example $SubString(batmobile,3,4) would return ‘mobi’. The $Substring function is often used in combination with $AdInfo() to generate user initials, for example for MS Office inital setup. That would look something like this: $substring($adinfo(firstname),1,1).$substring($adinfo(lastname),1,1). For yours truly, this combo would grab the first char of my first and last name and put dots inbetween, so the result would effectively be: M.R. If you need to work from the right end of the string, see $EndString.



T3 – [T] Acronym for Train The Trainer.

Target Computer [W, A, O] – Commonly used phrase to describe the endpoint where either an Agent is installed or a Automation Manager Job is scheduled

Task[A] – Basic object within RES Automation Manager which does something to the target computer. The other type of basic object is a query. There are 100+ different tasks and associated queries to chose from in RES Automation Manager, from the simple task of changing computer properties, to the advanced items which can manipulate Active Directory objects. All of them present a nice GUI to the console operator, so scripting is largely eliminated.

Team [A] – A group of Automation Manager Agents. Membership of a Team can be either static or based on Team Rules. An Automation Manager team can also be marked as a Primary Team. Finally it’s possible to assign a project or a module to be scheduled when an agent is respectively added to or removed from the team.

Team Rules [A] – These rules allow for Automation Manager to automatically place an agent into a team. Rules which can be used for this are Computer Function, FQDN, IP address, MAC address, OS bit version, OS suite, OS type, OS version/servicepack level and processor architecture (32/64bit)

Teleport Button [W] – Not official terminology, but used often among field engineers. When modifying any item that can be configured in a Workspace Model or the Global Model, a button will appear to the right that looks like this: . Clicking this button will teleport you straight into the node which it’s controlling. This is useful for configuring additional options for an option you’ve just enabled or disabled.

Template [W] – A catalog of built-in predefined HKCU registry settings and/or files+folders from beneath %userprofile% to be captured for a given application or operating system component by the User Settings feature of RES Workspace Manager. When used to create new User Settings, the templates contens can be edited. Templates include settings for multiple versions of the most popular apps such as all Office apps, FireFox, IE and Chrome and several more.

Tim the Toolman [W] – The name of an early version of DSbrowse.

Time Restrictions [W] Formerly known as PowerHours. A way of configuring an application to only be available in certain time frames on certain days. PowerHours are configured underneath an applications Access Control | Time Restrictions tab, where you can specify the available “opening hours” for an app in 30 minute intervals for a 7 day period. Note, currently in Workspace Manager 2010 SR1 the user will get warned 1 minute before he/she hits a time restriction on an application. If the user does not comply and closes the application, it will be forcefully terminated.

TITS [O] – Completely and utterly unofficial acronym for The IT Store. Hey, I didn’t coin it, however it did get your undivided attention for a second, didn’t it? :)

Tracing [W,P] – This is essentially switching on a debug log if there’s something strange in the neighborhood. You can enable this in both Workspace Manager and Automation Manager although the methods are a bit diffrent. To enable Tracing in Workspace Manager, look at the article here. To do the same in Automation Manager, have a look here.

Train the Trainer [T] – AKA T3. A course hosted by RES Software to train new European RCT candidates. Stateside RES trains RCT’s individually at this time. During the T3 course the participants present themselves and teaching techniques are discussed also. Their training method and style is evaluated by RES Software. Only candidates who have passed prometric exams for both Workspace Manager and Automation Manager are elligible to participate in either Train the Trainer programme. Contact RES Educaton for Europe or yours truly for the United States for more information.

Transaction [O] – The act of delivering or returning a service in the Service Orchestration Module for Automation Manager

Transaction Engine [O] – Initiates delivery and return of services using transactions and handles workflow actions in the Service Orchestration Module.

Trigger [O] – An event that initiaties the delivery or return of a service in the Service Orchstration Module for Automation Manager. For example, a trigger may be that a service will be delivered as soon as a person qualifies for it. Another trigger may be that a subscriber requests the service.



Vault [H] – References the encrypted local cache of RES HyperDrive

VDX [V] – Acronym for Virtual Desktop eXtender. VDX is a patented technology and a stand-alone product from RES Software, which provides Reverse Seamless Windows capabiltiy into Remote desktop environments delivered by VDI/TS/Citrix etc. This means applications which do not run well within a remote environment, can remain local, yet appear as if they are part of the remote, centrally managed desktop. Refer to this article for further information on how VDX works. Also have a look at the videos found here and here. VDX was released for GA on Febuary 14th 2011. The product is licensed seperatly, so there is no hard dependancy on the RES Workspace Manager. See also this posting for information on how licensing and the product works in general. Notes: VDX is also referenced as a feature Module in the context of Workspace Manager editions.

VDX Admin Pack [V] – An optional add-on package for VDX, which includes additional documentation, a sample configuration.xml file, a VDX GPO policy template and the VDX Editor. The admin pack also contain a console for the VDX License server.

VDX Editor [V] – A tool which is included in the VDX Admin Pack. This editor allows you to safely and swiftly edit the configuration.xml being used by the VDX Engine. The editor will allow you to configure static shortcuts, filetypes and mimetypes. Global options and VDX license server connection configuration can also be set here.

VDX Engine [V] – The component of VDX which is installed on the datacenter side. The VDX Engine can either be baked into a VDI image, or deployed on a terminal server with or without Xenapp on top. The VDX Engine is aware of either a dedicated VDX License server, or optionally an Enterprise licensed RES Workspace Manager instance as a source of licenses. To configure the VDX engine you can either use a XML file, called configuration.xml. Alternatively the engine can be configured via registry. See article RG032 for further information.

VDX License Server [V] –

VDX Plugin [V] – This is the client side of the VDX product, which communicates with the VDX Engine. This communication happens over a virtual channel inside either the Micrsoft RDS protocol or Citrix ICA/HDX. The Plugin just sits as a red icon in the system tray and has nothing to do with browser plugins. It’s just a funky name for a client.

Version number [W] – In Workspace Manager you have a 4 segment version number (x.x.x.x) indicated in the lower left corner of the console window.  The first digit indicates the Major release version, which is typically incremented every year. Workspace Manager 2010 is 9.x.x.x, Workspace Manager 2008 is 8.x.x.x, Workspace Manager 7 is 7.x.x.x. The second digit represents the minor release version. The minor version number hasn’t been used as far as I can remember. The third digit represents current servicepack level and the fourth and last digit represents the updatepack level.

VideoVault [B] – Part of the RESguru site which links to any and all RES related videoclips found on the Net. The VideoVault is divided up into 4 parts: Technical Presentations, Tutorials, Commercial videos and Legacy videos.

Virtual Appliance [H] – Basically a pre-packaged virtual machine, which you pop into your hypervisor platform. A good example of this is RES Hyperdrive.

Virtual Desktop eXtender [W] – See VDX.

Virtual Workspaces [W] New buzzword, I believe coined by Gartner Group to define what we’ve been doing all along with RES Workspace Manager since 1999. See this article on Dynamic Desktops for my two cents on the whole thing.



Web Portal [W] – Formerly known as WebTop, a feature of the RES Workspace Manager. Allows you to generate a web-page in the users session that will show the contents of the start menu as a web page. To address any confusion, NO – this is not a replacement for Citrix’s web interface. The HTML is rendered inside the users session in the %temp% folder. It is for use in environments where you want to provide a consistent web look-n-feel instead of the Windows explorer/aeroshell interfaces.

Website Security [W] – One of the cool new features that came out in Workspace Manager 2011 and up. This feature allows you to block certain parts of URL’s which users are trying to access on websites. This still however only works with Internet Explorer as of WM2012. For other browsers you would need to use the Network Security part of WM, which operates on layer 3.

WebTop [W] – Obsolete terminlogy, used prior to the release of RES Workspace Manager 2010 see Web Portal.

WFA [O] – Homemade acronym for WorkFlow Action.

Wisdom [A] – Obsolete name for the RES Automation Manager, prior to October 5th 2010.

Wisdom (acronym) [B] – Originally W.i.s.d.o.m. was an acronym for Windows Installation, Scheduling and Deployment Operations Manager. This is no longer in use. These days we primarily refer to change automation and Runbook Automation for Windows, when speaking about the RES Automation Manager.

WM(20xx) [W] – New, not-official acronym for the new RES Workspace Manager

WMC [A] – Obsolete unofficial acronym for the Wisdom Management Console. Note: There may be a point of confusion here, so pay good attention. The WMC acronym should be discarded and as the productname Wisdom became obsolete per Oct 5th 2010 when the product changed name to the RES Automation Manager. After this date, using the acronym WMC would logically refer to the Workspace Manager Console instead.

Workflow [O] – Sequence of delivery or return actions in and triggers that define how and when a service will be delivered or returned. For example, a workflow could begin with somebody requesting a service (like an app). Next step could be that somebody else has to approve the request, and finally the workflow may schedule an Automation Manager job to install that app on the subscriber‘s computer.

WorkFlow Action [O] – An action specified in either a Delivery or Return Workflow as part of a ServiceStore Service. Often abreviated by yours truely as a WFA.

Workspace Analysis [W] – A part of the RES Workspace Manager which will let you analyze a users workspace environment into details. You will be able to see every aspect of the central Workspace Manager configuration, but from the perspective of the user. Not only can you see what configuration items the user is eligible to receive, but also the result. Did they actually receive it and did it result in an error? Examples are what applications does the user have access to, and why do they have access? What printers, drives and registry settings will they receive? Account AD attributes. What security violations has this user incurred? What happened during the last X number of logons, ctc etc. The list is very extensive, which is why an Instant Report can be generated for every user.

Workspace Composer [W] – Formerly known as the Workspace Manager, not to be confused with the product name RES Workspace Manager. The Workspace Composer is the pfwsmgr.exe process that runs during logon, when the Workspace Manager splash screen is shown, and encapsulates the users session from beginning to end. Note that from the release RES Workspace Manager 2010, the splash screen of the WorkSpace Composer can be hidden from the user.

Workspace Container [W] – An object within RES Workspace Manager, which will allow you to cut out and manage certain parts of your environment. In it’s simplest form, a Workspace Container is just a list of computers, maintained on the Computer Control tab of the containers properties. Useful applications for a workspace include managing workstations, laptops and terminal servers from one console, or perhaps managing multiple silo’s in a XenApp farm. The uses are many, therefore I have dedicated a separate article to Workspace Containers and their many uses.

Workspace Designer [W] – A wizard within the Workspace Manager Console, which will let you import and process .DTS files recorded by the Desktop Sampler. Using the Workspace Designer, you are able to create configuration items in the Workspace Manager management console based on real-world data from your existing environment, rather than having to rely on assumptions and guesswork. The workspace designer even offers you the ability to experiment with what-if scenarios, in terms of coverage, slack and potential missed users, even before the resulting configuration items are saved. Note: The Workspace Designer can only analyze a number of DTS files equal to the number of Workspace Manager licenses you have installed. This is to prevent somebody with a 25-user trial license from analyzing a 10,000 user environment without anybody knowing about it. In that case, get in touch with your local RES representative and talk about an evaluation license for your project.

Workspace Extender [W] – This is a free component available from the RES portal, which you can use to extend applications, running locally, into a remote Workspace Manager desktop on a Citrix/TS environment. In effect what the Workspace Extender does is allowing you to do Reverse Seamless Windows. This means that apps which don’t run well on Server Based Computing environments (such as DVD burners, CAD and video apps, etc) can be run locally, yet seem as they are part of the centralized desktop. See article RG011 on how to set it up. See also Subscriber and Virtual Desktop Extender.

Workspace Manager Console [W] – Previously known as the PowerFuse Management Console and the Real Enterprise Manager. The only and last console you will ever need for User Workspace Management. The Workspace Manager console can be deployed separately to an administrative workstation. It must be noted that the Workspace Manager console is deployed as part of every full agent installation. This is however nothing to worry about (think about all the adminstrative MMC’s that are included with regular Windows out of the box.) In the case of the Workspace Manager Console, there are 3 separate security safeguards against unauthorized use. First the icon will not be shown to users who won’t have access. Second, the AppGuard kernal driver will intercept and block access. Third, even if one should be able to bypass the first two measures, the console has its own internal administrative roles that define who can do what (if anything) with that console.

Workspace Model [W] – A central part of the new Workspace Manager 2010 console which acts as a master circuitbreaker panel. It is located in the Setup | Workspace Model node. Here you will find the Global Model tab, where you can turn on/off all parts of the Workspace Manager experience. For example, if you turn everything off, you’ve effectively enabled Stealth Mode which is great for deploying on existing computers. The cool thing about the Workspace Model concept is that you can define several exception configuration sets, that differ from the Global Model. These can have many different uses and can be defined using the PlusMenu. An article has been written specifically about the Workspace Model. Click here to read it.

Workspace Preferences [W] Formerly known as PowerPanel. The WorkSpace Preferences is an application provided in the users’s start menu, which will allow him to change certain items in his environment, which in turn the admin has allowed. Per default, the user can change the contents of the start menu, desktop, quicklaunch and startup. Besides that there are options to change screensaver timeout, and similar things. Most Workspace Prefs items can at any time be overruled by the console operator. Alternatively, the WorkSpace Preferences panel can be disabled completely.

Workspacer [B] – Non-official term for someone who works a lot with Workspaces, specifically the RES Workspace Manager. I believe the term was originally coined by Yuri Haak on

WUID [A] – Acronym for Wisdom Unique IDentifier. This is a value written into the HKEY_LOCAL_MACHINE registry. The purpose of the value is to uniquely identify an Automation Manager.

WUP file [A] – These files are downloadable from the RES portal, when a new version or service release of Automation Manager is available. Automation Manager automatically updates all agent, dispatcher and Automation Manager console components. In Automation Manager 4.0 and up you can, if necessary, do a downgrade by loading up an older .WUP file. All components will then revert to the older version.



UpdatePack [W] – A minor set of fixes, which typically address one or more acute challenges. In the Microsoft world these are known as private hotfixes. A Workspace Manager updatepack is no different, as it’s not announced to the public. However, if a customer installation exhibits symptoms which the UpdatePack may solve, RES Support may advise the customer to download and install the given update pack. It is not recommended to install UpdatePacks unless being told to do so by RES Support. Every quarter, exising UpdatePacks are rolled up into Workspace Manager Servicepacks. See also version numbers. UpdatePacks are cumulative unless otherewise specified.

$UpperCase [W] – A string manipulation function within RES Workspace Manager which converts an input string to UPPERCASE letters. The syntax is the same as for $LowerCase.

UPF file [W] – UPF files contain the file based user setting which are recorded in Capture Targeted mode for a User Setting in Workspace Manager. The files in question are files/folders/foldertrees specified in the users %userprofile% path. See also UPR files.

UPF2 file [W] – This is the new immediate mode storage format for any file changes to the user’s profile in Workspace Manager 2010. These files are encrypted, but their contents can be viewed using WorkSpace Analysis on the user in the Workspace Manager Console. See also UPR2 files.

UPM file [W] – A file created in the user’s home directory and/or underneath the user’s %appdata% folder, when Smart Caching is used in Workspace Manager 2012.

UPR file [W] – These files store the HKCU registry User settings which are recorded for a user in Capture Targeted mode for a User Setting in Workspace Manager. These UPR files can be found in <Homedrive:>\PwrMenu\UserPrefs\{GUID}.UPR Note: the files are binary and can only be read by Workspace Manager and a certain old internal RES utility. This utility is however obsolete with the advent of Workspace Manager 2010, as you are now able to view the User Settings files directly in the RES Workspace Manager console. See also UPF files.

UPR2 file [W] – This is the new immediate mode storage format for HKCU registry based User Settings in Workspace Manager 2010 and up. These files are encrypted, but their contents can be viewed using WorkSpace Analysis on the user. See also UPF2 files.

Usage Tracking [W] – Formerly known as PowerTrace and before that; PowerWatch. Usage Tracking is an extensive historical logging system built into Workspace Manager, which can collect information about all application, web, user, department and computer activity: For example, which websites were visited by who and how long, what applications were used for how long. More information about Usage Tracking can be found here and here

USB Security [W] – See Removable Drive Security

User Installed Applications [W] – Formerly known as Partially Managed Workstations. This feature of Workspace Manager will allow installation of new unmanaged applications by certain specified users on certain computers. Note that the users usually need local admin privileges to execute MSIexec. All installations by the users are logged centrally in terms of time, date and software title. Tip: look into using Workspace Manager combined with Automation Manager to trigger installation.

Userprefs [W] – A folder created under the Personal Settings folder in the users homedirectory. This folder contains the .up* files that make up User Settings. Useless fact of the day: To this date the folder derives it name from the first name for User Settings. Back in PowerFuse 2008, these were called User Preferences.

User Preferences [W] – This was the first implementation of User Settings in Workspace Manager 2008. Back then, we only had the option to retrieve/store settings at login/logout. Workspace Manager 2010 maintains compatibility with User Preferences by offering user settings configured in Capture Targeted mode.

User Sessions [W] – A node in the RES Workspace Manager console, where you can see active sessions, where users are logged in and their session is managed by the Workspace Composer. This works across all windows platforms, both terminal services and workstations. Within the User Session node, you can rightclick on any user who is currently logged in somewhere. Here you can force a refresh of his session, analyze his workspace, ping the computer the user is logged in on, remote control (shadow) his session if applicable, offer Remote Assistance, Send the user a message, and finally Logoff, Reset or Disconnect the users session if applicable.

User Settings [W] – In RES Workspace Manager, this is the Next Gen implementation of user settings management technologies, known once as Hybrid Profiles, Flex Profiles, etc. The idea is to scoop up specified user settings from files/registry in the user’s profile, save it instantly or at application termination to a location unique to the user (typically the home directory), and then dunk it all back in there when you need the setting again. User Settings can be specified both globally and per application. The big deal here is that this happens in realtime. Workspace Manager will grab both HKCU settings and files modified in %userprofile% and you can do all sorts of exclusions to your hearts content. Besides that, user modified settings are NOT (unlike certain other vendors do) stored in the datastore, but easily accessible in the users home directory. Finally, you can record and log everything that’s going on, using Sampling Mode. See also hybrid profiles.

User Settings Linking [W] –  This is a feature of User Settings in RES Workspace Manager, which allows two or more Managed Apps to share the same set of settings. This is useful for example if you want to link a virtual application to it’s locally installed counterpart on another computer.

$UserShellFolder() [W] – This function will allow you to refer to UserShellFolders locations, such as favorites, desktop, appdata, sendto, cookies, etc. to name a few. This is especially useful when defining environment variables in Workspace Manager. For example usage of $UserShellFolder(favorites) will return the absolute file path to the favorites folder in the session. See this article for an overview of the functions.

UserVoice [B] – A special site on the RES Software web, where you as a registered customer or partner can submit feature requests to RES Software. What sets uservoice appart from other feature request sites is that you can actually see features submitted by others and vote on them. You get a limited amount of votes which can either be used to submit your own ideas or give 1-3 votes on others ideas, as someone else just might have thought about and submitted the idea you’ve just hatched :) You get your votes back as soon as an idea is either accepted or rejected. This does happen if your idea either is in the product portofolio already or sometimes completely out of context with what the product does. UserVoice can be reached through the RES Support portal or through this direct link. Note: You must have a portal account in order to access UserVoice. See this article on how to register.

User Workspace Management[B] Aka UWM- This is supposed to be a generic explanation of what User Workspace Management is all about. Until I figure out something useful to put here or some kind person submits a meaningfull blurb, go have a look at this article, which explains the basics of what Dynamic Desktops are all about.

UxM [B] – An acronym coined here on, to address the fact that there are multiple sets of verbiage being used in the IT business to describe anything that deals with configuring and maintaining user settings on Windows systems. While these things have traditionally been lobbed into the general category of Profile Management, it’s hopefully now becoming clear to everybody that this label quite doesn’t cover it. UxM covers things like User Settings Management, User Workspace Management, User Environment Management, etc.



XBB file [W, A] – A file being created sometimes when you export a BuildingBlock from a RES product. The .XBB file contains binary payload necessay for the buildingblock’s contents to operate correctly. For example, if you export an Automation Manager job which installs an MSI file, the .XBB would contain the resource for this file. Likewise in Workspace Manager, if you export Custom Resources, you would get an XBB file as well. Note: Some items such as icons, registry settings etc remain within the main buildingblock XML file but is encoded so the “Greenies” have a hard time reading them.



Zero Profile Mode [W] – The way you configure the Workspace Manager User settings feature to pick up profile registry or file changes for the users, so you are independent of what, if any profile that is being used. You can chose between immediate mode and Capture Targeted mode. In Workspace Manager 2010 SR2 and up, you now also have the third option to capture once and track further.

Zero-Profile Technology [W] – This is a term for using Workspace Manager 2010 to A) manage configuration settings which need to be rendered dynamically and B) grabbing User settings in real-time, storing them outside the profile, thereby C) not relying on any specific profile. To be perfectly candid about it, it’s way cool to do this, but since any Windows session in reality always needs to use some kind of profile in a session, one might be a bit more specific and refer to what RES does as zero profile reliance. Example: If you don’t configure a profile for users in a TS environment, this will work nicely. However local static profiles would start to pile up on every server, hence you really want to set up a fast locally stored mandatory profile everywhere you can in that example. There is a nice article on that right here. Other articles of interest in relation to Zero Profiling can be found here and here. Finally, take a moment to watch the introduction and tutorial videos.

Zone [W] – Often used terminology for Locations and Devices. The legacy logic behind that is in the old days, the Locations and Devices node used to be called PowerZones.

Zone Rule [W] – RES Workspace Manager has around 35 (and counting) Zone Rules for establishing the users session context within the Locations and Devices node. These range from Active directory specific rules (site, user properties), Computer hardware, ip, OS, etc, and much much more. However, from Workspace Manager SR1 the GUI for selecting rules has become somewhat confusing, making it more difficult to get a clear overview of all available types of zone rules, as they appear multiple times within the console. Stay tuned for a guide to these.

Z-Order [V] – AKA Virtual Z-order AKA Z-mode. This term describes the ability of the VDX Engine to be able to sandwich the window of a local application in between a remote desktop and a remote application. It looks something like the illustraton shown to the right.


  • By Luc, August 5, 2013 @ 05:04

    Super list of RES wiki’s.
    Any planns to update this to a 2013 version?

  • By RESguru, August 9, 2013 @ 15:22

    Hi Luc, uhm what do you mean by a 2013 version?
    BTW If you should be such inclined, feel free to contribute new or updated entries via the comments section and I’ll add them to the RESpedia and credit you for it. This is afterall a community resource.


  • By Luc, August 22, 2013 @ 05:21

    Hi Max,
    Sorry, that I was not that clear. Recently RES Software changed some of the names of the modules in RES Workspace Manager.
    Composition & Personalization Module is now called: Dynamic Configuration.
    Advanced Administration Module is now called: Delegation & Compliance.
    The Security & Performance Module is now called: Adaptive Security.
    The bundle DDS (Dynamic Desktop Studio) is now called Workspace Virtualisation Suite.

    Hopefully, this is enough.
    If you need additional information, feel free to contact me.


  • By RESguru, August 22, 2013 @ 09:48

    Good point Luc, The RESpedia needs to be updated with these new names.
    I’ll add them all as soon as I can.


  • By Engelbert, January 22, 2015 @ 14:23

    I want to extract which active directory membership is connected to a res application. Where is this data stored so i dan make a query?

  • By RESguru, March 7, 2015 @ 00:11

    Hi Engelbert, sorry for the late reply. Your comment had slipped throught the cracks in my blogs floor boards. Anyway to answer your question. The relationships between RES managed apps and their assignments are stored within the RES Workspace Manager datastore. Since several fields are encoded in the binary fields in the datastore, thus you can’t read them directly. The best way is probably to export a building block of the application(s) and read/process the resulting XML.

    Hope this helps,

Other Links to this Post

  1. Understanding Automation Manager Traffic | RES Software Blog — August 19, 2014 @ 14:15

  2. Fixing IE cookie trouble with RES WM | RES Software Blog — August 19, 2014 @ 14:18

  3. App Engine Datastore Exists | Free Documents App — January 14, 2015 @ 22:41

  4. App Engine Datastore Clear | Free Documents App — January 14, 2015 @ 23:04

  5. App Engine Datastore Does Not Support Operator In | Free Documents App — January 16, 2015 @ 20:28

  6. App Engine Datastore Backup | Free Documents App — January 19, 2015 @ 03:21

RSS feed for comments on this post. TrackBack URI

Leave a comment

You must be logged in to post a comment.