Deploy a macOS High Sierra Update Package with a Fileset (Legacy)

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 releases could download Apple update catalogs and expose updates through Software Update Filesets, but FW-19993 prevented some High Sierra and iTunes packages from installing through the Software Update Assistant. The workaround packages the Apple installer in a manual Fileset and runs it with an Activation Script.

Historical procedure

1. Download the required update from Apple Support.
2. Create an empty Fileset.
3. Add the installer package to the Fileset.
4. Create an Activation Script that runs the package installer.
5. Set up a pilot deployment. Older versions of FileWave called this an Association.
6. After the pilot succeeds, deploy only to computers that need that exact patch.

High Sierra 10.13.2 example

For a computer running High Sierra 10.13.1, download the macOS High Sierra 10.13.2 delta update. Apple also retains the 10.13.2 combo update.

Open the downloaded disk image, then add macOSUpd10.13.2.pkg to an empty Fileset with a destination of /private/var/tmp. That directory is normally cleared during a restart. Set the package verification to Ignore at 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 with:

• Execute once when activated
• Wait for execution > Infinite

Deploy the Fileset to a test virtual machine or other disposable pilot first. After a successful update, that computer no longer represents the original 10.13.1 test state.

After verifying the installation and restart behavior, expand the deployment only to the High Sierra computers that require this historical package.