AWCM (when set to use port 443) usually doesn't need any firewall exceptions, which does provide some level of comfort when trying to diagnose issues. However, on Android you need to fine tune your device profile settings to achieve equilibrium.
FCM on the othe hand has exclusive low level access to the chipset on Android Systems and has an unrivalled ability to wake up a device in sleep mode. I've done some field tests and GCM/FCM is amazingly reliable at waking up devices. The downside to FCM is that you need to have enabled ports 443, 5228-5230 going outbound to the FCM servers,.
Here are some more tips or considerations:
- if you use the AW Lockdown Launcher then make sure you refine your Hidden App whitelist so that all background tasks that need to run can run.
- Turn all Power saving features off. This includes Wifi setting, Battery Saving, Smart Manager. Power saving features has been known to cause a false AWCM online.
Thank you Dany. Can you confirm that you had the exact same issue as ours ? => awcm works fine with everything internal (internal apps and messages) but not with google play apps.
We are Saas customers so we could ask our support to have a look. Thank
After months of troubleshooting I’ve come to the conclusion it’s FW SSL packet inspection service that decrypts the SSL communication to inspect then encrypt. At this point is when Communication failure happens. I was able to confirm this by putting device on our public guest WIFI that doesn’t SSL packet inspect traffic.
Next step for me will be to get FW engineer for exclude all android and AirWatch traffic from SSL packet inspection. Which was done at one point then after Google updated their push services to FCM and use of ports 5228-5230
Found good network port requirement article for ports needed to allow Android management on corporate network.
Can you elaborate more on what was reloaded on the AWCM server to fix DLL issue? What version of console?
We are using 1811 on-premise.