General

After configuring Workspace Control managed applications, they are automatically assigned an ID and a GUID. Use this information, for example, when configuring published applications for which Workspace Control manages the necessary registry settings, mapping, substitutes, printer connections etc.

Open the managed application. The Edit application window now displays two additional fields: ID and GUID.

The ID and GUID fields cannot be changed.

Enter an appropriate name for the managed application.

Enter a description for the managed UWP application.

This is shown when users moves their mouse pointer over the application in their Start Menu. Users can disable this function in their Workspace Preferences tool. Hyperlinks can be used when configuring the application description (e.g. mailto:, http://, file://).

Select the executable for the managed application. Click on , navigate to the location of the executable, select it and then select Open.

Alternatively, enter the filepath for the executable in the Command line field. For example: C:\Windows\SYSTEM32\calc.exe.
Consider the following when entering the executable filepath:

• Environment variables can be used.

• To automatically replace the folder entered in the Command line field with its corresponding environment variables, right-click the Command line field and select Replace folder name with their associated environment string.

• The wildcard * can also be used. This means that instead of %ProgramFiles%\Microsoft Office\Office14\Winword.exe, it can be written as C:\*\Winword.exe or *\Winword.exe. The wildcard is resolved into a filepath when the application starts during user sessions. The more specific the path, the faster the application is found.

  When using wildcards, consider the following:

  • Ivanti recommends using wildcards only if no additional instances of the application are present. When using wildcards only the first instance of the application is found.

  • Only one wildcard can be used.

  • Only the * wildcard can be used. Using ? as a wildcard is not allowed.

  • The wildcard cannot replace the application name or part of it.

  • The application is searched only on local drives.

  Examples of valid wildcard use	Example of invalid wildcard use
  *\notepad.exe	*notepad.exe
  C:\*\notepad.exe	C:\*\note*.exe
  C:\progra*\notepad.exe	C:\note*.exe
  %ProgramFiles%\*\notepad.exe	notepad.*
  	*.exe

• Depending on the number of files and folders on the local drives, searching for a matching file can take a considerable amount of time. Once the file is found, its location is cached on the local machine.

• If Disable file system redirector on 64-bit systems is enabled under on the Properties > Settings tab, the file is searched in both the actual and redirected folders if applicable.

The Working directory field is automatically populated after selecting the application executable in the Command line field.

If necessary, chose a different folder by selecting in the Working directory field. Navigate to the location of the desired folder, select it and then select OK.

Alternatively, enter the filepath for the folder in the Working directory field. For example: C:\Windows\SYSTEM32.
Consider the following when entering the executable filepath:

• Environment variables can be used.

• To automatically replace the folder entered in the Working directory field with its corresponding environment variables, right-click the Working directory field and select Replace folder name with their associated environment string.

• The wildcard * can also be used. This means that instead of %ProgramFiles%\Microsoft Office\Office14\, it can be written as C:\*\Office14. The wildcard is resolved into a filepath when the application starts during user sessions. The more specific the path, the faster the application is found.

  When using wildcards, consider the following:

  • Only one wildcard can be used.

  • Only the * wildcard can be used. Using ? as a wildcard is not allowed.

  • The working directory is searched only on local drives.

If necessary, enter startup parameters for the application by clicking in the Parameters field. For example, use %password% ($password$ for applications configured to run as Workspace Extensions) to pass the cached version of the user's password to the application.

Consider the following when configuring startup parameters:

• To automatically replace the folder entered in the Parameters field with its corresponding environment variables, right-click the Parameters field and select Replace folder name with their associated environment string.

• If the application that you are configuring is a Microsoft App-V 4.x application, the Parameters field specifies the location of the OSD file that is needed to start the application.

• To configure an application that runs inside a Microsoft App-V 5.x virtual application bubble, the Parameters field specifies the PACKAGEID and VERSIONID of the virtual application as /appvve:<PACKAGEID>_<VERSIONID>. For example:
  /appvve:668b7873-3ecd-4a81-aa74-0136bad81e7e_31912d51-2d3c-4622-baed-b7ad136fb032
  

• To configure the application to run inside a Microsoft App-V 5.x virtual application bubble only if the virtual application package is deployed, add the parameter /ROW:NoPkgDelivery. For example:
  /ROW:NoPkgDelivery /appvve:668b7873-3ecd-4a81-aa74-0136bad81e7e_31912d51-2d3c-4622-baed-b7ad136fb032
  With this parameter, if the configured application is started in a session where:

  • The App-V application package is not deployed, then the configured application starts, but the /appvve parameter is ignored.

  • The App-V application package is deployed, then the configured application runs inside the bubble of the App-V application.

The Default icon field is automatically populated after selecting the application executable in the Command line field.

To preview the application's icon, double-click the application icon in the Default icon field. This opens the Icon Preview window and shows a preview of the various sizes of the application icon.

To refresh the icon, select in the Default icon field.

To choose a different application icon, select in the Default icon field. Custom icons are always shown in the size in which they are uploaded. If this size is not large enough for Microsoft Windows operating systems, then icons look pixelated if users choose to use larger icons for the applications. If this is undesirable, use one of the following methods to correct it:

• Upload a larger version of the custom icon and set the UWP application to use that version instead.

• Disable the use of large icons in Workspace Control sessions. This is done from Composition > Desktop > Lockdown and Behavior. In the Settings tab, navigate to the Microsoft Windows Shell section and deselect the Use high quality default icons instead of custom icons (Windows Vista and higher) option.

• Workspace Control considers an icon to be a high-quality icon if the uploaded file is an ICO file or it contains more than one icon.

• When selecting a different (custom) icon for a UWP application, user sessions need to log off and on again for the change to take effect.

To run the managed application as a Workspace Extension, select Run as Workspace Extension. This is useful if the managed application is located on a desktop and it needs to run as a Workspace Extension via a Terminal Server session using the Workspace Extender. For more details, see Workspace Extensions.

When configuring a Microsoft App-V 4.x application, select the option Use SCCM to deploy App-V application if the application is deployed with Microsoft Configuration Manager. This option is only available if both the App-V 4.x client and the Configuration Manager client are detected on the machine where the Console is running. It automatically selects Hide application if executable was not found on the Settings tab of the application which hides the application from the Start Menu unless Configuration Manager has distributed the application. In the background, the Workspace Composer will check the registry for the availability of Configuration Manager distributed App-V 4.x applications on the client. As soon as the App-V application is available and the menu is refreshed, the application will become available.

For Microsoft App-V 5 packages, the option Package delivery mode is available. Choose to only load the minimal parts of the App-V 5 package that are needed to start the managed application or choose to load the full App-V 5 package in the background as well once the managed application starts. Loading the full App-V 5 package is useful if the managed application needs to be available when the user session is offline, for instance, on laptops.

• If a managed application is configured to run as Workspace Extension, the Configuration, User Settings and Security sections of the Edit application window are unavailable.

• By default, the App-V client fully downloads a App-V application when a user starts that application for the first time. When selecting Minimal (global) or Minimal (per user) for the Package delivery mode, the registry value HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\Streaming\AutoLoad must be set to 0.

• After upgrading to RES Workspace Manager 2014 SR2, configuring the Package delivery mode for existing Microsoft App-V 5 packages (packages that were configured in an earlier version than RES Workspace Manager 2014 SR2) will require you to (re)specify the central location of the Microsoft App-V 5 packages.

• When configuring Package delivery mode for App-V 5 packages with Minimal (per user) or Full (per user), the feature Folder Redirection for the Windows folder AppData is not supported.

• In user sessions, when starting a App-V 5 application that is configured to be deployed by Workspace Control and is not yet available from the App-V cache on the system, a splash screen is displayed in user session in the lower-right corner of the primary monitor. The splash screen informs the user that the App-V application is deploying. Once it is deployed successfully, the application starts automatically. Starting multiple App-V applications simultaneously, a splash screen for each application is displayed. Only seven splash screens are displayed at once).

  To not display these splash screens in user sessions, in the Workspace Control Console, navigate to Composition > Desktop > Lockdown and Behavior. From the right-side pane, under the Workspace Composer section, select Hide mini splash screen at application start.

Optionally, enter an Administrative note. This can be any comment or remark useful for managing the application.

Select to configure the tags associated with the managed application.

It has information purpose only, so administrators can correlate an application object in Workspace Control Console with a Configuration Item in an external change management software (e.g. Jira or Topdesk). The notes are visible only in this dialog box.

It has information purpose only, so administrators can add notes. The notes are visible only in this dialog box.

It has information purpose only, so administrators can add notes. The notes are visible only in this dialog box.