Create AutoPkg Filesets in FileWave

What

FileWave's integrated AutoPkg workflow creates Apple Filesets from a curated software catalog. Administrators can search the available recipes, create a Fileset, choose a version strategy, and deploy it without running a separate AutoPkg service.

Fileset properties control whether a supported recipe uninstalls the software when its Deployment becomes inactive. Revision settings can track the latest recipe version or hold a specific version until an administrator chooses to move forward.

Traditional AutoPkg installations can add recipe repositories on a macOS host. FileWave instead exposes a curated set of repositories. This reduces repository sprawl, but it also means the integrated catalog may not contain every product available to a standalone AutoPkg workflow.

Use the integrated catalog for common recipes and a controlled version workflow. For custom repositories or recipes outside that catalog, use a standalone AutoPkg workflow and import the resulting package as a PKG Fileset.

When/Why

When to Use

Use the integrated workflow when the required software is available in the curated catalog and you want FileWave to manage its recipe versions. Use standalone AutoPkg when you need custom repositories, recipe overrides, or software not offered in the integrated catalog.

Why This Feature Matters

The curated repository set gives FileWave administrators a consistent catalog and removes the need to maintain a separate AutoPkg host for supported recipes. Version controls let a Fileset follow the latest catalog revision or hold a selected version until testing and change control are complete.

The curated catalog limits repository choices, but administrators should still inspect the Recipe URL, verify the package source, and pilot installation and removal before broad deployment.

How

Creating an AutoPkg Fileset:

Create the AutoPkg Fileset from FileWave Central, inspect its recipe source, choose the version strategy, and test installation and removal behavior before broad deployment.

• Create a new Fileset, select Apple, and choose AutoPkg as the type:

• Search for the software. Catalog entries may not include a description, so inspect the Recipe URL to identify the source and review the recipe before creating the Fileset.

• Create a Deployment. Select latest when the Fileset should follow new catalog revisions, or select a specific version when upgrades must remain administrator-controlled.

• In Fileset Properties, enable Uninstall when made passive only when the recipe includes a tested uninstall script and removal is the intended result.
  

Test removal before broad deployment. The passive-uninstall option works only when the recipe author included a functional uninstall script. Verify the result on a pilot device before relying on it for software removal.

Related Content

• AutoPkgr with FileWave

Digging Deeper

Your FileWave Server will make requests to le7bqzikha.execute-api.us-east-1.amazonaws.com in order to create Filesets with this integration. It is important that if you run your own FileWave Server that it be able to reach that host if you want to take advantage of the integrated AutoPkg functionality.