@mhegge Cache is simply a term being used here and is commonly utilized in the IT world to various degrees.

The only point to this that I see could be argued to change is the one time where it states "identify whether the Mojave installer has been cached to your Macs" and change to "identify whether the Mojave installer has been copied to your Macs". The others are fine as they're listed for Display Name and a Smart Computer Group. They're nothing more than labels describing what's intended to occur and the terminology fits even if it doesn't fit with the Jamf cache feature.

Not to sound like I'm judging or anything but anyone administering Jamf should understand that and be reading instructions carefully to understand what's going on as well as test, test, test before a real deployment.

I know my vote doesn't count but while I don't think it's a bad idea to change it I also don't think it's a necessity.

Looking over this process to see if our group will implement. I do have a few questions.

1. Does this still only work for APFS devices?
2. The Policy "Cache Install macOS Catalina.app" The 1st step has a Files & Processes with Command /usr/sbin/softwareupdate --fetch-full-installer. What is this for? Is this just to get the macOS? Do I need this after I upload the Catalina pkg by following the Composer steps? The 2nd step for Policy "Cache Install macOS Catalina.app". Has the pkg created in Composer. Just to be sure I am just removing the Files & Process entry and adding the pkg? Or is that a typo and should be a totally new Policy by cloning and renaming the Policy?
3. Creating the Self Service button. the frequency is set to ongoing. Why? I would think once per computer is the correct setting. That way it removes the button from Self Service when the button is selected.

The process does seem to work from me just not sure I have it setup the correct way. Catalina pkg created and uploaded to Jamf Policy "Cache Install macOS Catalina.app" created which installs pkg if in scope, excluded if Catalina version is already in Applications. Policy "Upgrade to macOS Catalina" with Command '/Applications/Install macOS Catalina.app/Contents/Resources/startosinstall' --agreetolicense --forcequitapps. (Not erasing in this setup)

It takes about 10 minutes for the policy in Self Service to complete and reboot before the upgrade starts. After install Catalina 10.15.6 is the new version and data is intact. After reboot this policy is still in self service due to frequency set to ongoing.