Product Documentation

Manage applications

Dec 30, 2015

Add applications to Delivery Groups

Good to know:

  • You cannot add applications to Remote PC Access Delivery Groups.
  • An application must belong to at least one Delivery Group.
  • You can change an application's properties when you add it to a Delivery Group, or later.
  • By default, new applications you add are placed in a folder named Applications. You can specify a different folder.
  • If you try to add an application and one with the same name already exists in that folder, you are prompted to rename the application you’re adding. If you decline, the application is added with a suffix that makes it unique within that application folder.
  • You cannot remove applications from one or more Delivery Groups using the Add Application wizard. That is a separate operation.
  • When you add an application to more than one Delivery Group, a visibility issue can occur if you do not have sufficient permission to view the application in all of those Delivery Groups.  In such cases, either consult an administrator with greater permissions or have your scope extended to include all the Delivery Groups to which the application was added.
  • If you publish two applications with the same name to the same users, change the Application name (for user) property in Studio; otherwise, users will see duplicate names in Receiver.
  • Alternatives: The following procedure allows you to add applications to one or more Delivery Groups. You can also add applications to a Delivery Group when you create the group (or later, by selecting the group and then selecting Add Applications in the Actions pane), but the applications are added to only that group. 

To add one or more applications:

Step 1: Select Applications in the Studio navigation pane, and then select Add Applications in the Actions pane. The Add Applications wizard opens.

Step 2: Select one or more Delivery Groups where the applications will be available.

Step 3: On the Applications page, click the Add dropdown to display the application sources, and then select the source you want.

  • From Start menu: Applications that are discovered on a machine created from the master image in a Machine Catalog used in the selected Delivery Group.
  • Manually defined: Applications for which you provide the path to the executable, working directory, optional command line arguments, and display names for administrators and users.
  • Existing: Applications previously added to the Site, perhaps in another Delivery Group. (This source is not available if there are no other Delivery Groups or if all applications have been removed.)
  • App-V: Applications in App-V packages.

If an application source is not available or valid, it is either not selectable or a message is displayed. For example, if no applications have been previously added to any Delivery Groups, the Existing source cannot be selected. Similarly, if an application is not compatible with supported session types on the machines in the selected Delivery Groups, it is either not selectable or a message is displayed.

Step 4: The applications found on the selected source are listed. Select or specify the applications you want to add, and then click OK.

Step 5: On the Summary page, verify the information and then click Finish.

Duplicate, enable/disable, rename, or delete an application

You might want to duplicate an application to create a different version with different parameters or properties. When you duplicate an application, it is automatically renamed with a unique suffix and placed adjacent to the original.

Good to know:

  • If you previously duplicated an application in one Delivery Group so that you could add it to another Delivery Group, you can either use the Add Application wizard to add an application to more than one Delivery Group, or change Delivery Group membership through the application’s properties.
  • Deleting an application removes it from the Delivery Group but not from the master image used in the Machine Catalog (if that was its source). Deleting an application is a different action than removing an application from a Delivery Group; see below.
  • Enabling and disabling an application is a different action than enabling and disabling the Delivery Group; see the Edit a Delivery Group article.

To duplicate, enable, disable, or delete an application:

  1. Select Applications in the Studio navigation pane.
  2. Select an application and then select the appropriate task in the Actions pane.

Remove an application from a Delivery Group

An application must be associated (belong) with at least one Delivery Group. If you attempt to remove an application from a Delivery Group that would remove that application’s association with any Delivery Group, you are given the option to delete the application instead. In that case, if you choose not to delete the application, you can add it to a different Delivery Group, and then remove it from the original Delivery Group.

  1. Select Delivery Groups in the Studio navigation pane.
  2. Select a Delivery Group. In the lower middle pane, select the Applications tab and then the application you want to remove.
  3. Select Remove Application from the Actions pane.

Change application properties

To change the properties of an application:

  1. Select Applications in the Studio navigation pane.
  2. Select an application and then select Edit Application Properties in the Actions pane.
  3. Select the page containing the property you want to change. When you complete the change, click OK or Apply on the page. (OK applies the change and closes the Edit Application Properties dialog box; Apply applies the change and leaves the  dialog box open.)

Property

Select this page

Category/folder in Receiver

Delivery

Command line arguments

Location

Delivery Group association

Groups

Description

Identification

File extensions

File Type Association

File type association

File Type Association

Icon

Delivery

Keywords for StoreFront

Identification

Limits (see below)

Delivery

Name

Identification

Path to executable

Location

Shortcut on user’s desktop

Delivery

Visibility

Limit Visibility

Working directory

Location

 

Application changes may not take effect for current application users until they log off their sessions.

Configure application limits

Configure application limits to help manage application use. For example, you can use application limits to manage the number of users accessing an application simultaneously. Similarly, application limits can be used to manage the number of simultaneous instances of resource-intensive applications, this can help maintain server performance and prevent deterioration in service.

