Alternative to the Active poll period policy, you can use Firebase Cloud Messaging (FCM) to control how and when Android devices connect to XenMobile. By using the following configuration, any security action or deploy command triggers a push notification to prompt the user to reconnect to the XenMobile Server.
This diagram shows the communication flow for FCM in the external and internal network.
1. Sign in to the following URL using your Google developer account credentials:
2. Click Create a project.
3. Type a Project name and then click Create Project.
4. Click the gear icon next to your project name in the top left and click Project Settings.
5. Select the Cloud Messaging tab. You can find your sender ID and Server Key on this page. Copy these values because you must provide them in XenMobile Server. It is important to note that any Server Keys created after September 2016 must be created in the Firebase console.
1. Sign in to XenMobile console and then click Settings > Server Properties. In the search bar, type GCM and click search.
a. Edit GCM API key, and type the Firebase Cloud Messaging API key that you copied in the last step of Firebase Cloud Messaging configuration.
b. Edit GCM Sender ID, and type the Sender ID value you noted in the previous procedure.
As a prerequisite to test your FCM configuration, do not have a Scheduling policy configured. Alternatively, do not set the policy to Always Connect. For more information about configuring the Scheduling policy, see Scheduling device policy.
1. Enroll an Android device.
2. Leave the device idle for some time, so that it disconnects from XenMobile Server.
3. Sign in to the XenMobile console, click Manage, select the Android device, and then click Secure.
4. Under Device Actions, click Selective Wipe.
In a successful configuration, selective wipe occurs on the device.