Skip to main content

Install Rosetta 2 via MDM for macOS 27 Golden Gate

Updated

Connect for macOS and macOS Authentication Agent rely on Rosetta 2 to work on Apple Silicon Macs, but upgrading to macOS 27 Golden Gate will remove Rosetta 2 from the device. If your school updated to macOS 27 Golden Gate, you must deploy the rosetta_check.sh script via your Mobile Device Management (MDM) to check and install Rosetta 2 on your Apple Silicon devices.The rosetta_check.sh script checks and installs Rosetta 2 and ensures Connect for macOS and macOS Authentication Agent are running. If Rosetta 2 is already installed on the device, the script will exit.

Before you begin

  • Your school must use Apple Silicon devices only (not Intel Macs).

  • You must have Administrative rights in your selected MDM platform.

  • Contact your Linewize Deployment Engineer for a copy of the rosetta_check.sh file.

Deploy via Jamf Pro

Step 1: Add the script to Jamf Pro

  1. Log in to Jamf Pro and go to Settings > Computer Management > Scripts.

  2. Select New.

  3. On the General tab, enter the following details:

    • Display Name: Rosetta 2 Check and Remediate.

    • Category: Select a category based on your school or district's naming convention.

  4. Select the Script tab and paste the contents of the rosetta_check.sh file.

  5. Select Save.

Step 2: Create the policy

  1. Go to Computers > Policies, and select New.

  2. Under the General payload, configure the following options:

    • Display Name: Rosetta_Check

    • Enabled: Yes

    • Trigger: Select Startup, Login, Recurring Check In, and Custom

    • Execution Frequency: Ongoing

  3. Under the Scripts payload, add the Rosetta 2 Check and Remediate script.

  4. Set the policy scope to your Apple Silicon Macs running macOS 27 Golden Gate.

Step 3: Configure triggers

Set triggers based on your fleet's deployment strategy, but set Execution Frequency to Ongoing in case a device misses the initial event. The script will exit immediately if Rosetta 2 is already present.

Trigger options summary

Table 1: Jamf Pro trigger options summary.

Trigger

Execution Behavior

Startup

Starts at boot before login (Recommended).

Recurring Check-in

Starts on every regular check-in (default ~15 minutes).

Enrollment Complete

Starts at the end of enrollment or DEP provisioning.

Custom

Starts via command line using jamf policy -event <name>

Deploy via other MDM platforms

The rosetta_check.sh script works on other MDM platforms, but configuration will vary:

Table 2: Deployment instructions for other MDM platforms.

Platform

Deployment Instructions

Microsoft Intune

Go to Devices > macOS > Shell scripts. Set Run as root to Yes and Script frequency to every 1 day.

Mosyle

Go to Management > Custom Command / Scripts, and scope the command to a dynamic device group.

FileWave

Create a Fileset containing an activation script and associate it with a smart group.

Jamf School

Configuration profiles cannot run scripts. Deploy the script using a package or migrate policy to Jamf Pro.

  Note

If your MDM can't run scripts at startup, schedule the script to run periodically or configure a custom trigger.

Looking ahead to macOS 28

Apple plans to remove general Intel translation support in macOS 28. Consequently, deploying the rosetta_check.sh file script s a temporary solution intended specifically for the macOS 27 Golden Gate release cycle.

Native Apple Silicon agent builds are currently on the Linewize product roadmap ahead of the macOS 28 release. Please monitor the Connect for macOS release notes for updates, or contact your Linewize Account Representative if your school has a large Apple Silicon fleet.