FileWave Official Version Support

FileWave development teams officially support two major versions at any time, N and N-1. For example, If we assume that the most recent version of FileWave is 14.9.x, then we will officially support versions 14.9.x and 14.8.x. Releases for major versions of FileWave occur roughly every quarter.

What does "officially support" mean? Officially supporting these versions means that we will investigate bug reports in these versions and patch issues that are significant. We will not produce patches for earlier versions than N-1, as this means allocating development resources to problems that are already potentially resolved instead of investing those resources into furthering the product. In short, if an issue is found in a version earlier than the officially supported versions, then remediation for the issue will be in the form of an application upgrade, or a patch to that more recent version.

This does not mean that you can't contact our support teams about an earlier version. They will, to the best of their ability, help you with older versions of the software but they will stop short of escalating tickets to our development teams and will likely recommend an upgrade so that you are getting the latest features and bug fixes.

A note on the Compatibility charts:  There are several states of compatibility for FileWave clients:  

• "Compatible" (the first table) indicates that we have run QA regression tests against these operating system versions, and they are fully supported
• Not being on the Compatibility chart (such as macOS 11) does not mean that platform is not supported...it just means we did not actively test against it, but we do expect it to function
  • Support of any issues experienced specifically on these platforms would be considered on a case-by-case basis (but these cases are exceedingly rare)
• "Legacy" versions mean that we don't test, but we do provide a retro-version of a client so that the device can still report in  
  • There is NO support for these platforms beyond the availability of the older client, and in almost all cases these are for OSes that are no longer supported by the developer in question
• Lastly, items do fall out of support, such as Windows XP and probably soon the older Android APK client as examples, but we always include these items in our release notes

An additional note on third-party software inclusion, such as TeamViewer:

• Partnerships we have with third party providers have their own set of system requirements for those released applications.  We test against their most recent versions, and support of those applications is limited to third-party vendor specifications. 

Fully Tested by QA

• macOS 12, 13 (Intel and Apple Silicon)
• Linux CentOS 7.9 x86_64

Expected to work

• macOS 10.15, 11 (Intel and Apple Silicon)

Fully Tested by QA

• macOS 12, 13 (Intel and Apple Silicon)
• Windows 10 (Ent/Pro 21H1 and above), 11 (Ent/Pro 21H2 and above)
  

Expected to work

• macOS 10.15, 11 (Intel and Apple Silicon)

Legacy

• macOS 10.11 → Legacy Version 13.1.5
• macOS 10.12 → Legacy Version 14.0.2
• macOS 10.13 → Legacy Version 14.5.4
• macOS 10.14 → Legacy Version 14.8.0
  

Fully Tested by QA

• iOS 15, 16
• iPadOS 15, 16
• tvOS 15, 16
• Android 12, 13 (EMM Client)
• Chromebook
  

Expected to work

• iOS 13, 14
• Android 8 to 11 (APK/EMM)
  

Legacy

• iOS 10, 11, 12 → Legacy Version 13.1.5
• Android 4 to 7 (APK) → Legacy Version 13.2.3
  

Fully Tested by QA

• macOS 12, 13 (Intel and Apple Silicon)
• Windows 10 (Ent/Pro 21H1 and above), 11 (Ent/Pro 21H2 and above)

Expected to work

• macOS 10.15, 11 (Intel and Apple Silicon)

Fully Tested by QA

• macOS 12, 13 (Intel and Apple Silicon)
• Windows 10 (Ent/Pro 21H1 and above), 11 (Ent/Pro 21H2 and above)
• Linux CentOS 7.9 x86_64

The FileWave Imaging Virtual Server (IVS) is a special appliance that provides imaging support for Windows 10 and 11 UEFI and non-UEFI devices.

The IVS appliance is CentOS 7.9 based and can be run on:

• VMWare VSphere ESX installations
• VMWare Fusion
• VMWare Player and Workstation
• Virtual Box

Historically the imaging appliance also supported macOS imaging, but the process for imaging Macs has changed from macOS 10.13.  If you are interested in imaging macOS devices, please read the Imaging in the age of High Sierra article for macOS 10.13 (and beyond) support.

• Deployments in FileWave Central: 

  • Deployments are now visible in Native Admin Console. Deployments are mostly read-only in this release: it is possible to delete deployments, but not to edit existing ones or create new deployments.

• Force reboot:
  • There is a new option for reboot for a Fileset to forcibly restart the client 2 minutes after the Fileset has been installed. This should be used only when required because open documents may not be saved.
    
    

    

    
    
• Help Menus:
  • In Anywhere and Central, the Help menus now include links to the KB, Foundry, Discord, and Alliance Forums.
• Quality/Stability:
  • A great deal of extra effort was placed this go-round on correcting some long standing bugs and defects that we hadn't been able to get to prior. 

• Customized Wallpaper:
  • It is now possible to add a text overlay on top of iOS / iPadOS wallpaper; the text can be parameterized with any inventory variable. ( Customizing iOS Device Wallpaper with Dynamic Text )

• Force reboot as mentioned in the FileWave Management Suite section.
• Login and Background Items settings has been added to Login Items Profile.
  
  

  

  
  

• Force reboot as mentioned in the FileWave Management Suite section.

• FileWave Networking Imaging 14.10.x brings compatibility with FileWave 14.10.x.
• PXE Kernel: 5.19.9
• Grub: 2.06
  

The following features are deprecated in FileWave 14.10.1 and will be removed in a future version:

• Device Discovery (Network Scanning) function of FileWave Boosters
  • Reason: This tool was never effective in production environments, has hardly ever been used, and is easily replaced by any off-the-shelf network scanning tool
• ZMQ based features for clients running 14.7 or older
  • Reason: ZMQ has been replaced by NATS, so older client devices must be updated to use the new notification framework 
• Android device management prior to Android EMM (using APKs, etc)
  • Reason: Android EMM is the replacement for the much older method of managing Android devices

 features are still functional in a current release, but will no longer be updated and in future will be removed.

Fixes in 14.10.1:

• FWRD-2848 Fixed an issue where text overlay on iPad WallPaper would be removed after a verify

Fixes in 14.10.0:

• CBD-600 Fixed an issue where "check_connections" management command could not report issues with Apple APN service
• FWRD-274 A bug regarding the TeamViewer integration has been fixed.
• FWRD-275 Fixed an issue where unattended TeamViewer access did not work in case the TeamViewer ID of the client had changed
• FWRD-336 Addressed an label issue in profile editor
• FWRD-337 A bug has been fixed, where the script editor in "Payload Contents" was closed after a file upload.
• FWRD-339 A bug has been fixed, where "No Data" was shown in the background
• FWRD-340 A bug has been fixed, where configuration policy could be duplicated
• FWRD-341 A bug has been fixed, where default columns ID in devices view could not be checked
• FWRD-362 Fixed an visual issue, where double scrollbars where shown
• FWRD-495 A bug has been fixed, where pinned columns where not removed correctly
• FWRD-498 Fixed an issue where certificate could not be uploaded for Apple profiles
• FWRD-595 A bug has been fixed in payload view, where priority column was not displayed correctly.
• FWRD-596 A bug has been fixed, where multiple clients with the same Device Name could not be added in DEP Clients
• FWRD-647 Fixed an issue related to sort order of "Status" column for Fileset report
• FWRD-653 Improved consistency of enrollment process
• FWRD-729 Deployment visibility now consistent with permissions
• FWRD-731 A bug has been fixed, where setup grafana and prometheus could fail
• FWRD-778 A critical bug has been fixed, where a admin with read only permission could edit smart groups
• FWRD-783 A critical bug has been fixed, where custom prometheus scrape targets stop working
• FWRD-801 Fixed an issue where loading Deployment view in FileWave AnyWhere could be very slow
• FWRD-821 A bug has been fixed concerning discard modal behavior
• FWRD-975 A bug has been fixed, where the status of verify command was shown incorrectly.
• FWRD-1118 A bug has been fixed where grafana updates cause issues
• FWRD-1139 Adressed an issue in patch detail view
• FWRD-1140 A security issues has been adressed
• FWRD-1141 The function "Copy in the Same Group" has been improved.
• FWRD-1144 A bug has been fixed in devices view, where "no actions" where not shown depending on admin permissions
• FWRD-1148 Improved error message when creating a payload, while another admin blocks it.
• FWRD-1150 A bug has been fixed, where conditions could not be added in a new workflow
• FWRD-1152 A bug has been fixed, where columns where unchecked in reports view
• FWRD-1157 A bug has been adressed, where web admin selected a verification mode for filesets.
• FWRD-1159 A bug has been fixed, where a confirmation modal when switching "Kiosk Self-Service" to "Direct Installation" was not shown.
• FWRD-1165 A bug has been fixed, where an admin without any permission could start Importing CSV files
• FWRD-1166 A bug has been fixed in reports, where changing the main component while editing lead to a wrong result
• FWRD-1169 Performance improvements in Payloads
• FWRD-1171 Fixed serveral issues with the restart device modal in device view.
• FWRD-1172 A bug has been fixed, where an admin could not see "Payload actions" and "Priority" in Payload Info
• FWRD-1173 Adressed an issue for long titles in software updates
• FWRD-1174 Improved save button behavior in payload configuration
• FWRD-1176 A bug has been fixed, where the app threw an error during creating of an report or workflow.
• FWRD-1177 A bug has been fixed, where a smart group with an empty condition was broken.
• FWRD-1179 A bug has been fixed, where 0 was not a valid value in geofencing payloads.
• FWRD-1180 A bug has been fixed, where a DEP Profile could not be saved.
• FWRD-1181 Addressed an label issue in deployments
• FWRD-1190 if you have no rights to perform device actions, the device actions drop down will be hidden now.
• FWRD-1198 A bug has been fixed where the FileWave client did not allow users to modify files in the All Users folder on Windows
• FWRD-1199 An inconsistency issue between headline sizes has been addressed.
• FWRD-1200 A bug has been fixed, where the smart group preview displayed only the name of devices in Anywhere
• FWRD-1230 Improved Notification descriptions in Profile Editor
• FWRD-1231 Fixed an issue where Command History sort order would change automatically
• FWRD-1232 Fixed an issue where macOS MDM enrolled would not show MDM details in Client Info until native admin is restarted
• FWRD-1237 Added a default value in LDAP payloads for Account Description
• FWRD-1238 A bug has been fixed in profile editor, where the value in subject field during creation of an SCEP was not saved correctly.
• FWRD-1239 A bug has been fixed in profile editor, where exchange and network profiles could be saved at the same time
• FWRD-1240 A critical bug has been fixed, where software updates where displayed correctly
• FWRD-1241 Addressed a label issue in DNS Proxy
• FWRD-1242 Fixed an issue where Provider type would be incorrect in Per-App-VPN profile (Native admin console)
• FWRD-1243 A critical bug has been fixed in profile editor (Home screen layout), where entries where not shown at all or where not resolved correctly (object Object)
• FWRD-1244 A critical bug has been fixed in profile editor, after uploading a fingerprint file, the hex string was not shown.
• FWRD-1245 Improved Time Machine Ui
• FWRD-1246 A bug has been fixed, where switching between Exchange ActiveSync (iOS only) and Exchange Web Services (macOS only) was not recognized correctly
• FWRD-1247 Ports and other small Ui issues in macOS Server Accounts has been fixed.
• FWRD-1248 A bug has been fixed, where PayloadOrganization had an initial value
• FWRD-1273 An other bug has been fixed, where DEP profiles where not visible
• FWRD-1278 A bug has been fixed, where DEP profiles where not visible
• FWRD-1383 Fixed an issue where "Root" entry in flat client view could be updated with not-yet enrolled devices data in FileWave Central Admin
• FWRD-1431 Fixed an issue where FileWave Central would be partially translated in environments like French where only Desktop Kiosk is translated
• FWRD-1470 A bug has been fixed, where workflows could be saved without any changes
• FWRD-1476 A bug has been fixed, where DEP profiles could not be opened or assigned to workflows
• FWRD-1498 A bug has been fixed, where the Webadmin is crashing during the creation of an Apple Profile, when using the search function
• FWRD-1500 A bug has been fixed, where authenticated restart was not shown.
• FWRD-1700 A visual bug has been fixed in Profile Editor
• FWRD-1781 FileWave Client 14.8.0 crashes on Windows
• FWRD-1811 A bug has been fixed, where the handling of special characters has been improved
• FWRD-1821 A bug has been fixed, where the wrong DEP Profile was pointed to in workflows table.
• FWRD-1974 Fixed an issue where macOS Requirements would be improperly displayed when Central Admin is translated in German
• FWRD-1976 Fixed an issue where any type of file could be uploaded as Windows Client for Windows MDM in FileWave Central
• FWRD-1980 A bug has been fixed, TeamViewer page does not open in a default browser in Windows 11 22h2
• FWRD-2295 Fixed an issue where editing deployments would not be possible after a revert model
• FWRD-2348 [booster] upgrade from 14.8.0 to 14.8.1+ will not clean the wrong NATS configuration
• FWRD-2373 Fixed an issue where system file dialog could have incorrect filters when Central admin is translated in German

