We have about 50/50 M1 vs Intel chip Macbooks.We are using Jamf Connect as well (not sure if relevant)We have a standard Admin account created and loaded for every computer during prestage enrollment.We are not able to run the MacOS Ventura Installer on the M1 macs because it does accept the Admin credentials provided. These same Admin credentials are working for installing apps, etc. The update does work if you switch to the mentioned Admin account on the computer and then run the update.The update has none of these issues for the Intel macs. I can run the update from the user's account using the same Admin credentials. Anyone know why the M1 would not let us run this update from the user's standard account, even providing the correct Admin credentials?

Unable to run MacOS Ventura update on M1 Macs only

@bravichandran I created some new resources to try and help you automate the process of implementing the major update from macOS Monterey to Ventura:

1. Configure erase - install to trigger the update from self-service using this workflow. Once that is done email users and let them know they can and should start updating from self-service . This is the best option IMO for user accounts that are standard. I your users have admin accounts there are more options.

2. Next you can use a simple pop-up box that tells the user they must update which has an action button that when pressed will - triggers the self-service policy above. Link to this workflow here. Once that is in production for two weeks or so it should work for ~50-70% of your users. *make sure to inventory update often for these non-updated users so they are excluded from the smart group of computers that have not been updated.

3. For the last ~ 30% configure nudge to prompt the user to update. Make sure, it also triggers the policy step one. This is the link to the workflow. ( this demo config is ugly however, it is functional)

Hi, I have followed that video link and tried with one of my test machine. its started the update process after 1 hr but the os not updated still the device in monterey. I have downloaded the earse installer depnitofy package and created a policy after that downloaded the dialog box package and script as mentioned the video link and job id mentioned.. all started well with dialog box and its accepted the current login standard user name and password. update process started but after reboot its again showing monterey only

Did the new OS download?

Run it again and watch the network on the activity monitor and see how much data is flowing into the test device.

Can you send screenshots of your configuration?

I am looking to see the following:

General:

1. Policy-enabled status

2. Trigger events

3. Execution frequency

Packages:

1. distribution point

2.erase-install-depnotify-27.1.pkg added with the action of install.

Files and Processes:

1. Execute Command:

/Library/Management/erase-install/erase-install.sh --force-curl --reinstall --update --current-user  --overwrite --depnotify

2. Scope: test computer

3. Self-Service = Make policy Available -

I am trying to help you @bravichandran. One thing you can do to help me help you is to share your lab testing information in sequential detail.

No one can debug a failed lab test based on a general summary alone.

I hope that helps!

Hi, I have followed that video link and tried with one of my test machine. its started the update process after 1 hr but the os not updated still the device in monterey. I have downloaded the earse installer depnitofy package and created a policy after that downloaded the dialog box package and script as mentioned the video link and job id mentioned.. all started well with dialog box and its accepted the current login standard user name and password. update process started but after reboot its again showing monterey only

maybe a dumb question but are you restricting the macos Ventura installer in your jamf instance?

Did the new OS download?

Run it again and watch the network on the activity monitor and see how much data is flowing into the test device.

Can you send screenshots of your configuration?

I am looking to see the following:

General:

1. Policy-enabled status

2. Trigger events

3. Execution frequency

Packages:

1. distribution point

2.erase-install-depnotify-27.1.pkg added with the action of install.

Files and Processes:

1. Execute Command:

/Library/Management/erase-install/erase-install.sh --force-curl --reinstall --update --current-user  --overwrite --depnotify

2. Scope: test computer

3. Self-Service = Make policy Available -

I am trying to help you @bravichandran. One thing you can do to help me help you is to share your lab testing information in sequential detail.

No one can debug a failed lab test based on a general summary alone.

I hope that helps!

Hi Sorry for the late response.

Will provide all the details. Even i have tried using erase-insatll.sh script directly with parameters. The upgrade process starting but its failing near 48 % for this machine. For another machine its success. Both Success and failure logs including steps provided below

1. Policy enabled

2. Recurring check in -- Once per computer

3.Erase-install.sh -- script used-- downloaded from github

