Anyone else having AWCM issues in CN135 (v1904)?
- Ethernet & Wi-Fi are not staying connected.
- Cellular is not impacted at the moment.
- Testing has been isolated to Android devices.
VMware support has confirmed the issue after enrolling one of their devices into our instance of CN135 - the analysis is ' ...it looks the timeout value for AWCM is changed as a result of which we see AWCM disconnected message.' However, there was no indication that the value would be changed, so I've requested it be set to the value prior, assuming this it truly root cause.
I'm trying to confirm ARM works for our Scanning devices and ARM times out when connecting to the device and I'm pretty certain it's due to the AWCM issue. I can remote into devices that are on Cellular, our Scanners are Wi-Fi only... As I wait to see if this will be addressed I thought I'd post this to see if others are experiencing the same issue. If yes, please ' like' and contact your VMware rep/support agent to get it fixed. I assume this is across all customer instances of CN135 for those using AWCM.
Thank you.
