Skip to main content

Looks like Apple finally released a version of 10.9.3 to non-beta users.

http://9to5mac.com/2014/05/15/apple-releases-os-x-10-9-3-software-update-with-improved-4k-display-support-contacts-and-calendar-syncing-improvements-more/
http://www.macrumors.com/2014/05/15/apple-releases-os-x-10-9-3/

From http://support.apple.com/kb/HT6228

This update: - Improves 4K display support on Mac Pro (Late 2013) and MacBook Pro with 15-inch Retina Display (Late 2013) - Adds the ability to sync contacts and calendars between a Mac and iOS device using a USB connection - Improves the reliability of VPN connections using IPsec - Resolves an issue that prevented Font Book from installing PostScript Type 1 fonts - Improves reliability of copying, editing and inspecting permissions of files on an SMB file server - Improves reliability of network home directories - Improves stability when installing configuration profiles - Improves login speed for users in Active Directory groups - Includes Safari 7.0.3

I love how when you go to the official update statement the Safari 7.0.3 line is in a smaller font. Just makes me giggle.

This brings me to a kind of interesting topic, at least for me. How do your enforce Software Updates? How quickly do you push them out to your users? What kind of policies do you have in place for Software and OS Updates?

most software updates I have on an ongoing policy to install, giving the users the option to defer if desired.

Trouble is, apple seems fairly adhoc for releases, so I haven't found a way to limit deferments for some of the packages but not others.

I guess I should be switching over to a more M$ approach and hold all updates until patch tuesday... and have separate scripts for each update.

13D65. So if you were testing, it's newer.

First to the DLs enjoy!

Mac OS 10.9.3
http://support.apple.com/kb/DL1745

Mac OS 10.9.3 Combo
http://support.apple.com/kb/DL1746

@jwojda, do you host your own ASUS?

By default it downloads new updates every day at 3am.

But you can change that. We have our replica's updating every Saturday at 10PM. These replica's replicate all updates via our master ASUS. This in turn replicates all updates every Sunday at 10PM.

Our clients then cache updates every Wednesday... So if a "bad" update is released, we have a week to turn off the master ASUS... That way the replicas never get it & neither do the clients.

Once an update has been corrected, we re-enable the master ASUS & the replicas will pull down as per the schedule.

I have Software Updates enabled on the 10.9.3 servers. But each server is acting as an standalone, they don't replicate between themselves.

@jwojda.. Ah.

Looks like i need to update my blog, but the post on how to do this for 10.8 is below... I think it's now in the app bundle in 10,9.

http://macmule.com/2013/12/16/managing-apple-software-update-server-across-multiple-servers-10-8/

Terms & ConditionsCookie settingsAccessibility statement