Product Documentation

Publishing Resources for Users

May 16, 2015

With XenApp, you provide users with access to information by publishing the following types of resources that can be virtualized on servers or desktops:

  • Applications installed on servers running XenApp. When users access them, the published applications appear to be running locally on client devices.
  • Streamed applications installed in application profiles and stored on a file server in your App Hub. Users access the profile and virtualize the applications on their client desktops. For information about preparing and publishing applications for streaming, see the topics for Application Streaming.
  • Data files such as Web pages, documents, media files, spreadsheets, and URLs. In XenApp, the combined total of data types you publish is referred to as content.
  • The server desktops, so users can access all of the resources available on the server.
    Note: Citrix recommends that server desktops be locked down to prevent user access to sensitive areas of the operating system.

Publish all of these resource types using the Publish Application wizard in the XenApp console. To further refine how your users launch and access published resources, refer to information about configuring content redirection and XenApp policies.

Citrix recommends installing applications that interact with each other on the same group of servers (called a silo). If you have multiple applications silos, Citrix recommends using separate organizational units, so they can be convenient targets for policies and worker groups. For more guidance about planning for applications and server loads, see the eDocs section about designing a XenApp deployment.

Important: Before you begin, refer to the system requirements for supported platforms and system prerequisites.

When you publish an application, configuration information for the application is stored in the data store for the server farm. The configuration information includes which types of files are associated with the application; users who can connect to the application; importance level for Preferential Load Balancing; and client-side session properties that include window size, number of colors, level of encryption, and audio setting.

When delivered to users, published applications appear very similar to applications running locally on the client device.

Users start applications depending on the delivery options you select in the publishing wizard and the plug-in they are running on their client devices. Consult the appropriate plug-in sections in eDocs or other documentation for more information about the plug-in with which your users start published applications.

Publishing in Domains with Thousands of Objects

For directory services or domain environments, such as Novell Domain Services for Windows or Microsoft Active Directory Service, containing over 10,000 objects, Citrix recommends the following:
  • Use groups to categorize and assign permissions to large numbers of users. An application published to one group of 1,000 users requires XenApp to validate only one object for all 1,000 users. The same application published to 1,000 individual user accounts requires IMA to validate 1,000 objects.
  • When adding users through the Citrix User Selector, if the Users container holds thousands of objects, add a list of names.

To configure servers to publish for multiple users

To ensure applications are enabled for multiple users, install the applications using one of the following methods:
  • Install applications as the Built-in Administrator
  • Select an “install for multiple users” option in the installation wizard for the application, if the Setup for the application provides this option
  • Install the application for all users from a command line

To install an application for all users, after enabling Remote Desktop Services, use these steps before installing the application:

  1. Open a command prompt so that you are running it with Administrator privileges; for example, right-click the command prompt and select Run as Administrator.
  2. Run the following command at a command prompt: change user /install
  3. From the command prompt, run the Setup executable for the application.

To publish a resource using the Publish Application wizard

Open the XenApp console from any computer that can connect to the farm.

Steps and options in the wizard vary depending on the application type you select. This procedure describes the basic options.

  1. From the XenApp console, under the XenApp node, expand the farm or server to which you want to publish an application.
    Tip: To add a server to the list of servers for a published desktop or application (after publishing the application), drag and drop the server onto the published desktop or application in the left pane of the console. You can also drag and drop the published desktop or application onto the server.
  2. Select the Applications node and from the Actions pane choose Create folder. Name the folder for the application you are publishing.
  3. Select the folder you created and from the Actions pane choose Publish application.
  4. In the Publish Application wizard, on the Name page, provide a display name (maximum 256 characters) and application description. The name appears on user devices when users access the application and on the console for the farm applications. XenApp supports application names that use Latin-1 and Unicode character sets, including characters used in Japanese, Chinese, and Korean.
  5. On the Type page, specify the type of resource you want to publish and the delivery method. Three types of resources can be published (server desktop, content, and application). The next few steps in the wizard differ based on which type you select. For more details, see To select a resource type and delivery method and To select a streaming delivery method.
  6. On the Location page, add the command-line and working directory (optional) to locate the application.
  7. On the Servers page, add the individual servers or worker groups on which the published application runs when accessed by an ICA connection.
    Note: If you add a worker group, make sure that all the servers in the worker group are running the application you are publishing.
  8. On the Users page, create the Configured users list for users or groups who have access to the application. Use the options to allow access to configured user accounts only or to anonymous users.
  9. On the Shortcut presentation page, select the icon for the application and choose how the application is enumerated on the user device. The console has a limit of 1,000 unique application icons. When that limit is exceeded, the console displays a generic icon for all new applications.
  10. On the Publish immediately page, choose whether or not to make the published application immediately available to users.
    • By default, the published application is available when you click Finish.
    • To prevent users from accessing the application until you manually enable it through application properties, select Disable application initially.
  11. To view and select advanced options, check Configure advanced application settings now. Alternatively, modify the advanced settings using the application properties.
When you finish, published resources (unless disabled) are available for users.

Publishing App-V Sequences in XenApp

You can deliver the Microsoft Application Virtualization (App-V) sequences to users by publishing the sequences in XenApp and delivering the Microsoft Application Virtualization Desktop client through Citrix Merchandising Server and Citrix Receiver Updater.

To deliver App-V sequences using the Citrix application streaming feature, Citrix provides a conduit utility that supports a dual mode execution. With dual-mode, users launch applications as they normally do, and the conduit checks for presence of the App-V client. If the App-V client is installed, the App-V sequence streams to the user device; if not, the application launches from a XenApp server and streams to the user device.

System requirements:
  • Citrix supports App-V sequences on all operating systems supported by Microsoft App-V.
  • Citrix Receiver Updater for Windows supports App-V clients 4.5 and 4.6.
  • User devices must have the Citrix Offline Plug-in 6.x installed locally.
Citrix recommends the following process:
  • Deliver the App-V client to users through Citrix Merchandising Server and Citrix Receiver Updater
  • Publish App-V sequences for virtualizing on user devices if possible, otherwise virtualizing on XenApp servers

Users can then launch the App-V sequences on their desktops by clicking on the icons delivered through XenApp.

Before you start, locate the following files and have them available:
  • Microsoft Application Virtualization Desktop Client installer (setup.exe) from your Microsoft Desktop Optimization Pack (MDOP) installation media, to upload to the Merchandising Server.
  • App-V Plug-in – Integration Kit from the Citrix download site.
    Save the unzipped contents locally:
    • Save the App Streaming To AppV Conduit folder on your App Hub (the server where you store your profiles). The folder contains a pre-created AppStreamingToAppVConduit.profile file, as well as the required support files for the profile. This single profile can be used to publish an unlimited number of App-V sequences.
    • Upload the App-V MetaData files and the App-V client's setup.exe file to the Merchandising Server to create an App-V client. Citrix provides these files to add the functionality to the client needed for Citrix Receiver Updater. These files include:
      • AppV_MetaData.xml
      • AppVReg.msi
      • AppVReg_MetaData.xml
    • Save the Streaming Conduit - source code folder locally. These files are not needed to publish your applications, but you can use them to modify the conduit, if needed. This folder contains the source code for the conduit.

To deliver the App-V client with the Citrix Merchandising Server and Citrix Receiver Updater

  1. In the Merchandising Server Administrator Console, navigate to the Plug-in > Upload page.
  2. To upload the App-V_Reg plug-in components:
    1. For the Metadata File, click Browse to navigate to the unzipped location of AppVReg_MetaData.xml.
    2. For the Plug-in File, click Browse to navigate to the unzipped location of AppVReg.msi.
    3. Click Upload.
  3. To upload the App-V client components:
    1. For the Metadata File, click Browse to where you downloaded App-V_MetaData.xml.
    2. For the Plug-in File, click Browse to navigate to the location of the Microsoft Application Virtualization Desktop Client installer, setup.exe.
    3. Click Upload.
  4. Configure a delivery to communicate with your App-V server. For additional information on creating and scheduling deliveries, see the Merchandising Server documentation in the Archive.

An overview of the entire Plug-in upload and delivery process when using Merchandising Server 1.0 can be viewed at http://www.citrix.com/tv/#videos/773.

