Update to Android Configuration Page Changes GCM API Key
Last Updated August 21, 2013
Upon update of a value on the "Settings" --> "Android Configuration" page in the console for Symantec Mobile Security 7.2, GCM push notifications to devices stop working. When you right-click and execute a device action, GCM will not initiate the device check-in.
In the Altiris Log Viewer, you may see the following error message displayed for each attempt to issue a right-click device action requiring GCM:
GCM notification to device <device ID> is failed due to System.Net.WebException: The remote server returned an error: (401) Unauthorized.
at System.Net.WebClient.UploadValues(Uri address, String method, NameValueCollection data)
at Symantec.Handheld.Android.GoogleService.GoogleServiceFacade.PushNotification(Object state)
The update and save of any value on the Android Configuration page causes the GCM API key to be lost.
This issue has been fixed with Symantec Mobile Security 7.2 MR1 hot fix 3. Once this hotfix is applied to the SMP, the GCM API key is maintained when other settings on the page are modified and saved. GCM continues working.
Should it not be possible to immediately upgrade to hot fix 3, there is a known workaround. Please include the correct GCM API Key in the API Key field when an update or change is required on the "Settings" --> "Android Configuration" page.
Symantec Mobile Security 7.2 MR1 (SMS 7.2 MR1) releases prior to hot fix 3
Symantec Management Platform (SMP)
Android mobile devices
Imported Document ID: TECH208785
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe