MDM Push Notification Migration: From Legacy FCM API to HTTP v1 API

What's Changing?

Google is updating its push notification services framework. Push notification services are used by MDM to remotely manage devices, send policies, and trigger over-the-air actions.

The deprecation of the legacy Firebase Cloud Messaging (FCM) API is effective from October 31, 2024. It is mandatory to upgrade your servers in order to comply with this change.

Who is Impacted?

1. If you are managing Android or iOS devices using one of the following products:

  • Mobile Device Manager Plus (On-Premises version)
  • Mobile Device Manager Plus MSP (On-Premises version)
  • Endpoint Central (On-Premises version)
  • Endpoint Central MSP (On-Premises version)

2. If you are using the mobile admin app for one of the following products:

  • Endpoint Central (On-Premises version)
  • Endpoint Central MSP (On-Premises version)
  • Patch Manager Plus
  • Remote Access Plus

Note: If you are using the cloud version of the above products, the migration or update will be automatically handled, so no manual upgrade is required.

Upgrading from the legacy Firebase Cloud Messaging (FCM) API to the HTTP v1 API is essential for increased security and improved reliability, ensuring uninterrupted device communication and performance.

Functionality Impact

Make sure you're aware of these disruptions due to the deprecation if you have not upgraded:

Functionality Impact
Android device over-the-air management Android devices will no longer receive over-the-air commands to push profile or policy changes, update inventory information, or complete enrollment.
Announcements feature for iOS devices iOS devices will not receive announcements sent from MDM.
Receive notifications on the mobile admin app Mobile admin apps will not receive push notifications for any configured alerts.

What Should You Do?

If your current build falls within the version ranges shown in the table, please use the respective upgrade links provided to update to the latest available build. Make sure to complete the upgrade before October 31, 2024.

Upgrade Details

 

Product Current Version Range Upgrade to the Build
Mobile Device Manager Plus (On-Premises version) 10.1.2006.1 to 10.1.2312.1 Upgrade to 11.1.2400.8, then upgrade to 11.1.2406.11
Mobile Device Manager Plus (On-Premises version) 11.1.2400.1 to 11.1.2403.2 Upgrade to 11.1.2406.11
Mobile Device Manager Plus MSP (On-Premises version) 10.1.2006.1 to 10.1.2312.1 Upgrade to 11.1.2400.8, then upgrade to 11.1.2406.11
Mobile Device Manager Plus MSP (On-Premises version) 11.1.2400.1 to 11.1.2403.2 Upgrade to 11.1.2406.11
Endpoint Central 11.3.2401.1 to 11.3.2414.1 Upgrade to 11.3.2416.29 or above
Endpoint Central Versions between 10.1.2121.1 and 11.3.2400.35 Upgrade to 11.3.2400.36
Endpoint Central MSP (On-Premises version) 11.3.2401.1 to 11.3.2414.1 Upgrade to 11.3.2416.29 or above
Endpoint Central MSP (On-Premises version) Versions between 10.1.2121.1 and 11.3.2400.35 Upgrade to 11.3.2400.36
Patch Manager (On-Premises version) 11.3.2401.1 to 11.3.2414.1 Upgrade to 11.3.2416.29 or above
Patch Manager (On-Premises version) Versions between 10.1.2121.1 and 11.3.2400.35 Upgrade to 11.3.2400.36
Remote Access Plus (On-Premises version) 11.3.2401.1 to 11.3.2414.1 Upgrade to 11.3.2416.29
Remote Access Plus (On-Premises version) Versions between 10.1.2121.1 and 11.3.2400.35 Upgrade to 11.3.2400.36

Note: To upgrade, customers must refer to the detailed steps on the Hotfixes and ServicePacks page of the respective product. Customers using Endpoint Central (On-Premises version), Endpoint Central MSP (On-Premises version), Patch Manager (On-Premises version), or Remote Access Plus (On-Premises version) must upgrade to either version 11.3.2416.29 or 11.3.2400.36 depending on the current version as specified in the table above.

Note: It is essential to upgrade to the latest build of MDM and MDM MSP products during your upgrade process.

For more detailed information on the FCM legacy API deprecation, please refer here .

If you require further assistance, please contact the support team of the respective product line.