![]() ![]() You can download that script from our GitHub repository. Our solution: We built a script-based on work we’ve done to make our Auto Apps-that creates a Universal macOS installer PKG. But delivering the correct versions is still a sticky problem. If you use a device management solution for Mac such as Kandji, the delivery part isn’t that hard. Some vendors let you download Universal installers, which check your system and install only the version of the app that’s correct for your particular Mac’s architecture.īut what if the app you want to install doesn’t have a Universal version or installer and, instead, has separate downloads for the two Mac architectures? And what if, as an admin, you want to deliver architecture-appropriate software to the /Applications folder of multiple Mac computers you manage, without packaging up two different apps and handling the complex scoping of how they'll be delivered? If it’s a Universal app, you just fetch the one download. If you download an app from the internet as an end-user, it’ll commonly be either a DMG or a ZIP file containing an app bundle that you then move into the /Applications folder. Here’s how to build such an installer yourself. This can mean twice as much work for you.Īnother strategy is to build a Universal installer of your own, in the form of a PKG that has the intelligence to detect what kind of computer it’s installing on and then deliver the right version. This requires you to maintain logic in your software distribution solution to ensure the right package (PKG) goes to the right Mac. One common strategy is to maintain two separate installers. So how do you efficiently deploy apps that don’t yet have Universal versions to the Mac computers you manage? (Universal apps take more time and bandwidth to build and deliver they are necessarily larger than single-architecture binaries.) Apple has been urging developers to convert their apps to Universal, but for a number of reasons, many vendors still haven’t heeded that advice. Sometimes app developers make that easier by distributing Universal apps-combined binaries that will run on either architecture. The continued coexistence of those two architectures means admins must often manage and deploy two different versions of any given app. The job of installing apps on your organization’s Mac computers-one of the most fundamental responsibilities for any Apple admin-is complicated by the fact that there are still two different Mac processor types in use: Intel and Apple silicon. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |