Here’s the solution to a problem that clients have run into on occasion. In a workgroup that relies on Adobe Creative Cloud apps, one person might upgrade to the latest versions of Photoshop, InDesign, and Illustrator, whereas others don’t. Suddenly, if that person opens and re-saves a file in the new version, those using the old version may not be able to open it, or certain aspects of the file may disappear.

Upgrading isn’t always possible—some people may have too-old Macs or not be running a new enough version of macOS. More commonly, however, the rest of the group is deep in a major project and quite reasonably doesn’t want to introduce potential problems by changing their software in mid-stream. What to do?
Luckily, Adobe makes it easy to download previous versions of all the Creative Cloud apps, allowing the person who upgraded to rejoin the rest of the team on the older version.
Open the Creative Cloud app, click the ••• button to the right of the desired app, and choose Other Versions from the pop-up menu.

In the list that appears, find the older version you want to install—likely the version that the rest of the team is using—and click Install. Creative Cloud warns you that the app will have its auto-update setting disabled so the newly installed old version won’t be overwritten during a future update.

You can ensure that you don’t lose access to older versions during updates by disabling a Creative Cloud setting that automatically removes previous versions of apps when you update. In the Creative Cloud app, choose Creative Cloud > Preferences > Apps. Then click Advanced Options to the right of the desired app’s name, and in the dialog that appears, deselect Remove Older Versions. When you’re finished, click Done.

That’s it—a potentially project-stopping problem eliminated quickly and easily. Just don’t let your Creative Cloud apps get too far out of date, since you can go back only so far when downloading previous versions.
AI Usage Transparency Report
Pre-AI Era · Written before widespread use of generative AI tools
AI Signal Composition
Score: 0.04 · Low AI Influence
Summary
A solution to a common problem in Adobe Creative Cloud workgroups, where one person's upgrade can cause issues for others. The solution involves downloading previous versions of the apps and disabling auto-update settings.
Related Posts
Setting up Ollama on macOS
Recently, after some bad experiences with OpenAI's ChatGPT and CODEX, I decided to look into and learn more about running local AI models. On its face it was intimidating, but I had seen a lot of people in the MacAdmins community posting examples of macOS setups, which really helped lower the bar for me both in terms of approachability and just making me more aware of the local AI community that exists out there today.
AI Agent Constraints and Security
I really feel like in this era of AI it's essential to write about and share experiences for others who are leveraging AI, especially now that AI usage seems almost ubiquitous. Specifically, when it comes to AI in development and the rapid growth of AI-driven automations in the IT landscape, I believe there's a need for open discussion and exploration.
ABM Warranty 0.4.1
The 0.4.x release series for ABM Warranty is focused on operational scale. The earlier 0.3 releases were about trust, correctness, and stabilizing the foundation. Version 0.4.1 builds directly on that work by making the app more practical for consultants, internal IT teams, and managed service providers who need to support multiple environments without losing isolation, control, or visibility. This includes improvements to user interface and workflow, as well as enhanced reporting capabilities to help these users manage their workflows more efficiently.
Vibe Coding with Codex: From Fun to Frustration
So there I was, a typically day, a typical weekend. As a ChatGPT customer, I had heard good things about Codex and had not yet tried the platform. To date my experience with agentic coding was simply snippit based support with ChatGPT and Gemeni where I would ask questions, get explanations and support with squashing bugs in a few apps that I work on, for fun, on the side. There were a few core features in one of the apps I built that I wanted to try implementing but the...
The warranty dashboard Apple doesn’t provide… yet
Download ABM Warranty
Why Apple Fleet Risk Isn’t a Security Problem—Until It Is
Security and risk are often treated as interchangeable concepts in modern IT environments, but they are not the same discipline. Security focuses on controls, enforcement, and prevention. Risk management, by contrast, is concerned with likelihood, impact, and consequence across operational, financial, and organizational domains. Frameworks such as those published by NIST make this distinction explicit: risk assessment is not a technical exercise, but a business one. Technology informs risk decisions, but it does not define them.
ABM Warranty 0.3.1
The 0.3.x release series for ABM Warranty is about tightening guarantees. Where earlier releases focused on surfacing data and making long-running operations observable, 0.3.x focuses on ensuring that what you see is complete, consistent, and safe to trust—particularly as the app is used in larger, slower, and more varied environments. This shift in focus aims to provide a more reliable foundation for users who require higher levels of assurance from their warranty management system.
ABM Warranty 0.2.0
ABM Warranty 0.2.0 is a feature release focused on visibility, safety, and scale. This version does not change what ABM Warranty is meant to be, but it significantly improves how the app behaves under real-world conditions—large device counts, API throttling, long-running imports, and the kinds of failure modes Apple IT admins actually encounter. The improvements in this release are designed to make the app more reliable and efficient, allowing it to handle complex scenarios without breaking or becoming unresponsive.
Running a Beta Program: Lessons Learned
Shipping software in isolation is comforting. You control the inputs, the environment, and the narrative you tell yourself about how things work. The moment you invite other people in—especially people who don’t share your assumptions—you lose that comfort. You also gain something far more valuable. Running a public beta for ABM Warranty through Apple’s TestFlight program forced me to confront that tradeoff head-on, and it fundamentally changed how quickly and confidently the app matured.
The Day I Unmanaged a Mac Into a Corner
There are a few kinds of mistakes you make as a Mac admin. There are the ones that cost you time, the ones that cost you sleep, and then there are the ones that leave you staring at a perfectly good laptop thinking, “How did I possibly make this *less* manageable by touching it?” These mistakes often stem from a lack of understanding or experience with macOS, but they can also be the result of rushing through tasks or not taking the time to properly plan and test.