4.Script parameter -- screenshot pasted above

5.Maintainance configured - for inventory update.

Executing Policy Mac OS Ventura Upgrade - M1 Chipset
Running script erase-install.sh...
Script exit code: 0
Script result:
[erase-install] v27.1 script execution started: Tue Dec 20 09:00:27 CST 2022
[erase-install] Caffeinating this script (pid=23951)
[check_free_space] OK - 422 GB free/purgeable disk space detected
[erase-install] Looking for existing installer app or pkg
[find_existing_installer] Installer sparse image found at /Library/Management/erase-install/Install_macOS_13.1-22C65.sparseimage.
[check_installer_is_valid] Checking validity of /Volumes/Install_macOS_13.1-22C65/Applications/Install macOS Ventura.app.
Volume Shared Support on disk5s2 force-unmounted
[check_installer_is_valid] Mounting /Volumes/Install_macOS_13.1-22C65/Applications/Install macOS Ventura.app/Contents/SharedSupport/SharedSupport.dmg
[check_installer_is_valid] Using Build value from com_apple_MobileAsset_MacSoftwareUpdate.xml
Volume Shared Support on disk5s2 force-unmounted
[compare_build_versions] Comparing (1) 21G72 with (2) 22C65
[check_installer_is_valid] Installer: 22C65 >= System: 21G72 : valid build.
[erase-install] Running on architecture arm64
yes SDaker is a member of everyone
[get_user_details] SDaker is a Volume Owner
[get_user_details] ask for password (attempt 1/5)
[check_password] Success: the password entered is the correct login password for SDaker.
[erase-install] Installer is at: /Volumes/Install_macOS_13.1-22C65/Applications/Install macOS Ventura.app
[erase-install] Closing DEPNotify download message (language=en)
[check_free_space] OK - 422 GB free/purgeable disk space detected

[erase-install] WARNING! Running /Volumes/Install_macOS_13.1-22C65/Applications/Install macOS Ventura.app with reinstall option

[erase-install] Opening DEPNotify confirmation message (language=en)
[erase-install] User CONFIRMED erase-install or reinstall
[erase-install] Opening DEPNotify message (language=en)
[launch_startosinstall] Launching startosinstall
[erase-install] Sending password to startosinstall
By using the agreetolicense option, you are agreeing that you have run this tool with the license only option and have read and agreed to the terms.
If you do not agree, press CTRL-C and cancel this process immediately.
Preparing to run macOS Installer...

