Upgrading to Monterey (Silicon Mac)

dpwlg
New Contributor III

Update:

Decided to push via Self Service using DEPNOTIFY. Sending out reminders to users to run updates.

Way easier than trying to automate the process.

 

I am currently trying to automate upgrading our macs M1 to Monterey.

I have had success with our Intel macs but stuck at the following stage where to install the OS on our M1 macs I get the following message in the logs.

dpwlg_0-1656069303894.png

Background:

I have set up two policies:

“Monterey Cache M1 Policy” caches the installer onto the machine.

“Monterey Install M1 Policy” installs/updates the OS.

 

“Monterey Cache M1 Policy” caches the installer onto the machine.

dpwlg_3-1656069586415.png

 

dpwlg_4-1656069594786.png

 

dpwlg_5-1656069604263.png

 

dpwlg_6-1656069611014.png

 

dpwlg_7-1656069621696.png

 

“Monterey Install M1 Policy” installs/updates the OS.

 

dpwlg_8-1656069635013.png

dpwlg_9-1656069646141.png+

 

dpwlg_0-1656069303894.png

6 REPLIES 6

JustDeWon83
New Contributor

.

Try adding the --nointeraction flag

dpwlg
New Contributor III

Still did not work. Any other suggestions?

echo ’password’ | '/private/var/Monterey.app/Contents/Resources/startosinstall' --agreetolicense --nointeraction --forcequitapps --user adminuser --stdinpass

JustDeWon
Contributor III

Just a curious question..

Why are you running it from /private/var instead of /Applications? 

Also, I would suggest prompting the user to enter their Filevault password vs attempting to do it as part of the startosinstall command..  As an example, try this instead

TheSeabass
New Contributor

Is the user being passed in the script a "secureTokenAdmin"? 

SureExclamation
New Contributor III

Sorry, disregard.