If users have the Self-service Plug-in, they can add published App-V sequences as they normally add applications.

To publish App-V sequences for streaming to desktops

The conduit utility AppStreamingToAppVConduit (which is the pre-created Citrix .profile) provides pre-launch and post-exit scripts that enable a dual-mode delivery method. This delivery method uses the App-V client to stream the application to the user device. If the user device does not support streaming or lacks the App-V client, the conduit triggers the secondary method and delivers the application to a XenApp server, which then delivers the application through session virtualization using a remote display protocol. The application can be locally installed on the XenApp server, or streamed through Citrix application streaming using the App-V client installed on the server.
  1. In the Citrix AppCenter, open the application publishing wizard and follow the on-screen instructions.
  2. Name the application with a name familiar to users, such as "Microsoft PowerPoint 2007."
  3. On the Type page, configure the dual-mode delivery method:
    • Select Application.
    • For application type, select the dual-mode option: Streamed if possible, otherwise accessed from a server.
    • For the server application type, select the secondary delivery method, such as Installed application.
  4. On the Location page:
    • Browse to your App-V server where both the conduit utility and App-V sequence are located.
    • The application to launch is AppStreamingToAppVConduit.
    • Add the command-line parameters to locate the specific App-V sequence on your App-V server.

      For Command Line:

      Enter the full path to your Microsoft Application Virtualization Client executable, followed by the location of your App-V sequence, such as:

      "C:\\Program Files\Microsoft Application Virtualization Client\sfttray.exe" "\\appv\content\Off2k7\Microsoft Office PowerPoint 2007 12.0.6425.0000.osd"

  5. On the Shortcut presentation page, manually select the icon from your icons directory (no icon by default), such as the icon for Microsoft PowerPoint.
  6. Finish the publishing wizard as you normally do.

For more information about the AppStreamingToAppVConduit utility, see http://support.citrix.com/article/CTX124860 in the Citrix Knowledge Center.

To launch the App-V sequences

When users log on:
  • Citrix Receiver Updater informs them of Plug-in updates, and if they accept the App-V client, it installs silently in the background.
  • If they use the Citrix Self-service Plug-in for the Receiver, they can subscribe to App-V sequences through that Plug-in.
Users launch applications as they normally do, and the conduit checks for presence of the App-V client:
  • If the App-V client is installed, the App-V sequence streams to the user device, where it runs in the App-V isolation environment.
  • If the client is not installed (or the device does not support streaming for other reasons), the conduit triggers the Offline Plug-in to initiate a XenApp server session where the application executes and is presented to the user over a remote display protocol.

To select a resource type and delivery method

In the Publish Application wizard, select the resource type that you want to deliver and the delivery method. To view the setting, from the Action menu, select Application properties and then select Type.

To change the resource type, from the Action menu, select Other Tasks > Change application type and follow the instructions in the wizard.

  1. Select one of the following resource types:
    • Server desktop. Publishes the entire Windows desktop of a server in the farm. When the plug-in connects to the server, the user sees a desktop interface from which any application installed on that server can be started. After selecting this application type, you must specify the server that you want to publish.

      To publish a desktop, you must be running XenApp. If you are running the console on a computer that is not running XenApp, you cannot publish the local desktop.

    • Content. Publishes nonexecutable information, such as media, Web pages, or documents. After selecting this application type, you must specify the URL (Uniform Resource Locator) or UNC (Uniform Naming Convention) path to the file you want to publish. Click Browse to view available content resources on your network.
    • Application (selected by default). Publishes an application installed on one or more servers in the farm. Note that if you are running the console on a computer that is not a member of the farm, you cannot publish local applications.

      You need to indicate one of the following application types:

      • Accessed from a server. Grants users access to applications that run on a XenApp server and use shared server resources. If you choose this option, you must then enter the location of the executable file for the application and the XenApp server on which it will run. Choose this option as the application type unless you intend to stream your applications.
      • Streamed if possible, otherwise accessed from a server (also called dual mode streaming). Grants users access to a profiled application that streams from the file share to their user devices and launches locally from within an isolation environment. Alternatively, for user devices that do not support streamed applications (for example, if the offline plug-in is not installed), this setting allows the use of an ICA connection to access the application installed on or streamed from a XenApp server.
      • Streamed to client. Grants users access to a profiled application that streams from the file share to their user devices and launches locally from within an isolation environment. With this option, the application uses client resources instead of server resources. Users must have the offline plug-in installed and access the application using online plug-in or a Web Interface site. If selected, user devices that do not support client-side application virtualization (such as, they use a non-Windows client) or do not have the offline plug-in installed locally cannot launch the application.
  2. If you selected Accessed from a server or Streamed if possible, otherwise accessed from a server, you also need to select the Server application type. These are:
    • Installed application. Enables users to launch an application installed on a XenApp server.
    • Streamed to server. Grants users access to stream a profiled application from the file share to a XenApp server and launch it from XenApp through an ICA connection.
      Note: For more information about client-side application virtualization through streaming, see the information for application streaming.

