Mac Rosetta Install

[Carlee Members]

timlarsen @sdagley @pchimombe Thanks for your responses and the information you provided. I spent a couple of hours re-reading forum posts before I saw your replies and ended up removing my prestage enrollment package and creating a first priority policy with script as per -nation/discussions/37357/deploy-rosetta-on-m1-machines-before-everything-else#responseChild210791. After stumbling with bad interpreter errors because I'm still learning how to create scripts, I was able to successfully enroll my M1 MacBook Air with all my configurations and policies.

Hi @bootrec based on your post, I think the problem is that all packages created with Composer (as of this writing and based on my experience - I'm not speaking for Jamf or quoting any official documentation) do not natively support ARM architecture without first having installed Rosetta, so it's a bit of a "catch 22". What I ended up doing was taking my pre-stage package (which includes the open source DEPNotify application as well as a script) and going through the following steps:

Your first run package should now run on both Intel and M1 Macs. Again, this worked for me, but others may experience difference results, or maybe I'm over complicating the whole thing so would love to hear better solutions if they exist!

@bootrec Another option that eliminates the need to create an enrollment package is to create a Script under Settings->Computer Management-Scripts with Priority:Before (in the Options tab) and the following Script Contents:

How does that "Distribution Point: None" work? I'm serious, what is that option even there for? I have a well-formed payload-free package with the script as post-install, on my AWS DP, and it won't run. Will it run if I put it on None?

hi @SCCM yes I already did this but my requirement is to have an Antivirus running as soon as the user lands on the desktop on enrolment so I install an antivirus during prestage enrolment, but using the policy as you mentionned installs Rosetta indeed on enrolment complete.

@jpoirson i had a similar requirement, i just changed the flow. Rather than selecting the Enrollement package (AV) to install in the prestage, i created a policy to install the AV on enrolment complete (which still runs before anyone longs in but after the rossetta one due to the name). Not sure if that would work in your environment.

Jamf's purpose is to simplify work by helping organizations manage and secure an Apple experience that end users love and organizations trust. Jamf is the only company in the world that provides a complete management and security solution for an Apple-first environment that is enterprise secure, consumer simple and protects personal privacy. Learn about Jamf.

This site contains User Content submitted by Jamf Nation community members. Jamf does not review User Content submitted by members or other third parties before it is posted. All content on Jamf Nation is for informational purposes only. Information and posts may be out of date when you view them. Jamf is not responsible for, nor assumes any liability for any User Content or other third-party content appearing on Jamf Nation.

How Can I Manually Install Rosetta 2 on my Late 2021 16" MacBook Pro M1 Max OS Ventura 13? Only answers I see is in regards to receiving a pop up window when trying to run Intel based app. I need to know how to actually manually install Rosetts 2 "without the pop up." Thanks

I'm compelled..... I'm trying to get one of the worst apps to work on the planet; Garmin Basecamp. It has always ran like a P.O.S. on Monterey and prior Mac O.S. Some users on the Garmin site states that it's working slightly better running Rosetta 2 therefore, I'm compelled to install it. It doesn't surprise me that I'm not getting the prompt for installing. Thanks.

The demos, tutorials, protocol captures, and all example inputs are provided with the full Rosetta distribution, under the demos/ directory. Rosetta is available for license (which is free of charge to academic users) at

For RosettaCommons users, the demos repository should be automatically downloaded by the get_rosetta.sh download script. Alternatively, RosettaCommons users can download the demos repository from GitHub. e.g.

These are introductory tutorials intended as a gentle introduction to Rosetta concepts, and using common functionality of Rosetta. For additional examples and information on using Rosetta, see the demos (below) or the Rosetta documentation

Many papers using Rosetta are accompanied by a protocol capture - an example of how to use the protocol discussed in the paper. The protocol captures below aren't meant to show the best way to solve problems in the current version of Rosetta, instead they are meant to show published solutions to problems that were addressed by members of the Rosetta community. The purpose of these protocol captures is both to serve as a historical record and to assist those trying to reproduce past results. See the demos (above) for updated versions of most protocol captures.

error. It says installed successfully, but if I rerun the script it tries again with the same result. If i try to run a policy that installs an Intel package it still errors out saying I need Rosetta.

I thought it might be because at one point I removed Rosetta on this one so I could use it as a test laptop. So I completely reinstalled Big Sur on it and tried again, but I still get the error. Any solutions?

Yes, this is one of the scripts that I tried. I still get the error that it's missing InstallKBytes attribute.

I've seen a couple of other people post that they've gotten this error. Someone said that manually double clicking /System/Library/CoreServices/Rosetta 2 Updater fixes it, but for me that comes back saying an error has occurred, please try again later.

I made a smart group called Macs with ARM Chip so that only those get the package installed.

I just did the command in terminal on a Macbook Pro with a M1 Pro chip. I get the exact same error when entering

I'm on an M1 mini on Monterey. I have multiple Rosetta apps running. There is no "/Library/Apple/System/Library/LaunchDaemons/com.apple.oahd.plist", and there is no process with "oahd" running. There is a "/Library/Apple/usr/share/rosetta/" directory. Every Rosetta install script I have found so far looks for things that do not exist on my mini. At this point I'm not even convinced Apple will allow Rosetta to be command line installed anymore. It seems like unless someone is available to dismiss a GUI dialog box the install fails. Either way, none of the popular install scripts seem to work anymore.

I've been having issues as well with Rosetta over the last week, it's just not getting installed properly by any jamf terminal command or script. So I made a pkg of the installer instead and deploy it at as the only pkg at enrolment to ensure it gets installed. To build the Rosetta pkg do this:

Managed to get hold of the RosettaUpdateAuto.pkg.

Quick question...

We currently run a script to determine if a device is M1 or not - if yes, then "softwareupdate --install-rosetta --agree-to-license". It's set to 'Enrolment'

If I were to create a policy that's set to 'Ongoing' with the RosettaUpdateAuto.pkg as a payload - if I call its trigger from inside our Enrolment script, will it be able to run the policy even though it hasn't finished running the Enrolment policies?

Via 'sudo jamf policy -trigger rosetta' (for example).

To summarise:

In the enrollment script, I'm suggesting replace "softwareupdate --install-rosetta --agree-to-license", with "sudo jamf policy -trigger rosetta"

'rosetta' being the trigger for a policy that is 'Ongoing'

I excluded an m1 mac from the script on enrollment so that rosetta does not get installed that way anymore. Then I ran just the basic command shown below; same error. So it's not the script. I'm on jss version 10.36.1

I do think Rosetta is installing via the old softwareupdate command, if it wasn't then following policies would've failed to run also (even stuff as standard as deploying basic desktop wallpapers).

I will still test deploying our own PKG though. I've seen our DEP script halt a couple of times on M1 Pro Max devices recently. I suspected it was related to our AntiVirus (because I've already recorrected the /usr/bin/python line). Just conscious that something has changed and would rather nothing was missing from Rosetta :D

(b) I will also run a second package to deploy DEP Notify, along with the script and custom triggers.

This process has worked flawlessly on our M1 devices. I like the idea of creating a Rosetta package also, which @tommyandersson provided above. Both methods should be solid.

3a8082e126