That usually means taking more than just one step.Following are some ideas from less restrictive to more intrusive.The easiest method for restricting unwanted installations is to disclose your organization’s policy to end users that states “Do not install major macOS upgrades unless authorized by the Information Technology Department”. This can result in lengthy support calls when something goes wrong.What steps can we take to prevent our end users from installing a new major macOS version? Keep in mind, end users can acquire the installer and run the installer in multiple ways. Instead, users simply connect to their iPad the same way they would.Not every administrator is ready to support macOS Big Sur, but sometimes our end users get ahead of us and install it themselves. Identifying Macs eligible to erase and install or upgradeSidecar doesnt require a dedicated app that has to load on either the Mac or the iPad. App Store App of the Year 2016.Adding the Delete Application option will delete it immediately, bypassing the Trash.When restricting by application name, be aware the end user can simply rename the installer and bypass the restriction.4. Instead of allowing the end user to continue, Jamf Pro will quit the installer before it can continue. Restrict using the application name and kill the process.This is similar to the first method, but it includes the Kill Process option. In the Execute Command field enter:3. Depending on your organization, this may be enough.To avoid end users receiving notifications that the macOS Big Sur installer is available, administrators can use the -ignore option built into the softwareupate command line tool.Create a new Jamf Pro policy and add the Files & Processes payload toward the bottom.Be sure each Mac has a unique password that won’t unlock any other computer.Administrators need to balance limiting access to the Big Sur installer with needing to install it themselves. Since this is at the hardware level, no one without the password can install or upgrade.The caveat with setting a firmware password is that someone in Desktop Support helping a remote user may have to provide this password to the end user. The most basic step we can take is to remove admin privileges for end users and require they use Self Service for running policies you allow.Removing admin privileges, though, makes your end users heavily rely on IT administration.Setting a firmware password prevents anyone without the password from booting to the Recovery HD, erasing the existing operating system and installing a new macOS. It will prevent any macOS installer from running when double-clicked including Catalina, Mojave, High Sierra, etc.Anyone with admin privileges on a Mac can do practically anything, including installing an operating system.
Must Osx Ap017 Download The RestWhen double-clicked or run using the startosinstall command line tool (discussed a little later), the Mac must be connected to the internet and it will download the rest of the files it needs to complete. It’s not a full installer but rather the same app without the 12 GB SharedSupport.dmg in the app bundle. This will download what some folks describe as a “stub” installer. That means we don’t need to upload an unwieldy package to our distribution points or manage new versions as they’re released.While this works well, it does have one caveat. Maybe, this will reliably work in the future.The Install macOS Big Sur application is available in Apps and Books when viewing either Apple Business Manager or Apple School Manager and is deployable like other Mac App Store apps. Deploying the installerBefore we can deploy the macOS installer, we need to acquire it.In the past, we’ve discussed Apple’s -fetch-full-installer option in the softwareupdate command.Still, it seems completely broken on the latest versions of macOS Catalina and Big Sur.![]() ![]() Be sure to get the current version of the installer app by selecting it and choosing File > Get Info.Now that we’ve identified Macs ready for macOS Big Sur, let’s end with methods for running the installer. 35.5GB of available storage for macOS Sierra 10.12 or later (I like to multiply that by about 1.5x to 2x for breathing room)MacOS Big Sur Compatible (Macs Smart Computer Group)Let’s create a new Smart Computer Group to identify eligible Macs and name it “macOS Big Sur Compatible Macs” and add the following criteria: Operating System Version greater than or equal 10.9And Boot Drive Available MB more than 53760After saving, be sure to click the View button to verify the group is working as expected.Install macOS Big Sur App Cached (Macs Smart Computer Group)While we’re at it, create a second Smart Computer Group named “Install macOS Big Sur App Cached” and add the following criteria: Application Title is Install macOS Big Sur.appThis will help us identify Macs that have the Big Sur installer app already downloaded to prevent Jamf Pro from downloading it again. Identifying Macs eligible to erase and installBefore running the installer to erase and install our Macs or even upgrade them, we need to first identify which ones meet Apple’s system requirements. So, let’s next examine macOS Big Sur’s installation requirements. Upload the package to your Jamf Pro distribution point and when deploying, it’ll place the Install macOS Big Sur application into the Applications folder.When we’re ready to deploy the installer using any of these methods, we need to make sure it’ll do so successfully. Mac bad lag for gamesIt also has the advantage of working even if we’ve used Software Restrictions to block the InstallAssistant process and we can invoke it as part of a script or a Jamf Pro policy (optionally, using Self Service).To find the command line tool, right-click or Control-click the Install macOS Big Sur application and choose Show Package Contents > Contents > Resources. It does the same thing as double-clicking the installer application without showing any of the dialogs and windows.
0 Comments
Leave a Reply. |
AuthorBrittany ArchivesCategories |