To configure locations of published applications

To access this option in the Citrix AppCenter, from the Publish Application wizard, continue to the Location page. Alternatively, to modify a location, select a published application and under Common Tasks, select Modify application properties > Modify all properties > Basic > Location.

When you publish an application, specify the command-line and working directory (optional) for the application:

  • Command-line. The full path of the application's executable file. Append the symbols "%*" (percent and star symbols enclosed in double quotation marks) to the end of the command-line to act as a placeholder for client-supplied application parameters. When a Plug-in makes a connection request, the server replaces the symbol "%*" in the command-line with application parameters provided by the Plug-in.
    If the path to the application's executable includes directory names with spaces, enclose the command line for the application in double quotation marks. Include a space between the closing quotation mark and the double quotation marks around the percent and star symbols. An example of the format to use with a path with spaces and a placeholder is:
     
    "C:\Program Files\Windows Media Player\mplayer1.exe" "%*" 
    
    Important: Changing the command-line text removes all file type associations from the application. If you change the command-line text, modify the Content Redirection application property page to select the file types you want to associate with the application for client to server content redirection.
  • Working directory. By default, this path is the same as the path in the Command line field. To run the application from a different directory, add an absolute path to this field.

To configure locations of published content

When you publish content, specify the location using address formats such as the following types (examples shown in parentheses):

  • HTML Web site address (http://www.citrix.com)
  • Document file on a Web server (https://www.citrix.com/press/pressrelease.doc)
  • Directory on an FTP server (ftp://ftp.citrix.com/code)
  • Document file on an FTP server (ftp://ftp.citrix.com/code/Readme.txt)
  • UNC file path (file://myServer/myShare/myFile.asf) or (\\myServer\myShare\myFile.asf)
  • UNC directory path (file://myServer/myShare) or (\\myServer\myShare)

To disable command-line validation

XenApp provides command-line validation for content that is redirected from the client to the server only. By default, XenApp validates published application command-line parameters passed from the client to the server. When you use the symbols "%*", XenApp ensures the parameters are valid before the application launches. If the parameters are invalid, the application launches without passing the parameters. XenApp records all failed validation attempts in the server's system log and in the security event log.

If your environment includes published applications that use customized client-supplied parameters for purposes other than content redirection from client to server, these applications might not function correctly when command-line validation is enabled. To ensure client-supplied parameters are passed from client to server, disable command-line validation for these published applications.

When using command-line validation, add all servers that store content, such as Word documents or PDF files, to the Trusted Sites list on the XenApp server. When adding servers to the Trusted Sites list, ensure you are logged on to the XenApp server as Administrator. If the content servers reside in separate domains, ensure trust relationships are established between these servers and the XenApp server.

You can disable command-line validation for selected published applications or all published applications on a server.

  • If your environment includes published applications that use customized client-supplied parameters for purposes other than content redirection from client to server, these applications might not function correctly when command-line validation is enabled. To ensure client-supplied parameters are passed from client to server, disable command-line validation for these published applications.
  • To disable command-line validation for selected published applications, from the Location page of the application properties, append the symbols “%**” (percent and two star symbols enclosed in double quotation marks) to the command-line parameter.