I'm testing some things with the new Apple M1 Macbook Pro in combination with Jamf.
The problem I'm currently struggling with, is that when you perform a wipe on the device initiated by Jamf is that you can't install new clean system again.
After the wipe has been done, I boot from recovery mode to start a clean install.
First you have to open disk utility to erase the SSD and create a volume to install on. But then I get the following attached error message.
Did anyone else test this also and are you having the same issue?
The only option to get the Mac working now, is by attaching it to another Mac and revive it with Apple Configurator 2.
Solved! Go to Solution.
I've seen this as well, had some success with running:
Enter macOS recovery. If you have FileVault 2 enabled, click the Recovery Assistant menu and then select “Erase Mac”. If you don’t have FileVault 2 Enabled or have already erased the drive, click utilities from the top menu bar and then click Terminal. Enter in the command resetpassword This will bring you back to the Recovery Assistant menu. Click the Recovery Assistant menu bar item at the top and then select “Erase Mac”.
Deleting the volume entirely, rebooting, then creating the volume again.
Yes I understand.
But if you send the Wipe commando trough Jamf, you don't have the container and volume anymore.
So my problem is still there, I can't wipe the "SSD" in the screenshot to create a volume on.
Then I get the error message as you can see in the screenshot.
I have also tried the way by using the reset password command pchrichard, ends up in the same issue :(.
I've also encountered this issue while testing new provisioning process in Big Sur and M1. Used Apple Configurator to reinstall the OS for testing.
Some articles about it:
@gforsyth The M1 Big Sur "Wipe and Reinstall" policy is exactly like the Intel one. The policy puts Big Sur installer in /Applications and runs install command in a script. Only the script is different.
The command I tried in script looks like this:
/usr/bin/su -l Admin -c "echo <user_password> | /Applications/Install macOS Big Sur.app/Contents/Resources/startosinstall --eraseinstall --newvolumename 'Macintosh HD' --nointeraction --agreetolicense --forcequitapps --user <name> --stdinpass"
This is not a good solution as you need to put admin password in clear text.
Another way is to save password into a hidden file, then run a command like this:
/Applications/Install macOS Big Sur.app/Contents/Resources/startosinstall --eraseinstall --newvolumename 'Macintosh HD' --nointeraction --agreetolicense --forcequitapps --user <name> --stdinpass < /path/to/file.text
The user must have a Secure Token.
@user-aj The entire script is just one line:
/usr/bin/su -l Admin -c "echo $4 | /Applications/Install\ macOS\ Big\ Sur.app/Contents/Resources/startosinstall --eraseinstall --newvolumename 'Macintosh HD' --nointeraction --agreetolicense --forcequitapps --user Admin --stdinpass"
Enter Admin account password as Parameter 4 in the policy scripts options
Admin user _must_ have Secure Token.
Oh thanks jannsen! So i was fed up with a big sur mac and decided to remote wipe it. But then i boot up into recovery and go to try and install the OS, but there are no volumes to install to (the list is blank).
Using disk utility, i select "partition" and then click the large part of the pie circle. Set the volume to ASPF or whatever the osx file system is and then go forward with the partitioning. I was able to make a volume and now the installer works!
was previously trying to just erase it but it wouldn't let me with a disk in use error.
the wipe command doesn't really work right in jamf i think with bigsur as its not intuitive at all what you need to do. it also never asked me for the code i created so what was the point of that then? But at least the OS was able to recover from some kind of inbuilt recovery. But it did need to connect to the network at one point so maybes its downloading from the internet.. who knows.
As part of my testing of an M1 MacBook Pro I did a "remote" wipe with Jamf Pro (the M1 was on the desk next to me), and it was immediately bricked, no amount of pivoting or faking would get it back to life except for Configurator (tried everything above). Never presented the unlock code that I put into the wipe command.
This presents a security problem. Anyone can look up the Configurator procedure on the internet and restore a wiped M1. Very not good.