General

On the General tab of the Properties section you can review (and edit) the settings that have been made for the application. If you add an application without the wizard, these settings must be entered manually.

How to configure the general properties of an application

• Open the application and click Properties > General.
• Use the information in the ID and the GUID field e.g. when configuring published applications, in which Workspace Control takes care of the necessary registry settings, mappings, substitutes, printer connections, etc. These fields cannot be changed and are first shown when you edit an existing application.
• Enter a title for the application in the Title field.
• Enter a description for the application in the Description field. This will be shown when the user moves his mouse pointer over the application in his Start Menu. The user can disable this function in his "Personalize My Workspace" tool. You can use hyperlinks (e.g. mailto:, http://, file://).
• Click in the Command line field to select the executable for the application.
  • You can use environment variables.
  • Right-click the Command line field and select Replace folder names with their associated environment string to automatically replace the selected folder in the command line with corresponding environment variables. This option is also available for the fields Working directory and Parameters.
  • You can also use a wildcard (*). This means that instead of: %ProgramFiles%\Microsoft Office\Office14\Winword.exe you could also use: C:\*\Winword.exe or *\Winword.exe. The wildcard is resolved into a path when the application is started in a user session. The more specific the path, the faster the application will be found.
  When using a wildcard, keep the following in mind:
• In the command line only one wildcard can be used. Only the use of "*" is allowed, not "?".
• The wildcard cannot be used to replace (part of) an application name.
• The application will only be searched in local drives.
• You should only use a wildcard if no additional instances of the application are present (as only the first instance will be found).
• Examples of valid use:
  *\notepad.exe
  C:\*\notepad.exe
  C:\progra*\notepad.exe
  %ProgramFiles%\*\notepad.exe
• Examples of invalid use:
  *notepad.exe
  C:\*\note*.exe
  C:\note*.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 has been found, its location will be cached on the local machine.
• When Disable file system redirector on 64-bit systems has been enabled at Composition > Applications on the Properties > Settings tab, the file will be searched in both the actual and redirected folders if applicable.

• If necessary, select the working directory of the application by clicking in the Working directory field. Although this field is populated automatically when you select the application's executable in the Command line field, you can select a different folder.
  • You can use environment variables.
  • You can use wildcards (*).
• 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. You can use environment variables.
  • 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 will run 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>.
    Example:
    /appvve:668b7873-3ecd-4a81-aa74-0136bad81e7e_31912d51-2d3c-4622-baed-b7ad136fb032
    
    To configure that the application will run inside a Microsoft App-V 5.x virtual application bubble only if the virtual application package is deployed, add the parameter /ROW:NoPkgDelivery.
    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 application will start, but the /appvve parameter will be ignored.
    • the App-V application package is deployed, then the configured application will run inside the bubble of the App-V application.
• To view a preview of the application's icon, double-click the application icon in the Icon field. This will open the Icon Preview window, which shows a preview of the various sizes of the application icon.
• To refresh the icon, click in the Icon field. To select a different application icon, click in the Icon field. If you select a custom icon, it is always shown in the size in which it was uploaded. If this size is not large enough for Microsoft Windows 7, Windows Server 2008 R2 or Windows Vista, this icon will not look good if users opt to see larger icons. If this is undesirable, you have two choices:
  • obtain a larger version of the custom icon, and set the application to use that version instead. To do so, open the application at Applications and browse to the icon file at Icon.
  • disable the use of large icons in Workspace Control sessions. To do so, go to Composition > Desktop > Start Menu and Taskbar, and clear the option Use high quality icons (Windows Vista and higher) under Microsoft Windows Shell only.
  • Workspace Control considers an icon to be a high-quality icon, if the file selected in the Icon field:
    • is an ICO file
    • contains more than one icon.
  • To make previously selected (before RES Workspace Manager 2014 SR2) high quality icons available in user sessions, after an upgrade to RES Workspace Manager 2014 SR3 or higher, custom icons need to be reselected.
  • When selecting a different (custom) icon for an application, user sessions need to be logged off and on again to reflect this change.

• To run the application as a Workspace Extension, select Run as Workspace Extension. This is useful if the application is located on a desktop and it should run as a Workspace Extension via a Terminal Server session using the Workspace Extender. See Workspace Extensions for more information.
  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 Microsoft App-V 4.x client and the Microsoft Configuration Manager client are detected on the machine on which 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 Microsoft 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 Microsoft App-V 5 package that are needed to start the application or choose to load the full Microsoft App-V 5 package in the background as well once the application has started. Loading the full Microsoft App-V 5 package might be useful if the application needs to be available when the user session is offline, for instance, on laptops.
  • By default, the Microsoft App-V client will fully download a Microsoft 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 the Workspace Control option Package delivery mode for Microsoft 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 a user session, when starting a Microsoft App-V 5 application that has been configured to be deployed by Workspace Control and is not yet available from the Microsoft App-V cache on the system, a Splash screen in the lower-right corner of the primary monitor will be displayed to the user. The Splash screen informs the user that the Microsoft App-V application will be deployed. Once it has been deployed successfully, the application will start automatically. Starting multiple Microsoft App-V applications (almost) simultaneously, a Splash screen per application will be displayed (with a maximum of 7 Splash screens at once).
    With the option Hide mini splash at application start enabled (at Composition > Desktop > Lockdown and Behavior, in the Workspace Composer section), these Splash screens will be hidden in the user session.

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