Preparing: 0.0%
Preparing: 0.1%
Preparing: 0.2%
Preparing: 0.3%
Preparing: 0.4%
Preparing: 0.5%
Preparing: 0.6%
Preparing: 0.7%
Preparing: 0.8%
Preparing: 0.9%
Preparing: 1.0%
Preparing: 1.1%
Preparing: 1.2%
Preparing: 1.3%
Preparing: 1.4%
Preparing: 1.5%
Preparing: 1.6%
Preparing: 1.7%
Preparing: 1.8%
Preparing: 1.9%
Preparing: 2.0%
Preparing: 2.1%
Preparing: 2.2%
Preparing: 2.3%
Preparing: 2.4%
Preparing: 2.5%
Preparing: 2.6%
Preparing: 2.7%
Preparing: 2.8%
Preparing: 2.9%
Preparing: 3.0%
Preparing: 3.1%
Preparing: 3.2%
Preparing: 3.3%
Preparing: 3.4%
Preparing: 3.5%
Preparing: 3.6%
Preparing: 3.7%
Preparing: 3.8%
Preparing: 5.9%
Preparing: 6.0%
Preparing: 6.1%
Preparing: 6.2%
Preparing: 6.3%
Preparing: 6.4%
Preparing: 6.5%
Preparing: 6.6%
Preparing: 6.7%
Preparing: 6.8%
Preparing: 6.9%
Preparing: 7.0%
Preparing: 7.1%
Preparing: 7.2%
Preparing: 7.3%
Preparing: 7.4%
Preparing: 7.5%
Preparing: 7.6%
Preparing: 7.7%
Preparing: 7.8%
Preparing: 7.9%
Preparing: 8.0%
Preparing: 8.1%
Preparing: 8.2%
Preparing: 8.3%
Preparing: 8.4%
Preparing: 8.5%
Preparing: 8.6%
Preparing: 8.7%
Preparing: 8.8%
Preparing: 8.9%
Preparing: 9.0%
Preparing: 9.1%
Preparing: 9.2%
Preparing: 9.3%
Preparing: 9.4%
Preparing: 9.5%
Preparing: 9.6%
Preparing: 9.7%
Preparing: 9.8%
Preparing: 9.9%
Preparing: 10.0%
Preparing: 10.1%
Preparing: 10.2%
Preparing: 10.3%
Preparing: 10.4%
Preparing: 10.5%
Preparing: 10.6%
Preparing: 10.7%
Preparing: 10.8%
Preparing: 10.9%
Preparing: 11.0%
Preparing: 11.1%
Preparing: 11.2%
Preparing: 11.3%
Preparing: 11.4%
Preparing: 11.5%
Preparing: 11.6%
Preparing: 11.7%
Preparing: 11.8%
Preparing: 11.9%
Preparing: 12.0%
Preparing: 12.1%
Preparing: 12.2%
Preparing: 12.3%
Preparing: 12.4%
Preparing: 33.5%
Preparing: 34.1%
Preparing: 38.7%
Preparing: 38.8%
Preparing: 43.3%
Preparing: 43.4%
Preparing: 48.1%
Preparing: 52.7%
Preparing: 53.2%
Preparing: 73.4%
Preparing: 77.0%
Preparing: 77.5%
Preparing: 78.4%
Preparing: 79.3%
Preparing: 80.2%
Preparing: 80.9%
Preparing: 84.0%
Preparing: 85.4%
Preparing: 86.1%
Preparing: 86.6%
Preparing: 87.1%
Preparing: 88.5%
Preparing: 89.1%
Preparing: 89.8%
Preparing: 90.4%
Preparing: 91.1%
Preparing: 91.7%
Preparing: 92.3%
Preparing: 93.1%
Preparing: 93.9%
Preparing: 94.8%
Preparing: 95.3%
Preparing: 96.2%
Preparing: 97.2%
Preparing: 98.1%
Preparing: 98.8%
Preparing: 99.9%
Preparing: 100.0% [post_prep_work] Skipping rebootdelay of 0s

[erase-install] attempting to terminate the 'Self Service' process - Termination message indicates success

[erase-install] attempting to terminate the 'caffeinate' process - Termination message indicates success
[erase-install] ERROR: 'caffeinate' could not be killed

[finish] Script exit code: 0

Error log :

[STEP 1 of 5]
Executing Policy Mac OS Ventura Upgrade - M1 Chipset
[STEP 2 of 5]
Running script erase-install.sh...
Script exit code: 42
Script result:
[erase-install] v27.1 script execution started: Tue Dec 20 13:15:29 CST 2022
[erase-install] Caffeinating this script (pid=1788)
[check_free_space] OK - 424 GB free/purgeable disk space detected
[erase-install] Looking for existing installer app or pkg
[find_existing_installer] Installer sparse image found at /Library/Management/erase-install/Install_macOS_13.1-22C65.sparseimage.
[check_installer_is_valid] Checking validity of /Volumes/Install_macOS_13.1-22C65/Applications/Install macOS Ventura.app.
[check_installer_is_valid] Mounting /Volumes/Install_macOS_13.1-22C65/Applications/Install macOS Ventura.app/Contents/SharedSupport/SharedSupport.dmg
[check_installer_is_valid] Using Build value from com_apple_MobileAsset_MacSoftwareUpdate.xml
Volume Shared Support on disk5s2 force-unmounted
[compare_build_versions] Comparing (1) 21E258 with (2) 22C65
[check_installer_is_valid] Installer: 22C65 >= System: 21E258 : valid build.
[erase-install] Running on architecture arm64
yes SDaker is a member of everyone
[get_user_details] SDaker is a Volume Owner
[get_user_details] ask for password (attempt 1/5)
[check_password] Success: the password entered is the correct login password for SDaker.
[erase-install] Installer is at: /Volumes/Install_macOS_13.1-22C65/Applications/Install macOS Ventura.app
[erase-install] Closing DEPNotify download message (language=en)
[check_free_space] OK - 424 GB free/purgeable disk space detected

