Can't find start osinstall via JAMF #45
Comments
|
The script was unable to download the macOS installer because no policy with the trigger Is your target machine scoped to the download policy correctly? |
|
This is what I have |
|
Do you have the |
|
I had one policy with the pkg set to cache and the script to run. |
|
You can still have a policy to cache the pkg but you would need a separate policy to install the package before running the script. For us, caching the pkg beforehand is not necessary. |
|
Did you build a .pkg or .dmg for the install macOS .app |
|
I built a .pkg using Packages that places the installer app in the Applications folder. |
|
I get the .app to download and the script runs but doesn't do anything here is my log. Feb 23 13:12:06 jamf-test-01 softwareupdate_notify_agent[3671]: appstoreupdateagent notified |
|
I haven't tested the script in a Parallels VM before though it should work fine. Try running the |
|
I ran this on the VM in terminal and it worked fine sudo "/Applications/Install macOS Sierra.app/Contents/Resources/startosinstall" --applicationpath "/Applications/Install macOS Sierra.app" --nointeraction Spoke too soon errors with this: |
|
I got this to work on a 10.11.6 machine to 10.12.6. I then modified it for 10.13.3 via JAMF and it never kicks off. I run the sh manually and it reboots and installs the OS in about 60secs. |
|
What is the Jamf policy log on the 10.13.3 machine? |
|
Script result: Power Check: OK - AC Power Detected |
|
Well, that all looks fine. Does the install log offer any helpful detail? |
|
Let me check after this other update goes through. |
|
I am seeing something similar..going from 10.12.6 to 10.13.3...In my logs it looks like the AssetCacheLocatorService is trying to do something, fails, then that causes osinstallersetupd to send a kill signal and stop the upgrade. If you run the same policy a second time, after the first time has failed, does it work? That is what I am seeing...if I run the same policy a second time after the first one has failed, it just works. |
|
Yes I get the same result it fails the first time and 2nd time works fine. |
|
Slightly different here. I’ve modified this script and used it as a post install script in a single pkg. However pkg locally from cli or gui and it works. Run it via a Casper policy and it fails first time, works second. Sounds like the jamf binary or framework maybe causing the problem. Has any one tried killing AssetCacheLocatorService before starting the upgrade? Or maybe a loop around startosinstall ? |
|
I don't know if it's JAMF or Apple at this point. Just to see the difference, I packaged up 10.13.2 full installer and was able to run the script with no issues from a policy. It's worked 2 times in a row on one of my test VMs, going to try on a physical machine now and see if that works. Not seeing the AssetCacheLocator error anywhere in the install.log |
|
OK found my problem, I was testing on a Mac that had not finished Filevaulting, so was getting an error from startosinstall of Target not found. Once FV had finished all was good. I have had constant success now on 3 Macs and 4 VM's using the script as a post install item in a PKG |
|
I tried it on a Mac Mini with FV disabled and it still fails the first time, always will go the second time. |
|
FYI, I have now tried this as a post install script in a PKG and its working fine on over 20 Macs. iMacs, Macbook's either FileVaulted or not running 10.10 to 10.12.6 |
|
Upgrade to 10.12.6 works every time. Upgrade to 10.13.3 fails 1st time works the 2nd time. |
|
Has anyone tried with 10.13.4 yet? |
|
I've been using the workflow with 10.13.4 and it's worked reasonably well. |
|
Does anyone know why this policy always fails the first time via JAMF and goes through the second time right away? |
|
@kyleericson This is what @Palgus had found:
|
|
@Hacksore Yes that's what I see could we add into the script to kill the AssetCacheLocatorService or to just run the upgrade script again. |
|
@kyleericson If I recall correctly the script exits fine, right? So I'm guessing running it twice could work but super it's hacky. As for killing AssetCacheLocatorService, when would you do that? From what I've seen as of High Sierra this is no longer an issue and looks to be limited to the 10.12.x. branch (Someone feel free to correct me if I'm wrong). |
|
I had tested on 10.11.6 and had the same issues |
|
@kyleericson So maybe anything less than 10.13? |
|
I'm working on a updated version of this script today (as long as my queue doesn't blow up), but I have been unable to duplicate the issue of having to all the script twice to kick off the upgrade. So if someone can confirm killing the |
|
@kc9wwh So, I have not been able to test this out..killing |
|
So I'm a noob and completely stuck, keep getting Not sure what I am doing wrong and this doesn't make much sense to me at all: totally not getting the custom trigger portion if that is my issue. Which policy needs to be triggered by the other and how? What tells the computer or jamf to look for the custom trigger? |
|
@swilliams83 The custom trigger is the name you named your custom trigger for the download. For instance mine was called deploy-High-Sierra and that appears on the policy under General -> Trigger -> select Custom and type name deploy-High-Sierra. The error your getting is complaining that the installer in not being found in the Applications folder. That may be because you're not getting the installer installed on the computer because of your custom trigger not being correct. If this doesn't help resolve your issue let me know I'd be happy to go in more detail to assist you. |
|
@mpermann thanks for replying. So just making sure I understand. For the policy that deploys the package that places the .app in /Applications I add a custom trigger and name it? Then in the policy for the script, I add that custom trigger name to parameter at $6 ?? I feel like I did that and it still didn't work. I'll double-check my policies if this is correct? |
|
Here is what the policy that installs the installer into the Applications folder looks like.
The policy that contains the script looks like the following: Does this help clarify? If not let me know. |
|
@mpermann thanks so much man, that did the trick but now getting an error "Helper tool crashed" so troubleshooting that. |
I get this error via JAMF self service install.
For the Variable via JAMF I set this.
OSINSTALLER /Applications/Install macOS Sierra.app
VERSION 10.12.6
DOWNLOAD_TRIGGER download-sierra-install
Script result: Power Check: OK - AC Power Detected
Disk Check: OK - 51571163136 Bytes Free Space Detected
0Checking for policies triggered by "download-sierra-install" for user "Administrator"...
No policies were found for the "download-sierra-install" trigger.
mkdir: /usr/local/jamfps: File exists
Launching jamfHelper as FullScreen...
Launching startosinstall...
/Library/Application Support/JAMF/tmp/Mac OS 10.12.6 Upgrade: line 281: /Applications/Install macOS Sierra.app/Contents/Resources/startosinstall: No such file or directory
The text was updated successfully, but these errors were encountered: