XenMobile Server Current Release

Firebase Cloud Messaging


Firebase Cloud Messaging (FCM) was previously known as Google Cloud Messaging (GCM). Some XenMobile console labels and messages use the GCM terminology.

Citrix recommends that you use Firebase Cloud Messaging (FCM) to control how and when Android devices connect to XenMobile. XenMobile, when configured for FCM, sends connection notifications to Android devices that are enabled for FCM. Any security action or deploy command triggers a push notification to prompt the user to reconnect to the XenMobile Server.

After you complete the configuration steps in this article and a device checks in, the device registers with the FCM service in the XenMobile Server. That connection enables near real-time communication from your XenMobile Service to your device by using FCM. FCM registration works for new device enrollments and previously enrolled devices.

When XenMobile needs to start a connection to the device, it connects to the FCM service. Then, the FCM service notifies the device to connect. This type of connection is similar to what Apple uses for its Push Notification Service.


  • Latest Secure Hub client
  • Google developer account credentials
  • Google Play services installed on FCM-enabled Android devices

Firewall ports

  • Open port 443 on XenMobile to fcm.googleapis.com and Google.com.
  • Open outgoing Internet communication for device Wi-Fi on ports 5228, 5229, and 5230.
  • To allow outgoing connections, FCM recommends allowing ports 5228 through 5230 with no IP restrictions. However, if you require IP restrictions, FCM recommends allowing all the IP addresses in the IPv4 and IPv6 blocks. Those blocks are listed in the Google ASN of 15169. Update that list monthly. For more information about FCM ports, see the Google documentation on FCM ports.

For more information, see Port requirements.


This diagram shows the communication flow for FCM in the external and internal network.

The FCM architecture

To configure your Google account for FCM

  1. Sign in to the following URL using your Google developer account credentials:


  2. Click Add project.

    The Create a project option

  3. After you create the project, click Project settings.

    The Project settings option

  4. Click the Cloud Messaging tab.

  5. If the Cloud Messaging API (Legacy) is disabled, then the Server key is not be displayed.

    Cloud Messaging API (Legacy) disabled

    Enable the Cloud Messaging API (Legacy) as follows:

    1. Click the Ellipses button next to Cloud Messaging API (Legacy) and then click Manage API in Google Cloud Console.

      Manage API in Google Cloud Console

    2. Under CLoud Messaging, click the Enable button.

      Enable Cloud Messaging

  6. Copy the Server key and Sender ID values. In the next procedure, you paste those values in the XenMobile console. From October 2016, you must create Server Keys in the Firebase console.

    The Cloud Messaging tab

For steps to set up an FCM client app on Android, see this Google Developers Cloud Messaging article: https://firebase.google.com/docs/cloud-messaging/android/client.

To configure XenMobile for FCM

In the XenMobile console, go to Settings > Firebase Cloud Messaging.

  • Edit API key and type the Firebase Cloud Messaging Server key that you copied in the last step of the Firebase Cloud Messaging configuration.

  • Edit Sender ID, and type the Sender ID value you copied in the previous procedure.

The Sender ID value entry

After you complete the setup, you can remove your Scheduling device policy or change that policy to connect less often.

To test your configuration

  1. Enroll an Android device.

  2. Leave the device idle for some time, so that it disconnects from XenMobile.

  3. Sign in to the XenMobile console, click Manage, select the Android device, and then click Secure.

    The Secure Android device option

  4. Under Device Actions, click Selective Wipe.

    The Selective Wipe option

    In a successful configuration, selective wipe occurs on the device.

Firebase Cloud Messaging