[erase-install] WARNING! Running /Volumes/Install_macOS_13.1-22C65/Applications/Install macOS Ventura.app with reinstall option

[erase-install] Opening DEPNotify confirmation message (language=en)
[erase-install] User CONFIRMED erase-install or reinstall
[erase-install] Opening DEPNotify message (language=en)
[launch_startosinstall] Launching startosinstall
[erase-install] Sending password to startosinstall
By using the agreetolicense option, you are agreeing that you have run this tool with the license only option and have read and agreed to the terms.
If you do not agree, press CTRL-C and cancel this process immediately.
Preparing to run macOS Installer...

Preparing: 0.0%
Preparing: 0.1%
Preparing: 0.2%
Preparing: 0.3%
Preparing: 0.4%
Preparing: 0.5%
Preparing: 0.6%
Preparing: 0.7%
Preparing: 0.8%
Preparing: 0.9%
Preparing: 1.0%
Preparing: 1.1%
Preparing: 1.2%
Preparing: 1.3%
Preparing: 1.4%
Preparing: 1.5%
Preparing: 1.6%
Preparing: 1.7%
Preparing: 1.8%
Preparing: 1.9%
Preparing: 2.0%
Preparing: 2.1%
Preparing: 2.2%
Preparing: 2.3%
Preparing: 2.4%
Preparing: 2.5%
Preparing: 2.6%
Preparing: 2.7%
Preparing: 2.8%
Preparing: 2.9%
Preparing: 3.0%
Preparing: 3.1%
Preparing: 3.2%
Preparing: 3.3%
Preparing: 3.4%
Preparing: 3.5%
Preparing: 3.6%
Preparing: 3.7%
Preparing: 3.8%
Preparing: 3.9%
Preparing: 4.0%
Preparing: 4.1%
Preparing: 4.2%
Preparing: 4.3%
Preparing: 6.4%
Preparing: 6.5%
Preparing: 6.6%
Preparing: 6.7%
Preparing: 6.8%
Preparing: 6.9%
Preparing: 7.0%
Preparing: 7.1%
Preparing: 7.2%
Preparing: 7.3%
Preparing: 7.4%
Preparing: 7.5%
Preparing: 7.6%
Preparing: 7.7%
Preparing: 7.8%
Preparing: 7.9%
Preparing: 8.0%
Preparing: 8.1%
Preparing: 8.2%
Preparing: 8.3%
Preparing: 8.4%
Preparing: 8.5%
Preparing: 8.6%
Preparing: 8.7%
Preparing: 8.8%
Preparing: 8.9%
Preparing: 9.0%
Preparing: 9.1%
Preparing: 9.2%
Preparing: 9.3%
Preparing: 9.4%
Preparing: 9.5%
Preparing: 9.6%
Preparing: 9.7%
Preparing: 9.8%
Preparing: 9.9%
Preparing: 10.0%
Preparing: 10.1%
Preparing: 10.2%
Preparing: 10.3%
Preparing: 10.4%
Preparing: 10.5%
Preparing: 10.6%
Preparing: 10.7%
Preparing: 10.8%
Preparing: 10.9%
Preparing: 11.0%
Preparing: 11.1%
Preparing: 11.2%
Preparing: 11.3%
Preparing: 11.4%
Preparing: 11.5%
Preparing: 11.6%
Preparing: 11.7%
Preparing: 11.8%
Preparing: 11.9%
Preparing: 12.0%
Preparing: 12.1%
Preparing: 12.2%
Preparing: 12.3%
Preparing: 12.4%
Preparing: 12.5%
Preparing: 12.6%
Preparing: 12.7%
Preparing: 12.8%
Preparing: 33.8%
Preparing: 34.4%
Preparing: 39.0%
Preparing: 43.6%
Preparing: 43.7%
Preparing: 48.3%
Preparing: 100.0% An error occurred preparing the update.
[erase-install] Timeout reached for PID 2113!
/Library/Application Support/JAMF/tmp/erase-install.sh: line 2660: 2098 Killed: 9 dep_notify_progress startosinstall > /dev/null 2>&1
/Library/Application Support/JAMF/tmp/erase-install.sh: line 2660: 2113 Terminated: 15 /bin/cat 0<&4
[erase-install] Reached end of script. Exit with error 42.

[erase-install] attempting to terminate the 'caffeinate' process - Termination message indicates success
[erase-install] ERROR: 'caffeinate' could not be killed

[finish] Script exit code: 42
Error running script: return code was 42.
[STEP 3 of 5]
[STEP 4 of 5]
Inventory will be updated when all queued actions in Self Service are complete.
[STEP 5 of 5]

Did the new OS download?

Run it again and watch the network on the activity monitor and see how much data is flowing into the test device.

Can you send screenshots of your configuration?

I am looking to see the following:

General:

1. Policy-enabled status

2. Trigger events

3. Execution frequency

Packages:

1. distribution point

2.erase-install-depnotify-27.1.pkg added with the action of install.

Files and Processes:

1. Execute Command:

/Library/Management/erase-install/erase-install.sh --force-curl --reinstall --update --current-user  --overwrite --depnotify

2. Scope: test computer

3. Self-Service = Make policy Available -

I am trying to help you @bravichandran. One thing you can do to help me help you is to share your lab testing information in sequential detail.

No one can debug a failed lab test based on a general summary alone.

I hope that helps!

even if we used dialog box approach also same its failing nearing 48 %

@bravichandran I am not 100% sure why the script work flow is not working for you.

Are you open to using the .pkg workflow instead of the script work flow? The one in this film?

Also, I could do some consulting for you and help you -- your org get this update process moving forward. Let me know if you are intrested in that option as well.

Ya, this film showing my configuration to force stander accounts to update proves it is possible to update from Monterey to Ventura on a stander user's account.

They can self-initiate as well with this configuration.

So far I have had over 100 m1 client computers in the standard user account category update to Ventura successfully.

Hope that helps. ~ B

Hi @bcrockett I have a qs regarding the packages you download and upload to Jamf.

1. From where you download erase-install-depnotify-271.pkg. If I upload the .pkg still do I have to upload the Script: erase-install.sh

2. From where you download dialog-2.0-3810.pkg

The link you shared I see only script no .pkg. So please help me on that.

Hi @bcrockett I have a qs regarding the packages you download and upload to Jamf.

1. From where you download erase-install-depnotify-271.pkg. If I upload the .pkg still do I have to upload the Script: erase-install.sh

2. From where you download dialog-2.0-3810.pkg

The link you shared I see only script no .pkg. So please help me on that.

That information is in the description section of the film.

The software is downloaded from github.

##### Links referenced above and in the film

1. Erase-install https://github.com/grahampugh/erase-i...

2. swiftDialoog https://github.com/bartreardon/swiftD...

3. Nudge https://github.com/macadmins/nudge

That information is in the description section of the film.

The software is downloaded from github.

##### Links referenced above and in the film

1. Erase-install https://github.com/grahampugh/erase-i...

2. swiftDialoog https://github.com/bartreardon/swiftD...

3. Nudge https://github.com/macadmins/nudge

@sharif_khan It sounds like you are new to using GitHub. No worries we all started somewhere and it is a bit confusing how to download the .pkgs.

Check out this film of the workflow you can use to download .pkg from erase install

hope that helps!

@sharif_khan It sounds like you are new to using GitHub. No worries we all started somewhere and it is a bit confusing how to download the .pkgs.

Check out this film of the workflow you can use to download .pkg from erase install

hope that helps!

@bcrockett Thanks for the workflow. i download the package and upload to Jamf distribution and create policy with that erase-install-29.1.pkg and added /Library/Management/erase-install/erase-install.sh --reinstall --confirm to File & process. then execute that policy as self-service. That started without Ventura icon just an gear icon and I had to hit OK button and then that started after few min after click confirm button start upgrade with Ventura icon. So I guess this policy I have to involve user to upgrade macOS. Is there any way I can make that as required instead of available? if not then please let me know why not?

