Your Hosted FileWave Server Has Been Upgraded - What Are Your Next Steps?

Use this workflow only if the automatic upgrade is unavailable, you previously declined it, or FileWave Support or the release notes direct you to install Central manually.

1. Open the FileWave Downloads page and select the FileWave version running on the Server.
2. Expand macOS Downloads or Windows Downloads.
3. Download macOS Admin or Windows Admin for your workstation.
4. Run the PKG or MSI and follow the installer prompts. You do not need to uninstall the existing version first.
5. Launch FileWave Central and reconnect to the upgraded Server.

The next step once the FileWave Central/Admin application is upgraded is to launch the Central/Admin application to connect to the newly upgraded server. After an upgrade, you always want to connect to the server and verify everything is running and working correctly. This will allow you to spot any issues quickly and, if necessary, contact our FileWave Support Team for assistance.

Do not hesitate to contact our Support Team quickly if you think there may be an issue as that will help us get you back up and running as quickly as possible.

1. Check the warning light in the bottom left-hand corner. You are looking for it to say "Everything is OK" as shown below. If you see the light as yellow or red please select the message to view the error. If you’re unsure how to resolve an error, please contact Support.

   

2. Make sure Filesets are showing. Select the Filesets tab and make sure you see your Filesets and structure. If you are having issues contact our support team. 

3. If you have iOS devices, Select "iOS Inventory" to make sure you see rows of iOS device information. Also, select "Refresh" from the top menu to make sure this information refreshes. While in this tab as well please select an iOS device you know is on to make sure it is trying to check in. If you receive any errors or information is not showing please contact our Support team. 

4. Go to the Clients tab of the FileWave Admin and make sure you see your correct group structure and your Clients showing. Remember your FileWave Clients should still be locked so they will not be getting any changes yet. 

5. Update the Model, If this fails please contact our Support team

6. Go back to the FileWave client tab and look at one or two clients that you know are on to make sure they are checking in correctly. 
   

7. If everything looks good, move on to upgrading your Boosters and Clients if needed. 

FileWave Server 16.4 automatically schedules eligible customer-managed Boosters for upgrade after the Server upgrade. The default delay is seven days.

In FileWave Central, open Preferences > Upgrades to review or change the delay. The same pane contains the client-upgrade batch size, error threshold, and report schedule.

FileWave Central 16.4 centralizes client-upgrade controls and the automatic Booster-upgrade delay.

FileWave 16.4 validates both the reported upgrade state and the installed Booster version. Failed automatic upgrades are retried within defined limits, and one failed Booster does not cancel upgrades for the remaining Boosters.

• Use the Boosters view to monitor upgrade availability, scheduled work, and results.
• Investigate Boosters that remain below the target version or report repeated failures.
• Contact FileWave Support if a hosted upgrade leaves customer-managed Boosters unable to update.

FileWave Servers earlier than 16.4 continue to use their version-specific manual Booster upgrade workflow.

If your environment uses FileWave Network Imaging, include each Imaging Virtual Server in the post-upgrade review. The FileWave Server upgrade does not remove the need to verify the IVS version and status.

IVS 16.4.0 and later: In FileWave Central, open Preferences > Imaging to view available IVS updates, schedule an upgrade, and monitor its progress and outcome. FileWave handles the package download, installation, and required reboot.

Do not begin an IVS upgrade while image capture or deployment is active. FileWave blocks the upgrade during active imaging so those operations can finish safely.

IVS earlier than 16.4.0: Perform one final manual IVS upgrade using the version-specific package and instructions from FileWave Downloads. After the IVS reaches 16.4.0, future upgrades can be managed through Central.

• FileWave IVS 16.3.0 and later require Debian 13.
• After the reboot, confirm that Central reports the intended IVS version and healthy Imaging status.
• If a customer-managed IVS connected to a hosted FileWave Server cannot enroll or upgrade, contact FileWave Support.

See FileWave Network Imaging / IVS Overview for the complete version-aware upgrade workflow.

When the FileWave Server is running 16.4 or later, macOS and Windows clients already running FileWave Client 16.3 or later can be upgraded through Software Updates > Manage > FileWave Client Upgrades.

The integrated workflow stages upgrades in controlled batches, monitors progress, retries transient failures, pauses a target version when the configured permanent-failure threshold is reached, and provides reporting.

1. Review Preferences > Upgrades and confirm the batch size, error threshold, and report schedule.
2. Open Software Updates > Manage > FileWave Client Upgrades and select the target client version.
3. Start with a representative pilot group.
4. Monitor download, installation, retry, and failure status before expanding the rollout.

Clients running versions earlier than FileWave Client 16.3 must first use the macOS or Windows Upgrade Fileset from the FileWave Downloads page. The FileWave 16.4 Upgrade Filesets include a client-version requirement and are skipped on clients already running 16.3 or later.

1. Open the FileWave Downloads page and download the macOS or Windows Upgrade Fileset for the target FileWave version.
2. Import the downloaded .fileset into FileWave Central.
3. Deploy it to a small test group of clients running versions earlier than 16.3 and update the Model.
4. Confirm that the test clients upgraded successfully before expanding the deployment.
5. After the bridged clients reach 16.3 or later, manage future upgrades through the integrated Software Update workflow.

Each Upgrade Fileset also includes operating-system requirements. A client on an unsupported operating system remains on its original FileWave Client version.

Windows upgrade troubleshooting: If a Windows Client Upgrade Fileset does not complete, inventory does not show the new version, or the client service does not restart, see Troubleshooting Windows Client Upgrade Fileset Issues.

FileWave Kiosk for iOS and iPadOS is distributed through the Apple App Store as a VPP/Apps and Books application. Before upgrading, confirm that FileWave is synchronizing with Apple School Manager or Apple Business Manager and that enough free FileWave Kiosk licenses have been acquired.

See Automatic updating of iOS/iPadOS Kiosk for the complete workflow.

FileWave uses custom macOS and Windows client packages for initial enrollment and new installations. These packages are not the upgrade mechanism for already enrolled clients.

FileWave Server 16.4 or later

1. In FileWave Central, open Preferences > Mobile.
2. Select macOS or Windows.
3. Select Show settings and review the package configuration.
4. Select Build macOS client package or Build Windows client package.
5. After the build completes, use the corresponding Download button when you need the installer for a new deployment.
6. Enable Keep the package up to date when FileWave should rebuild the package after future Server upgrades.

FileWave Server 16.4 manages the macOS enrollment package directly in FileWave Central.

FileWave Server 16.4 manages the Windows enrollment package directly in FileWave Central.

FileWave Server earlier than 16.4

Earlier supported FileWave Server versions continue to use custom.filewave.com until the Server is upgraded to 16.4.

1. Build the required custom PKG or MSI at custom.filewave.com.
2. Download and unzip the package.
3. In FileWave Central, open Preferences > Mobile and select the applicable macOS or Windows pane.
4. Upload the unzipped installer, wait for the successful-upload message, then select OK.
5. Update the Model when the change requires distribution.

Do not deploy either package to an already enrolled device as an upgrade. Use the client-upgrade workflow described in section 5.