Hello everyone,
We are trying to use the following process to upgrade user machines from Catalina to either Big Sur or Monterey (depending on hardware support):
- Use a policy to cache an install of MacOS, targeted by static group
- Once the cached install has completed successfully, add the computer to a second group to manually extract and install the cached installer using a script. The script uses jamfHelper to allow users to delay the upgrade, etc., and ultimately culminates in the following command:
/Applications/Install\\ macOS\\ Big\\ Sur.app/Contents/Resources/startosinstall --agreetolicense --nointeraction --forcequitapps --pidtosignal $jamfHelperPID >> /var/log/startosinstall.log 2>&1 &
We've verified that the script works when run directly, as well as when run by a policy that is triggered by login. However, if we set the policy to run on recurring check-in, we see miscellaneous oddities including Jamf Helper launching in full screen and then immediately exiting, or launching in full screen but the upgrade never being executed.
Is this something anyone has run into? I'd be content to just let the upgrade occur on login, but we have several users who don't log off despite the requests and we're a bit weary of potentially causing data loss from unsaved work, etc.
Thanks in advance!