@sharif_khan you are asking the right questions.

However, if you looking for more direct support from me in putting together this workflow in your environment we would need to do an online session to get this done quickly.

Feel free to direct message me if you are interested in consulting further on this.

@sharif_khan you are asking the right questions.

However, if you looking for more direct support from me in putting together this workflow in your environment we would need to do an online session to get this done quickly.

Feel free to direct message me if you are interested in consulting further on this.

@bcrockett I able to put together as make available with the package and self-service install by user but I think if we can make that as a required install like without involve end user then that will be great. May be I couldn't make you understand. Sorry for that. But I am not looking for dirrect support from you. I am talking about this solution on this forum. I belive most of IT admin should like that update process without involve user. So I asked that is there any option to make this install package from self-initiate to Automate from Jamf.

I am unable to get password authorization. while doing ventura update with following script via self service

#!/bin/bash
softwareupdate --list-full-installers | grep 'macOS' | awk '{print ++count " " $0}'
softwareupdate --list-full-installers
softwareupdate --fetch-full-installer
softwareupdate --fetch-full-installer --full-installer-version 13.0.1
echo $pass | '/Applications/Install macOS Ventura.app/Contents/Resources/startosinstall' --user $admin --stdinpass --agreetolicense --nointeraction --forcequitapp

Install finished successfully Error: failed to authorize for installation. Provide a password with --stdinpass or --passprompt. By using the agreetolicense option, you are agreeing that you have run this tool with the license only option and have read and agreed to the terms. If you do not agree, press CTRL-C and cancel this process immediately.

This is the method I use to update any macOS update or upgrade

echo $pass | '/Applications/Install macOS Ventura.app/Contents/Resources/startosinstall' --user $admin --stdinpass --agreetolicense --nointeraction --forcequitapp

But before that I deploy the macOS installer.app as .dmg which I package via composer to avoid every endpoint to reach apple server to Download the installer. Then deploy to endpoint with another policy which will deploy the installer to /Applications folder. Then use another policy with the following command

echo $pass | '/Applications/Install macOS Ventura.app/Contents/Resources/startosinstall' --user $admin --stdinpass --agreetolicense --nointeraction --forcequitapp

That worked like charm for me any machine (M1/Intel) for admin/nonadmin user.

@bcrockett I able to put together as make available with the package and self-service install by user but I think if we can make that as a required install like without involve end user then that will be great. May be I couldn't make you understand. Sorry for that. But I am not looking for dirrect support from you. I am talking about this solution on this forum. I belive most of IT admin should like that update process without involve user. So I asked that is there any option to make this install package from self-initiate to Automate from Jamf.

If your goal is to update without user interaction super
<>is the software with the best chance at
making that possible right now IMO.

I plan to make some films about my lab test with this software soon. I have
still not been able to use it to update standard users without user
interaction however, that could be related to a mistake in my own
configuration.

That said check out the wiki <>
for S.U.P.E.R.M.A.N. by Kevin M. White it is an exciting contribution to
the mac admin community that combines all the tools for updating macOS
computers with notifications in a single configuration.

--
Thanks,

Buck Crockett
Director of Technology
6835 Trinidad Drive | San Jose, CA 95120 | USA
T 408 997-0424 x274
C 303-809-1430
bcrockett@almadencountryday.org
almadencountrydayschool.org <>

FOLLOW. CONNECT. SHARE.
Facebook <> | LinkedIn
<> | Twitter
<> | Instagram
<>

*LOVING THE NOW. READY FOR NEXT.*

*Send ALL tech requests to:*helpdesk@almadencountryday.org

I met with Kevin M at JNUC 2022 and attend to his session. And also talked with him regarding this update process. He told me that will work only for update I guess not upgrade as I recall, I could be wrong.

This is the method I use to update any macOS update or upgrade

