Skip to main content

Building Custom Clients During Early Access

Description

Use this article to build custom macOS and Windows FileWave Client enrollment installers while participating in the FileWave Early Access Program. Early Access, also called Beta, provides supported pre-release packages for customers validating an upcoming FileWave release.

Early Access baseline: The Early Access program now assumes FileWave Server 16.4.0 or later. All current and future Early Access releases build custom enrollment packages directly in FileWave Central. External Early Access custom-client builders are no longer part of this workflow.

Enable the Early Access package channel first. Self-managed customers must complete Enable Early Access (Beta) Package URLs on the FileWave Server. FileWave Operations handles this server-side configuration for hosted environments enrolled in Early Access. Confirm that FileWave Central shows BETA before building or scheduling Beta packages.

Choose the correct package or upgrade path

TaskUse this workflow
Install a new client, reinstall a client, or test an enrollment installerBuild and download the custom package from FileWave Central > Preferences > Mobile.
Upgrade an enrolled FileWave Client already running 16.3.0 or laterUse Software Updates > Client Upgrades and schedule the Beta target from the right-click menu.
Upgrade an enrolled FileWave Client earlier than 16.3.0Use the applicable macOS or Windows Client Upgrade Fileset to reach the integrated upgrade baseline.

Build an Early Access enrollment package in Central

  1. Confirm that FileWave Central shows BETA in the window title and bottom-right status area.
  2. Open FileWave Central > Preferences > Mobile.
  3. Select macOS or Windows.
  4. Select Show settings and review the enrollment-package configuration.
  5. Select Build macOS client package or Build Windows client package.
  6. After the build completes, use the corresponding Download button to obtain the installer.
  7. Enable Keep the package up to date when FileWave should rebuild the enrollment package after future Server upgrades.

These are enrollment packages, not the upgrade mechanism for enrolled clients. Use them for new installations, reinstalls, and controlled deployment testing. Do not deploy a custom PKG or MSI over an already enrolled client as its upgrade path.

Upgrade existing clients during Early Access

Clients running FileWave 16.3.0 or later

Use Software Updates > Client Upgrades. The FileWave 16.4 Upgrade Filesets return requirements not met on these clients so the legacy Fileset does not replace the integrated upgrade mechanism.

Schedule the Beta target from the right-click menu. Select the eligible client or group, right-click it, and choose Schedule Beta Upgrade. The toolbar scheduling action targets the non-Beta upgrade.

Clients earlier than FileWave 16.3.0

Use the applicable macOS or Windows Client Upgrade Fileset to bring the client to the integrated upgrade baseline. Clients earlier than 16.3.0 do not appear in Client Upgrades, so All Clients Up to Date does not account for them. If a FileWave 16.4 Upgrade Fileset is unavailable for the legacy version being upgraded, deploy the FileWave 16.3 Upgrade Fileset first, then continue with the integrated workflow.

See Upgrading FileWave Clients for the complete inventory audit, Upgrade Fileset bridge, and illustrated scheduling workflow.

The Upgrade Fileset may also be used as a support-directed recovery path during Early Access testing. Do not modify its requirement checks unless FileWave Support provides a specific recovery procedure.

Support

If you encounter issues or require assistance, contact Customer Technical Support through your standard support channels. Feedback during Early Access helps FileWave validate upgrade and enrollment workflows before general availability.

No comments to display

Back to top