Deploy a macOS High Sierra Update Package with a Fileset (Legacy)
Description
This is a historical workaround for macOS High Sierra 10.13.1 to 10.13.2 and FileWave engineering issue FW-19993 from 2017. Do not use it as the general workflow for current macOS updates. See Software Updates (Apple) for current guidance.
What the legacy workflow does
The affected FileWave serverreleases automaticallycould pullsdownload OSApple update catalogs and expose updates through Software Update CatalogsFilesets, forbut computersFW-19993 prevented some High Sierra and theseiTunes arepackages madefrom availableinstalling through the ‘New Desktop Fileset’. To prevent unwanted updates being installed on incorrect machines, we would recommend using the Software Update DesktopAssistant. Filesets.
As of December 13, 2017, we are aware of one particular issue (logged as engineering ticket FW-19993) that will prevent successful installation of certain macOS patchworkaround packages ("macOS 10.13.2 Update" and "iTunes" have been confirmed to be affected) using the recommendedApple Softwareinstaller Update Assistant. As such, it may be necessary to createin a manual filesetFileset toand deployruns theseit updates. with an Activation Script.
Directions
Historical
Theprocedure
steps to follow are:
PullDownload therelevantrequiredinstaller downupdate fromApple’sApplesupport site:https://support.apple.comSupport.- Create an empty
file setFileset. PlaceAdd thepkginstallerwithinpackage to thefilesetFileset.- Create an Activation Script
tothattriggerruns theinstallationpackage installer.
Example:
High Upgrading a 10.13.1 computer toSierra 10.13.2
example
DownloadFor thea deltacomputer ‘macOSUpd10.running High Sierra 10.13.2.pkg’ from: https://support.apple.com/kb/DL1946
(Alternatively,1, download the macOS High Sierra 10.13.2 delta update. Apple also retains the 10.13.2 combo updater from: https://support.apple.com/kb/DL1944update).
DropOpen the downloaded disk image, then add macOSUpd10.13.2.pkg intoto an Emptyempty Fileset. Fileset Inwith thisa exampledestination weof are going to use /private/var/. tmp,tmpas thisThat directory is naturallynormally cleanedcleared out onduring a reboot. restart. ChangeSet the package verification to ‘Ignore at Verify’Verify.
Create the following script and add it as an Activation Script:
#!/bin/bash
# Edit the path/file to match the installer that you have downloaded
installer -pkg /private/var/tmp/macOSUpd10.13.2.pkg -target /
Configure the Activation Script should be set as:with:
- Execute once when activated
- Wait for execution > Infinite
TheDeploy filesetthe can now be associatedFileset to a test machines. We would recommend testing on virtual machines,machine sinceor onceother successfullydisposable updatedpilot youfirst. willAfter a successful update, that computer no longer berepresents ablethe original 10.13.1 test state.
After verifying the installation and restart behavior, expand the deployment only to testthe onHigh Sierra computers that devicerequire ifthis youhistorical wish to re-run the test.package.
Once satisfied it is working as expected, you may now associate to a broader range of machines.