Again we are reminded of how badly unable we are to force updates on Mac users.
Why Apple? Why.
Given that this is not the first time this has happened with a Safari release (I forget if it's the 3rd or 4th time) and the complete lack of reliability in the macOS software update mechanism the past couple of macOS generations it does make one wonder if there is any adult supervision for Apple's software releases. Yes I'm grumpy, but I've been working on Macs since you had to have a Lisa to write software for them and I'm not happy with Apple's current level of attention to detail.
Again we are reminded of how badly unable we are to force updates on Mac users.
We don't manage devices over here, that is not the Apple Way. We politely herd sheep to do the right thing.
Why does this not surprise me.
We don't manage devices over here, that is not the Apple Way. We politely herd sheep to do the right thing.
Apple offers full management of supervised, company owned prestage ADE registered Macs through MDM unless - of course - the current user doesn't want to.
So which build numbers are we talking about?
On macOS 13.2.1 I am seeing
- 18614.4.6.1.6
- 18614.4.6.1.5
- 18614.2.9.1.12
- 18614.3.7.1.5
On macOS 12 I am seeing
- 17614.4.6.11.6
- 17614.3.7.1.7
- 17614.1.25.9.10
Just going with a hunch that the highest numbers are the correct latest patches and when there's a discrepancy (like 13.2.1 with older build) this could be because OS numbers are sent through the new declarative management status channel, while the CFBundle ID has to be extracted programmatically by the EA script, with a delay.
I did install it on our test devices and the version changed, but in Jamf, it's labeling it 16.3.1 in patch management. When I look at the installs for this, it shows zero. I'm assuming because it's not technically called 16.3.1.
Apple offers full management of supervised, company owned prestage ADE registered Macs through MDM unless - of course - the current user doesn't want to.
I got an email from JSS this morning at 3:41a that a patching definition for Apple Safari v16.3.1 was added.
It was not there yesterday. I was annoyed that I had to downgrade all my patching definitions so I could replace the 16.3 package with the 16.3.1 package. I figured it best to get the vulnerable package out of the mix.
Apple left the Version to be 16.3* instead of 16.3.1, so patch management will be inaccurate.
https://support.apple.com/en-us/HT213638
After installing this update, the build number for Safari 16.3 is 167614.4.6.11.6 on macOS Big Sur and 177614.4.6.11.6 on macOS Monterey.
Even Apple's Article appears incorrect. I'm seeing the following build IDs as the latest:
macOS Ventura
Bundle ID 18614.4.6.1.6
macOS Monterey
Bundle ID 17614.4.6.11.6
macOS Big Sur 16614.4.6.11.6
So which build numbers are we talking about?
On macOS 13.2.1 I am seeing
- 18614.4.6.1.6
- 18614.4.6.1.5
- 18614.2.9.1.12
- 18614.3.7.1.5
On macOS 12 I am seeing
- 17614.4.6.11.6
- 17614.3.7.1.7
- 17614.1.25.9.10
Just going with a hunch that the highest numbers are the correct latest patches and when there's a discrepancy (like 13.2.1 with older build) this could be because OS numbers are sent through the new declarative management status channel, while the CFBundle ID has to be extracted programmatically by the EA script, with a delay.
Same here. Not overly concerned with 11 and 12 since sdagley was able to provide those packages. Thank you so much!!
However, I am seeing multiple different Safari builds when the OS is claiming to be upgraded to 13.2.1. Not sure if we are compliant with remediation.
Is it possible to get the correct Safari package for Ventura so we can update it manually?
I got an email from JSS this morning at 3:41a that a patching definition for Apple Safari v16.3.1 was added.
It was not there yesterday. I was annoyed that I had to downgrade all my patching definitions so I could replace the 16.3 package with the 16.3.1 package. I figured it best to get the vulnerable package out of the mix.
Oh it gets better. After I complained yesterday that the re-use of the Safari 16.3 version number for the new Safari releases didn't match the 16.3.1 version listed in the Security update bulletins Apple revised the Security bulletins to roll the version number back to 16.3 and add a mention of checking the Build number. <HeadExplodingEmoji/>
Oh it gets better. After I complained yesterday that the re-use of the Safari 16.3 version number for the new Safari releases didn't match the 16.3.1 version listed in the Security update bulletins Apple revised the Security bulletins to roll the version number back to 16.3 and add a mention of checking the Build number. <HeadExplodingEmoji/>
I mean, one would have problems assuming Apple is one of the largest companies in the world making mistakes that would cause you to fail an assignment in a system analysis college course.
Oh it gets better. After I complained yesterday that the re-use of the Safari 16.3 version number for the new Safari releases didn't match the 16.3.1 version listed in the Security update bulletins Apple revised the Security bulletins to roll the version number back to 16.3 and add a mention of checking the Build number. <HeadExplodingEmoji/>
They should call this update "Safari+".
Boom.
They should call this update "Safari+".
Boom.
@mvu Now I want Safari Pro and Safari Max.
@mvu Now I want Safari Pro and Safari Max.
You win.
Same here. Not overly concerned with 11 and 12 since sdagley was able to provide those packages. Thank you so much!!
However, I am seeing multiple different Safari builds when the OS is claiming to be upgraded to 13.2.1. Not sure if we are compliant with remediation.
Is it possible to get the correct Safari package for Ventura so we can update it manually?
Like I mentioned, that might be because you have some machines that report their version number using declarative device management, whereas the Safari build won't be updated until the next recon.
Given that this is not the first time this has happened with a Safari release (I forget if it's the 3rd or 4th time) and the complete lack of reliability in the macOS software update mechanism the past couple of macOS generations it does make one wonder if there is any adult supervision for Apple's software releases. Yes I'm grumpy, but I've been working on Macs since you had to have a Lisa to write software for them and I'm not happy with Apple's current level of attention to detail.
Yup, apparently Apple has discovered there is a shortage of numbers, you know, those things that are infinite. Why they do this I just can't even wrap my head around. It's like rank incompetence. How difficult is it to give something a new proper number? Apparently very difficult for Apple.
Safari 16.3.1 appeared today in Software Update for one of my Big Sur machines. I installed it and the version number is indeed 16.3.1 and the build ID is 16614.4.6.11.7
Safari 16.3.1 appeared today in Software Update for one of my Big Sur machines. I installed it and the version number is indeed 16.3.1 and the build ID is 16614.4.6.11.7
@atlantamacguru Thanks for the heads up! Looks like Apple added macOS Big Sur 11.7.4 and Safari 16.3.1 for Big Sur to SUS on 2023-02-15
EDIT: Looks like @ClassicII identified the reason for the Safari 16.3.1 release for Big Sur on the MacAdmins Slack channel:
The update "fixes an issue that may cause website icons to not load."
The Big Sur 11.7.4 update is required before you can install the Safari 16.3.1 update.
For Monterey, this requires macOS 12.3 or later - but it will install on 12.0.1 - 12.2.1. Beware!
For Monterey, this requires macOS 12.3 or later - but it will install on 12.0.1 - 12.2.1. Beware!
@AaronInTX Thanks for the warning. Normally the Apple installers have a list of builds they're usable on, but it could be that these .pkgs don't because they were expecting Software Update to do the build verification.
Running the software update command seems to pull down the latest Safari build. Using @sdagley EA to report the build version.
Found a link for Safari 16.3.1 (Big Sur) that reports back 16614.4.6.11.7
https://swcdn.apple.com/content/downloads/62/14/032-51569-A_6C8JMC4NSY/3excb9qywqf00i87sfss53vk636jizy6ck/Safari16.3.1BigSurAuto.pkg
How does one find/access a list of swcdn download links? I happen to come across the above from another forum.