echo $pass | '/Applications/Install macOS Ventura.app/Contents/Resources/startosinstall' --user $admin --stdinpass --agreetolicense --nointeraction --forcequitapp

But before that I deploy the macOS installer.app as .dmg which I package via composer to avoid every endpoint to reach apple server to Download the installer. Then deploy to endpoint with another policy which will deploy the installer to /Applications folder. Then use another policy with the following command

echo $pass | '/Applications/Install macOS Ventura.app/Contents/Resources/startosinstall' --user $admin --stdinpass --agreetolicense --nointeraction --forcequitapp

That worked like charm for me any machine (M1/Intel) for admin/nonadmin user.

@sharif_khan can you please elaborate the steps in detail to try in my environmet

This is the method I use to update any macOS update or upgrade

echo $pass | '/Applications/Install macOS Ventura.app/Contents/Resources/startosinstall' --user $admin --stdinpass --agreetolicense --nointeraction --forcequitapp

But before that I deploy the macOS installer.app as .dmg which I package via composer to avoid every endpoint to reach apple server to Download the installer. Then deploy to endpoint with another policy which will deploy the installer to /Applications folder. Then use another policy with the following command

echo $pass | '/Applications/Install macOS Ventura.app/Contents/Resources/startosinstall' --user $admin --stdinpass --agreetolicense --nointeraction --forcequitapp

That worked like charm for me any machine (M1/Intel) for admin/nonadmin user.

@sharif_khan can you please elaborate the steps in detail. so that i can try in my environment

1. Download new version of macOS on my test machine whihc download to my /Applications folder as instaler.app. for example I am trying to update macOS Ventura. Then download latest version of macOS Ventura and that will cached to my machine Install macOS Ventura.app

2. Package that installer as .dmg via composer

3. Upload to Jamf distribution point

4. Create a policy to deploy installer to client machine as recurring check-in with Inventory update payload

5. Create a smart group with that application (Install macOS Ventura.app) presence

6. Create another policy with command: echo 'local admin password' | '/Applications/Install macOS Ventura.app/Contents/Resources/startosinstall' --agreetolicense --forcequitapps --nointeraction --user localAdminuser --stdinpass Note: User single quite ' ' for password and no qoute for username

7. Add restart payload and Inventory update payload.

I hope that help. I had to push another Inventory update to endpoints to get update macOS update information to Jamf from endpoints.

@sharif_khan can you please elaborate the steps in detail. so that i can try in my environment

I deployed Super script with a policy to Apple Silicon computers with the following parameters:

Super can automate updates by utilizing an account with a token volume to start the process.

Thus, in my test environment, I created every account possible to give the scrip all options for success these include:

a. a local accout

b. a admin accout

b. and a jamf - admin account though the API process

When I trigger the script from the test computer the client still must enter their username and password for it to work.

After they enter their username and password the policy log looks is as follows:

#######

Script result: tee: /Library/Management/super/super.log: No such file or directory

Tue Mar 21 13:47:28 testMac S.U.P.E.R.M.A.N.[1704]: **** S.U.P.E.R.M.A.N. 3.0b8 INSTALLATION ****

Tue Mar 21 13:47:28 testMac S.U.P.E.R.M.A.N.[1704]: Installation: Made working folder: /Library/Management/super

Tue Mar 21 13:47:28 testMac S.U.P.E.R.M.A.N.[1704]: Installation: Copying file: /Library/Management/super/super

Tue Mar 21 13:47:28 testMac S.U.P.E.R.M.A.N.[1704]: Installation: Creating default path link: /usr/local/bin/super

Tue Mar 21 13:47:28 testMac S.U.P.E.R.M.A.N.[1704]: Installation: Creating file: /Library/Management/super/super-starter

Tue Mar 21 13:47:28 testMac S.U.P.E.R.M.A.N.[1704]: Installation: Setting permissions in: /Library/Management/super

Tue Mar 21 13:47:28 testMac S.U.P.E.R.M.A.N.[1704]: **** S.U.P.E.R.M.A.N. 3.0b8 STARTUP ****

Tue Mar 21 13:47:28 testMac S.U.P.E.R.M.A.N.[1704]: Startup: Deleting all local non-account preferences.

