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

If you’re upgrading FileWave Central (Admin) on your server and you downloaded the bundle to upgrade the server, the Central/Admin package is already downloaded and you can install it from the .dmg

1. On your macOS workstation go to the Knowledge Base → Downloads and select the most recent version of FileWave 
   FileWave Downloads Page

   

2. You will then scroll down on the page until you see "macOS Downloads" and expand the section. Select and download “macOS Admin”

   

3. Double-click on the downloaded PKG to launch the installer and follow the install instructions on the screen. 

4. Once the installation finishes, you are ready to connect to your FileWave Server using FileWave Central (FileWave Admin).

If you’re upgrading FileWave Central (Admin) on your server and you downloaded the bundle to upgrade the server, the Central/Admin package is already downloaded and you can install it from the .msi

1. On your Windows workstation, go to the Knowledge Base → Downloads and select the most recent version of FileWave 
   FileWave Downloads Page

   

2. You will then scroll down on the page until you see "Windows Downloads" and expand the section. Select and download “Windows Admin”

   

3. Double-click on the downloaded Windows Installer to launch the installer and follow the install instructions on the screen. 

4. Once the installation finishes you are ready to connect to your upgraded FileWave Server using FileWave Central (FileWave Admin). 

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. 

TheFileWave processServer of16.4 upgradingautomatically schedules eligible customer-managed Boosters isfor similarupgrade to upgradingafter the Central/AdminServer applicationupgrade. asThe itdefault doesdelay notis requireseven you to back up your FileWave Booster before the upgrade or uninstall the existing version. Starting with FileWave 14.4.0, you can upgrade the Boosters inside Admin. If your Boosters are not on 14.4.0 yet, download the installers directly on the Booster to install.days.

In FileWave CentralCentral, (FileWaveopen Admin),Preferences go> Upgrades to review or change the Boosters tab.delay. The simplestsame waypane to upgrade multiple boosters is to usecontains the "Upgradeclient-upgrade Allbatch Boosters"size, buttonerror inthreshold, theand toolbarreport of the Boosters section of the native console:schedule.

ItFileWave automaticallyCentral schedules16.4 allcentralizes boostersclient-upgrade to upgrade. Alternatively, you can select multiple boosterscontrols and usethe automatic Booster-upgrade delay.

FileWave 16.4 validates both the context menu or toolbar button toreported upgrade them.

To trackand the progressinstalled ofBooster upgradingversion. multipleFailed boosters,automatic youupgrades canare useretried within defined limits, and one failed Booster does not cancel upgrades for the newremaining BoosterBoosters.

Ifearlier onethan 16.4 continue to use their version-specific manual Booster fails to upgrade, all remaining Boosters will cancel their scheduled upgrade to prevent any issues.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.

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

macOSalready clientrunning upgrade16.3 filesetor later.

1. On your workstation go toOpen the Knowledge Base → Downloads and select the most recent version of FileWave 
   FileWave Downloads Pagepage

   

   and download the macOS or Windows Upgrade Fileset for the target FileWave version.

2. Scroll down on the page until you see "macOS Upgrade Fileset" and select it. This will download a pre-made .fileset file that you can easily deploy to your devices without any modification.

   

Open your FileWave Central/Admin application and go to the Filesets tab. 

Drag and dropImport the downloaded Fileset.fileset into theFileWave Filesets tab. This will automatically create a Fileset in FileWave. We highly recommend dragging it into the root level of the Filesets structure so that it is not accidentally associated without being tested. 

Once it is in FileWave you should associateDeploy it to a handfulsmall test group of testclients devicesrunning asversions youearlier wouldthan for any other Fileset in FileWave and Update the model. 

After you’ve confirmed that the tested Clients upgraded successfully, associate to all macOS Clients16.3 and update the model.Model.

Each upgradeUpgrade Fileset hasalso Requirementsincludes foroperating-system compatiblerequirements. versions of macOS. If aA client ison tooan oldunsupported tooperating supportsystem your version of FileWave, it will fail and remainremains on theits original version.

Windows client upgrade fileset

On your workstation go to the Knowledge Base → Downloads and select the most recent version of FileWave
FileWave Downloads Page

Scroll down on the page until you see "Windows Upgrade Fileset" and select it. This will download a pre-made .fileset file that you can easily deploy to your devices without any modification.

Open your FileWave Central/Admin application and go to the Filesets tab. 

Drag and drop the downloaded Fileset into the Filesets tab. This will automatically create a Fileset in FileWave. We highly recommend dragging it into the root level of the Filesets structure so that it is not accidentally associated without being tested. 

Once it is in FileWave you should associate it to a handful of test devices as you would for any other Fileset in FileWave and Update the model. 

After you’ve confirmed that the tested Clients upgraded successfully, associate to all Windows Clients and update the model. You can remove any old client upgrade Filesets after the new one is associated.

Each upgrade Fileset has Requirements for compatible versions of Windows. If a client is too old to support your version of FileWave, it will fail and remain on the originalClient version.

Windows upgrade troubleshooting: If thea Windows Client upgradeUpgrade filesetFileset does not complete, the client versioninventory does not updateshow inthe inventory,new version, or the client service does not restart, see Troubleshooting Windows Client Upgrade Fileset Issues.

FileWave Kiosk onfor iOS /and iPadOS is nowdistributed deployed fromthrough the Apple App Store as a VPP / VPP/Apps and Books app.application. Before upgrading, makeconfirm surethat FileWave is syncingsynchronizing with ASM/ABMApple School Manager or Apple Business Manager and that enough free FileWave Kiosk licenses have already been acquired.

See ReadAutomatic Moreupdating of iOS/iPadOS Kiosk) for the complete workflow.

FileWave uses custom macOS DEP and Windows MDM:client Upgradepackages Clientfor Packages

When a macOS device finishes DEPinitial enrollment intoand FileWave,new yourinstallations. serverThese sendspackages aare singlenot clientthe installerupgrade package.mechanism Whenfor youalready updateenrolled yourclients.

FileWave toServer a16.4 neweror one, you may also update this package.later

1. In FileWave Central, open Preferences > Mobile.

Visit

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 anduntil buildthe aServer newis upgraded to 16.4.

Once downloaded,and unzip the download

ThenFileWave visitCentral, theopen admin preferences and upload the package into the appropriate tab.

macOS DEP:

Windowsthe MDM

Browsewait for the downloadedsuccessful-upload andmessage, unzippedthen installer

Wait forUpdate the messageModel thatwhen itthe ischange uploaded.

PressDo OKnot deploy either package to savean andalready finishenrolled device as an upgrade. Use the client-upgrade workflow described in section 4.