A issue was opened recently for AutoCasperNBI, where 10.11.2 NBI’s generated for not accessible over ARD or VNC.
Some digging revealed this this only affected NBI’s with the “Reduce Image Size” option selected.
NBI’s for 10.7.x – 10.11.1 work fine over ARD or VNC with that option selected, so some investigation was needed. Below is the investigative work, but you can also skip straight to the resolution.
AirWatch only keeps a record of the devices currently enrolled user, if the device is re-enrolled by/for someone else the details are overwritten.
Worse is that if your devices are not supervised, it’s trivial to unenroll a device. This then leaves a device record on AirWatch but with no user information.
To counter this, I’ve written the below API script that will add the enrolment users information to the devices notes. A new note is created with each scripts run, meaning that if a device is enrolled by another user, we’ll have a record & these notes are not deleted when a device is unenrolled.
This is detailed below.
We’ve started to look at enabling “Compliance Policies” within AirWatch.
However, these are scoped to “Assignment Groups” (was “Smart Groups”, another thing that seems to be mid-rename) & “Assignment Groups” do not have criteria for a devices “Enrolment Status”.
Below is an API script that I am using to automate device deletion if a device meets certain conditions & the method to the madness.
As mentioned in my previous post, I have been doing some work with AirWatch’s REST API & at the same time I have been learning Python.
This post is to show how you can access AirWatch’s REST API with Python to return devices information, as well as serve as a template for the scripts I use to access AirWatch’s REST API.
I’ve recently been doing some work with AirWatch’s REST API.
One call required me to pass the LocationGroupId for an Organization Group, this is not readily available & the below are some methods that can be used to get the LocationGroupId for an Organization Group.
Continue reading
Soon Microsoft are to release an update to the Office 2016 Volume License installer on VLSC.
This update is 15.17 & is the first that has a few changes that may affect the way you deploy Office 2016.
These changes are going to be later enforced in 15.20 & onwards. Below are some details on the changes, some of the why & how via the power of the MacAdmins.org Slack & the awesome @pbowden that some of us have had a sneak peek.
Continue reading
I’ve blogged a few times about how to not only create, but also deploy & update “Safari Extensions”.
With the release of Safari 9 Apple have stopped all automated deployment methods, & I’m partly to blame.
Continue reading
If you manually download a Configuration Profile from the JSS, you’ll see that the profile largely reads as gobbledegook.
Luckily a couple of bash commands later & you’ll have a readable profile.
Way back in Jan 2014 grabbed a test iPhone & after charging I was greeted with the above.
After various exclamations along the lines of “Holy fishsticks, Batman!” we did get the iPhone enabled & this did not involve a time machine or me waiting the 23,053,554 minutes for the device.
Below is how & some guess work as to what happened.
Continue reading
Early today people launching some Mac App Store purchased apps where greeted with errors upon launching them.
This has been pretty widely reported, & after reading a few other articles I started to panic. After which I wanted to try see how this would affect us Mac admins & if I could help detect affected apps.
Continue reading