Add Pre-flight Check for OS version

[mani2care]

Hi Dan , really wonderful script to onboard the macOS via enrolment trigger or DEP .

one consent my location users macs are BYOD setup and some of talented users are having old version of Mac OS catalina and below. They will not read the instructions during the enrolment. Sometimes users are enrolled to JAMF and setup your mac script will be failed due to swift dialog compatibility.

Might be your able to add the limitation it will help us to use it without any error.
If in case users is old version just to run a policy trigger and exit with JAMF dialog as complete.

2)And we need a built in automation for the swift dialog version validation. If in case I am using old versions of swifdialog and install it latest version so it will help us to additional effort to do
Swiftdialogversion =$8any version /Autoupdate get always latest xyz version.

[dan-snelson]

Thanks for the double Feature Request, @mani2care; will you please open a separate issue for Item No. 2?

As discussed in the MacAdmins Slack #setup-your-mac Channel, we're handling this use-case at the Jamf Pro Policy level; computers which enroll with OSes of macOS 10.15.7 Catalina and earlier only see two policies:

1. Update Inventory
2. Upgrade to macOS Ventura

In the meantime, you're welcome to use this and this.

[dan-snelson]

Revised Issue Title

• From: Restructuring macOS to avoid the error setup your mac script
• To: Feature Request: Add Pre-flight Check for OS version

[dan-snelson]

@mani2care:

Please test-drive 1.7.0-rc4 (which is not production-ready):

[SirDrSpiderpig]

I also think macOS validation would be awesome since we’re constantly chasing zero days and need to make sure new builds are at latest level.

[dan-snelson]

@SirDrSpiderpig: Currently, the check is just to confirm the Mac can run swiftDialog.

[dan-snelson]

@mani2care and @SirDrSpiderpig:

Please test-drive 1.7.0-rc5 which introduces the ability to specify a requiredMinimumBuild.

[SirDrSpiderpig]

Will do and report back.

[mani2care]

I need some time to test due to test device unavailability 🥺

On Wed, 25 Jan 2023 at 8:11 PM, SirDrSpiderpig ***@***.***> wrote: Will do and report back. — Reply to this email directly, view it on GitHub <#31 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMUGJUYYVFBUZXTS2NNAOIDWUE3QRANCNFSM6AAAAAAUCH5TXE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Thanks & Regards, Manikandan R Contact: +91-9902103878 E-mail: ***@***.***

[SirDrSpiderpig]

Downloaded it now and will tear on Jamf cloud beta instance.

If I can suggest to make the requireMinimumbuild variable added as part of the script variables in Jamf so it can be updated by the policy as opposed to going into the code. Just like debug and welcome screen are.

Will report back after testing

[dan-snelson]

Thanks for the prompt feedback, @SirDrSpiderpig.

How frequently do you see yourself updating requiredMinimumBuild ?

[SirDrSpiderpig]

Anytime there is a zero day. This year we’ve have plenty of those that kept us scrambling

[dan-snelson]

Ah, OK.

Currently, requiredMinimumBuild is at Line 44 and the Script Parameters don't start until Line 148.

[dan-snelson]

@SirDrSpiderpig:

In case it helps, 1.7.0-rc6 includes a yet-to-be-tested requiredMinimumBuild="${8:-"22D"}".

[dan-snelson]

Catalina

Ventura

[SirDrSpiderpig]

Looking good!

[dan-snelson]

Just uploaded a screencast for 1.7.0's new Outdated OS Action.

[dan-snelson]

Addressed in 1.7.0.