Launchctl asuser "$uid" sudo -u "$currentUser" "no user logged in" # convenience function to run a command as the current user # global check if there is a user logged in ![]() #!/bin/bashĬurrentUser=$( scutil <<< "show State:/Users/ConsoleUser" | awk '/Name :/ & ! /loginwindow/ ' ) See my example below ( Just change the path to the path of a Ventura installer. This can be accomplished with some Apple Script wrapped in a bash function. When running the startosinstall command on an M1 device, the user will need to be prompted for a password. You can track volume ownership with an extension attribute.Ģ. Contrary to popular belief, the startosinstall command does not require the user to be admin, they just need to be the volume owner. From what I can see, you basically need to place an installer with Jamf and make Nudge run the startosinstall command. I did some extensive testing on M1 upgrades for a majority of the year to find the best upgrade path and concluded that Nudge was the answer. Anyway, I think I can help with the process that you're using. Hi I'm currently just waiting for Apple to allow delta upgrades so that I can just use the default Nudge functionality. Erase-install seems like the answer but I am having a bear of a time getting it all to work and make it pretty for the end user. ![]() I’ve tried having Nudge do the caching of the installer and upgrade and that also fails.Įach time I am running into issues trying to get a prompt to happen for the current volume owner so that the install can, you know, actually run.ĭoes anyone have a working process for Intel and M1 macs with standard users (non-admin) to upgrade in-place to Ventura? At this point, I’m open to any ideas or tools or whatever. I have tried using the Erase-Install app to do the caching of the installer and run upgrade but that doesn’t work. Here is where I am losing it, when it comes time to issue the upgrade command, it doesn’t work, at least on M1 macs. I have Nudge configured and working and it invokes a policy from Self Service that kicks off the upgrade script. I would like to use front end this process with Nudge to make users aware of the upgrade and allow deferrals until they click Upgrade. ![]() I have a policy that temporarily elevates user to Admin (script), installs nudge suite (pkg), nudge branding (pkg), mist-cli (pkg) and then runs the Mist command (script) to download the Ventura installer and it places it in /Users/Shared/Mist with the normal “Install macOS Ventura.app” format. All of our users are standard accounts on their devices and Filevault is mandatory. As with every upgrade, I am losing my mind finding a good process that works. I am currently working on a process to upgrade all of our fleet (50% Intel, 50% M1 roughly) to Ventura.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |