- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I think the Agent 5.7 has problems with the iOS11.2 and below. Once 11.4.x is installed it seems to work fine.
Anyone noticed the same ??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've seen the same thing. Just couldn't tell which Agent version is causing the problem, since I'm automatically pushing the updates. Then console then only shows that the new version is being pushed, but doesn't show the version of the agent.
I'm update the devices (iOS12) now, and the check back in.
Sometimes it helps to reinstall the agent on the device or just start the Agent.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good luck!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I just had 47% of my iOS devices get triggered as non-compliant by a 'not seen in 15 days' compliance policy. And that makes them all get kicked off the network. Joy. So, is this because of the ' Hub' app update? Had the APNS for Apps script run yesterday. Had many server vulnerabilities mitigated yesterday where there were no issues found in Test environment when I did this. Patched server OS too.
So for the moment I've had to turn off the compliance policy.
Update: my own device got the Hub (Agent) app update last night and I verified that it was connected. I've been using my device since 3:30AM PST, and yet AirWatch says my device hasn't been seen for 13 hours. Just checked, Hub app is literally open on my device right now.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Going to restart the device scheduler in the next maintenance window, as Gerald mentioned.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The only issue I see with this design is the device needs to check in with AirWatch to receive the policy. So, until that happens the ones that are not checking in will not know to receive the reminder to check in. Kind of a chicken-egg situation.
See this document for more details, specifically the information in the third paragraph: https://support.workspaceone.com/solutions/SOL-1472
I will be implementing the Compliance Policy soon!
Sean
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks in advance for your help,
Sean
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
From the MDM Protocol Reference: ' When the MDM payload is installed, the device initiates communication with the check-in server. The device
validates the TLS certificate of the server, then uses the identity specified in its MDM payload as the client
authentication certificate for the connection.'
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Update on my issue:
Wasn't hub. Wasn't AirWatch. Wasn't Apple. Wasn't the devices. Was us!
Turned out, we'd disabled some encryption protocols that didn't meet NIST recommendation on our on-prem servers. That is what totally broke APNS for us. The cipher suites that Apple supports and the version of Windows server we're running supports that are both NIST recommended didn't jive. Once we figured that out, which was difficult since no logs were ever really indicative of that being a problem (kind of... from our end, APNS request sent... silence and darkness from Apple.), we restored the protocols and everything started working again.
Apple supports:
TLS_RSA_WITH_3DES_EDE_CBC_SHA (rsa 2048) - C
TLS_RSA_WITH_AES_128_CBC_SHA (rsa 2048) - A
TLS_RSA_WITH_AES_256_CBC_SHA (rsa 2048) - A
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (ecdh_x25519) - A
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (ecdh_x25519) - A
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (ecdh_x25519) - A
Hope this helps someone!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
On prem. installation.
4000 iOS devices not checking in in the past 15 days.
Restarting the AirWatch Device Scheduler service helped immediately
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, somone have the same problem with ' Last seen' in version 1903?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, we are struggling with this issue in version 1903 (on premises).
I created a ticket and VMware support told me that is normal and end user need to open intelligent hub... No comment. They should be ashamed.
At this moment we restarted ' Airwatch device scheduler' services and looks that devices are slowly communicating with the console. I will update my post soon.