Actions

Use the Actions tab to configure specific actions to be invoked when a user launches or closes the application. Application actions will only be invoked whenever the application is managed by Workspace Control. This is the case if the application is started from the Start Menu, when the application is started by a configured File Type, or when the application is intercepted by Workspace Control. Applications are not managed by Workspace Control if they are started from a command prompt, directly started from the Windows Explorer or from the run command.

The user's Event Log will be appended with the results of the applied settings. You can view the contents of this Event Log in the Workspace Analysis window of this user.

Configuration

All Actions for applications are configurable at application start. The following Actions for applications can be configured both at application start and at application end:

Execute Command
- To run an Execute Command action at application start and end, duplicate the action and change the timing.
- For Execute Command actions configured At application end for a Microsoft App-V 5.x application, the option Run outside App-V virtual environment is grayed out. The command will always be executed outside the App-V virtual environment.
Folder Synchronization
- A single Folder Synchronization action can be configured to run at both application start and end.

Actions configured for a managed application are listed per timing on two subtabs At application start and At application end (on the Actions tab in the Configuration section).

For Linked Actions a placeholder is displayed on both At application start and At application end tabs, regardless of the timing of the actions configured for the source application.
- Please note that when changing Linked actions, this is applied to all applications for which a Linked Actions action to the same source application is configured.
When editing an application-level action that is configured to run At application end to At application start or to move it to global, this action will show up in the Audit Trail with a Delete entry and Add entry. This is expected behavior.
When running multiple instances of the same managed application, with an action configured to run at application start, the action is invoked when starting the first instance. With an action configured to run at application end, the action is invoked when ending the last instance.

If Microsoft Outlook is added as a new application in Workspace Control, a registry key is automatically added on the Configuration > Actions tab. This key disables the check whether Microsoft Outlook is the default e-mail client. If Microsoft Outlook is started through a File Type a notification that Microsoft Outlook is not the default e-mail client can appear, because the associated application in the registry is pwrgate.exe [appid] instead of outlook.exe. If the user then chooses to set Microsoft Outlook as the default mail client, the associated application in the registry is changed from pwrgate.exe [appid] to outlook.exe, making the application unmanaged.

The Registry key that is added is:

[HKEY_CURRENT_USER\Software\Microsoft\Office\<officeversion>\Outlook\Options\General]

Value name and data:

Check Default Client: 0

The order in which application Actions are executed

When a managed application starts, the application's Actions are executed by category, in the following order:

Environment Variables
Drive and Port Mappings
Drive Substitutes
Printers
User Registry Settings
User Registry Policies
User Home Directory actions
User Profile Directory actions
Folder Synchronizations
Execute Commands
Automation tasks
Microsoft ConfigMgr distributions
LANDesk software distributions
Linked actions

Global Actions

Actions can also be configured on a global level.

Actions for applications are identical to global Actions, except:

In Drive and Port Mappings, Hide Drive behavior is not available.
In Printers:
- Set as default printer is mandatory, but will not reset the user’s preference. The next time the user logs on, only the preferred default printer will be restored. The user will also be notified of this event by the "Printing Preferences" tool.
- Fast Connect is not available.

Moving and Duplicating Actions

It is possible to Move and Duplicate settings related to Actions. This makes it possible to:

duplicate application settings and move them from one application to another
duplicate application settings and move them to a global level
duplicate global settings and move them to an application
move global actions to an application
move application actions to global

When moving actions from an application to global, the timing changes as displayed in the table below:

Timing of application action	Timing of global action
At application start	At logon before other actions
At application end	At logoff

When moving actions from global to an application, the timing changes as displayed in the table below:

Timing of global action	Timing of application action
At logon before other actions	At application start
At logon after other actions	At application start
At refresh	At application start
At reconnect session	At application start
At logoff	At application end

In a user session, if a user starts an application using Run as different user / Run as administrator, actions configured for the application (on the Configuration > Actions tab of the application) will not be applied. In this situation, only the settings related to the start of the application (configured on the Properties > Settings tab of the application) are applied:

Parameters
Startup style of application
Process priority of application
Disable file system redirector on 64-bit systems