It’s been a while since my last post. That’s because I joined dataJAR as a Systems Engineer in October after 15 years of working at the University of East London. It’s been a huge change and I’m loving every minute. I’m learning a huge amount from a fantastic team of wonderful people as I settle into the new role.
So, we’re approaching a milestone in computing history. All good things must come to an end and love it or hate it, Adobe’s Flash Player is no exception. As we enter a new decade, we say goodbye to this venerable piece of the interwebs, as it goes End of Life later this year.
As an admin, the announcement of Flash Player’s demise a mixed bag. Pleasure/pain, perhaps. Pleasure, in that you won’t have to manage the deployment of updates for one of the most frequently updated software titles ever (weren’t you using Autopkg so you didn’t have to anyway?). Then, as the serotonin wears off, the pain sets in. Because the slow realisation dawns on you; how are you going to automate the removal of this on all the computers you manage? Since it won’t get any more updates, that means any as-yet-undiscovered security vulnerabilities will remain unpatched. So it has to go. And there are a few ways to do the deed…
A major pain point of Adobe’s new Shared Device Licensing (SDL) is was a dialog that would appear 90 minutes following sign-in to a Creative Cloud application. This dialog would prompt the user to confirm that they were still themselves, offering the option to sign-out or continue.
It would also interrupt background processing and rendering in applications like After Effects and Premiere Pro. This impacts people in environments where they would quite reasonably leave a video render churning away overnight, for example. I support shared-use video edit suites where students do this.
Even better, is this appears to apply to installations that pre-date the announcement. I tested it specifically with Premiere Pro 13.1.4 and Photoshop 20.0.4 and an SDL “license only” package I created in July. For those playing at home, the Creative Cloud Desktop App (CCDA) was the current version 220.127.116.114, having auto-updated itself. I left the applications open for over 90 minutes. The dialog did not appear during app usage or if I closed and re-opened an app. It didn’t come back when opened a different Creative Cloud app either.
Here’s a script that might help. Feed it a text file containing the serial numbers of all the 2015 MacBook Pros in your fleet and remediate the ones that are “eligible”. Data is output in CSV format, which you could redirect to a file.
How to use it (once you’ve downloaded and made it executable):
That file ^^. If you’ve ever deployed the Adobe Creative Cloud Desktop App (CCDA) or any Adobe application that uses it, you might have come across this little nugget. On macOS it lives in /Library/Application Support/Adobe/OOBE/Configs/ and on Windows it’s in C:\Program Files (x86)\Common Files\Adobe\OOBE\Configs\. This is especially interesting if you wanted to have a bit more control over what’s shown or hidden post-deployment (because sometimes we change our minds).
There’s a new craze sweeping the community. “Dad jokes”. The special kind of joke that makes you roll your eyes and cringe because it’s so bad, yet at the same time you feel a great wave of embarrassment because you find it funny.
So why am I blogging about this? I have kids, so any new way to annoy them will naturally peak my interest. But what have dad jokes got to do with systems administration? Let’s see…
I was lucky enough to share the stage with Joel Rennich at this year’s Apple Admin and Developer Conference UK. We spoke about how to achieve more automation and improve the ways we get Macs enrolled into our MDM solutions. The icing on the cake was a deep dive into some new functionality baked into NoMAD Login AD with the release of version 1.3.0.
Check out the video:
All my slides, documentation, example scripts and other bits and bobs are all available here: