Skip to main content

Building Custom Clients During Early Access

Description

Use this article to build custom FileWave Client installers duringwhile participating in the FileWave Early Access Program. Early Access, also called Beta, provides supported pre-release resourcespackages for customers testingvalidating an upcoming FileWave releases.release.

Choose the workflow by FileWave Server and Client version. FileWave 16.4.0 and later build macOS and Windows enrollment packages directly in FileWave Central. Earlier FileWave Server versions continue using the external Early Access builders until the Server is upgraded.

CustomChoose the correct package or upgrade path

SituationUse this workflow Build a new macOS or Windows enrollment installer on FileWave Server 16.4.0 or laterUse integrated package management in 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 existing FileWave Client already running 16.3.0 or laterUse the integrated client upgrade workflow. Do not deploy an Upgrade Fileset. Upgrade an existing FileWave Client earlier than 16.3.0Use the applicable Client Upgrade Fileset as the bridge to the integrated upgrade baseline.

FileWave 16.4.0 and later: build linkspackages in Central

When a FileWave 16.4.0 or later Server is configured for the Early Access/Beta package channel, the integrated macOS and Windows package sources can use the matching Early Access packages.

    Configure the Server for Early Access packages as described in Enable Early Access (Beta) Package URLs. In FileWave 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 package after future Server upgrades.

    These are enrollment packages, not the upgrade mechanism for enrolled clients. Use them for new installations, reinstalls, and manual deployment testing. Use the integrated client upgrade workflow for clients already running FileWave 16.3.0 or later.

    Servers earlier than 16.4.0: external Early Access builders

    During the Early AccessAccess, period,FileWave useServers theearlier followingthan links16.4.0 tocontinue using these build custom clients:links:

    Note:Use the version that matches the intended deployment. CustomEarly clientAccess 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 duringand proceed under the Early Access window.guidance Ignoreprovided unsupported-statuswith messagesthat showntest.

    by the beta build system when you have been directed to use the Early Access build; these builds are supported for Early Access testing. Make sure you select the

    Existing client version that matches your intended deployment.

    Client upgrades are a separate path

    Custom client installers are useful for new installs, reinstalls, and manual deployment testing. For upgrading existing macOS and Windows clients during the FileWave 16.4 Early Access cycle, keep the Client Upgrade Filesets in your plan.

    Clients running FileWave Client16.3.0 16.2or needlater

    a Client

    Upgrade Fileset path before they can continue through theFileWave's newerintegrated automatic/integratedclient upgrade path.workflow. TheFileWave 16.4 Client Upgrade Filesets are designed to return requirements not met on these clients alreadyso runningthe legacy Fileset does not replace the integrated mechanism.

    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. If a FileWave 16.4 Upgrade Fileset is unavailable for the legacy version being upgraded, deploy the FileWave 16.3 orUpgrade later,Fileset whilefirst, stillthen providingcontinue with the integrated workflow.

    The Upgrade Fileset may also be used as a bridgesupport-directed forrecovery olderpath clients.

    Your Hosted FileWave Server Has Been Upgraded—What Are Your Next Steps? Upgrading your On-Premise FileWave Server

    Support

    If you encounter issues or require assistance, contact Customer Technical Support through your standard support channels. Feedback during Early Access helps improve the FileWave experiencevalidate forupgrade alland customers.enrollment workflows before general availability.

    Back to top