Catalina Package using Composer.

Isn’t there an agree to license option as well?

Is the computer able to get to the internet to check for updates?

@donmontalvo : Do we really required internet for this ? am looking for offline package can be create from composer and pus to self service ... So user no need to depend on internet to upgrade their OS.

@jstillio : Its suppose to be even i have tried using that commands as well .. which somebody was already refereed to this forum.

Seem to be i am missing some lines in the commands which i have tired my best.. The surprise is that i was using the same commands when high sierra was released.

@sushanth.gopinath here is what we have used, after insuring the computer is on the network:

sudo /Applications/Install macOS Catalina.app/Contents/Resources/startosinstall --agreetolicense --nointeraction && reboot

@donmontalvo : Thank you for the input.

Do i need to enter above commands to "post install" while creating the package through composer ?
My requirement is that we would like to have a package which user can install from self service.

Apart from this am going to create a single package which contains Catalina OS, security apps, along with other few apps) .. What is the best approach you can suggested here, this approach worked for me high sierra OS but Catalina have some challenges like package is not executing .

Cache the installer as a push, so it shows in Self Service when available. Keep that as a separate workflow. The other stuff should happen after user is upgraded.

@donmontalvo : Thanks you so much for your support and guidance. Few Quires please,

Cache the installer as a push : You mean that installer path should be /private/tmp ?
My plan is that i would like to have single package which should cover ( Mac OS Catalina and 2 security apps). Do you recommend this ? I can create via composer if possible.... As per your above comment ( Keep that as a separate workflow) i felt that you are recommending to keep macos installer alone at self service portal ?

My suggestion is to only have the installer in the package, then have a script in a policy to run the command.
That way you can change the way you use it to meet individual requirements, ie. when you want to wipe and reinstall for example.

@donmontalvo How does & differ from && and && reboot

+1 on what @look said. :)

I have changed the tag from Jamf Nation to Composer if you disagree please let me know.