Previously, I have mentioned that Adobe are moving away from Device Pool & Serial Number licensing.
However, at the time we had very little detail on what the new licensing would be.
Well, earlier today Adobe started to release some details. See below for more information & links to Adobes documentation on this new licensing.
When macOS Mojave’s Mac App Stores new look was unveiled during WWDC 2018 it was also announced that Microsoft would be bringing the Office suite to the Mac App Store.
Well, earlier this week the announcement was fulfilled.
See below for some information on how this might affect us admins as well as some things to consider.
For a while now, Adobe has had a documented method to manage some of the options with the Adobe Creative Cloud Desktop App.
At dataJAR, we have used this successfully for some time. I’ve just forgotten to post it here.
Until now! See below.
When looking into the issue in my last post, I found I could no longer access Airwatch’s online API documentation.
Heading to Ask Airwatch & looking for the API documentation revealed why.
With the 8.3 release, Airwatch have started a process of refactoring & remotion of the Uniform Resource Identifier (read: URI) used for API calls.
See below for more information on these changes.
On Friday, Apple released an update titled “Incompatible Kernel Extension Configuration Data: Version 3.28.1”
This update was an exclude list of bad Kernel Extension’s for 10.11 & included an Apple Kernel Extension.
Below is some more information on this & a possible way to detect affected Macs via the JSS.
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.
Sometimes being an Apple admin in an org with a largely Microsoft infrastructure can be a bit of a chore.
It’s not uncommon to hear of Windows admins dismissing issues as being an “Apple” issue without actually expending any effort to look into the issues at all.
However, I’ve been fortunate in that I’ve been able to bend the ear of several sympathetic Windows admins & this has lead to posts such as “How To: Check Your Active Directory Domains Time” & “OSX & AD Certificate Requests, some tips”.
This post is another of those ilk & one that came up quite recently in the MacAdmins.org Slack & I mentioned this in my JNUC 2015 talks Q&A too, thought it would be a good time to share.
If your environment is based around Active Directory, chances are you may leverage Active Directory Certificate Services (ADCS) as your internal public key infrastructure (PKI). The certificates from which may be used to authenticate clients to various services within your organisation.
As MacAdmins, we may need to configure our Macs to request certificates from our ADCS, below are some hopefully helpful tips that might make that easier.