In an RES Workspace Manager environment you have to deal with the following settings:
- Application Security Rules
- User settings (Zero Profile)
An issue can be, to know and keep track for what reason a specific setting has been set. A way to keep track is to make use of the “Administrative note”. When filling in this field, make it short and descriptive. With “Security Rule” you can end up with more than one rule for a specific application, eg. Java. You will end up adding “Java” to each rule.
A more organized way, is making use of a “Stub” (Dummy) application Object and Move all security rule, belonging to Java to this “Stub” object. To move the security rule to the “stub”, select the rule, click right, select “Move…” and select the “stub” object. Name this object “stub Java” . To keep these special Application Objects together (more than one stub), you can put the “Stub”s in a separate start menu folder.
To make sure that this special Application Object doesn’t behave as a normal Application Object, some settings needs to be set on the Application Object:
- General -> Command Line = empty
- General -> ☐ Create Start Menu Shortcut
- Settings -> ☑ Hide application
- Settings -> ☑ Do not list in PowerHelp
- Settings -> ☑ Do not show in “New Applications”
- Settings -> ☑ Autolaunch at session start: Mandatory
“Identity”, “Location” and devices” and “Workspace Containers” needs to be adjusted according to the need of the security rules.
This technique can also be used with an application suite (a collection of Application objects, eg. Office). By doing so you can configure the “user settings” and “Configuration” actions once and link to the application objects of the suite.
- User settings: ☑ Use the user settings from the following application: “…” and select the stub
- Configuration: Add “Linked Action” and select the stub
The “Zero profile mode” configured in the Usersettings of the “stub” need to be set to “capture on session end”.
To get the Zero profile activated at the start of a session, configure the “User Settings” -> “Application user settings”, global or for a Workspace conatainer, to “Prefetch in background, check on application start”.
Having all the settings for a specific Application, collected in the “stub”, you have a better overview of what is necessary for that application. Also changing from a Test to a Production environment is a lot easier, one Building Block instead of…
Update 14-10-2014: For “User settings” to save settings at session end, it is nessesarry to start the “stub” at session start. Added setting 6. to the setting for a sub application object.