In today's world of Mac's we have a hodgepodge of Intel, M1 and M2 MacBook Pro's. I have several policies that install different software with PKG files that have run fine without any issues because, until we started to buy M2 Mac's.
All of the policies/packages that fail to install all have errors relating to Rosetta 2 not being installed, despite it actually being installed on the machines. I even went as far as putting a script to run prior to the package install that installs Rosetta 2 that returns a successful install log.
When I manually install the exact same package files on the M2 Macs they install fine without error or mention of Rosetta 2, which confirms that it is actually installed. It is only when Jamf installs the PKG file on the M2 that it fails because of Rosetta 2.
All of these same scripts and package policies run fine on M1 Macs. All of our Macs are running MacOS 12.5. The only difference in the Pass vs Fail is processor type.
Executing Policy Xerox 5.10.0 Drivers
Running script Rosetta 2 Installer...
Script exit code: 0
Script result: usage: softwareupdate <cmd> [<args> ...]
** Manage Updates: -l | --list List all appropriate update labels (options: --no-scan, --product-types) -d | --download Download Only -i | --install Install <label> ... specific updates -a | --all All appropriate updates -R | --restart Automatically restart (or shut down) if required to complete installation. -r | --recommended Only recommended updates --os-only Only OS updates --safari-only Only Safari updates --stdinpass Password to authenticate as an owner. Apple Silicon only. --user Local username to authenticate as an owner. Apple Silicon only. --list-full-installers List the available macOS Installers --fetch-full-installer Install the latest recommended macOS Installer --full-installer-version The version of macOS to install. Ex: --full-installer-version 10.15 --install-rosetta Install Rosetta 2 --background Trigger a background scan and update operation ** Other Tools: --dump-state Log the internal state of the SU daemon to /var/log/install.log --evaluate-products Evaluate a list of product keys specified by the --products option --history Show the install history. By default, only displays updates installed by softwareupdate. ** Options: --no-scan Do not scan when listing or installing updates (use available updates previously scanned) --product-types <type> Limit a scan to a particular product type only - ignoring all others Ex: --product-types macOS || --product-types macOS,Safari --products A comma-separated (no spaces) list of product keys to operate on. --force Force an operation to complete. Use with --background to trigger a background scan regardless of "Automatically check" pref --agree-to-license Agree to the software license agreement without user interaction. --verbose Enable verbose output --help Print this help Rosetta has been successfully installed.
Downloading Xerox Drivers 5.10.0.pkg...
Downloading <Server Name>
Verifying package integrity...
Installing Xerox Drivers 5.10.0.pkg...
Installation failed. The installer reported: installer: This package requires Rosetta 2 to be installed.
Please install Rosetta 2 and then try again. `sudo softwareupdate --install-rosetta` installer: Error - Xerox Drivers can’t be installed on this computer.
the Script results shows that the used softwareupdate command is not accepted as correct.
Did you make sure that Rosetta 2 is really installed?
We are using a Extension Attribute to check this. The Script for this Extension Attribute is:
#!/bin/sh # # reports status of rosetta install RESULT=$(/usr/bin/pgrep -q oahd && echo Yes || echo No) echo "<result>$RESULT</result>"
this script checks if the process for rosetta 2 is running, if rosetta 2 is installed the process is always started with the system boot.
Sadly i do not have a M2 in our Test environment yet. But it looks like the Rosetta 2 Install script is not accepted, as mentioned above.