macOS Installers DMG (md5: 039821dc17eaf9e7dec8f5bb81169e90)
macOS Upgrade Fileset (md5: c54e88f6b85a243b1570a13639d48c0a)
macOS Admin (md5: 2bcfe84acc82c8000ddbe3c6f6655b1a)
macOS Booster (md5: c6552cceb9bf66cb125816b0b7629b0b)
macOS Server (md5: be9e54aba70fcefcacedb1065f10a3cc)
macOS Client (md5: 416405947956092fef2c48efe8822f99)

Windows Upgrade Fileset (md5: c6b77dc1f9ed017698d6e42f1ac43316)
Windows Admin (md5: 4f6e25d0cc45c9734b7f655e78b05c6f)
Windows Booster (md5: 3c1294ee99614252917a6224a09def82)
Windows Client (md5: abd4631d4b5c5e974f0f75b674cc473e)

NOTE: v14.10.1 had a bug that prevented Windows OS updates from being detected and applied. Use 14.10.3 below.

Windows Upgrade Fileset v14.10.3 (md5: 74e005a73b0255fb84747f113d8b6ed2)
Windows Client v14.10.3 (md5: 2cdbcbe8f28e31cf843ededd9f89abae)

This is a native app version of the traditional Web Clip kiosk/app portal that is sent to devices; it provides for a better end-user experience and is required for location information.

iOS 12+ : FileWave Enterprise.ipa (md5: aeb83c551c01f031896e1f26c2191bcb)
Static CDN URL :

https://fwdl.filewave.com/14.10.1/filewave/App Portal 14.10.1.ipa

The FileWave Inventory extension for Chromebook has to be installed via the Google Admin Console for your domain. Please see Quickstart Guide for Chromebooks for detailed instructions

White Labeling the Chromebook Extension (md5: c6f1be708b54feab33e4a1753a81bd45)

Linux Installers (md5: aef9beeebdbb5f2c7c9f67ed8ebf0964)
Linux Server (md5: 45f407f0c3d770227bc638e28d7dfcd9)
Linux Booster (md5: 71ea5ff487cf498dfba0ec727036c4ef)

Upgrading the FileWave Server
To install or upgrade the FileWave Server, use the following :

# login via ssh / root
$ yum update -y 
$ yum install -y --nogpgcheck https://fwdl.filewave.com/14.10.1/fwxserver-14.10.1-1.0.x86_64.rpm
$ /usr/local/filewave/python/bin/python /usr/local/filewave/django/manage.pyc flush_scheduler
$ reboot

Upgrading a Booster
To install or upgrade the FileWave Booster, use the following : 

# login via ssh / root
$ yum update -y
$ yum install -y --nogpgcheck https://fwdl.filewave.com/14.10.1/fwbooster-14.10.1-1.0.x86_64.rpm
$ reboot

Note that you can upgrade boosters centrally using the Auto-Upgrade feature within the admin console. You can find out how to do that at this KB article.

Most likely, your IVS is already at CentOS 7, and you can run the following to easily upgrade your existing IVS appliance:

# login via ssh / root
$ yum update -y
$ yum update -y https://fwdl.filewave.com/14.10.1/filewave-IVS-14.10.1-1.0.x86_64.rpm
$ reboot

If you get a response to the above command that "no packages are marked for update", then you'll need to run the below just one time on this IVS:

# login via ssh / root
$ yum update -y
$ yum install -y https://fwdl.filewave.com/14.10.1/filewave-IVS-14.10.1-1.0.x86_64.rpm
$ reboot

If the version of your IVS is still running on CentOS 6, the upgrade path requires replacing your current appliance as CentOS 6 is End of Life. Upgrade instructions are detailed here for this scenario : IVS Upgrade/Migration Options.

VMware and VirtualBox (OVA) Server Appliance (md5: 631d928114d19cc6d8e9d4f75f9aac21)
VMware and VirtualBox (OVA) Booster Appliance (md5: 3922dd2a4178bcc240eb63936712490d)
VMware and VirtualBox (OVA) Imaging Appliance (md5: 96ade18cc323951e1b7aeb8909b197cb)

For more information about importing the appliances please see: Importing FileWave Appliances

Hyper-V (VHD) Server Appliance (md5: 509fb5b67c48c05e78acb0a175146670)
Hyper-V (VHD) Booster Appliance (md5: 8c7788d0133eeabcf96aadbd893ffd7a)
Hyper-V (VHD) Imaging Appliance (md5: 593ca38cba7e060885f8d948e051b87f)