Most Endpoint Management administrators know about the Android scheduling policy. This policy is configured to define when MDM managed Android devices check-in. Unfortunately, this policy often is configured before administrators are seasoned with the technology. An inappropriate configuration can lead to poor battery performance on enrolled Android devices. This is either due to scheduling policies configured to have devices constantly connected, or to have devices connecting too often.
As of Android 6.0, some of our customers that are using these types of scheduling policies are seeing inconsistent connectivity from the devices. The Android OS now is preventing applications from running too frequently when the device is in Doze mode.
Implementing Google’s Firebase Cloud Messaging service is an ideal solution for enrolled Android devices. It mitigates these issues. With this service, you can set a less aggressive scheduling policy or remove the scheduling policy all together.
How does the Firebase Cloud Messaging Service work with Citrix Endpoint Management?
Once implemented and your device checks in, the device will register itself with the Firebase Cloud Messaging service in Citrix Endpoint Management. This will enable near real-time communication from your Endpoint Management service to your device via FCM. When the Endpoint Management needs to initiate a connection to the device, it will connect to the FCM service and the FCM service will notify the device to connect. This type of connection is similar to what Apple uses for its Push Notification Service and it is the reason that there is not a need for scheduling policies for iOS, MacOS and AppleTV devices.
The process to enable this in your Endpoint Management Server is simple.
Browse to https://console.firebase.google.com and sign in with your Google credentials.
Next, create a project by clicking on “Add project.”
After the project has been created, click on “Project settings.”
Click on the “Cloud Messaging” tab.
Copy the “Server key” and “Sender ID.”
Log in to your Endpoint Management Service and go to the “Google Cloud Messaging” section under the Server column in Settings.
Enter your server key from the Firebase console into the “API Key” field. Do the same with the Sender ID in the “Sender ID” field.
After you have completed the process, you can remove or change your current schedule to connect less often. Now, you can enroll new devices; you will be able to push to them or send commands — selective wipes on command, for example — to Secure Hub. Firebase Cloud Messaging service will be able to communicate with enrolled devices as soon as they have been checked back in.