Important: This feature limits the number of application launches that are brokered by the Controller (for example, from Citrix Receiver and StoreFront), and not the number of running applications that could be launched by other methods. This means that application limits assist administrators when managing concurrent usage, but do not provide enforcement in all scenarios. For example, application limits cannot be applied when the Controller is in leased connection mode.

By default, there is no limit on how many application instances can run at the same time. There are two application limit settings; you can configure either or both:

  • The maximum number of concurrent instances of an application by all users in the Delivery Group.
  • One instance of the application per user in the Delivery Group

If a limit is configured, an error message is generated when a user attempts to launch an instance of the application that will exceed the configured limit.

Examples using application limits:

  • Maximum number of simultaneous instances limit. In a Delivery Group, you configure the maximum number of simultaneous instances of application Alpha to 15. Later, users in that Delivery Group have 15 instances of that application running at the same time. If any user in that Delivery Group now attempts to launch Alpha, an error message is generated, and Alpha is not launched because it would exceed the configured simultaneous application instance limit (15).
  • One-instance-per-user application limit. In another Delivery Group, you enable the one-instance-per-user option for application Beta. User Tony launches application Beta successfully. Later in the day, while that application is still running in Tony’s session, he attempts to launch another instance of Beta. An error message is generated and Beta is not launched because it would exceed the one-instance-per-user limit.
  • Maximum number of simultaneous instances and one-instance-per-user limits. In another Delivery Group, you configure a maximum number of simultaneous instances of 10 and enable the one-instance-per-user option for application Delta. Later, when ten users in that Delivery Group each have an instance of Delta running, any other user in that Delivery Group who tries to launch Delta will receive an error message, and Delta will not be launched. If any of the ten current Delta users attempt to launch a second instance of that application, they will receive an error message and second instance will not be launched.

If application instances are also launched by methods other than Controller brokering (for example, while a Controller is in leased connection mode) and configured limits are exceeded, users will not be able to launch additional instances until they close sufficient instances to no longer exceed the limits. The instances that exceeded the limit will not be forcibly shut down; they will be allowed to continue until their users close them.

If you disable session roaming, then disable the one-instance-per-user application limit. If you enable the one-instance-per-user application limit, do not configure either of the two values that allow new sessions on new devices. For information about roaming, see the Sessions article.

To configure application limits:

  1. Select Applications in the Studio navigation pane and then select an application.
  2. Select the Edit Application Properties in the Actions pane.
  3. On the Delivery page, choose one of the options listed below. When you are finished, click OK or Apply. (OK applies the change and closes the Edit Application Properties dialog box; Apply applies the change and leaves the  dialog box open.)
  • Allow unlimited use of the application. There is no limit to the number of instances running at the same time. This is the default.
  • Set limits for the application. There are two limit types; specify either or both.
    • Specify the maximum number of instances that can run concurrently
    • Limit to one instance of the application per user

Manage application folders

By default, new applications you add to Delivery Groups are placed in a folder named Applications.  You can specify a different folder when you create the Delivery Group, when you add an application, or later.

Good to know:

  • You cannot rename or delete the Applications folder, but you can move all the applications it contains to other folders you create.
  • A folder name can contain 1-64 characters. Spaces are permitted.
  • Folders can be nested up to five levels.
  • Folders do not have to contain applications; empty folders are allowed.
  • Folders are listed alphabetically in Studio unless you move them or specify a different location when you create them.
  • You can have more than one folder with the same name, as long as each has a different parent folder. Similarly, you can have more than one application with the same name, as long as each is in a different folder.
  • You must have View Applications permission to see the applications in folders, and you must have Edit Application Properties permission for all applications in the folder to remove, rename, or delete a folder that contains applications.
  • Most of the following procedures request actions using the Actions pane in Studio. Alternatively, you can use right-click menus or drag and drop. For example, if you create or move a folder in a location you did not intend, you can drag/drop it to the correct location.

To manage application folders, select Applications in the Studio navigation pane. Use the following list for guidance.

  • To view all folders (excluding nested folders), click Show all above the folder list.
  • To create a folder at the highest level (not nested), select the Applications folder. To place the new folder under an existing folder other than Applications, select that folder. Then, select Create Folder in the Actions pane. Enter a name.
  • To move a folder, select the folder and then select Move Folder in the Actions pane. You can move only one folder at a time unless the folder contains nested folders. Tip: The easiest way to move a folder is to use drag and drop.
  • To rename a folder, select the folder, and then select Rename Folder in the Actions pane. Enter a name.
  • To delete a folder, select the folder, and then select Delete Folder in the Actions pane. When you delete a folder that contains applications and other folders, those objects are also deleted. Deleting an application removes the application assignment from the Delivery Group; it does not remove it from the machine.
  • To move applications into a folder, select one or more applications. Then, select Move Application in the Actions pane. Select the folder. (To move applications to a different folder from within the Create Delivery Group wizard, select Change on the Applications page in the wizard, and then select or create a folder.)