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.

ChooseEarly theAccess workflowbaseline: byThe Early Access program now assumes FileWave Server and Client version. FileWave 16.4.0 or later. All current and laterfuture Early Access releases build macOS and Windowscustom enrollment packages directly in FileWave Central. Earlier FileWave Server versions continue using the externalExternal Early Access custom-client builders untilare no longer part of this workflow.

Enable the ServerEarly isAccess upgraded.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

SituationTaskUse this workflow
BuildInstall a new macOSclient, reinstall a client, or Windowstest an enrollment installer on FileWave Server 16.4.0 or laterUseBuild integratedand download the custom package management infrom FileWave Central > Preferences > Mobile.
Build an Early Access enrollment installer for a FileWave Server earlier than 16.4.0Use the external Early Access custom-client builders listed below.
Upgrade an existingenrolled FileWave Client already running 16.3.0 or laterUse Software Updates > Client Upgrades and schedule the integratedBeta clienttarget upgradefrom workflow.the Doright-click not deploy an Upgrade Fileset.menu. Upgrade an existingenrolled FileWave Client earlier than 16.3.0Use the applicable macOS or Windows Client Upgrade Fileset asto the bridge toreach the integrated upgrade baseline.

FileWaveBuild 16.4.0an andEarly later:Access buildenrollment packagespackage in Central

When

aConfirm that FileWave 16.4.0Central orshows laterBETA Server is configured forin the Earlywindow Access/Beta package channel, the integrated macOStitle and Windowsbottom-right packagestatus sources can use the matching Early Access packages.
    Configure the Server for Early Access packages as described in Enable Early Access (Beta) Package URLs.area. InOpen FileWave Central,Central open> Preferences > Mobile. Select macOS or Windows. Select Show settings and review the enrollment-package configuration. Select Build macOS client package or Build Windows client package. After the build completes, use the corresponding Download button to obtain the installer. 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 manualcontrolled deployment testing. UseDo thenot integrateddeploy a custom PKG or MSI over an already enrolled client as its upgrade workflowpath.

    for

    Upgrade existing clients already running FileWave 16.3.0 or later.

    Servers earlier than 16.4.0: externalduring Early Access builders

    During Early Access, FileWave Servers earlier than 16.4.0 continue using these build links:

      macOS: Early Access macOS custom-client builder Windows: Early Access Windows custom-client builder

      Use the version that matches the intended deployment. Early Access builds may not be available immediately for every version. If the beta builder reports unsupported status for a build FileWave directed you to test, confirm the version and proceed under the Early Access guidance provided with that test.

      Existing client upgrades

      Clients running FileWave 16.3.0 or later

      Upgrade through FileWave's integrated client upgrade workflow inUse Software Updates > Client Upgrades. The FileWave 16.4 Upgrade Filesets are designed to return requirements not met on these clients so the legacy Fileset does not replace the integrated upgrade mechanism.

      When targeting an Early Access/Beta client, do not useSchedule the toolbarBeta schedulingtarget button.from the right-click menu. Select the eligible client or group, right-click it, and choose Schedule Beta Upgrade. The toolbar scheduling action schedulestargets 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 auditaudit, 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.

      Upgrading your On-Premise FileWave ServerClients

      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.

      Back to top