Product Documentation

Connecting Users to Citrix Receiver

Apr 28, 2015

You can send an automatic email to users that lets them know that they can use Citrix Receiver to access their documents and apps. You can also manually send the email to a group of users by providing their email addresses at any time.

The email template in App Controller includes a link to the site where users can download Receiver. You can also attach a configuration file to the email. The file contains the settings that enable users to configure Receiver on their device.

To send the Receiver email

  1. In the App Controller management console, click the Settings tab.
  2. In the left pane, under System Configuration, click Receiver Email Template.
  3. In the right pane, next to Automatically send invite, click Edit.
  4. In Send invite to employees as they are added to XenMobile App Controller, click Yes.
  5. Do one or both of the following:
    1. To send the email automatically, you can edit the information in Subject and Message and then click Save.
    2. To send the email manually, under Manually send invite, type the email addresses of the individuals to whom you want to send the email and then click Send.

      Separate email address with commas.

  6. To include the configuration file in the email, select Attach .cr file to email. This is an optional step.

Downloading the Receiver Configuration File

The Citrix Receiver configuration file is an XML file that contains all the settings users need to connect to the App Controller or StoreFront store. You can download the configuration file and save it to your local computer. Then, you can provide the file as a download link from your web site or you can email the file to users.

To download the Receiver configuration file

  1. In the App Controller management console, click the Settings tab.
  2. Under System Configuration, under Quick Links, click Download .cr file.
  3. In the Opening receiverConfig.cr dialog box, click Save File and then click OK. The file downloads to your computer.

Configuring Beacons in App Controller

App Controller uses beacon points to determine whether users are connecting from local or public networks and then selects the appropriate access method. Each instance of App Controller contains one store. In the store, you can configure internal and external beacons. The internal beacon is the App Controller fully qualified domain name (FQDN) and the external beacon is the NetScaler Gateway web address.

Beacons in App Controller support multiple accounts in Citrix Receiver in the following way. Because Receiver contains one account ID that you cannot change, you cannot add multiple accounts to Receiver. Instead, you can add multiple accounts through App Controller. Each App Controller instance must have one account ID. When users log on, App Controller generates a random number for the account ID. This number is set when users start the device and cannot be configured. If you export the App Controller configuration as a snapshot and then import the snapshot to another instance of App Controller, both instances would have the same account ID. Hence, you have multiple accounts. The account ID is associated with one store. For each store, this is a corresponding beacon table that contains the beacon information. You should configure one beacon, either internal or external. All internal and external beacons are configured for one store.

You must configure at least one beacon in App Controller. You can use the default setting for the internal beacon without configuring any other beacon settings.

To configure the beacons in the management console:

  • Internal beacons. You can configure one internal beacon and zero to many external beacons. The default setting for the internal beacon is to use the App Controller FQDN. If you keep the default setting for the internal beacon, App Controller disables the text box. To use your own beacon, you clear the default setting and then enter the URL in the text box. The internal beacon accepts a valid URL format only. You can use one URL and it allows a maximum of 256 characters.
  • External beacons. The default setting for external beacons in App Controller uses the web address you configure on the Deployment tab. To use your own beacon, you clear the default setting and enter the URL in the text box. The external beacon accepts comma-separated URLs without spaces after the comma. For example, you can enter https://ng1.com,https://ng2.com,https://ng3.com. The maximum length allowed is 1,024 characters
  • Store name. When you enter the store name, you can use alphanumeric, spaces, hyphens, and underscores. App Controller removes leading spaces.

To create beacons in App Controller

You only need to configure an internal beacon in App Controller and can use the default beacon. You can configure multiple external beacons. You can create one store in App Controller.

  1. In the App Controller management console, click the Settings tab.
  2. In the navigation pane, under System Configuration, click Beacons.
  3. In the details pane, next to Beacons, click Edit.
  4. In Store name, type a name for the store. This name appears in Receiver when users log on.
  5. In Default store view, select how the store appears in Receiver: alphabetically or as a category.
  6. In Internal beacons do one of the following:
    1. Leave the default setting enabled.
    2. Disable Use internal and then in Internal beacon enter the FQDN of App Controller.
      Note: The check box Internal beacon becomes active when you disable Internal beacons.
    3. Select Check internal beacon first for Citrix Receiver and Worx Home to have App Controller use the internal beacon when users log on.
      Note: This check box becomes active when you disable Use internal and enter an FQDN in Internal beacon.
  7. In External beacons, do one of the following;
    1. Leave the default setting Use NetScaler Gateway. When you leave the default setting, App Controller uses the NetScaler Gateway settings on the Deployment tab on the Settings page.
    2. In External beacons, enter the URL of each NetScaler Gateway or virtual server to which users log on. Separate each URL with a semi-colon (;).
  8. Click Save.