Yes.. For right now it's going to one test machine. When I run the policy through self service, it goes through the prompt "We nee to download macOS High Sierra to your computer..." Then after that, it gets stuck with that error.
To confirm the test machine is added to the scope of your "DLHIGHSIERRA" policy? What is the frequency of this policy set to?
Hi @sbirdsley
Yes the test machine has been added to the scope. Right now the policy is set for once per computer.
I am getting the same issue, did you manage to figure out why you kept getting the initial download message?
Here is the log file I can find, ^CScript exit code: 0 is where I CONTROL+C to kill the script
P52265:tmp root#
P52265:tmp root# jamf policy -event START_HS_UPGRADE
Checking for policies triggered by "START_HS_UPGRADE" for user "p52265"...
Executing Policy macOS Upgrade to High Sierra
Running script macOS Upgrade to High Sierra...
^CScript exit code: 0
Script result: Power Check: ERROR - No AC Power Detected
Disk Check: OK - 470642335744 Bytes Free Space Detected
Downloading macOS Installer...
Checking for policies triggered by "recurring check-in" for user "p52265"...
No policies were found for the "recurring check-in" trigger.
Checking for patches...
No patch policies were found.
Downloading macOS Installer...
/Library/Application Support/JAMF/tmp/macOS Upgrade to High Sierra: line 123: 27024 Terminated: 15 /Library/Application Support/JAMF/bin/jamfHelper.app/Contents/MacOS/jamfHelper -windowType hud -windowPosition $dlPosition -title "$title" -alignHeading center -alignDescription left -description "$dldescription" -lockHUD -icon "/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/SidebarDownloadsFolder.icns" -iconSize 100
Checking for policies triggered by "recurring check-in" for user "p52265"...
No policies were found for the "recurring check-in" trigger.
Checking for patches...
No patch policies were found.
Downloading macOS Installer...
/Library/Application Support/JAMF/tmp/macOS Upgrade to High Sierra: line 123: 27113 Terminated: 15 /Library/Application Support/JAMF/bin/jamfHelper.app/Contents/MacOS/jamfHelper -windowType hud -windowPosition $dlPosition -title "$title" -alignHeading center -alignDescription left -description "$dldescription" -lockHUD -icon "/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/SidebarDownloadsFolder.icns" -iconSize 100
Checking for policies triggered by "recurring check-in" for user "p52265"...
No policies were found for the "recurring check-in" trigger.
Checking for patches...
No patch policies were found.
Downloading macOS Installer...
/Library/Application Support/JAMF/tmp/macOS Upgrade to High Sierra: line 123: 27201 Terminated: 15 /Library/Application Support/JAMF/bin/jamfHelper.app/Contents/MacOS/jamfHelper -windowType hud -windowPosition $dlPosition -title "$title" -alignHeading center -alignDescription left -description "$dldescription" -lockHUD -icon "/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/SidebarDownloadsFolder.icns" -iconSize 100
Checking for policies triggered by "recurring check-in" for user "p52265"...
I'm in a continuous loop where the "We need to download macOS High Sierra to your computer" jamfhelper message
I am having an issue with the script and wondering if the version listed on 'Install macOS High Sierra.app' should be the one listed in 'Get Info'. Currently I have the script set to 10.13.6, but 'Get Info' states that it is 13.6.2
@LewisB Did you every find a resolution to your issue. I am in the same boat as you.
@Cyrano5 @LewisB which script are you guys running?
I am using the script from https://github.com/kc9wwh/macOSUpgrade.
Here are the variables.
For the OS Version, I have tried 10.13.6, 10.13.6.02, and 13.6.02 since the installer in the above image shows the version to be 13.6.02.
@Cyrano5 I think you're putting the values in the parameter labels rather than the parameter field. Here's a link on Parameter Labels: https://derflounder.wordpress.com/2014/03/20/setting-parameter-labels-in-casper/
So I reset the labels to just use the default $4, $5, etc. Then I entered the values into the fields in the script portion of the policy and the results ended up being the same. I get the HUD stating 'We need to download macOS High Sierra to your computer, this will take several minutes", this just seems to run in a cycle as previously mentioned by other users.
I know I am missing something obvious, just I just can't see it.
And for clarification, this is the policy that is referenced in the 'download-high-sierra-install' trigger. (I deleted the name of the policy in the screen shot, just think of it as High Sierra Cache)
It's a simple Composer package that puts the 'Install macOS High Sierra.app' in /Applications.
If I run this policy be itself in Self Service, it puts 'Install macOS HighSierra.app' in /Applications without issue.
Firstly, thanks for these scripts, hopefully will save me a heap of time and other methods I tried seemed to fail.
EDIT: Not sure why but after checking GitHUB again, seems i was using an earlier version 2.6.x of Roskos' script rather than the latest 2.7.2
Testing again with latest, if it corrects the issue I will update below...
Update: Ok now I get a failed to download notification after the loop which is better (thanks for that). I was starting to think that it had something to do with the location of the installer on the device as the download notification kicks in and loops as if it is not detecting the downloaded app. So seems like it has something to do with where it thinks it should look for the app?
That should surely be the $OSInstaller variable which is: /Applications/Install macOS High Sierra.app
scratches head more
Update2: In the end I went with BP's script and that seemed to work better. I also went with 2 seperate policies in the end instead of 1. 1 to download the installer and the second to install it on devices scoped to a smart group that looks for devices with the installer there and that meet other requirements such as minimum os etc.
Thanks.
Running into an issue using this: https://github.com/kc9wwh/macOSUpgrade
We're trying to set this up for use from self-service, but when using it from a user's network account, we get prompted for admin credentials. Is there a way we can set this up to bypass the admin prompt so end-users can run this independently?
Is this working with High Sierra 13.6.02 as I get download failed even though if I run the download policy separate it downloads fine?
I'm having issues using this method and I can't for the life of me figure out what's going wrong.
The update starts running via self service no problem, it downloads the installer via a policy with custom trigger just fine, starts the startosinstaller and then restarts and comes up with the black background, white apple logo and progress bar with countdown.
What I can't figure out though is that it seemingly finishes and drops the mac back to the login screen, seemingly done. If you click a few times in the right time it clearly shows OS is now 10.13.6 (have tried going from 10.11.x and 10.12.x). If I ssh in and run sw_vers -productVersion is also confirms 10.13.6. The JSS doesn't seem to be aware of this though, even though one of the tasks in the "usr/local/jamfps/finishOSInstall.sh" file is to do a recon.
As soon as I log in as a user, it then immediately brings up the same black screen, white logo and progress bar again for over 10 minutes and then just returns to the login screen without any more restarts.
Has anyone experienced this behaviour? Is this normal?
@allanp81 Yes, it is being discussed here.
I believe you get the login screen if the user attempting to upgrade is a Standard user, and not an Administrator.
@mark.mahabir I'm not sure if that's the case as I've got 2 machines I'm testing on and 1 has an admin user initiate and the other is a standard user and they both exhibit the same issue :(
I'm wondering if the issue is because the startosinstall is initiated as root, rather than the logged in user?
Will this method work to upgrade HFS+ on spinny drives to APFS & Mojave?
If they are supported then yes, in theory it will. The High Sierra upgrade from El Capitan and Sierra HFS+ certainly updates them to APFS, although I only have SSD Macs now.
I've noticed a few annoying things that the macOS updater does after finishing the upgrade, the main annoying one being that it seems to remove any customisations you've done to the user template(s). I know that Apple recommend against doing this but it's so annoying that it clearly just wipes the templates and recreates again.
Oh another thing I noticed is that the /var/log/jamf.log also gets wiped out during the upgrade, so might be worth taking a copy of this before initiating the upgrade.
Is anyone using Apple School Manager and VPP to deploy the latest OS X upgrade(s) via JAMF Self Service? Seems like there should be a way to do this cleanly but I'm unable to include any script to help avoid further user interaction since VPP deployment does not have any straightforward way of including the "startosinstall" or any other script. Any advice or insigts are greatly appreciated. Thanks!
@JMenacker A user has to be logged into the system to run the startosinstall command. With VPP you could simply get the installer.app on the device, that is it. You'd then have to have a policy scoped to a smart group of machines (smart group of devices with the installer present), that has a script leveraging the startosinstall command.
If you wanted something automatic, you'd have to write a script that checked for the installer.app, checked for a logged in user, if there is somebody logged in then alert them (or not) and execute the startosinstall command.
Based on your post though, I would recommend https://github.com/kc9wwh/macOSUpgrade if you don't want to script something yourself. It is a nice way to allow a user the opportunity to upgrade their Macs from Self Service. You can also notify them of the policy via Self Service Notifications.
