- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on
06-26-2020
03:11 PM
- last edited
Tuesday
by
kh-richa_mig
We are attempting to create a policy in self service that performs an upgrade. We use the macOSUpgrade.sh. After downloading the needed files, we get a "We were unable to prepare your computer for macOS Catalina: error (see attached). Our machines are FileVaulted. Not sure what's going on. It does not do this every time... even on the same machine.
Solved! Go to Solution.
- Labels:
-
Self Service

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 06-26-2020 03:56 PM
How are you calling the .app? Dropping it in /Applications ? Have you also modified the script with that version?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 06-26-2020 03:17 PM
@rpayne have you tried updating your install macOS catalina.app ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 06-26-2020 03:42 PM
I JUST did. It's 10.15.5.02

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 06-26-2020 03:56 PM
How are you calling the .app? Dropping it in /Applications ? Have you also modified the script with that version?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 06-27-2020 11:54 AM
Hi @rpayne,
By default, the main log (most complete) is located:
osinstallLogfile="/var/log/startosinstall.log"
You may also be able to find the reason for the error within Jamf's policy log history.
Happy to help if you can provide a little more info about what error you're getting.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 06-28-2020 12:18 AM
@mack525 I'm dropping it in the applications folder and using a custom trigger per the macOSUpgrade.sh. I have modified the script to reflect the current 10.15.5.02 (also tried the current installer version 15.5.02)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 06-28-2020 12:25 AM
I'm an idiot. Putting it to 10.15.5 (even the CURRENT is 10.15.5.02) works.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Posted on 06-28-2020 12:50 AM
@rpayne it’s always 1 simple step that screws things up. Good hear it’s working
