We use AirWatch as our Mobile Device Management platform, & recently we launched the “Self Service Portal” to our user base.
This also coincided with restructuring our AirWatch SaaS instance, after which we noticed that devices could only be seen that we enrolled into the new organisation group. But we only had 20 devices in this new structure, with 500 enrolled on the old. So those that were on the old structure would see the below when logging into the “Self Service Portal.”
After a couple of weeks of troubleshooting, which verified that we had all setup correctly, AirWatch support pointed us to a simple solution.
Earlier today we started to tighten up one of our wireless networks, moving from PEAP to EAP-TLS authentication. In testing on 10.9.x & win7 clients, all worked well. But when deploying the same config profile that connected the 10.9.x clients to a 10.8.x Mac, the device failed to authenticate.
The 10.8.x clients console log didn’t show much information, so I took a look on the NPS servers logs (which are not a pretty sight) & after a time we came to a solution.
We updated our JSS from 8.73 – 9.22 back in January, we thought all was well until we needed to deploy some large packages.
This lead to our network guys not being to happy as Mac clients were downloading a 200MB installer across our MPLS irregardless of the distribution points assigned in our network segments.
After a few calls with JAMF support we discovered that the issue was due to the v8-v9 upgrade not updating a MySQL table, below is the how to check if your affected & what to do to fix.
UPDATE: My fork of ADPassMon has now been merged with main & many changes have been made, for more information follow this link.
Over the past few Mac OS revisions, you’ve been able to alert users to impending password expiry. Shown below is this on 10.8:
We’ve been supporting iDevice clients for a few years now, but recently ran into an issue that even a Cisco TAC call & the ever helpful resources of JAMFNation & MacEnterprise we not able to resolve.
Our users authenticate to the wireless using their AD credentials, after a password change they should be prompted to enter their new password. Once done they should reconnect to the wireless.
Oddly, after a password change the iDevices started to be offered a blank cert such as that below:
Several months after going launching our BYOD scheme, we started getting reports from people that their iOS devices would fail to connect to our Exchange servers for company email.
They would fail with an error like that shown below;
UPDATE: We've since updated to JSS 9.3 & we no longer have this issue.
We recently updated our JSS from 8.73 > 9.22 & on the whole it’s been a non-event.
However, we started to find that some Self Service policies were erroring with the below message post the upgrade.
Shortly after we resolved the an issue where the SharePoint Newsfeed iOS App was crashing, we found an issue where some people’s NewsFeed apps were getting the error “We couldn’t get new data right now, try again later.”
There are actually 2 solutions to this error, the 2nd is below & more than a little bit of hair pulling was involved!
We recently went live with a SharePoint 2013 project, the projects launch included the SharePoint NewsFeed iOS App too.
However, before go live we noticed an issue where under some circumstances the SharePoint Newsfeed iOS App (1.0-1.2) would crash when trying to sign in.
We had an issue where our Macs stopped NetBooting, they would attempt to NetBoot but forever stay at the spinning gear.
On Verbose booting the Macs we saw multiple errors like the below;