Tue Mar 21 13:47:28 testMac S.U.P.E.R.M.A.N.[1704]: Status: Restarting automatically set zero day date.

Tue Mar 21 13:47:28 testMac S.U.P.E.R.M.A.N.[1704]: Status: Restarting maximum deferral counters.

Tue Mar 21 13:47:29 testMac S.U.P.E.R.M.A.N.[1704]: Status: Current GUI user is testAdmin with a UID of 501.

Tue Mar 21 13:47:29 testMac S.U.P.E.R.M.A.N.[1704]: Startup: No custom display icon found, copying default icon from: /System/Library/PrivateFrameworks/SoftwareUpdate.framework/Versions/A/Resources/SoftwareUpdate.icns

Tue Mar 21 13:47:29 testMac S.U.P.E.R.M.A.N.[1704]: Startup: Bootstrap token escrow validated.

Tue Mar 21 13:47:33 testMac S.U.P.E.R.M.A.N.[1704]: Startup: Saving new credentials for local account "testAdmin"...

Tue Mar 21 13:47:33 testMac S.U.P.E.R.M.A.N.[1704]: Startup: Validated saved credentials for local account "testAdmin".

Tue Mar 21 13:47:33 testMac S.U.P.E.R.M.A.N.[1704]: Startup: Saving new credentials for super service account "super"...

Tue Mar 21 13:47:33 testMac S.U.P.E.R.M.A.N.[1704]: Startup: Validated saved credentials for new super service account "super".

Tue Mar 21 13:47:33 testMac S.U.P.E.R.M.A.N.[1704]: Startup: Deleting existing super service account "super" in preparation for new account.

Tue Mar 21 13:47:33 testMac S.U.P.E.R.M.A.N.[1704]: Startup: Creating new super service account "super" with full name "Super Update Service" and UID 504...

Tue Mar 21 13:47:38 testMac S.U.P.E.R.M.A.N.[1704]: Startup: Validated the creation of new super service account "super".

Tue Mar 21 13:47:38 testMac S.U.P.E.R.M.A.N.[1704]: Startup: Saving new credentials for Jamf Pro API account "superapi"...

Tue Mar 21 13:47:38 testMac S.U.P.E.R.M.A.N.[1704]: Startup: Validated saved credentials for Jamf Pro API account "superapi".

Tue Mar 21 13:47:38 testMac S.U.P.E.R.M.A.N.[1704]: Startup: Apple Silicon Mac computer running macOS 13.2-22D49.

Tue Mar 21 13:47:38 testMac S.U.P.E.R.M.A.N.[1704]: Startup: Last macOS startup was Tue Mar 21 13:44.

Tue Mar 21 13:47:38 testMac S.U.P.E.R.M.A.N.[1704]: Startup: macOS update/upgrade workflows authenticated via local account.

Tue Mar 21 13:47:39 testMac S.U.P.E.R.M.A.N.[1704]: Startup: Attempting to download and install IBM Notifier.app...

Tue Mar 21 13:47:40 testMac S.U.P.E.R.M.A.N.[1704]: Startup: Found that Jamf is installing or is the parent process, restarting with new LaunchDaemon...

Tue Mar 21 13:47:41 testMac S.U.P.E.R.M.A.N.[1704]: Exit: LaunchDaemon com.macjutsu.super.plist is scheduled to start right now.

Tue Mar 21 13:47:41 testMac S.U.P.E.R.M.A.N.[1704]: **** S.U.P.E.R.M.A.N. 3.0b8 EXIT ****

############

That is not great detail. I will record a screencast with more detail soon.

The short of it is that I am not sure how to configure the script so that the stander user does not have to enter their token volume credentials for the update to happen.

Perhaps I am given it to many options by allowing it to use;

an existing local account, super service account, and a custom local super service account.

https://github.com/Macjutsu/super/wiki/Local-Update-Credentials

Perhaps I will try testing with one account type at a time and see if that helps me identify one that will work to enforce software updates on Mac computers with apple silicon without additional update credentials.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded