Enable Early Access (Beta) Package URLs

Description
Starting with FileWave 16.4.0, self-managed Early Access customers can enable Beta package URLs on the FileWave Server. Early Access, also shown as Beta in FileWave Central, allows package sources that use the server runtime environment to access Beta packages, including Integrated Custom Package and Integrated Client Upgrade package sources.
Use this only for FileWave Early Access/Beta testing when directed by FileWave. Early Access packages are intended for validation before general availability.
This setting is changed on the FileWave Server. Self-managed customers need shell access to the server. Hosted FileWave customers should open a Technical Support case so FileWave Operations can handle the hosted-server Early Access process.
Plan Server, Booster, and client upgrades
Enabling Beta package URLs means the environment is opting into Early Access/Beta upgrade sources, not just changing the label shown in Central. After this setting is enabled, FileWave Server uses Early Access/Beta URLs for Server upgrade packages, Boosters become eligible for Beta Booster upgrade packages, and package sources that use the server runtime environment can access Beta packages.
Client upgrades during 16.4 Early Access
At least during the FileWave 16.4 Early Access cycle, keep the macOS and Windows Client Upgrade Filesets in your client-upgrade plan. The newer integrated client upgrade path depends on the client already being at the newer upgrade baseline.
For example, clients running FileWave Client 16.2 need a Client Upgrade Fileset path first. Without a 16.4 Client Upgrade Fileset, you would first deploy a 16.3 Client Upgrade Fileset and then let the automatic/integrated upgrade path continue from there.
The 16.4 macOS and Windows Client Upgrade Filesets are designed to return requirements not met on devices that are already running FileWave Client 16.3 or later, so they can act as a bridge for older clients without replacing the integrated upgrade behavior for clients that already meet the newer baseline.
The Client Upgrade Fileset also remains a support-guided fallback during Early Access testing. If the integrated client upgrader does not behave as expected, FileWave Support may direct you to import the Client Upgrade Fileset and adjust its requirement check for a specific recovery path.
After a FileWave Server upgrade, compatible Boosters are automatically scheduled for upgrade. By default, that automatic Booster upgrade is scheduled 7 days after the Server upgrade. For Early Access testing, set the automatic Booster upgrade delay to 0 days before upgrading the Server if you want Boosters to upgrade immediately instead of waiting the default week.
That delay is controlled in FileWave Central > Preferences > General. The setting is evaluated when the Server upgrade schedules Booster upgrades, so changing it afterward does not retroactively reschedule Boosters that were already queued.
For the Booster behavior and screenshots, see Upgrading Multiple Boosters.
Enable Early Access package URLs
On the FileWave Server, edit the environment file:
/usr/local/etc/filewave/.env
Add this line on its own line:
RUNTIME_ENVIRONMENT=beta
Save the file.
Restart FileWave Server so the runtime environment is loaded:
sudo fwcontrol server restart
Confirm FileWave Central is using Beta
When Central connects to a server using the Beta runtime environment, FileWave Central shows BETA in the window title and in the bottom-right status area. Clicking the BETA indicator opens this article.
Disable Early Access package URLs
Remove this line from 
/usr/local/etc/filewave/.env:
RUNTIME_ENVIRONMENT=beta
Save the file.
Restart FileWave Server again:
sudo fwcontrol server restart
Related articles
What is the Early Access Program?
Building Custom Clients During Early Access
Upgrading Multiple Boosters
Notes
Early Access and Beta refer to the same testing channel in this context.
The server restart is required after enabling or disabling the flag because FileWave Server reads the runtime environment during startup.
The short link for this article is https://go.filewave.com/beta.