Receiver provides users with secure, self-service access to virtual desktops and applications, and on-demand access to Windows, web, and Software as a Service (SaaS) applications. Citrix StoreFront or legacy webpages created with Web Interface manage the user access.
The Receiver home page displays virtual desktops and applications that are available to users based on their account settings (that is, the server they connect to) and settings configured by Citrix XenDesktop or Citrix XenApp administrators. Using the Preferences > Accounts page, users can perform that configuration themselves by entering the URL of a StoreFront server or, if email-based account discovery is configured, by entering their email address.
After connecting to a store, users can search for desktops and applications or browse them by clicking + (the plus sign) on the Receiver home page. Clicking a desktop or application icon copies the resource to the home page, from where users can start it with another click. A connection is created when they do so.
You can configure a number of default settings for connections between Receiver and XenApp and XenDesktop servers. You can also change those settings for individual connections, if required.
You create connections to servers when you click on a desktop or application icon on the Receiver home page. In addition, you can open connections from a command line or from a web browser.
To create a connection to a Program Neighborhood or StoreFront server using a command line
As a prerequisite, ensure the store is available on the server. If necessary, add it using the following command:
./util/storebrowse --addstore <store URL>
./util/storebrowse -E <store URL>
./util/storebrowse -S <store URL>
./util/storebrowse –L <desktop or application ID> <store URL>
If you cannot connect to a server, your administrator may need to change the server location or SOCKS proxy details. See Connect through a proxy server for details.
To create a connection from a web browser
If you are configuring Mozilla, Netscape, or Chrome, connection configuration is normally carried out automatically during installation.
If you need to set up .mailcap and MIME files for Firefox, Mozilla, or Chrome manually, use the following file modifications so that .ica files start up the Receiver executable, wfica. To use other browsers, you need to modify the browser configuration accordingly.
application/x-ica; /opt/Citrix/ICAClient/wfica.sh %s; x-mozilla-flags=plugin:Citrix ICA
The x- in front of the format ica indicates that ica is an unofficial MIME type not supported by the Internet Assigned Numbers Authority (IANA).
Users can manage their active connections using the Connection Center. This feature is a useful productivity tool that enables users and administrators to troubleshoot slow or problematic connections. With Connection Center, users can manage connections by:
The servers that are used are shown and, for each server, the active sessions are listed.
To change advanced or less common settings, you can modify Receiver's configuration files. These configuration files are read each time wfica starts. You can update various different files depending on the effect you want the changes to have.
Be aware that, if session sharing is enabled, an existing session might be used instead of a newly reconfigured one. This might cause the session to ignore changes you made in a configuration file.
Apply changes to all Receiver users
Apply changes to new Receiver users
If you want the changes to apply to all future new Receiver users, modify the configuration files in the $ICAROOT/config directory. For changes to apply to all connections, update wfclient.ini in this directory.
Apply changes to all connections for particular users
If you want the changes to apply to all connections for a particular user, modify the wfclient.ini file in that user’s $HOME/.ICAClient directory. The settings in this file apply to future connections for that user.
Validate configuration file entries
If you want to limit the values for entries in wfclient.ini, you can specify allowed options or ranges of options in All_Regions.ini. See the All_Regions.ini file in the $ICAROOT/config directory for more information.
About the parameters in the files
The parameters listed in each file are grouped into sections. Each section begins with a name in square brackets indicating parameters that belong together; for example, [ClientDrive] for parameters related to client drive mapping (CDM).
Defaults are automatically supplied for any missing parameters except where indicated. If a parameter is present but is not assigned a value, the default is automatically applied; for example, if InitialProgram is followed by an equal sign (=) but no value, the default (not to run a program after logging in) is applied.
All_Regions.ini specifies which parameters can be set by other files. It can restrict values of parameters or set them exactly. If you want changes to apply to all Receiver users, modify module.ini.
For any given connection, the files are generally checked in the following order:
If no value is found in any of these files, the default in the Receiver code is used.
This topic applies only to deployments using Web Interface.
Citrix XenApp enables users to connect to published resources (that is, published applications, server desktops, and published content) through a server running a XenApp Services site. Citrix XenApp also creates the menu and desktop items through which users access published resources.
Customizable options for all users running Citrix XenApp on your network are defined in a configuration file, config.xml, which is stored on the Web Interface server. When a user starts Citrix XenApp, it reads the configuration data from the server. After that, Citrix XenApp updates its settings and user interface periodically, at intervals specified in the config.xml file.
Typically, Receiver connects to applications and desktops. Receiver can also open specific files associated with an application. In this case, the administrator publishes a file, rather than an application. This process is referred to as publishing content, and is a useful way to share any type of electronic information with network users.
There is a limitation to the type of files that are recognized by Receiver. For the system to recognize the file type of the published content and for users to view it through Receiver, a published application must be associated with the file type of the published file. For example, to view a published Adobe PDF file using Receiver, an application such as Adobe PDF Viewer must be published. Unless a suitable application is published, users cannot view the published content.