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 12) 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 14, 15 (Intel and Apple Silicon)
  
• Debian 12.6 x86_64 (Note that any Debian 12.x is expected to work, and applying security updates may move you to a higher version.)
  

Expected to work

• macOS 11, 12, 13 (Intel and Apple Silicon)

Virtual Appliances

• HyperV - The images are available as Generation 1 or Generation 2
• VMWare ESX - The images require vmx-19 support which means VMWare vCenter 7.0 Update 2 is the minimum version. ( https://knowledge.broadcom.com/external/article?legacyId=2007240 )
• VMWare Fusion
• VMWare Player and Workstation
• VirtualBox

All OS must be 64bit.

Fully Tested by QA

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

Expected to work

• Windows Server 2022, Windows Server 2025
• macOS 11, 12, 13 (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
  
• macOS 10.15 → Legacy Version 15.0.1

Fully Tested by QA

• iOS 17.6, 18
• iPadOS 17.6, 18
• tvOS 17.6, 18
• Android 14, 15 (EMM Client)
• Chromebook
  

Expected to work

• iOS 14, 15, 16
• iPadOS 14, 15, 16
• tvOS 14, 15, 16
• Android 8 to 13 (EMM Client)
  

Legacy

• iOS 13 → Legacy Version 15.0.1
• iOS 10, 11, 12 → Legacy Version 13.1.5

All OS must be 64bit.

Fully Tested by QA

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

Expected to work

• macOS 11, 12, 13 (Intel and Apple Silicon)

All OS must be 64bit.

Fully Tested by QA

• Debian 12.6 x86_64 (Any Debian 12.x is expected to work.)
• macOS 14, 15 (Intel and Apple Silicon)
• Windows 10 (Ent/Pro 21H1 and above), 11 (Ent/Pro 21H2 and above)

Expected to Work

• Windows Server 2022, Windows Server 2025

Virtual Appliances

• HyperV - The images are available as Generation 1 or Generation 2
• VMWare ESX - The images require vmx-19 support which means VMWare vCenter 7.0 Update 2 is the minimum version. ( https://knowledge.broadcom.com/external/article?legacyId=2007240 )
• VMWare Fusion
• VMWare Player and Workstation
• VirtualBox

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

Virtual Appliances

• HyperV - The images are available as Generation 1 or Generation 2
• VMWare ESX - The images require vmx-19 support which means VMWare vCenter 7.0 Update 2 is the minimum version. ( https://knowledge.broadcom.com/external/article?legacyId=2007240 )
• VMWare Fusion
• VMWare Player and Workstation
• VirtualBox

End user notifications: Now, admins using FileWave Anywhere or FileWave Central can send custom messages to enrolled devices, displaying them as system notifications for users. This feature empowers administrators to communicate important information directly to users' devices, enhancing engagement and user experience. More...

Keycloak IDP integration for admin login: We’ve introduced support for Keycloak as an Identity Provider (IDP) in FileWave Anywhere and Central. Administrators can now log in using their Keycloak accounts, enhancing security and simplifying credential management.

Qt 6 Upgrade: FileWave 15.5 is now using Qt 6 open-source library, which brings better support for recent operating systems, security fixes and optimizations. On macOS, FileWave Central is now a fully universal (Intel and Apple Silicon) application, Rosetta 2 is not required anymore. It also brings better support for internal web browser thanks to updated Chromium engine. Windows components are now 64-bit only.

Add to deployment: It is now possible to easily add devices or filesets to existing (or new) deployments, using new context menu options in FileWave Central.

Dark Mode improvements: Window decoration (typically window header) is now properly following dark mode setting.

API Improvements: New public API endpoints have been introduced to facilitate external service integration. These endpoints allow users to fetch results of stored inventory queries in FileWave and execute ad-hoc inventory queries via the Preview API without saving them. The results are returned as JSON objects, with customizable page sizes to enhance flexibility. Detailed Swagger documentation is available for these endpoints, ensuring clear guidance on their usage. These updates provide seamless access to inventory data for external integrations. New APIs that are now available:

• /reports/v1/reports

• /reports/v1/reports/{id}

• /notifications/v1/notifications

New Fileset dialog:  With the addition of the different new fileset types (DDM configuration, DDM asset, Winget, Autopkg…), revisiting the New Fileset dialog was required - the new one is lean and much simpler !

FileWave Appliances: There are a few key changes for someone setting up a new FileWave Server, Booster or IVS appliance that should be noted for 15.5.0.

• HyperV images are now provided as Gen1 as well as now Gen2 allowing you to take advantage of more modern HyperV features when setting up a new appliance. Gen1 images will continue to be provided for those who need them until further notice.
• fail2ban has been added to all of the Appliance images to protect them from brute force SSH attacks. Existing images will not get this, but it can be manually added if you would like. SSH shouldn't normally be exposed to the Internet, but also some attacks can happen on a protected network by an infected host.
• When setting up a new Appliance the root user is not enabled. Instead you will login via console or SSH as "fwadmin" with a password of "filewave" and you will be forced to change the password on first login. To do actions as root you will use sudo. Existing Appliances will not be changed by filewave but you can make the same changes. 
  
  

  #!/bin/bash
  
  # Ensure the script is run as root
  if [ "$EUID" -ne 0 ]; then
    echo "Please run this script with sudo or as root."
    exit 1
  fi
  
  # Prompt for the password
  echo "Creating user 'fwadmin'."
  read -s -p "Enter password for 'fwadmin': " password
  echo
  read -s -p "Confirm password: " password2
  echo
  
  # Check if passwords match
  if [ "$password" != "$password2" ]; then
    echo "Error: Passwords do not match."
    exit 1
  fi
  
  # Create the 'fwadmin' user without a password prompt
  adduser --gecos "" --disabled-password fwadmin
  
  # Set the password for 'fwadmin'
  echo "Setting password for 'fwadmin'."
  echo "fwadmin:$password" | chpasswd
  
  # Add 'fwadmin' to the sudo group
  usermod -aG sudo fwadmin
  echo "'fwadmin' has been added to the sudo group."
  
  # Lock the root account
  passwd -l root
  echo "The root account has been locked."
  
  echo "Setup complete. You can now log in as 'fwadmin' and use sudo."

  
  

MDM Command history: MDM command history is now available in inventory, allowing troubleshooting or reporting related to MDM based features.

New "Last Changed" Field in FileWave Inventory: We've added a new "Last Changed" field in FileWave Inventory.

• "Last Changed" Field: This new field records the date and time when any custom or built-in field value is updated for a client or when the client reports to the inventory.

• Field Updates: The "Last Changed" field is also updated when a new custom field is associated or disassociated with the device.

• API Integration: The "Last Changed" field is visible in existing public inventory API responses, enabling more accurate data synchronization and integration.

This feature ensures that any changes made to client data are accurately tracked, improving workflow automation and third-party integrations.

Autopkg integration

In addition to Winget support in 15.4, Autopkg, a well-known package tool in mac admin community is now supported in FileWave:

• Not need to run Autopkg ; FileWave runs autopkg, creates packages and hosts them.

• Filesets are made available via a CDN, using private to your instance links.

• Currently, autopkg repositories are selected and curated by FileWave. Please contact us if you have suggestions for other repositories or recipes.

• Package versioning is managed with revisions ; automatic upgrade is managed when selecting “latest” specific revision.

Signed Profiles: Profiles deployed using FileWave are now signed before being installed on the device. FileWave 15.5 also allows:

• modifying imported signed profiles ; in that case, existing profile signature will be removed and replaced by a new one

• exporting profiles as signed, making sure profiles can be shared without being altered

• duplicating signed profiles ; in that case, as payload UUIDS are regenerated, existing profile signature will be removed and replaced by a new one

ACME Certificate profile: ACME certificate profile can now be configured ; other payloads can reference ACME payloads the same way as SCEP payloads.

Extensible SSO: Various new options have been added to the Extensible SSO profile, allowing to define various policies like FileVault, Authentication Grace period or unlock behavior.

Login Window: Login Window Profile has been updated to replace a non-functional combobox with a checkbox labeled "Show heading information when clicking the clock." When checked, this option will allow the macOS login screen to display hostname, OS version, and IP address in rotation when the clock is clicked. If unchecked, the clock will have no effect. This update simplifies the user interface and aligns it with macOS behavior.

Network: Made sure WPA2 Enterprise is used for Passpoint interface.

Network Usage Rules: SIM Attributes can now be directly edited in the form.

Parental Control (macOS Restrictions): Options to configure Allowed Applications based on application signature have been added.

Passcode: Minor description update related to Maximum Failed Attempt behavior

Restrictions: New options:

• control if transferring eSIM to another device is allowed

• control if auto dim is available for OLED iPads

• control if Genmoji is available

• control if Image Playground is available

• control if iPhone Mirroring is available

• control if Writing Tools are available

• control if Image Wand is available

• control if Personalized Hand Writing is available

• control if Remote control and Video Conferencing is available

• control if Apps can be hidden
• control if Apps can be locked
• control if Call recording is available
• control if RCS messaging is available
• control if Mail summary is available
• control if Media Sharing is available
• prevents user notifications for content capture technologies on managed devices

Security and Privacy: New setting to control XProtect malware upload

Security and Privacy (Privacy and Consent Control): New Bluetooth service

System Extension (macOS): New options for Non Removable from UI and Non Removable System extensions settings

System Logging (macOS): It is now possible to configure system logging options profile.

VPN: New options to configure Post-Quantum Pre-shared Key (PPK) for IKE.V2

DDM configurations: FileWave 15.5 brings Apple’s new way of configuring devices, DDM configurations. While profiles are still widely used, Apple is extending DDM config every release.

To simplify device management, parts of the configurations can be shared amongst different configurations. Typical example is user credentials, used to authenticate to different services. The same credentials will be used by many configurations (caldav, mail…) ; instead of duplicating the settings, you can now create a unique Asset and use the asset in multiple configurations. Assets are available in the form of a new fileset (so you can organize them the way you need, grant permission….) and will be automatically handled as dependency of the configuration using the asset.

FileWave 15.5 introduces a first set of DDM configurations:

• CalDAV account
  

• Passcode settings

   

   

• Screen Sharing application settings (configures connections)
  
  

  

• Screen Sharing host options

  

• Software Update settings

  

More configurations will be added in future versions.

New or modified device management options:

Admin Password management (MDM Command - macOS): Adds the ability to change the admin password from FileWave Central, for devices enrolled via Automated Device Enrollment (DEP). The admin account must have been created during enrollment using DEP profile options.

Control Await Configuration state (DEP enrolled devices): When enrolled via DEP, devices are in a specific mode where the user is not allowed to interact with the device, which will stay in this state until configuration is over. By default, FileWave releases the device as soon as possible to shorten initial setup times. FileWave 15.5 now allows controlling when the device is released:

• DEP profile has a new setting to not automatically release the device from the state

• it is possible to send the Device Configured command either manually (context menu) or via Command Policy fileset.

DEP skip keys: The following skip keys have been added to DEP profile (together with Setup Assistant Profile):

• Action Button

• Apple Intelligence

• Voice Selection

iOS application installed on Apple Silicon mac devices: iOS application filesets can now be associated to macOS devices ; if both application and device are compatible, application will be installed, as long as a license is available.Service Background (DDM status - macOS):  Background tasks based on a launch daemon are now reported in Inventory for macOS devices supporting DDM.

Return to Service (RTS) for Apple TVs: Return to Service options are now available for Apple TVs (tvOS 18+) ; this allows Wi-Fi only Apple TVs to have zero-touch wipe and re-enroll process.

Account Driven Enrollment: For iOS/iPadOS devices, supports new BYOD workflow based on Apple Account Driven Enrollment.

Chrome Extension: New version is available with 15.5 release. Extension is needed for Notifications to function properly and also contains several issues fixed. The extension should automatically update on clients.

Chrome Management in FileWave Anywhere: Verify option is now available in FileWave Anywhere for single and bulk devices action. It is also supported as a bulk action for different platforms (i.e mac and chrome). Note: “Modify Chromebook” permission is not needed to preform Verify action.

Android Lost Mode: EMM devices which are in “Missing” device state will now use Android Lost Mode mechanism. As Android Lost mode allows the end user to exit lost mode by entering device passcode, FileWave will then report in inventory the current state and the expected state. It is also possible to “Play Lost Mode Alert” on lost devices.

64-bit client for Windows

FileWave relies on several opensource components - you can find exhaustive list on each download page. Keeping these components up to date is mandatory for both security reasons and for better features. Starting with version 15.5, FileWave uses now Qt 6, which is running only on 64-bit operating systems. FileWave 15.5 can’t run on Windows 32-bit edition anymore.

The change from 32-bit to 64-bit executable on Windows has an impact on how filesets are delivered:

• On a 32-bit Windows, programs are located on c:\Program Files.
• On a 64-bit Windows, 32-bit programs are located on c:\Program Files (x86)\ while 64-bit programs are on C:\Program Files\

To facilitate the transition to the 64-bit platform, Microsoft added silent, automatic redirection. When a 32-bit program tries to access c:\Program Files\, Windows automatically redirects file system calls to C:\Program Files (x86) ; this allows legacy program to work smoothly on both platforms. This redirection applies in several concepts and is documented by Microsoft in the WOW64 (Windows On Windows 64) page.

As FileWave Agent (fwcld) 15.4 is a 32-bit application, it is impacted by the silent redirect from Windows ; files deployed using FileWave may then be deployed in a different location. A Fileset property setting allows to control wether redirection mechanism should be disabled or not.

Starting with FileWave 15.5, filesets can be configured as 32-bit or 64-bit:

This has an impact on:

• files delivery, depending on the redirection setting
• registry modifications
• script interpreter environment. Typically, Powershell can run as 32-bit or as 64-bit 

To facilitate migration:

• filesets created with FileWave 15.5 will be 64-bit by default and can be marked as 32-bit if required
• all existing filesets, created prior to 15.5, are marked as 32-bit (redirection setting is kept) and can be marked as 64-bit if required

As 64-bit applications are located in c:\Program Files instead of c:\Program Files (x86), if you have scripts calling fwcld.exe to manage "Command Line" custom fields will need to be updated to use the new path.

Firewall Script for Client Monitor

If you use Client Monitor with Windows clients then you've deployed some version of the firewall script from the KB. With the move to 64bit Windows there is a change in location for the executable used in the firewall rule. The normal Client Update Fileset will add the new rule without you needing to do anything. Read More...

Windows Client Upgrade Fileset

We have further enhanced the Windows Client Upgrade Fileset to try to account for additional scenarios that could lead to a failed upgrade. The updates include trimming a log file that could grow to be too large and enhancements to how the scheduled task is created and executed that performs the actual upgrade.  

FileWave Windows Imaging solution relies on PXE Boot, which delivers a tiny Linux image containing all required components to run the imaging process. Compatibility with different hardware depends on how the tiny linux image is built - mainly which Linux kernel version and embedded packages and modules.

• The list of modules and packages embedded with IVS 15.5 has been entirely revisited and supports a much broader set of hardware.
• NFS shares on the IVS 15.5 are protected in a new way. When a device boots up to image or capture its image there is a VPN session created in order to access the NFS shares. Unauthenticated access to the NFS shares was removed. This change requires clients to be able to reach the IVS on TCP/UDP 20490 rather than the previous TCP/UDP 2049 port.

Company Information

With 15.4.0 - Company information are now available in Desktop versions of the Kiosk (macOS, Windows):

Reinstall and Go To App Store actions

Reinstall and Go To App Store actions have been added in Fileset Details and Browse Filesets views:

• Go To App Store button is visible for all VPP filesets.

• Reinstall button is visible for non-VPP filesets in the following scenarios:

  • If the fileset is already installed.

  • If the installation of the fileset failed.

New design for Join Organization modal

New organization modal is showing both active and retired VPP invites. Red indicator is shown only if the action is required (pending organization(s) to join).

The following features have been deprecated from FileWave 15.5.0. They are present but will be removed in a future release:

• macOS Support: macOS 12 will be the minimum macOS supported version.
• Kiosk 1.0 for macOS/Windows - The original Kiosk is still bundled with macOS/Windows clients, but in a future version, this will be removed because Kiosk 2.0, introduced in FileWave 15.3.0, will be the only Kiosk.
• Minimum version of Server for upgrades: Upgrading FileWave server to version 16.0 will require to run FileWave 14.1.5 or later.
• FileWave Central Dashboard: The Dashboard in FileWave Central will be replaced by a view of a Grafana Dashboard to not maintain 2 Dashboard systems.
• Automatically deploy to requesting clients: In 16.0 this option for OS updates will be removed in favor of using a Smart Group like All Windows or All macOS or All iOS as part of the improvements to reporting and use of OS updates in FileWave. Improved automation related to software update will be added in a future version.

We encourage you to provide product feedback if you have any concerns: FileWave Product Management

The following features have been removed from FileWave 15.5.0:

• Windows 32-bit - With FileWave 15.5, the FileWave Client, Boosters, and Admin are 64-bit only now.
  

The following features were removed from FileWave 15.4.0 and are worth mentioning again due to being major changes:

• CentOS - As CentOS 7 being End-Of-Life on June 30, 2024, FileWave is available and supported on Debian. New versions of FileWave won't be released on CentOS after CentOS is EOL.
• Compatibility Mode: Communication between FileWave components is encrypted and has relied on TLS certificates for several years now. Back in the day, to facilitate the transition, a Compatibility Mode was introduced, allowing clients running versions older than 13.1 to still be managed by a more recent server despite not supporting proper encryption. It is now time to drop compatibility mode to enforce secured communications. This means the minimum OS versions that can be enrolled are macOS 10.11 and Windows 7 SP1 - but it is obviously not recommended to run outdated, unsecured end-of-life Operating Systems.

• Google FCM Deprecation Support:

  • • Legacy Firebase Cloud Messaging (FCM) APIs are deprecated by Google.

    • Enable (if are not already enabled) the following API to manage ChromeOS on FileWave:

      • Firebase Cloud Messaging API

      • Firebase Management API

      • More...

Bug fixes:

Fixes in 15.4.3:

macOS Upgrade Fileset (md5: 3248583970caad8e85871081533ee198)
macOS Admin (md5: fa07a9b2d5bd80557727f423e30f90b4)
macOS Booster (md5: 81ffaa06de0662ff4b6eccf6ab58020f)
macOS Server (md5: c0f1f77856b34752e8bf956d076c5e4b)

Remember that to upgrade macOS FileWave clients you should use the Upgrade Fileset. Never deploy the macOS Client installer from https://custom.filewave.com to an existing device. It is intended for new installs. 

Windows Upgrade Fileset (md5: 6b8be5bb4aa7b49e620e436b0e34b90d)
Windows Admin (md5: 0888f119ead03619ebbba7f4622dd503)
Windows Booster (md5: d5ab85c6991b7929e6fc2e1690b91751)

Remember that to upgrade Windows FileWave clients you should use the Upgrade Fileset. Never deploy the Windows Client installer from https://custom.filewave.com to an existing device. It is intended for new installs.

Kiosk on iOS / iPadOS is now automatically installed from a CDN. (Read More)

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

Debian Linux Server (md5: 3b10d63df0d7c9592502c60b398e5458)
Debian Linux Booster (md5: 512302baf6d352afdceca6ac264e4bf3)
Debian Linux IVS: FileWave Admin (md5: 3e9a566f885a02b2f00516589c9f7cd2)
Debian Linux IVS: FileWave Imaging Client (md5: 3933b6b2306a8147d854d8eee4cf713b)
Debian Linux IVS: IVS Kernel (md5: 75e0d74a28d1bf7b2ea6372d9e0170f0)
Debian Linux IVS: FileWave IVS (md5: e079ab71c4ef957386fec878eb9a09a0)

For any of the below upgrades you would want to console or SSH to your Server/Booster/IVS and then run the command listed to upgrade the relevant component.

If you are using a FileWave appliance that before 15.4.0 the SSH access was with the user "root" and for any appliance setup from 15.4.0 or later the user is "fwadmin" and you would have been forced to set the password on first login.

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

wget -qO- https://kb.filewave.com/attachments/411 | sudo bash -s -- -v 15.5.0 -r 1 -p -y

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

wget -qO- https://kb.filewave.com/attachments/412 | sudo bash -s -- -v 15.5.0 -r 1 -p -y

Upgrading a IVS
To upgrade the FileWave IVS, use the following:

wget -qO- https://kb.filewave.com/attachments/408 | sudo bash -s -- -v 15.5.0 -r 1 -p -y

OVA Images
These three images are OVA images suitable for VMWare or other systems that use OVAs:
VMware and VirtualBox (OVA) Server Appliance (md5: 04ca58d741d4943b5c1eaa61dee3bd9b)
VMware and VirtualBox (OVA) Booster Appliance (md5: a60eed781b80c56755040f4d4ea1ae7d)
VMware and VirtualBox (OVA) Imaging Appliance (md5: fcc38d772cdf1e862ccf089a05be6d35)

HyperV Images
These three images are Hyper-V images suitable for Microsoft Hyper-V (Gen 1):
Hyper-V (VHD) Server Appliance (md5: 832be21c369d082e75c2852d7449afb3)
Hyper-V (VHD) Booster Appliance (md5: bf93cd727614a28b9cb926abd79158fa)
Hyper-V (VHD) Imaging Appliance (md5: a0d2541405914c84e5b38b82771b7773)

These three images are Hyper-V images suitable for Microsoft Hyper-V (Gen 2):
Hyper-V (VHD) Server Appliance (md5: a59de4edb35a65505d8383ab6d4c1ca8)
Hyper-V (VHD) Booster Appliance (md5: c3f4e46d59e04b514c2829fee7255dc9)
Hyper-V (VHD) Imaging Appliance (md5: 0c34d4051526594c86ec38aee47347e6)

To get started with the FileWave Server appliance please see: 1. Installation and Setup | FileWave KB
For a Booster you would setup networking just like you do with Server and then: Booster Installation | FileWave KB
For more information about importing the IVS appliance please see: Importing FileWave Appliances

Please note that the below is only to be used when Support has identified that they are needed to fix an issue. Normally these Client packages are not used. Pushing the PKG or MSI below from FileWave can break a client.

macOS Client (md5: a20567dc69e94394f3a9d17f513c7b92)
Windows Client (md5: 037884b744e435348d55fe39fc45410f)

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 12) 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 13, 14 (Intel and Apple Silicon)
• Debian 12.2 x86_64 (Note that any Debian 12.x is expected to work, and applying security updates may move you to a higher version.)
  

Expected to work

• macOS 11, 12 (Intel and Apple Silicon)

Virtual Appliances

• HyperV - The images are of Generation 1 type currently
• VMWare ESX - The images require vmx-19 support which means VMWare vCenter 7.0 Update 2 is the minimum version. ( https://knowledge.broadcom.com/external/article?legacyId=2007240 )
• VMWare Fusion
• VMWare Player and Workstation
• VirtualBox

Fully Tested by QA

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

Expected to work

• macOS 11, 12 (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
  
• macOS 10.15 → Legacy Version 15.0.1

Fully Tested by QA

• iOS 16.1, 17
• iPadOS 16, 17
• tvOS 16, 17
• Android 13, 14 (EMM Client)
• Chromebook
  

Expected to work

• iOS 14, 15
• iPadOS 14, 15
• tvOS 14, 15
• Android 8 to 12 (EMM)
  

Legacy

• iOS 13 → Legacy Version 15.0.1
• iOS 10, 11, 12 → Legacy Version 13.1.5

Fully Tested by QA

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

Expected to work

• macOS 11, 12 (Intel and Apple Silicon)

Fully Tested by QA

• macOS 13, 14 (Intel and Apple Silicon)
• Windows 10 (Ent/Pro 21H1 and above), 11 (Ent/Pro 21H2 and above)
  
• Debian 12.2 x86_64 (Note that any Debian 12.x is expected to work, and applying security updates may move you to a higher version.)
  

Virtual Appliances

• HyperV - The images are of Generation 1 type currently
• VMWare ESX - The images require vmx-19 support which means VMWare vCenter 7.0 Update 2 is the minimum version. ( https://knowledge.broadcom.com/external/article?legacyId=2007240 )
• VMWare Fusion
• VMWare Player and Workstation
• VirtualBox

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

Virtual Appliances

• HyperV - The images are of Generation 1 type currently
• VMWare ESX - The images require vmx-19 support which means VMWare vCenter 7.0 Update 2 is the minimum version. ( https://knowledge.broadcom.com/external/article?legacyId=2007240 )
• VMWare Fusion
• VMWare Player and Workstation
• VirtualBox

Bug fixes and security update

FileWave 15.4.1 brings bug fixes and 3rd party open source component updates.

Unified backend for Model Update (Technical Preview)

Model Update is one of the key features of FileWave; Model Update allows you to apply complex changes to your organization only when you’re ready to deploy them and to revert unwanted changes. FileWave 15.3.0 brings a new Model Update mechanism, now running in a single component. This is the first step before new features and improvements can be added to Model Update. In this version, we focused on consistency with existing Model Update (to make sure nothing changes in your deployments) and on shortening update times. Model Update “v2” is a Technical Preview in 15.4.0, so it is not enabled by default.

Minor improvements (Central) 

• It is now possible to filter any table of Client Info dialog.
• Inventory Queries can now be imported and exported.
• Inventory Queries can easily be exposed to Grafana Dashboard
• json file format is now part of default editable file format list

More Dark Mode (Central)

Stand-alone assistants (Client Assistant, Booster Monitor...) now support dark mode

macOS 15 Sequoia and iOS 18

Basica support for macOS 15 Sequoia and iOS 18 betas was added to 15.4.1 and 15.4.2 to support testing. More robust support and features will be added to FileWave 15.5.0 in October 2024. 

Software Update revisited

With the introduction of Declarative Device Management, Apple announced having fixed several issues related to OS update management, mainly on macOS. This is the opportunity for FileWave to revisit how Apple updates are handled, to remove old mechanisms which are either decommissioned by Apple or known to be not reliable, in order to simplify the user experience.

GDMF (Global Device Management Framework) as unique source of truth

One major issue with Software Update Apple side is the multiplicity of sources:

• Legacy systems (older macOS version) rely on an online sucatalog file containing metadata about updates, and used by softwareupdate command line system.
• MDM capable devices can report Available OS Updates at the time they are requesting it.
• GDMF is the new, simplified online catalog, about OS updates for Apple devices.

To ease the support of a broader set of devices, FileWave would combine all sources into one, which could lead to confusions for updates available in multiple sources, as they would show multiple times due to different identifiers.
Starting with FileWave 15.4, the only source of truth will be GDMF.

Which means:

• no more duplicated entries as long GDMF has unique entries per update
• only OS updates will be displayed - while old legacy catalog could contain system apps or system items like XProtect.

On macOS DDM replaces MDM
Legacy macOS versions allowed fine control on how to install updates using softwareupdate command line tool ; using this tool has been made deprecated by Apple several years ago and using MDM protocol was the recommended approach. Unfortunately, this mechanism was not only giving very limited control (MDM can kindly ask device to install the update, that’s it), but was not as reliable as it should. Unfortunately (again), Apple has not been able to fix reported issued with the MDM protocol, preferring a complete rewrite using the new DDM system.

Therefore, starting with FileWave 15.4, macOS OS updates will be managed only using DDM - older not supported or not working mechanisms are decommissioned. Which means:

• macOS OS updates can now be triggered and managed
• only OS-Update DDM capable devices can be managed, so macOS 14 (Sonoma) is the minimum version

Apple Spring Release 2024 support

New restrictions : 

• Allow Live Voicemail (iOS 17.2)
• force preserve ESIM on erase (iOS 17.2)
• allow market place installation (iOS 17.4, EU iPhones)
• allow web installation of apps (iOS 17.5, EU iPhones)

DEP new skip item (and corresponding Setup Assistant): Wallpaper

Installed Application List now reports Distributor Identifier to identify MarketPlace (EU iPhones)

Declarative Device Management (DDM)

FileWave 15.3 introduced the first support of Apple new DDM protocol. With 15.4, this support is expanded to:

• OS update (see above)
  
• Application Management (Technical preview as the functionality is still in developer preview Apple side and not complete)
  
• Status report expanded:
  
  • FileVault status
  • Battery Health report

Minor improvements

FileWave Central will now check, when renewing APN certificate, if the Common Name of the new certificate matches the one from the existing one, to avoid communication break.

API Changes

The most important thing to talk about is the change to the Chrombook APIs. When going to 15.4 you will need to make sure 2 APIs are enabled.  Firebase Cloud Messaging API and  Firebase Management API are required. In fact if you do not upgrade to 15.4 the old APIs will be disabled by Google on June 20, 2024 so you should be sure to upgrade. If you miss upgrading in time, it's ok. Just upgrade and then enable the APIs. Confirming Firebase APIs are enabled for Chromebooks (15.4+) has a script that on-premise customers can run but the easiest thing is just to click https://console.developers.google.com/flows/enableapi?apiid=firebase.googleapis.com,fcm.googleapis.com and make sure your Firebase project is picked and it'll enable the 2 APIs. You can do this before or after you update to 15.4. 

Chromebook commands in FileWave Anywhere

1. REMOTE_POWERWASH Command

• Description: System administrators can remotely powerwash ChromeOS devices, resetting them to factory settings for efficient troubleshooting and maintaining device security.
• Execution: Initiates the powerwash process, erasing all user data and configurations.

2. WIPE_USERS Command

• Description: System administrators can remotely and securely wipe user data from devices, ensuring compliance with data protection regulations and maintaining organizational security.
• Execution: Initiates the data-wiping process on all user accounts.

3. REBOOT Command

• Description: Introducing the REBOOT command, enabling system administrators to reboot devices for troubleshooting remotely and applying system updates.
• Execution: Initiates the remote reboot process on the selected devices.

4. Command History tab

• Description: Users can now view all information related to sending REMOTE_POWERWASH, WIPE_USERS, and REBOOT Commands in the Command History tab for Chromebook devices.

More details available → Powerwash / Wipe Users on ChromeOS (15.3+) & Reboot for ChromeOS (15.3+)

Error handling in case of missing permissions

If the user doesn’t have right permissions or looses permissions in the middle of executing an action, the appropriate error message will be shown in both FileWave Anywhere and Central:

Annotated fields in FileWave Anywhere

Admins using FileWave Anywhere now have the possibility of editing and bulk editing annotated fields in FileWave Anywhere.

Select device(s) → Actions → Edit Fields

Network Policy

It is now possible to set DomainSuffixMatch and UseSystemCA settings for EAP configure networks.

USB data transfer restriction

USB File transfer option has been added to both Default Policy and to Restriction Policy to allow USB data transfer on managed Android devices.

Winget integration - third-party patching made easy

Deploying applications available via Microsoft Winget was already possible using FileWave, but it required script manipulation and some steps to set up properly. FileWave 15.4 introduces a much simpler way to deploy applications to Windows devices.

Welcome new Winget Fileset

A new search assistant allows creating a Winget Fileset just by searching the name of the application to deploy.

• Winget will be automatically installed or updated if required
• With FileWave 15.4.0, the most recent package will always be installed at initial deployment
• You can define if the package will be upgraded at verify if a new version is available
• You can define if the package will be uninstalled if the association is removed - in case the package allows silent uninstallation

More...

FileWave Networking Imaging 15.4.x brings compatibility with FileWave 15.4.x.

• PXE Kernel: 6.7.9
• Buildroot: 2024.02
  

Company Information

With 15.4.0 - Company information are now available in Desktop versions of the Kiosk (macOS, Windows):

Reinstall and Go To App Store actions

Reinstall and Go To App Store actions have been added in Fileset Details and Browse Filesets views:

• Go To App Store button is visible for all VPP filesets.

• Reinstall button is visible for non-VPP filesets in the following scenarios:

  • If the fileset is already installed.

  • If the installation of the fileset failed.

New design for Join Organization modal

New organization modal is showing both active and retired VPP invites. Red indicator is shown only if the action is required (pending organization(s) to join).

The following features have been deprecated from FileWave 15.4.0. They are present but will be removed in a future release:

• CentOS - As CentOS 7 being End-Of-Life on June 30, 2024, FileWave is available and supported on Debian. New versions of FileWave won't be released on CentOS after CentOS is EOL. 
• Windows 32-bit - With FileWave 15.3, the new Kiosk was already running only on 64-bit Windows. FileWave 15.4 can theoretically run on Windows 32-bit without Kiosk (but is not tested by our QA), but 32-bit support will be completely removed in FileWave 15.5.
• Kiosk 1.0 for macOS/Windows - The original Kiosk is still bundled with macOS/Windows clients, but in a future version, this will be removed because Kiosk 2.0, introduced in FileWave 15.3.0, will be the only Kiosk. 

We encourage you to provide product feedback if you have any concerns: FileWave Product Management

The following features have been removed from FileWave 15.4.1:

• CentOS - As CentOS 7 being End-Of-Life on June 30, 2024, FileWave is available and supported on Debian. New versions of FileWave won't be released on CentOS after CentOS is EOL.

The following features have been removed from FileWave 15.4.0:

• Compatibility Mode: Communication between FileWave components is encrypted and has relied on TLS certificates for several years now. Back in the day, to facilitate the transition, a Compatibility Mode was introduced, allowing clients running versions older than 13.1 to still be managed by a more recent server despite not supporting proper encryption. It is now time to drop compatibility mode to enforce secured communications. This means the minimum OS versions that can be enrolled are macOS 10.11 and Windows 7 SP1 - but it is obviously not recommended to run outdated, unsecured end-of-life Operating Systems.
• Legacy macOS Imaging: Changes made by Apple with APFS, T2 chips, and Apple Silicon have long been part of macOS device imaging history. With the deprecation of Compatibility mode, the last reason for keeping macOS imaging options in FileWave is gone.
  

• Google FCM Deprecation Support:

  • • Legacy Firebase Cloud Messaging (FCM) APIs are deprecated by Google.

    • Enable (if are not already enabled) the following API to manage ChromeOS on FileWave:

      • Firebase Cloud Messaging API

      • Firebase Management API

      • More...
• White Labeling of Chrome Extension: This is removed as a process. More...
  

Several 3rd party have been updated, for bug or security issue fixes or new features. Mainly:

• OpenSSL 3.2.2

• Apache 2.4.61

Bug fixes:

• FWRD-1530 Fixed an issue where fwxserver (admin) process could crash under DOS attempt
• FWRD-13304 Fixed an issue in hosted (cloud) environment where default log file level would be debug
• FWRD-13414 Fixed an issue where internal notification system could be blocked causing various issues like blocking model update
• FWRD-13422 Fixed an issue where upgrade to 15.4 could fail due to remaining macOS Imaging associations
• FWRD-13451 Fixed an issue where restarting server during Model Update would not be properly handled
• FWRD-13484 Fixed incorrect macOS version numbers in German Central admin
• FWRD-13516 Fixed an issue where shared iPad users could not be deleted from Client Info
• FWRD-13519 Fixed incorrect macOS version numbers in Chinese, Japanese and Korean Central admin
• FWRD-13525 Fixed an issue where tvOS updates would be visible in iOS list
  

Bug fixes:

• FWRD-990 Fixed issue with expanding groups and clones on Devices View in FileWave Anywhere.
• FWRD-2307 Fixed issue with IP addresses (100.115.92.129 and 100.115.92.133) not being ignored/filtered on ChromeOS client 
• FWRD-2318 Ensure Booster Monitor uses TSL encrypted connection
• FWRD-2706 Fixed an issue where Windows Upgrade Fileset requirements would not exclude unsupported Windows versions
• FWRD-2877 Fixed an issue where Up and Down buttons would not be properly updated after changing selection in Inventory Query Builder Criteria
• FWRD-3532 Fixed an issue where searching in FileWave Central Profile Editor would not keep text case in highlighted text
• FWRD-3537 Fixed an issue where File Browser assistant window title would show incorrect search type
• FWRD-3649 Fixed cosmetic issue related to tooltip on New Document fileset dialog
• FWRD-3661 Fixed incorrect context menu on Cart items
• FWRD-3671 Fixed an issue where Scripts section would not be properly saved in Login Window profile
• FWRD-3676 Fixed an issue where Export Current Tab would export twice iOS Client info tables
• FWRD-3732 Fixed a performance issue when changing a group permission with "Propagate to children" enabled
• FWRD-3837 Fixed an issue where Single App Mode Profile for iOS could not be edited
• FWRD-4228 Fixed an issue where Central Admin translations could not be loaded properly
• FWRD-4366 Fixed an issue where LDAP extraction would not work properly on macOS server
• FWRD-11553 Fixed issue with visibility of Minimize, Maximize and Close buttons in Windows Kiosk.
• FWRD-12131 Fixed an issue where Return To Service options would be available for tvOS devices
• FWRD-12213 Fixed inconsistent wording for fileset status between Fileset Report and Client Info
• FWRD-12449 Fixed an issue where Policy editor would present misleading Close button instead of Save
• FWRD-12457 Fixed an issue where ActivationLock could not be removed if the device has been removed from the model
• FWRD-12474 Fixed UI issue - Search icon when no items found is now centered in Kiosk.
• FWRD-12536 Fixed an issue where a client in conflict could never be presented in the Conflict Solver Dialog
• FWRD-12626 Fixed issue where emptying Asset ID field in Google Admin showed non empty Annotated Assed ID field in Central Admin.
• FWRD-12638 Fixed a cosmetic issue where errors in Inventory Query Builder would not be marked as red
• FWRD-12646 Fixed issue with favicons in Grafana when opening Grafana from FileWave Anywhere.
• FWRD-12690 Fixed a backend issue where removing IDP setup could lead to recurring errors in server logs
• FWRD-12693 Fixed an issue where Search Client in FileWave Anywhere could fail
• FWRD-12721 Fixed an issue where Google Playstore Managed Properties would not be displayed correctly
• FWRD-12780 Fixed issue with showing fileset with different revisions in Kiosk.
• FWRD-12805 Fixed incorrect selection background color in Software Update Dialog
• FWRD-13014 Fixed an issue where Reinstall fileset would not work for desktop devices if fileset ID is higher than 2147483647
• FWRD-13020 Fixed behavior of Requires Reboot indicator in Kiosk.
• FWRD-13026 Fixed an issue where importing profiles like MDM-type profile could prevent creating DEP Profile
• FWRD-13030 Fixed an issue where "Renew client token" would not work for EMM enrolled Android devices (Central)
• FWRD-13055 Fixed an issue where Model Update could fail at EMM Manifest build step (Model Update v2 tech preview)
• FWRD-13064 Fixed an issue where fileset status for excluded from deployment devices could be incorrect (Model Update v2 Technical Preview)
• FWRD-13069 Fixed incorrect font color in new license from Fileset dialog (Dark Mode)
• FWRD-13070 Fixed issue for setting Custom Fields values after Client Enrollment in FileWave Anywhere.
• FWRD-13074 Fixed an issue where server logs would contain long exception when trying to send APN for non properly enrolled Apple device
• FWRD-13089 Fixed issue with VC Redist 64 not being properly installed during upgrade on Windows.
• FWRD-13091 filewave_web_model_update_total expression is missing from prometheus
• FWRD-13099 Fixed an issue where Software Update list would only contain 100 entries in Client Info (Central)
• FWRD-13108 Fixed an issue where enrolling a booster would not work if FileWave client would be installed on the same device
• FWRD-13110 Chromebook Commands added to Audit Log.
• FWRD-13115 Fixed an issue where specific serial numbers on Windows would prevent enrolling boosters due to conflict detection
• FWRD-13121 Fixed an issue where cell text font size could briefly change when expanding treeview (Central)
  

macOS Installers DMG (md5: c17dfcaca37616a8d52886bcaa2f8c5f)
macOS Upgrade Fileset (md5: 22d8fc75877615edb9b1d006d7218f50)
macOS Admin (md5: 158b6f17e4af2dac34bfece5afac2650)
macOS Booster (md5: 411b3ad5642796834552790dc3bdea87)
macOS Server (md5: ac88a1928ce8f776184ff2d772fae1fd)
macOS Client (md5: 0dcfc145b1a349ad3ef2099d5ef03cb1)

Remember that to upgrade macOS FileWave clients you should use the Upgrade Fileset. Never deploy the macOS Client listed above to an existing device. It is intended only for manual initial installs, and even for those you are better off creating an installer at https://custom.filewave.com 

Windows Upgrade Fileset (md5: 48535fe84f23b864f47f4511c301613a)
Windows Admin (md5: c1fa0c30e3b746e0d6910d4136b74d4f)
Windows Booster (md5: 4087563bf334f7483deeafdd33a735bf)
Windows Client (md5: 392bfdebb3fd79252831a7cd23940b32)

Remember that to upgrade Windows FileWave clients you should use the Upgrade Fileset. Never deploy the Windows Client listed above to an existing device. It is intended only for manual initial installs, and even for those you are better off creating an installer at https://custom.filewave.com 

Kiosk on iOS / iPadOS is now automatically installed with no action required. (Read More)

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

Debian Linux Installers (md5: 125001faf4b9c37ff93ac33e85d8bcda)
Debian Linux Server (md5: d53ef141ae4d489b03f347970391bb03)
Debian Linux Booster (md5: 927d4ec39b2aa7f909976558876eb907)

Upgrading the FileWave Server

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

# Ensure you're using sudo for the commands. 
# 1. OS Upgrades:
sudo apt update -y
sudo DEBIAN_FRONTEND=noninteractive apt-get upgrade -y -o Dpkg::Options::="--force-confold"
# 2. Install Essential Tools:
sudo apt install -y zip net-tools gdebi-core
# 3. Download the FileWave Server package:
wget "https://fwdl.filewave.com/15.4.1/fwxserver_15.4.1_amd64.deb" -P /tmp
# 4. Install the FileWave Server using gdebi:
sudo gdebi -n /tmp/fwxserver_15.4.1_amd64.deb
# 5. Reboot the system to complete the installation:
sudo reboot

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

# Ensure you're using sudo for the commands. 
# 1. OS Upgrades:
sudo apt update -y
sudo DEBIAN_FRONTEND=noninteractive apt-get upgrade -y -o Dpkg::Options::="--force-confold"
# 2. Install Essential Tools:
sudo apt install -y zip net-tools gdebi-core
# 3. Download the FileWave Booster package:
wget "https://fwdl.filewave.com/15.4.1/fwbooster_15.4.1_amd64.deb" -P /tmp
# 4. Install the FileWave Booster using gdebi:
sudo gdebi -n /tmp/fwbooster_15.4.1_amd64.deb
# 5. Reboot the system to complete the installation:
sudo reboot

Upgrading a IVS
To upgrade the FileWave IVS, use the following :

# Ensure you're using sudo for the commands. 
# 1. Install Essential Tools:
sudo apt install -y zip net-tools gdebi-core
# 2. Download the FileWave IVS package:
wget https://fwdl.filewave.com/15.4.1/filewave-ivs_15.4.1_amd64.deb -P /tmp
# 3. Install the FileWave IVS using gdebi:
sudo gdebi -n /tmp/apt install /tmp/filewave-ivs_15.4.1_amd64.deb
# 4. OS+IVS Upgrades:
sudo apt update -y
sudo DEBIAN_FRONTEND=noninteractive apt-get upgrade -y -o Dpkg::Options::="--force-confold"
# 5. Reboot the system to complete the installation:
sudo reboot

Debian Linux: It is preferred that you use this for a new server, booster or IVS.
VMware and VirtualBox (OVA) Server Appliance (md5: a8f39b3e0cdc449ee801a1636b1e1751 )
VMware and VirtualBox (OVA) Booster Appliance (md5: d784682c63e9360f160381c9994f7bb3)
VMware and VirtualBox (OVA) Imaging Appliance (md5: d877dc4fe91d51c1ef86400a427412fb)

To get started with the FileWave Server appliance please see: 1. Installation and Setup | FileWave KB
For a Booster you would setup networking just like you do with Server and then: Booster Installation | FileWave KB
For more information about importing the IVS appliance please see: Importing FileWave Appliances

Debian Linux: It is preferred that you use this for a new server, booster or IVS.
Hyper-V (VHD) Server Appliance (md5: 3ee1f54176721ebc7a161e30964fb957)
Hyper-V (VHD) Booster Appliance (md5: 3d4df08ea89176579e5e950af7c51ad9)
Hyper-V (VHD) Imaging Appliance (md5: dc67041f5103ac109b5b7228257cfe96)

To get started with the FileWave Server appliance please see: 1. Installation and Setup | FileWave KB
For a Booster you would setup networking just like you do with Server and then: Booster Installation | FileWave KB
For more information about importing the IVS appliance please see: Importing FileWave Appliances

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 12) 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 13, 14 (Intel and Apple Silicon)
• Linux CentOS 7.9 x86_64
• Debian 12.2 x86_64 (Note that any Debian 12.x is expected to work, and applying security updates may move you to a higher version.)
  

Expected to work

• macOS 11, 12 (Intel and Apple Silicon)

Virtual Appliances

• HyperV - The images are of Generation 1 type currently
• VMWare ESX - The images require vmx-19 support which means VMWare vCenter 7.0 Update 2 is the minimum version. ( https://knowledge.broadcom.com/external/article?legacyId=2007240 )
• VMWare Fusion
• VMWare Player and Workstation
• VirtualBox

Fully Tested by QA

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

Expected to work

• macOS 11, 12 (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
  
• macOS 10.15 → Legacy Version 15.0.1

Fully Tested by QA

• iOS 16.1, 17
• iPadOS 16, 17
• tvOS 16, 17
• Android 13, 14 (EMM Client)
• Chromebook
  

Expected to work

• iOS 14, 15
• iPadOS 14, 15
• tvOS 14, 15
• Android 8 to 12 (EMM)
  

Legacy

• iOS 13 → Legacy Version 15.0.1
• iOS 10, 11, 12 → Legacy Version 13.1.5

Fully Tested by QA

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

Expected to work

• macOS 11, 12 (Intel and Apple Silicon)

Fully Tested by QA

• macOS 13, 14 (Intel and Apple Silicon)
• Windows 10 (Ent/Pro 21H1 and above), 11 (Ent/Pro 21H2 and above)
• Linux CentOS 7.9 x86_64
• Debian 12.2 x86_64 (Note that any Debian 12.x is expected to work, and applying security updates may move you to a higher version.)
  

Virtual Appliances

• HyperV - The images are of Generation 1 type currently
• VMWare ESX - The images require vmx-19 support which means VMWare vCenter 7.0 Update 2 is the minimum version. ( https://knowledge.broadcom.com/external/article?legacyId=2007240 )
• VMWare Fusion
• VMWare Player and Workstation
• VirtualBox

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

Virtual Appliances

• HyperV - The images are of Generation 1 type currently
• VMWare ESX - The images require vmx-19 support which means VMWare vCenter 7.0 Update 2 is the minimum version. ( https://knowledge.broadcom.com/external/article?legacyId=2007240 )
• VMWare Fusion
• VMWare Player and Workstation
• VirtualBox

Unified backend for Model Update (Technical Preview)

Model Update is one of the key features of FileWave; Model Update allows you to apply complex changes to your organization only when you’re ready to deploy them and to revert unwanted changes. FileWave 15.3.0 brings a new Model Update mechanism, now running in a single component. This is the first step before new features and improvements can be added to Model Update. In this version, we focused on consistency with existing Model Update (to make sure nothing changes in your deployments) and on shortening update times. Model Update “v2” is a Technical Preview in 15.4.0, so it is not enabled by default.

Minor improvements (Central) 

• It is now possible to filter any table of Client Info dialog.
• Inventory Queries can now be imported and exported.
• Inventory Queries can easily be exposed to Grafana Dashboard
• json file format is now part of default editable file format list

More Dark Mode (Central)

Stand-alone assistants (Client Assistant, Booster Monitor...) now support dark mode

Software Update revisited

With the introduction of Declarative Device Management, Apple announced having fixed several issues related to OS update management, mainly on macOS. This is the opportunity for FileWave to revisit how Apple updates are handled, to remove old mechanisms which are either decommissioned by Apple or known to be not reliable, in order to simplify the user experience.

GDMF (Global Device Management Framework) as unique source of truth

One major issue with Software Update Apple side is the multiplicity of sources:

• Legacy systems (older macOS version) rely on an online sucatalog file containing metadata about updates, and used by softwareupdate command line system.
• MDM capable devices can report Available OS Updates at the time they are requesting it.
• GDMF is the new, simplified online catalog, about OS updates for Apple devices.

To ease the support of a broader set of devices, FileWave would combine all sources into one, which could lead to confusions for updates available in multiple sources, as they would show multiple times due to different identifiers.
Starting with FileWave 15.4, the only source of truth will be GDMF.

Which means:

• no more duplicated entries as long GDMF has unique entries per update
• only OS updates will be displayed - while old legacy catalog could contain system apps or system items like XProtect.

On macOS DDM replaces MDM
Legacy macOS versions allowed fine control on how to install updates using softwareupdate command line tool ; using this tool has been made deprecated by Apple several years ago and using MDM protocol was the recommended approach. Unfortunately, this mechanism was not only giving very limited control (MDM can kindly ask device to install the update, that’s it), but was not as reliable as it should. Unfortunately (again), Apple has not been able to fix reported issued with the MDM protocol, preferring a complete rewrite using the new DDM system.

Therefore, starting with FileWave 15.4, macOS OS updates will be managed only using DDM - older not supported or not working mechanisms are decommissioned. Which means:

• macOS OS updates can now be triggered and managed
• only OS-Update DDM capable devices can be managed, so macOS 14 (Sonoma) is the minimum version

Apple Spring Release 2024 support

New restrictions : 

• Allow Live Voicemail (iOS 17.2)
• force preserve ESIM on erase (iOS 17.2)
• allow market place installation (iOS 17.4, EU iPhones)
• allow web installation of apps (iOS 17.5, EU iPhones)

DEP new skip item (and corresponding Setup Assistant): Wallpaper

Installed Application List now reports Distributor Identifier to identify MarketPlace (EU iPhones)

Declarative Device Management (DDM)

FileWave 15.3 introduced the first support of Apple new DDM protocol. With 15.4, this support is expanded to:

• OS update (see above)
  
• Application Management (Technical preview as the functionality is still in developer preview Apple side and not complete)
  
• Status report expanded:
  
  • FileVault status
  • Battery Health report

Minor improvements

FileWave Central will now check, when renewing APN certificate, if the Common Name of the new certificate matches the one from the existing one, to avoid communication break.

API Changes

The most important thing to talk about is the change to the Chrombook APIs. When going to 15.4 you will need to make sure 2 APIs are enabled.  Firebase Cloud Messaging API and  Firebase Management API are required. In fact if you do not upgrade to 15.4 the old APIs will be disabled by Google on June 20, 2024 so you should be sure to upgrade. If you miss upgrading in time, it's ok. Just upgrade and then enable the APIs. Confirming Firebase APIs are enabled for Chromebooks (15.4+) has a script that on-premise customers can run but the easiest thing is just to click https://console.developers.google.com/flows/enableapi?apiid=firebase.googleapis.com,fcm.googleapis.com and make sure your Firebase project is picked and it'll enable the 2 APIs. You can do this before or after you update to 15.4. 

Chromebook commands in FileWave Anywhere

1. REMOTE_POWERWASH Command

• Description: System administrators can remotely powerwash ChromeOS devices, resetting them to factory settings for efficient troubleshooting and maintaining device security.
• Execution: Initiates the powerwash process, erasing all user data and configurations.

2. WIPE_USERS Command

• Description: System administrators can remotely and securely wipe user data from devices, ensuring compliance with data protection regulations and maintaining organizational security.
• Execution: Initiates the data-wiping process on all user accounts.

3. REBOOT Command

• Description: Introducing the REBOOT command, enabling system administrators to reboot devices for troubleshooting remotely and applying system updates.
• Execution: Initiates the remote reboot process on the selected devices.

4. Command History tab

• Description: Users can now view all information related to sending REMOTE_POWERWASH, WIPE_USERS, and REBOOT Commands in the Command History tab for Chromebook devices.

More details available → Powerwash / Wipe Users on ChromeOS (15.3+) & Reboot for ChromeOS (15.3+)

Error handling in case of missing permissions

If the user doesn’t have right permissions or looses permissions in the middle of executing an action, the appropriate error message will be shown in both FileWave Anywhere and Central:

Annotated fields in FileWave Anywhere

Admins using FileWave Anywhere now have the possibility of editing and bulk editing annotated fields in FileWave Anywhere.

Select device(s) → Actions → Edit Fields

Network Policy

It is now possible to set DomainSuffixMatch and UseSystemCA settings for EAP configure networks.

USB data transfer restriction

USB File transfer option has been added to both Default Policy and to Restriction Policy to allow USB data transfer on managed Android devices.

Winget integration - third-party patching made easy

Deploying applications available via Microsoft Winget was already possible using FileWave, but it required script manipulation and some steps to set up properly. FileWave 15.4 introduces a much simpler way to deploy applications to Windows devices.

Welcome new Winget Fileset

A new search assistant allows creating a Winget Fileset just by searching the name of the application to deploy.

• Winget will be automatically installed or updated if required
• With FileWave 15.4.0, the most recent package will always be installed at initial deployment
• You can define if the package will be upgraded at verify if a new version is available
• You can define if the package will be uninstalled if the association is removed - in case the package allows silent uninstallation

More...

FileWave Networking Imaging 15.4.x brings compatibility with FileWave 15.4.x.

• PXE Kernel: 6.7.9
• Buildroot: 2024.02
  

Company Information

With 15.4.0 - Company information are now available in Desktop versions of the Kiosk (macOS, Windows):

Reinstall and Go To App Store actions

Reinstall and Go To App Store actions have been added in Fileset Details and Browse Filesets views:

• Go To App Store button is visible for all VPP filesets.

• Reinstall button is visible for non-VPP filesets in the following scenarios:

  • If the fileset is already installed.

  • If the installation of the fileset failed.

New design for Join Organization modal

New organization modal is showing both active and retired VPP invites. Red indicator is shown only if the action is required (pending organization(s) to join).

The following features have been deprecated from FileWave 15.4.0. They are present but will be removed in a future release:

• CentOS - As CentOS 7 being End-Of-Life on June 30, 2024, FileWave is available and supported on Debian. New versions of FileWave won't be released on CentOS after CentOS is EOL.
• Windows 32-bit - With FileWave 15.3, the new Kiosk was already running only on 64-bit Windows. FileWave 15.4 can theoretically run on Windows 32-bit without Kiosk (but is not tested by our QA), but 32-bit support will be completely removed in FileWave 15.5.
• Kiosk 1.0 for macOS/Windows - The original Kiosk is still bundled with macOS/Windows clients, but in a future version, this will be removed because Kiosk 2.0, introduced in FileWave 15.3.0, will be the only Kiosk. 

We encourage you to provide product feedback if you have any concerns: FileWave Product Management

The following features have been removed from FileWave 15.4.0:

• Compatibility Mode: Communication between FileWave components is encrypted and has relied on TLS certificates for several years now. Back in the day, to facilitate the transition, a Compatibility Mode was introduced, allowing clients running versions older than 13.1 to still be managed by a more recent server despite not supporting proper encryption. It is now time to drop compatibility mode to enforce secured communications. This means the minimum OS versions that can be enrolled are macOS 10.11 and Windows 7 SP1 - but it is obviously not recommended to run outdated, unsecured end-of-life Operating Systems.
• Legacy macOS Imaging: Changes made by Apple with APFS, T2 chips, and Apple Silicon have long been part of macOS device imaging history. With the deprecation of Compatibility mode, the last reason for keeping macOS imaging options in FileWave is gone.
  

• Google FCM Deprecation Support:

  • • Legacy Firebase Cloud Messaging (FCM) APIs are deprecated by Google.

    • Enable (if are not already enabled) the following API to manage ChromeOS on FileWave:

      • Firebase Cloud Messaging API

      • Firebase Management API

      • More...
• White Labeling of Chrome Extension: This is removed as a process. More...
  

Bug fixes:

• FWRD-990 Fixed issue with expanding groups and clones on Devices View in FileWave Anywhere.
• FWRD-2307 Fixed issue with IP addresses (100.115.92.129 and 100.115.92.133) not being ignored/filtered on ChromeOS client 
• FWRD-2318 Ensure Booster Monitor uses TSL encrypted connection
• FWRD-2706 Fixed an issue where Windows Upgrade Fileset requirements would not exclude unsupported Windows versions
• FWRD-2877 Fixed an issue where Up and Down buttons would not be properly updated after changing selection in Inventory Query Builder Criteria
• FWRD-3532 Fixed an issue where searching in FileWave Central Profile Editor would not keep text case in highlighted text
• FWRD-3537 Fixed an issue where File Browser assistant window title would show incorrect search type
• FWRD-3649 Fixed cosmetic issue related to tooltip on New Document fileset dialog
• FWRD-3661 Fixed incorrect context menu on Cart items
• FWRD-3671 Fixed an issue where Scripts section would not be properly saved in Login Window profile
• FWRD-3676 Fixed an issue where Export Current Tab would export twice iOS Client info tables
• FWRD-3732 Fixed a performance issue when changing a group permission with "Propagate to children" enabled
• FWRD-3837 Fixed an issue where Single App Mode Profile for iOS could not be edited
• FWRD-4228 Fixed an issue where Central Admin translations could not be loaded properly
• FWRD-4366 Fixed an issue where LDAP extraction would not work properly on macOS server
• FWRD-11553 Fixed issue with visibility of Minimize, Maximize and Close buttons in Windows Kiosk.
• FWRD-12131 Fixed an issue where Return To Service options would be available for tvOS devices
• FWRD-12213 Fixed inconsistent wording for fileset status between Fileset Report and Client Info
• FWRD-12449 Fixed an issue where Policy editor would present misleading Close button instead of Save
• FWRD-12457 Fixed an issue where ActivationLock could not be removed if the device has been removed from the model
• FWRD-12474 Fixed UI issue - Search icon when no items found is now centered in Kiosk.
• FWRD-12536 Fixed an issue where a client in conflict could never be presented in the Conflict Solver Dialog
• FWRD-12626 Fixed issue where emptying Asset ID field in Google Admin showed non empty Annotated Assed ID field in Central Admin.
• FWRD-12638 Fixed a cosmetic issue where errors in Inventory Query Builder would not be marked as red
• FWRD-12646 Fixed issue with favicons in Grafana when opening Grafana from FileWave Anywhere.
• FWRD-12690 Fixed a backend issue where removing IDP setup could lead to recurring errors in server logs
• FWRD-12693 Fixed an issue where Search Client in FileWave Anywhere could fail
• FWRD-12721 Fixed an issue where Google Playstore Managed Properties would not be displayed correctly
• FWRD-12780 Fixed issue with showing fileset with different revisions in Kiosk.
• FWRD-12805 Fixed incorrect selection background color in Software Update Dialog
• FWRD-13014 Fixed an issue where Reinstall fileset would not work for desktop devices if fileset ID is higher than 2147483647
• FWRD-13020 Fixed behavior of Requires Reboot indicator in Kiosk.
• FWRD-13026 Fixed an issue where importing profiles like MDM-type profile could prevent creating DEP Profile
• FWRD-13030 Fixed an issue where "Renew client token" would not work for EMM enrolled Android devices (Central)
• FWRD-13055 Fixed an issue where Model Update could fail at EMM Manifest build step (Model Update v2 tech preview)
• FWRD-13064 Fixed an issue where fileset status for excluded from deployment devices could be incorrect (Model Update v2 Technical Preview)
• FWRD-13069 Fixed incorrect font color in new license from Fileset dialog (Dark Mode)
• FWRD-13070 Fixed issue for setting Custom Fields values after Client Enrollment in FileWave Anywhere.
• FWRD-13074 Fixed an issue where server logs would contain long exception when trying to send APN for non properly enrolled Apple device
• FWRD-13089 Fixed issue with VC Redist 64 not being properly installed during upgrade on Windows.
• FWRD-13091 filewave_web_model_update_total expression is missing from prometheus
• FWRD-13099 Fixed an issue where Software Update list would only contain 100 entries in Client Info (Central)
• FWRD-13108 Fixed an issue where enrolling a booster would not work if FileWave client would be installed on the same device
• FWRD-13110 Chromebook Commands added to Audit Log.
• FWRD-13115 Fixed an issue where specific serial numbers on Windows would prevent enrolling boosters due to conflict detection
• FWRD-13121 Fixed an issue where cell text font size could briefly change when expanding treeview (Central)
  

macOS Installers DMG (md5: e91d9e2702be584a8ecff1636279da5f)
macOS Upgrade Fileset (md5: 9e80fc47504748ce4273bdda507ef5f8)
macOS Admin (md5: eb0896f5e28df853bb73289d6c45e03d)
macOS Booster (md5: 300853665938ef6293bbad69ad0b5109)
macOS Server (md5: dd724c3e9810be47b6deb0098fe11ee0)
macOS Client (md5: 77873a6ae4d7b5cafa346044999d5a43)

Remember that to upgrade macOS FileWave clients you should use the Upgrade Fileset. Never deploy the macOS Client listed above to an existing device. It is intended only for manual initial installs, and even for those you are better off creating an installer at https://custom.filewave.com 

Windows Upgrade Fileset (md5: 2bb3ae71c257a4520afdfde7076a0f51)
Windows Admin (md5: 41afdaeab0a018c9ab12baa3f3e7c889)
Windows Booster (md5: 50692769f5733c59da31f353930f0967)
Windows Client (md5: b87b9cece03ef18148c4bbc786513f23)

Remember that to upgrade Windows FileWave clients you should use the Upgrade Fileset. Never deploy the Windows Client listed above to an existing device. It is intended only for manual initial installs, and even for those you are better off creating an installer at https://custom.filewave.com 

Kiosk on iOS / iPadOS is now automatically installed from a CDN. (Read More)

Debian Linux Installers (md5: 48c9ac8e00af106d31beb9fa66044155)
Debian Linux Server (md5: 76cb0c56d8601eaa435bfdd12c8afda0)
Debian Linux Booster (md5: f7bdbbe314081c3fec3e5747d1f756c1)

Upgrading the FileWave Server

Upgrades are generally done by SSH or terminal session to the server as root. 

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

# Ensure you're using sudo for the commands. 
# 1. OS Upgrades:
sudo apt update -y
sudo DEBIAN_FRONTEND=noninteractive apt-get upgrade -y -o Dpkg::Options::="--force-confold"
# 2. Install Essential Tools:
sudo apt install -y zip net-tools gdebi-core
# 3. Download the FileWave Server package:
wget  "https://fwdl.filewave.com/15.4.0/fwxserver_15.4.0_amd64.deb" -P /tmp
# 4. Install the FileWave Server using gdebi:
sudo gdebi -n /tmp/fwxserver_15.4.0_amd64.deb
# 5. Reboot the system to complete the installation:
sudo reboot

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

# Ensure you're using sudo for the commands. 
# 1. OS Upgrades:
sudo apt update -y
sudo DEBIAN_FRONTEND=noninteractive apt-get upgrade -y -o Dpkg::Options::="--force-confold"
# 2. Install Essential Tools:
sudo apt install -y zip net-tools gdebi-core
# 3. Download the FileWave Booster package:
wget https://fwdl.filewave.com/15.4.0/fwbooster_15.4.0_amd64.deb -P /tmp
# 4. Install the FileWave Booster using gdebi:
sudo gdebi -n /tmp/fwbooster_15.4.0_amd64.deb
# 5. Reboot the system to complete the installation:
sudo reboot

Upgrading a IVS
To upgrade the FileWave IVS, use the following :

# Ensure you're using sudo for the commands. 
# 1. OS+IVS Upgrades:
sudo apt update -y
sudo DEBIAN_FRONTEND=noninteractive apt-get upgrade -y -o Dpkg::Options::="--force-confold"
# 2. Make sure the IVS package was installed (Note this may not show anything is needed if you did this in a past update)
sudo apt install filewave-ivs
# 3. Reboot the system to complete the installation:
sudo reboot

Debian Linux: It is preferred that you use this for a new server, booster or IVS.
VMware and VirtualBox (OVA) Server Appliance (md5: 73446d642133530b4a899de1fdc00796 )
VMware and VirtualBox (OVA) Booster Appliance (md5: 77bab15c8cca288d7e0c6d5327d46f25)
VMware and VirtualBox (OVA) Imaging Appliance (md5: f5445764a6f2010d5cce97c5c4b06daa)

CentOS Linux:
VMware and VirtualBox (OVA) Server Appliance (md5: 128af104f5c48d1e345e029536f283e6)
VMware and VirtualBox (OVA) Booster Appliance (md5: e12c3b4d10981ec8a030902e3d4929c0)
VMware and VirtualBox (OVA) Imaging Appliance (md5: 44143c821ac2321f5e96c990a05d2bf8)

To get started with the FileWave Server appliance please see: 1. Installation and Setup | FileWave KB
For a Booster you would setup networking just like you do with Server and then: Booster Installation | FileWave KB
For more information about importing the IVS appliance please see: Importing FileWave Appliances

Debian Linux: It is preferred that you use this for a new server, booster or IVS.
Hyper-V (VHD) Server Appliance (md5: 21f9040e34ff302c7f6263b973061711)
Hyper-V (VHD) Booster Appliance (md5: 993bc30ca18aacf3f60117a194855fbb)
Hyper-V (VHD) Imaging Appliance (md5: 2d64c139d932cfa2718df36449af9d93)

CentOS Linux:
Hyper-V (VHD) Server Appliance (md5: 2430069179746b6b65a9840cc588a1e4)
Hyper-V (VHD) Booster Appliance (md5: e48776dcb3407fd933da2d57abf4cac9)
Hyper-V (VHD) Imaging Appliance (md5: 6a446d733156a642b5d42f868041b0a3)

To get started with the FileWave Server appliance please see: 1. Installation and Setup | FileWave KB
For a Booster you would setup networking just like you do with Server and then: Booster Installation | FileWave KB
For more information about importing the IVS appliance please see: Importing FileWave Appliances

CentOS is EOL in 2024. Migrating to Debian is required. FileWave 15.4.0 will be the final release of FileWave on CentOS. Please review Migrating your On-Premise FileWave Server to new Hardware 

CentOS Linux Installers (md5: 7c11c331055c3824bece78f51c792824)
CentOS Linux Server (md5: 71c74aad992c594bb8d3a7a36d045427)
CentOS Linux Booster (md5: 77c4fe1f30a3a7c4016a4467314eed4f)

If when doing yum update or upgrade you get a note that no updates are available it may be that you block access to some countries. yum clean all can clear the cache so that the upgrades can happen.

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

# login via ssh / root or put sudo at the start of each line
sudo yum update -y
sudo yum upgrade -y
sudo yum install -y --nogpgcheck https://fwdl.filewave.com/15.4.0/fwxserver-15.4.0-1.0.x86_64.rpm
sudo reboot

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

# login via ssh / root
sudo yum update -y
sudo yum upgrade -y
sudo yum install -y --nogpgcheck https://fwdl.filewave.com/15.4.0/fwbooster-15.4.0-1.0.x86_64.rpm
sudo 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
sudo yum update -y
sudo yum update -y filewave-IVS
sudo yum upgrade -y
sudo 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
sudo yum install -y filewave-IVS
sudo yum upgrade -y
sudo 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.

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 12) 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 13, 14 (Intel and Apple Silicon)
• Linux CentOS 7.9 x86_64
• Debian 12.2 x86_64 (Note that any Debian 12.x is expected to work, and applying security updates may move you to a higher version.)
  

Expected to work

• macOS 11, 12 (Intel and Apple Silicon)

Fully Tested by QA

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

Expected to work

• macOS 11, 12 (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
  
• macOS 10.15 → Legacy Version 15.0.1

Fully Tested by QA

• iOS 16.1, 17
• iPadOS 16, 17
• tvOS 16, 17
• Android 13, 14 (EMM Client)
• Chromebook
  

Expected to work

• iOS 14, 15
• iPadOS 14, 15
• tvOS 14, 15
• Android 8 to 12 (EMM)
  

Legacy

• iOS 13 → Legacy Version 15.0.1
• iOS 10, 11, 12 → Legacy Version 13.1.5

Fully Tested by QA

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

Expected to work

• macOS 11, 12 (Intel and Apple Silicon)

Fully Tested by QA

• macOS 13, 14 (Intel and Apple Silicon)
• Windows 10 (Ent/Pro 21H1 and above), 11 (Ent/Pro 21H2 and above)
• Linux CentOS 7.9 x86_64
• Debian 12.2 x86_64 (Note that any Debian 12.x is expected to work, and applying security updates may move you to a higher version.)
  

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 Debian 12 and 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.

Central goes Dark

FileWave Central introduces a new Dark Mode UI - for FileWave admins working at night ! More...

Unified backend for Model Update (Technical Preview)

Model Update is one of the key features of FileWave; Model Update allows you to apply complex changes to your organization only when you’re ready to deploy them and to revert unwanted changes. FileWave 15.3.0 brings a new Model Update mechanism, now running in a single component. This is the first step before new features and improvements can be added to Model Update. In this version, we focused on consistency with existing Model Update (to make sure nothing changes in your deployments) and on shortening update times. Model Update “v2” is a Technical Preview in 15.3.0, so it is not enabled by default.

Improved Client / Booster / Server communication

FileWave 11 introduced Booster Routing, a feature that allows off-loading direct traffic to the server by routing messages via Booster. This feature provides additional security if you only allow boosters to connect to your server and have all your devices only reach boosters. With FileWave 15.0, the internal notification system has switched entirely to NATS, replacing ZMQ; NATS, in addition to built-in security features and improved performances, brings much more flexibility and can then be used in more areas. FileWave 15.3 can now use NATS as the communication protocol for all maintenance messages between client and server. Fileset delivery still uses the classic protocol, but messages like Fileset status or check-in now use the lightweight and fast delivery mechanism offered by NATS. 

Declarative Device Management

FileWave 15.3.0 is the first implementation of Apple’s new device management mechanism, Declarative Device Management (DDM). It will use the new Status Report for applications, providing quick and accurate Fileset Status updates for apps installed via MDM (App Store apps) on compatible iOS, iPadOS, and tvOS devices.

Therefore, FileWave 15.3.0 contains the foundations for support for more DDM features, such as software update management or application installation via DDM, which are being built and will be provided in coming releases.

More...

We are excited to announce the expansion of Chromebook Management, addressing significant performance improvements and introducing new features to enhance user experience.

Commands

1. REMOTE_POWERWASH Command

• Description: System administrators can remotely powerwash ChromeOS devices, resetting them to factory settings for efficient troubleshooting and maintaining device security.

• Execution: Initiates the powerwash process, erasing all user data and configurations.

2. WIPE_USERS Command

• Description: System administrators can remotely and securely wipe user data from devices, ensuring compliance with data protection regulations and maintaining organizational security.

• Execution: Initiates the data-wiping process on all user accounts.

3. REBOOT Command

• Description: Introducing the REBOOT command, enabling system administrators to reboot devices for troubleshooting remotely and applying system updates.

• Execution: Initiates the remote reboot process on the selected devices.

4. Command History tab

• Description: Users can now view all information related to sending REMOTE_POWERWASH, WIPE_USERS, and REBOOT Commands in the Command History tab for Chromebook devices.

More details available → Powerwash / Wipe Users on ChromeOS (15.3+) and Reboot for ChromeOS (15.3+)

Bug Fixes and Improvements

1. Reduced Chromebook Sync Time

Issue: Some users reported extended sync times, with an average duration of around 15 minutes for certain customers. Sync was only performed once per day.

Resolution: We have addressed this concern by implementing optimizations that result in a 30% reduction in sync time. Chromebook syncing is now more efficient and streamlined, ensuring a faster and smoother experience.

2. Manual Sync Time Configuration

Issue: Users had limited control over the timing of Chromebook sync, with synchronization occurring only once daily.

Resolution: In response to user feedback, we have introduced a new feature that allows users to set up manual sync times. Sync intervals can be configured between 1 and 24 hours. If no specific time is set, the default sync interval remains at 24 hours. This enhancement provides greater flexibility in managing Chromebook updates according to your organization's needs.

3. Custom Field(s) Annotation Sync

Issue: Changes to annotated fields were causing discrepancies when updating the model.

Resolution:

• Annotated fields in Edit Custom Fields now update immediately upon clicking Save, independently of the Model Update, ensuring swift and accurate changes.

• The Chromebook Data tab in Device Details is removed. Users can access Chromebook-related info by double-clicking on the device, eliminating the need for an additional tab.

• The Device Details View now offers a more informative and user-friendly experience for Annotated fields.

• Annotated fields are seamlessly displayed and editable in the Edit Custom Fields dialog, like any other custom fields.

• A convenient button in the Client Info dialog allows users to sync annotated fields (one way: Google to FileWave) individually for specific devices, offering granular control over data synchronization.

These comprehensive resolutions address the reported issues, providing a seamless and efficient experience in managing Chromebooks, with real-time syncing of annotated fields and enhanced control over synchronization intervals.

FileWave IVS Appliance is now based on Debian!

FileWave Networking Imaging 15.3.x brings compatibility with FileWave 15.3.x.

• PXE Kernel: 6.6.7
• Buildroot: 2023.11
  

App portal for iOS/iPadOS

Evolution of App Portal for iOS/iPadOS: Transition from Technical Preview to Official Release

In our commitment to continuous improvement and user-centric development, we are excited to announce a significant milestone in the journey of App Portal for iOS/iPadOS. Starting from version 15.3.0, App Portal has officially graduated from its technical preview phase, now standing as a fully realized and polished application.

Key Points:

1. From Technical Preview to Real App:
   In previous releases, App Portal for iOS/iPadOS was introduced as a technical preview, allowing users to explore its functionalities and provide valuable feedback. With version 15.3.0, we are thrilled to elevate App Portal to the status of a fully-fledged, official application.

2. Enhancements and Stability:
   The transition signifies not only the culmination of user feedback but also substantial enhancements and optimizations to ensure the stability, reliability, and performance of the App Portal for iOS/iPadOS.

3. A Seamless User Experience:
   Users can now enjoy a seamless and refined experience with App Portal, harnessing its full potential for efficient and intuitive mobile application management.5.3.0 and beyond.

More details here → Automatic updating of iOS Kiosk (15.3+)

Desktop Kiosk for macOS and Windows

The transition from App Portal version 15.0.0 to version 15.3.0 represents a significant evolution, akin to the transformative experience observed when comparing the Android Play Store and the App Store. This upgrade places a primary emphasis on completely overhauling the user interface (UI) to provide a sleek, contemporary, and exceptionally intuitive platform, aligns with our users' evolving expectations.

While version 15.0.0 laid the groundwork for functionality, version 15.3.0 responds to user feedback and industry trends, recognizing the demand for a more sophisticated and streamlined UI. Here's how the new version draws inspiration from the design excellence of both the Android Play Store and the App Store:

1. Unified Design Paradigm:
   The UI design seamlessly unifies elements from both the Android Play Store and the App Store, creating a harmonious blend of familiarity and innovation.

2. Intuitive Navigation:
   Building on the success of version 15.0.0, version 15.3.0 introduces a reimagined navigation system with intuitive menus, recognizable icons, and seamless flows, akin to the ease of navigation in both app marketplaces.

3. Visual Delight:
   The new UI isn't just functional; it's a visual delight with engaging animations, subtle transitions, and tastefully curated visuals, providing an immersive experience similar to the Android Play Store and the App Store.

4. Enhanced Customization:
   Version 15.3.0 brings enhanced customization options, allowing users to personalize their interface similar to the Android Play Store and the App Store, fostering a sense of ownership over their app experience.

5. Responsive Design:
   Like the responsiveness of the Android Play Store and the App Store across devices, our app now adapts seamlessly to various screen sizes, ensuring a consistent and optimized experience.

Additionally, with version 15.3.0, we've introduced some enhancements. Users will now receive clear indications when installing certain filesets that a reboot is required for optimal performance. This improvement ensures transparency and empowers users with the necessary information for a seamless experience. By incorporating these enhancements, App Portal solidifies its commitment to delivering a cutting-edge, user-friendly experience that aligns with evolving user expectations and industry trends. Version 15.3.0 sets the stage for a future where App Portal evolves dynamically, staying at the forefront of user-centric innovation.

More details here → Setting the Primary Color, Name and Logo in App Portal (15.3+)

The following features have been deprecated from FileWave 15.3.0. They are present but will be removed in a future release:

• CentOS: As CentOS 7 being End-Of-Life on June 30, 2024, FileWave is available and supported on Debian. FileWave won't be released on CentOS after CentOS is EOL.

• Compatibility Mode: Communication between FileWave components is encrypted and relies on TLS certificates for several years now. Back in the day, to facilitate the transition, a Compatibility Mode was introduced, allowing clients running versions older than 13.1 to still be managed by a more recent server despite not supporting proper encryption. It is now time to drop compatibility mode to enforce secured communications. This means the minimum OS versions that can be enrolled are macOS 10.11 and Windows 7 SP1 - but it is obviously not recommended to run outdated, unsecured end-of-life Operating Systems.

• OS Updates on Apple Devices: Managing OS updates on Apple devices has evolved significantly. Initially relying on manual commands and customizable catalogs, the process transitioned to MDM protocols, introducing challenges in reliability and control. Apple's introduction of GDMF and the more recent DDM protocol aims to simplify and enhance the reliability of OS update management. FileWave 15.4.0 will adopt GDMF for update reporting and switch to DDM for macOS updates (Sonoma and later), while continuing to use MDM for older iOS/iPadOS versions. This update signifies FileWave's commitment to improving the management of OS updates, addressing past issues and leveraging Apple's latest technologies for a streamlined process. More...
  
• Legacy macOS Imaging: Changes made by Apple with APFS, T2 chips and Apple Silicon, Imaging macOS devices has been part of history for a long time. With the deprecation of Compatibility mode, the last reason for keeping macOS imaging options in FileWave are gone.
  

• FCM Deprecation Support:

  • Legacy Firebase Cloud Messaging (FCM) APIs are being deprecated by Google.
  • FileWave will support this deprecation in the official release of 15.4.
  • More...

The following features have been removed from FileWave 15.3.0:

• As the new desktop kiosk is based on 64-bit libraries, FileWave 15.3.0 will not be supported on Windows 32-bit platforms. FileWave Agent (fwcld) is still a 32-bit executable, meaning there is no change in how Filesets are deployed, and scripts are executed. Moving to a 64-bit application is expected to happen later this year.

Bug fixes:

• FWRD-12751 Tray icon for Kiosk v1 is visible if settings.ini file exists without hide_system_tray setting

• FWRD-12764 Fixed an issue where database constraints could be reported as missing after 15.3.0 upgrade

• FWRD-12782 Fixed an issue where FileWave Central could crash when connection to server is lost

• FWRD-12792 Made sure scheduler locks are cleared when server restarts to avoid locking issues

• FWRD-12794 Fixed an issue where Model Update would be blocked by partial filesets

• FWRD-12831 Fixed authentication issue with API call to update model

• FWRD-12834 Fixed an issue where Updating Model would not be logged in Audit Log
  

Apache 2.4.59

Several 3rd party have been updated, for bug or security issue fixes or new features. Mainly:

• OpenSSL 3.2.1

• Python 3.11.7

• Django 5.0.1

• Postgresql 12.18

Bug fixes:

• FWRD-1439 Fixed an issue where Custom Field Dialog could incorrectly detect changes
  
• FWRD-1440 Fixed an issue where automatically created LDAP based smart groups could be modified
  
• FWRD-2118 Fixed an issue where changing the revision of a fileset dependency would remove and reinstall the dependency instead of only updating differences between revisions
  
• FWRD-2445 Fixed an issue where it would be possible to change permission of a fileset group for which current admin does not have write permission
  
• FWRD-3173 Improved logs when using unsupported image type for iOS WallPaper
  
• FWRD-3365 Fixed an issue where Preferences would show incorrect description for preferred licensing option
  
• FWRD-3458 Made German translations regarding dependencies clearer
  
• FWRD-3800 Fixed an issue where enrolling two IVS would fail due to duplicated fingerprint
  
• FWRD-4232 Fixed UI issue in Device Info view in FileWave Anywhere.
  
• FWRD-4339 Fixed a potential issue where Windows Upgrade Fileset would fail to update Windows client
  
• FWRD-4715 Fixed handling multiple Organization Invite in Registration modal in Kiosk for iOS/iPadOS.
  
• FWRD-11165 Fixed issue with logo qualities in Kiosk for iOS/iPadOS.
  
• FWRD-11403 Fixed font in Kiosk UI.
  
• FWRD-11414 Fixed bug regarding error message related to Faild to fetch data in iOS/iPadOS App Portal.
  
• FWRD-11489 Fixed bug by Chromebooks sync time - it is now reduced by 30%. Also there is new field in FileWave Central Preferences where setup shorter sync interval (in hours) is possible.
  
• FWRD-11581 Fixed an issue where legacy dashboard would report incorrect disk space if server data folder is not on the same volume as root
  
• FWRD-11594 Fixed a cosmetic issue related to Country names displayed by App Store dialogs
  
• FWRD-11750 Fixed an issue where logs could be incorrectly be filled by entries related to errors when synchronizing VPP apps metadata after 9646 error
  
• FWRD-11776 Improved internal scheduler startup phase
  
• FWRD-11810 Fixed issues/added functionalities with managing LDAP Smart Groups in FileWave Anywhere.
  
• FWRD-11830 Fixed an issue on macOS Sonoma where client assistant and client monitor would not use the same device name
  
• FWRD-11867 Fixed a potential issue where invalid request could be made to VPP service, leading to error 9602
  
• FWRD-11879 Improved how VPP errors 9646 are handled
  
• FWRD-11973 Fixed minor UI issues in Filtering section of Kiosk for iOS/iPadOS.
  
• FWRD-12001 Fixed an issue where query builder would not allow using numbers larger than 2147483647
  
• FWRD-12007 Fixed a cosmetic issue where Association option fields would have inconsistent width
  
• FWRD-12104 Fixed an issue related to Dock profile where Merge with User's dock option would not be applied properly
  
• FWRD-12169 Fixed an issue where inventory reports would return incorrect data due to the way client id is retrieved
  
• FWRD-12171 Fixed issue regarding Devices view load being slow in FileWave Anywhere.
  
• FWRD-12214 Debian appliances have now also 500 GB of free space
  
• FWRD-12336 Fixed an issue where Webmin would not be properly configured on Debian appliances
  
• FWRD-12338 Fixed an issue where rpm installer would not properly stop upgrade in preflight step if a Database error is detected
  
• FWRD-12415 Fixed an issue where Associated Domains options would not be properly applied to Enterprise Applications (IPA)

macOS Installers DMG (md5: dc72710e565f127fc608bfb8aa3f5f14)
macOS Upgrade Fileset (md5: 0e7cf29cb759e8a3105f86e3604c48d1)
macOS Admin (md5: 180ed957391f297760832496b7a03a95)
macOS Booster (md5: dc50b5d514f718cc1741e0f08f6a0239)
macOS Server (md5: 1df7ceed1a5deda8d484724ad0dc5789)
macOS Client (md5: e147133402afb9339d0e343912f591f5)

Remember that to upgrade macOS FileWave clients you should use the Upgrade Fileset. Never deploy the macOS Client listed above to an existing device. It is intended only for manual initial installs, and even for those you are better off creating an installer at https://custom.filewave.com 

Windows Upgrade Fileset (md5: 61924c93173e63a30aa3357a03bcd752)
Windows Admin (md5: 4e00be9d1fc57f066a7affd2c37df5dd)
Windows Booster (md5: 6770f46614774262a77ad5cd2d5127fb)
Windows Client (md5: 323d2b13e4af04357e3c35ebea914213)

Remember that to upgrade Windows FileWave clients you should use the Upgrade Fileset. Never deploy the Windows Client listed above to an existing device. It is intended only for manual initial installs, and even for those you are better off creating an installer at https://custom.filewave.com 

Kiosk on iOS / iPadOS is now automatically installed from a CDN. (Read More)

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: 740f1a780bed1d1a25d01a08ae2e53c9)

Debian Linux Installers (md5: d87606803638c028beac5f8afc3bbb64)
Debian Linux Server (md5: c35f56e1c81c577e68a6edcc533d5fc9)
Debian Linux Booster (md5: 1b0cfeff43386dd5a36f62398016ffd2)

Upgrading the FileWave Server

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

# Login via SSH as root or ensure you're using sudo for the commands

# 1. OS Upgrades:
sudo apt update -y
sudo DEBIAN_FRONTEND=noninteractive apt-get upgrade -y -o Dpkg::Options::="--force-confold"

# 2. Install Essential Tools:
sudo apt install -y zip net-tools gdebi-core

# 3. Download the FileWave Server package:
wget https://fwdl.filewave.com/15.3.1/fwxserver_15.3.1_amd64.deb -P /tmp

# 4. Install the FileWave Server using gdebi:
sudo gdebi -n /tmp/fwxserver_15.3.1_amd64.deb

# 5. Reboot the system to complete the installation:
sudo reboot

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

# Login via SSH as root or ensure you're using sudo for the commands

# 1. OS Upgrades:
sudo apt update -y
sudo DEBIAN_FRONTEND=noninteractive apt-get upgrade -y -o Dpkg::Options::="--force-confold"

# 2. Install Essential Tools:
sudo apt install -y zip net-tools gdebi-core

# 3. Download the FileWave Booster package:
wget https://fwdl.filewave.com/15.3.1/fwbooster_15.3.1_amd64.deb -P /tmp

# 4. Install the FileWave Booster using gdebi:
sudo gdebi -n /tmp/fwbooster_15.3.1_amd64.deb

# 5. Reboot the system to complete the installation:
sudo reboot

Debian Linux: It is preferred that you use this for a new server, booster or IVS.
VMware and VirtualBox (OVA) Server Appliance (md5: 5404fe6160437b332da674ba6bf69ba7 )
VMware and VirtualBox (OVA) Booster Appliance (md5: 6ba9ce6b69712afc069fc40fef615c12)
VMware and VirtualBox (OVA) Imaging Appliance (md5: 2795e0258c24f19b1780b867dfa04cd2)

CentOS Linux:
VMware and VirtualBox (OVA) Server Appliance (md5: c8f1cc7cc2d581cd1dda8e229dab437f)
VMware and VirtualBox (OVA) Booster Appliance (md5: 814be015055f1e77418f2f34e8702ed0)
VMware and VirtualBox (OVA) Imaging Appliance (md5: 2b1776bb9a6bcacaf51b27c096f78d4f)

To get started with the FileWave Server appliance please see: 1. Installation and Setup | FileWave KB
For a Booster you would setup networking just like you do with Server and then: Booster Installation | FileWave KB
For more information about importing the IVS appliance please see: Importing FileWave Appliances

Debian Linux: It is preferred that you use this for a new server, booster or IVS.
Hyper-V (VHD) Server Appliance (md5: e48e649a4b09849d1c0a30d6f25d8575)
Hyper-V (VHD) Booster Appliance (md5: ca31a5c0930defdf70eba8465eb85416)
Hyper-V (VHD) Imaging Appliance (md5: 809d88619ab359a641a4cc570a40c77f)

CentOS Linux:
Hyper-V (VHD) Server Appliance (md5: 005d5cc74a68428547c7cc8d7f797482)
Hyper-V (VHD) Booster Appliance (md5: dee0d85e7bc9398c2d41a950a1e39fea)
Hyper-V (VHD) Imaging Appliance (md5: 0b71704316983552b242765ef1e7add0)

To get started with the FileWave Server appliance please see: 1. Installation and Setup | FileWave KB
For a Booster you would setup networking just like you do with Server and then: Booster Installation | FileWave KB
For more information about importing the IVS appliance please see: Importing FileWave Appliances

CentOS is EOL in 2024. Migrating to Debian is highly recommended.

CentOS Linux Installers (md5: b7beaf517f3bccad73b3358962df9ff4)
CentOS Linux Server (md5: fa30b9e3aa2a6514e13e94b1e12009b5)
CentOS Linux Booster (md5: dd7d2bf1abbf4399cda50b809cef1190)

If when doing yum update or upgrade you get a note that no updates are available it may be that you block access to some countries. yum clean all can clear the cache so that the upgrades can happen.

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

# login via ssh / root or put sudo at the start of each line
sudo yum update -y
sudo yum upgrade -y
sudo yum install -y --nogpgcheck https://fwdl.filewave.com/15.3.1/fwxserver-15.3.1-1.0.x86_64.rpm
sudo reboot

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

# login via ssh / root
sudo yum update -y
sudo yum upgrade -y
sudo yum install -y --nogpgcheck https://fwdl.filewave.com/15.3.1/fwbooster-15.3.1-1.0.x86_64.rpm
sudo 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
sudo yum update -y
sudo yum update -y filewave-IVS
sudo yum upgrade -y
sudo 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
sudo yum install -y filewave-IVS
sudo yum upgrade -y
sudo 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.

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 12) 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 13, 14 (Intel and Apple Silicon)
• Linux CentOS 7.9 x86_64
• Debian 12.2 x86_64 (Note that any Debian 12.x is expected to work, and applying security updates may move you to a higher version.)
  

Expected to work

• macOS 11, 12 (Intel and Apple Silicon)

Fully Tested by QA

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

Expected to work

• macOS 11, 12 (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
  
• macOS 10.15 → Legacy Version 15.0.1

Fully Tested by QA

• iOS 16.1, 17
• iPadOS 16, 17
• tvOS 16, 17
• Android 13, 14 (EMM Client)
• Chromebook
  

Expected to work

• iOS 14, 15
• iPadOS 14, 15
• tvOS 14, 15
• Android 8 to 12 (EMM)
  

Legacy

• iOS 13 → Legacy Version 15.0.1
• iOS 10, 11, 12 → Legacy Version 13.1.5

Fully Tested by QA

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

Expected to work

• macOS 11, 12 (Intel and Apple Silicon)

Fully Tested by QA

• macOS 13, 14 (Intel and Apple Silicon)
• Windows 10 (Ent/Pro 21H1 and above), 11 (Ent/Pro 21H2 and above)
• Linux CentOS 7.9 x86_64
• Debian 12.2 x86_64 (Note that any Debian 12.x is expected to work, and applying security updates may move you to a higher version.)
  

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 Debian 12 and 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.

Central goes Dark

FileWave Central introduces a new Dark Mode UI - for FileWave admins working at night ! More...

Unified backend for Model Update (Technical Preview)

Model Update is one of the key features of FileWave; Model Update allows you to apply complex changes to your organization only when you’re ready to deploy them and to revert unwanted changes. FileWave 15.3.0 brings a new Model Update mechanism, now running in a single component. This is the first step before new features and improvements can be added to Model Update. In this version, we focused on consistency with existing Model Update (to make sure nothing changes in your deployments) and on shortening update times. Model Update “v2” is a Technical Preview in 15.3.0, so it is not enabled by default.

Improved Client / Booster / Server communication

FileWave 11 introduced Booster Routing, a feature that allows off-loading direct traffic to the server by routing messages via Booster. This feature provides additional security if you only allow boosters to connect to your server and have all your devices only reach boosters. With FileWave 15.0, the internal notification system has switched entirely to NATS, replacing ZMQ; NATS, in addition to built-in security features and improved performances, brings much more flexibility and can then be used in more areas. FileWave 15.3 can now use NATS as the communication protocol for all maintenance messages between client and server. Fileset delivery still uses the classic protocol, but messages like Fileset status or check-in now use the lightweight and fast delivery mechanism offered by NATS. 

Declarative Device Management

FileWave 15.3.0 is the first implementation of Apple’s new device management mechanism, Declarative Device Management (DDM). It will use the new Status Report for applications, providing quick and accurate Fileset Status updates for apps installed via MDM (App Store apps) on compatible iOS, iPadOS, and tvOS devices.

Therefore, FileWave 15.3.0 contains the foundations for support for more DDM features, such as software update management or application installation via DDM, which are being built and will be provided in coming releases.

More...

We are excited to announce the expansion of Chromebook Management, addressing significant performance improvements and introducing new features to enhance user experience.

Commands

1. REMOTE_POWERWASH Command

• Description: System administrators can remotely powerwash ChromeOS devices, resetting them to factory settings for efficient troubleshooting and maintaining device security.

• Execution: Initiates the powerwash process, erasing all user data and configurations.

2. WIPE_USERS Command

• Description: System administrators can remotely and securely wipe user data from devices, ensuring compliance with data protection regulations and maintaining organizational security.

• Execution: Initiates the data-wiping process on all user accounts.

3. REBOOT Command

• Description: Introducing the REBOOT command, enabling system administrators to reboot devices for troubleshooting remotely and applying system updates.

• Execution: Initiates the remote reboot process on the selected devices.

4. Command History tab

• Description: Users can now view all information related to sending REMOTE_POWERWASH, WIPE_USERS, and REBOOT Commands in the Command History tab for Chromebook devices.

More details available → Powerwash / Wipe Users on ChromeOS (15.3+) and Reboot for ChromeOS (15.3+)

Bug Fixes and Improvements

1. Reduced Chromebook Sync Time

Issue: Some users reported extended sync times, with an average duration of around 15 minutes for certain customers. Sync was only performed once per day.

Resolution: We have addressed this concern by implementing optimizations that result in a 30% reduction in sync time. Chromebook syncing is now more efficient and streamlined, ensuring a faster and smoother experience.

2. Manual Sync Time Configuration

Issue: Users had limited control over the timing of Chromebook sync, with synchronization occurring only once daily.

Resolution: In response to user feedback, we have introduced a new feature that allows users to set up manual sync times. Sync intervals can be configured between 1 and 24 hours. If no specific time is set, the default sync interval remains at 24 hours. This enhancement provides greater flexibility in managing Chromebook updates according to your organization's needs.

3. Custom Field(s) Annotation Sync

Issue: Changes to annotated fields were causing discrepancies when updating the model.

Resolution:

• Annotated fields in Edit Custom Fields now update immediately upon clicking Save, independently of the Model Update, ensuring swift and accurate changes.

• The Chromebook Data tab in Device Details is removed. Users can access Chromebook-related info by double-clicking on the device, eliminating the need for an additional tab.

• The Device Details View now offers a more informative and user-friendly experience for Annotated fields.

• Annotated fields are seamlessly displayed and editable in the Edit Custom Fields dialog, like any other custom fields.

• A convenient button in the Client Info dialog allows users to sync annotated fields (one way: Google to FileWave) individually for specific devices, offering granular control over data synchronization.

These comprehensive resolutions address the reported issues, providing a seamless and efficient experience in managing Chromebooks, with real-time syncing of annotated fields and enhanced control over synchronization intervals.

FileWave IVS Appliance is now based on Debian!

FileWave Networking Imaging 15.3.x brings compatibility with FileWave 15.3.x.

• PXE Kernel: 6.6.7
• Buildroot: 2023.11
  

App portal for iOS/iPadOS

Evolution of App Portal for iOS/iPadOS: Transition from Technical Preview to Official Release

In our commitment to continuous improvement and user-centric development, we are excited to announce a significant milestone in the journey of App Portal for iOS/iPadOS. Starting from version 15.3.0, App Portal has officially graduated from its technical preview phase, now standing as a fully realized and polished application.

Key Points:

1. From Technical Preview to Real App:
   In previous releases, App Portal for iOS/iPadOS was introduced as a technical preview, allowing users to explore its functionalities and provide valuable feedback. With version 15.3.0, we are thrilled to elevate App Portal to the status of a fully-fledged, official application.

2. Enhancements and Stability:
   The transition signifies not only the culmination of user feedback but also substantial enhancements and optimizations to ensure the stability, reliability, and performance of the App Portal for iOS/iPadOS.

3. A Seamless User Experience:
   Users can now enjoy a seamless and refined experience with App Portal, harnessing its full potential for efficient and intuitive mobile application management.5.3.0 and beyond.

More details here → Automatic updating of iOS Kiosk (15.3+)

Desktop Kiosk for macOS and Windows

The transition from App Portal version 15.0.0 to version 15.3.0 represents a significant evolution, akin to the transformative experience observed when comparing the Android Play Store and the App Store. This upgrade places a primary emphasis on completely overhauling the user interface (UI) to provide a sleek, contemporary, and exceptionally intuitive platform, aligns with our users' evolving expectations.

While version 15.0.0 laid the groundwork for functionality, version 15.3.0 responds to user feedback and industry trends, recognizing the demand for a more sophisticated and streamlined UI. Here's how the new version draws inspiration from the design excellence of both the Android Play Store and the App Store:

1. Unified Design Paradigm:
   The UI design seamlessly unifies elements from both the Android Play Store and the App Store, creating a harmonious blend of familiarity and innovation.

2. Intuitive Navigation:
   Building on the success of version 15.0.0, version 15.3.0 introduces a reimagined navigation system with intuitive menus, recognizable icons, and seamless flows, akin to the ease of navigation in both app marketplaces.

3. Visual Delight:
   The new UI isn't just functional; it's a visual delight with engaging animations, subtle transitions, and tastefully curated visuals, providing an immersive experience similar to the Android Play Store and the App Store.

4. Enhanced Customization:
   Version 15.3.0 brings enhanced customization options, allowing users to personalize their interface similar to the Android Play Store and the App Store, fostering a sense of ownership over their app experience.

5. Responsive Design:
   Like the responsiveness of the Android Play Store and the App Store across devices, our app now adapts seamlessly to various screen sizes, ensuring a consistent and optimized experience.

Additionally, with version 15.3.0, we've introduced some enhancements. Users will now receive clear indications when installing certain filesets that a reboot is required for optimal performance. This improvement ensures transparency and empowers users with the necessary information for a seamless experience. By incorporating these enhancements, App Portal solidifies its commitment to delivering a cutting-edge, user-friendly experience that aligns with evolving user expectations and industry trends. Version 15.3.0 sets the stage for a future where App Portal evolves dynamically, staying at the forefront of user-centric innovation.

More details here →

The following features have been deprecated from FileWave 15.3.0. They are present but will be removed in a future release:

• CentOS: As CentOS 7 being End-Of-Life on June 30, 2024, FileWave is available and supported on Debian. FileWave won't be released on CentOS after CentOS is EOL.

• Compatibility Mode: Communication between FileWave components is encrypted and relies on TLS certificates for several years now. Back in the day, to facilitate the transition, a Compatibility Mode was introduced, allowing clients running versions older than 13.1 to still be managed by a more recent server despite not supporting proper encryption. It is now time to drop compatibility mode to enforce secured communications. This means the minimum OS versions that can be enrolled are macOS 10.11 and Windows 7 SP1 - but it is obviously not recommended to run outdated, unsecured end-of-life Operating Systems.

• OS Updates on Apple Devices: Managing OS updates on Apple devices has evolved significantly. Initially relying on manual commands and customizable catalogs, the process transitioned to MDM protocols, introducing challenges in reliability and control. Apple's introduction of GDMF and the more recent DDM protocol aims to simplify and enhance the reliability of OS update management. FileWave 15.4.0 will adopt GDMF for update reporting and switch to DDM for macOS updates (Sonoma and later), while continuing to use MDM for older iOS/iPadOS versions. This update signifies FileWave's commitment to improving the management of OS updates, addressing past issues and leveraging Apple's latest technologies for a streamlined process. More...
  
• Legacy macOS Imaging: Changes made by Apple with APFS, T2 chips and Apple Silicon, Imaging macOS devices has been part of history for a long time. With the deprecation of Compatibility mode, the last reason for keeping macOS imaging options in FileWave are gone.
  

• FCM Deprecation Support:

  • Legacy Firebase Cloud Messaging (FCM) APIs are being deprecated by Google.
  • FileWave will support this deprecation in the official release of 15.4.
  • More...

The following features have been removed from FileWave 15.3.0:

• As the new desktop kiosk is based on 64-bit libraries, FileWave 15.3.0 will not be supported on Windows 32-bit platforms. FileWave Agent (fwcld) is still a 32-bit executable, meaning there is no change in how Filesets are deployed, and scripts are executed. Moving to a 64-bit application is expected to happen later this year.

Several 3rd party have been updated, for bug or security issue fixes or new features. Mainly:

• OpenSSL 3.2.1

• Python 3.11.7

• Django 5.0.1

• Postgresql 12.18

Bug fixes:

• FWRD-1439 Fixed an issue where Custom Field Dialog could incorrectly detect changes
  
• FWRD-1440 Fixed an issue where automatically created LDAP based smart groups could be modified
  
• FWRD-2118 Fixed an issue where changing the revision of a fileset dependency would remove and reinstall the dependency instead of only updating differences between revisions
  
• FWRD-2445 Fixed an issue where it would be possible to change permission of a fileset group for which current admin does not have write permission
  
• FWRD-3173 Improved logs when using unsupported image type for iOS WallPaper
  
• FWRD-3365 Fixed an issue where Preferences would show incorrect description for preferred licensing option
  
• FWRD-3458 Made German translations regarding dependencies clearer
  
• FWRD-3800 Fixed an issue where enrolling two IVS would fail due to duplicated fingerprint
  
• FWRD-4232 Fixed UI issue in Device Info view in FileWave Anywhere.
  
• FWRD-4339 Fixed a potential issue where Windows Upgrade Fileset would fail to update Windows client
  
• FWRD-4715 Fixed handling multiple Organization Invite in Registration modal in Kiosk for iOS/iPadOS.
  
• FWRD-11165 Fixed issue with logo qualities in Kiosk for iOS/iPadOS.
  
• FWRD-11403 Fixed font in Kiosk UI.
  
• FWRD-11414 Fixed bug regarding error message related to Faild to fetch data in iOS/iPadOS App Portal.
  
• FWRD-11489 Fixed bug by Chromebooks sync time - it is now reduced by 30%. Also there is new field in FileWave Central Preferences where setup shorter sync interval (in hours) is possible.
  
• FWRD-11581 Fixed an issue where legacy dashboard would report incorrect disk space if server data folder is not on the same volume as root
  
• FWRD-11594 Fixed a cosmetic issue related to Country names displayed by App Store dialogs
  
• FWRD-11750 Fixed an issue where logs could be incorrectly be filled by entries related to errors when synchronizing VPP apps metadata after 9646 error
  
• FWRD-11776 Improved internal scheduler startup phase
  
• FWRD-11810 Fixed issues/added functionalities with managing LDAP Smart Groups in FileWave Anywhere.
  
• FWRD-11830 Fixed an issue on macOS Sonoma where client assistant and client monitor would not use the same device name
  
• FWRD-11867 Fixed a potential issue where invalid request could be made to VPP service, leading to error 9602
  
• FWRD-11879 Improved how VPP errors 9646 are handled
  
• FWRD-11973 Fixed minor UI issues in Filtering section of Kiosk for iOS/iPadOS.
  
• FWRD-12001 Fixed an issue where query builder would not allow using numbers larger than 2147483647
  
• FWRD-12007 Fixed a cosmetic issue where Association option fields would have inconsistent width
  
• FWRD-12104 Fixed an issue related to Dock profile where Merge with User's dock option would not be applied properly
  
• FWRD-12169 Fixed an issue where inventory reports would return incorrect data due to the way client id is retrieved
  
• FWRD-12171 Fixed issue regarding Devices view load being slow in FileWave Anywhere.
  
• FWRD-12214 Debian appliances have now also 500 GB of free space
  
• FWRD-12336 Fixed an issue where Webmin would not be properly configured on Debian appliances
  
• FWRD-12338 Fixed an issue where rpm installer would not properly stop upgrade in preflight step if a Database error is detected
  
• FWRD-12415 Fixed an issue where Associated Domains options would not be properly applied to Enterprise Applications (IPA)

macOS Installers DMG (md5: 58878b66ea0c19ce919f7ab3584c9089)
macOS Upgrade Fileset (md5: 1f1f14ccab8de1452f4895d081134a42)
macOS Admin (md5: 3f4eed7f47d313515b9338d6c0329322)
macOS Booster (md5: bf7f95a9d4b8065203a3bb613f8ff4f7)
macOS Server (md5: 02182b1f2cbbfce5d6290f150cccdfaf)
macOS Client (md5: 539e9101de919a93d47a30634908027c)

Remember that to upgrade macOS FileWave clients you should use the Upgrade Fileset. Never deploy the macOS Client listed above to an existing device. It is intended only for manual initial installs, and even for those you are better off creating an installer at https://custom.filewave.com 

Windows Upgrade Fileset (md5: 155f3494d034631bb154d9e5c67f3668)
Windows Admin (md5: d44c9440f70e3c3db990d07f6217ef37)
Windows Booster (md5: 3600de850d3df9f3d0d08f0395c52eca)
Windows Client (md5: ac298e932e4103b0a5851cf12c21d17d)

Remember that to upgrade Windows FileWave clients you should use the Upgrade Fileset. Never deploy the Windows Client listed above to an existing device. It is intended only for manual initial installs, and even for those you are better off creating an installer at https://custom.filewave.com 

Kiosk on iOS / iPadOS is now automatically installed from a CDN. (Read More)

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: 045629b134ca114e83247866e2a251bb)

Debian Linux Installers (md5: 7a4e8d0ce7c3394fc15948f5d5f4eef5)
Debian Linux Server (md5: f1c904956a3448e1d02b698c455145fd)
Debian Linux Booster (md5: 09785f7cf3aeff309c9a0c545fa2fc2c)

Upgrading the FileWave Server

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

# Login via SSH as root or ensure you're using sudo for the commands

# 1. OS Upgrades:
sudo apt update -y
sudo DEBIAN_FRONTEND=noninteractive apt-get upgrade -y -o Dpkg::Options::="--force-confold"

# 2. Install Essential Tools:
sudo apt install -y zip net-tools gdebi-core

# 3. Download the FileWave Server package:
wget https://fwdl.filewave.com/15.3.0/fwxserver_15.3.0_amd64.deb -P /tmp

# 4. Install the FileWave Server using gdebi:
sudo gdebi -n /tmp/fwxserver_15.3.0_amd64.deb

# 5. Reboot the system to complete the installation:
sudo reboot

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

# Login via SSH as root or ensure you're using sudo for the commands

# 1. OS Upgrades:
sudo apt update -y
sudo DEBIAN_FRONTEND=noninteractive apt-get upgrade -y -o Dpkg::Options::="--force-confold"

# 2. Install Essential Tools:
sudo apt install -y zip net-tools gdebi-core

# 3. Download the FileWave Booster package:
wget https://fwdl.filewave.com/15.3.0/fwbooster_15.3.0_amd64.deb -P /tmp

# 4. Install the FileWave Booster using gdebi:
sudo gdebi -n /tmp/fwbooster_15.3.0_amd64.deb

# 5. Reboot the system to complete the installation:
sudo reboot

Debian Linux: It is preferred that you use this for a new server, booster or IVS.
VMware and VirtualBox (OVA) Server Appliance (md5: 7255385e19f3e900654c43270a862aba )
VMware and VirtualBox (OVA) Booster Appliance (md5: 56818d3f2c9e582a7bac3e442fb15b7b)
VMware and VirtualBox (OVA) Imaging Appliance (md5: 4dc61fb85ab6162437b831d64847eb0f)

CentOS Linux:
VMware and VirtualBox (OVA) Server Appliance (md5: 5032f97463f0f7ee7e980e71b1bd98d2)
VMware and VirtualBox (OVA) Booster Appliance (md5: 9276045e7e2cfec887c28c344d3c0a2f)
VMware and VirtualBox (OVA) Imaging Appliance (md5: 7e28a5f16421799848a956c624f45763)

To get started with the FileWave Server appliance please see: 1. Installation and Setup | FileWave KB
For a Booster you would setup networking just like you do with Server and then: Booster Installation | FileWave KB
For more information about importing the IVS appliance please see: Importing FileWave Appliances

Debian Linux: It is preferred that you use this for a new server, booster or IVS.
Hyper-V (VHD) Server Appliance (md5: 3eb029196f6b108016196e0f4b766dad)
Hyper-V (VHD) Booster Appliance (md5: 98aef762380e04fa1993a8e26ffbe4ae)
Hyper-V (VHD) Imaging Appliance (md5: 7167d18d719df982cc42272ae9a48533)

CentOS Linux:
Hyper-V (VHD) Server Appliance (md5: 7d3c093b11b8fb0fc50770d62e699f5f)
Hyper-V (VHD) Booster Appliance (md5: 7d3c093b11b8fb0fc50770d62e699f5f)
Hyper-V (VHD) Imaging Appliance (md5: e8c3656e767b3d7372826233fb85e7e6)

To get started with the FileWave Server appliance please see: 1. Installation and Setup | FileWave KB
For a Booster you would setup networking just like you do with Server and then: Booster Installation | FileWave KB
For more information about importing the IVS appliance please see: Importing FileWave Appliances

CentOS is EOL in 2024. Migrating to Debian is highly recommended.

CentOS Linux Installers (md5: a181ccd087b30f6b2a66bf73becc494c)
CentOS Linux Server (md5: 4db68bfc34d29ddb25e9c422327f75c8)
CentOS Linux Booster (md5: 4a30568a37943af7158894aa55311174)

If when doing yum update or upgrade you get a note that no updates are available it may be that you block access to some countries. yum clean all can clear the cache so that the upgrades can happen.

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

# login via ssh / root or put sudo at the start of each line
sudo yum update -y
sudo yum upgrade -y
sudo yum install -y --nogpgcheck https://fwdl.filewave.com/15.3.0/fwxserver-15.3.0-1.0.x86_64.rpm
sudo reboot

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

# login via ssh / root
sudo yum update -y
sudo yum upgrade -y
sudo yum install -y --nogpgcheck https://fwdl.filewave.com/15.3.0/fwbooster-15.3.0-1.0.x86_64.rpm
sudo 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
sudo yum update -y
sudo yum update -y filewave-IVS
sudo yum upgrade -y
sudo 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
sudo yum install -y filewave-IVS
sudo yum upgrade -y
sudo 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.

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 12) 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 13, 14 (Intel and Apple Silicon)
• Linux CentOS 7.9 x86_64
• Debian 12.2 x86_64 (Note that any Debian 12.x is expected to work, and applying security updates may move you to a higher version.)
  

Expected to work

• macOS 11, 12 (Intel and Apple Silicon)

Fully Tested by QA

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

Expected to work

• macOS 11, 12 (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
  
• macOS 10.15 → Legacy Version 15.0.1

Fully Tested by QA

• iOS 16.1, 17
• iPadOS 16, 17
• tvOS 16, 17
• Android 13, 14 (EMM Client)
• Chromebook
  

Expected to work

• iOS 14, 15
• iPadOS 14, 15
• tvOS 14, 15
• Android 8 to 12 (EMM)
  

Legacy

• iOS 13 → Legacy Version 15.0.1
• iOS 10, 11, 12 → Legacy Version 13.1.5

Fully Tested by QA

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

Expected to work

• macOS 11, 12 (Intel and Apple Silicon)

Fully Tested by QA

• macOS 13, 14 (Intel and Apple Silicon)
• Windows 10 (Ent/Pro 21H1 and above), 11 (Ent/Pro 21H2 and above)
• Linux CentOS 7.9 x86_64
• Debian 12.2 x86_64 (Note that any Debian 12.x is expected to work, and applying security updates may move you to a higher version.)
  

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.

Note that a Debian version of IVS will be coming soon.

FileWave Central User Interface has been refreshed ; FileWave Central is adopting FileWave Anywhere more modern look and feel. We hope you’ll love as much as we do the new FileWave Central !

Support for macOS Sonoma (macOS 14):

Testing macOS 14, we found that some changes are required to properly restart FileWave Desktop agent (fwcld) after upgrade. These changes have been added to version 15.1.

This means that:
* It is recommended to upgrade macOS clients to FileWave 15.1 prior to upgrade to macOS 14 ;
* As the changes are related to permissions and are solved by automatically deploying a TCC profile, it is recommended to MDM-enroll macOS devices. This issue can be worked around by making upgrade fileset a reboot fileset.

FileVault 2 enforcement:

It is now possible to enforce Full Disk Encryption (FileVault 2) at enrollment time to increase security in your organization.

Return to Service (iOS / iPadOS 17): Learn More...

Parameterized WiFi profiles are now support with Return To Service.

Profile is delivered to the device at the time EraseDevice command is issued, and parameterization is done by FileWave server ; this means that parameterization happens at the time the command is sent to the device, and uses current values, including user-based values.
As WiFi profile is required prior to the enrollment, it can't use new enrollment credentials for parameterization.

New profiles or profile modifications:

• Managed Domains: new setting to configure urls to relax cross-site tracking prevention
• Dock: new settings to configure persistent items in the dock, and enforce settings like Auto-Hide or Show-Indicator, as well as new option for “Dock Fixup Override”.
• Security & Privacy : new “App Data” System Policy to pre-approve apps to access other app’s data (TCC)
• VPN Profile :
  • Extend DNS options with encryption options
  • Support for Transparent Proxy for Cisco AnyConnect, Cisco AnyConnect Legacy, Juniper SSL, F5 SSL, SonicWALL Mobile Connect, Aruba VIA
  • new options to exclude Cellular Services or APNS
• Network Relays can now be configured using corresponding profiles
• Extensible Singled Sign On profile extended with Platform SSO options
• Network Profile : New setting to configure TLS Trusted Certificates, settings to specify AD or OD credentials, HESSID

Network Relays:

• Applications can be configure to automatically use Network Relays as defined in the newly supported Network Relays profile

Shared iPads:

• Passcode policy and Auto Lock time can now be configured for Shared iPads ; these settings are deployed using Command Policy profile.

VPP API : “v2” is now enabled by default (15.1)

VPP v2 API is not compatible with legacy VPP tokens (created before Apple School or Business Manager but with legacy vpp.itunes.apple.com service). Transferring licenses to Location-based token is highly recommended.

MSI properties:

It is now possible to specify MSI properties to be applied during installation and, for installers supporting it, during uninstallation.

Default script:

Default script type is now PowerShell instead of Python (Central).

FileWave Networking Imaging 15.1.x brings compatibility with FileWave 15.2.x.

• PXE Kernel: 6.5.5
• Buildroot: 2023.08.01
  

The transition from version 1.0 to version 2.0 of our app signifies a major leap forward in terms of user experience and visual appeal, much like the transformation seen when comparing the Android Play Store and the App Store. In this upgrade, the primary focus has been on completely revamping the user interface (UI) to provide a sleek, modern, and highly intuitive platform that caters to our users' evolving expectations.

Version 1.0 laid the foundation for the app's functionality and introduced users to a diverse array of features and content. However, user feedback and industry trends have illuminated the need for a more sophisticated and streamlined UI that aligns with contemporary design principles and enhances the overall user journey.

With version 2.0, the app undergoes a stunning visual makeover, drawing inspiration from the aesthetic excellence of both the Android Play Store and the App Store:

1. Unified Design Paradigm: Our new UI design unifies elements from both the Android Play Store and the App Store, creating a harmonious blend of familiarity and innovation. This design consistency ensures that users across various platforms feel comfortable while navigating the app.

2. Intuitive Navigation: Building on the success of version 1.0, version 2.0 introduces a reimagined navigation system. Users can effortlessly explore and discover content thanks to intuitive menus, recognizable icons, and seamless navigation flows, akin to the ease of navigation in both app marketplaces.

3. Visual Delight: The new UI is not just about functionality; it's a visual treat. Engaging animations, subtle transitions, and tastefully curated visuals combine to make every interaction with the app a delightful experience, echoing the immersive nature of the Android Play Store and the App Store.

4. Enhanced Customization: Version 2.0 introduces enhanced customization options, allowing users to personalize their interface just as they would within the Android Play Store and the App Store. Users can arrange and prioritize content according to their preferences, granting them a sense of ownership over their app experience.

5. Responsive Design: Much like the Android Play Store and the App Store's responsiveness across devices, our app now adapts seamlessly to various screen sizes and orientations. This ensures a consistent and optimized experience whether users are browsing on smartphones, tablets, or desktops.

By transitioning from version 1.0 to version 2.0 with a UI overhaul reminiscent of the Android Play Store and the App Store, our app solidifies its commitment to delivering an unparalleled user experience. This transformation isn't just about aesthetics; it's a testament to our dedication to meeting the evolving needs of our users in an engaging, intuitive, and visually striking manner. As we bridge the gap between the old and the new, version 2.0 sets the stage for a future where our app continues to evolve in tandem with user expectations and industry trends.

Kiosk 2.0 (Technical Preview) Enterprise app can be downloaded here : https://fwdl.filewave.com/15.2.0/App_Portal_Beta_15.2.0.ipa

More: Kiosk 2.0 for iOS (Technical Preview)

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

• FileWave Server, Boosters and IVS running on CentOS will cease to be published due to the pending EOL of CentOS. Debian replaces it, but we will publish a 15.3.0 for CentOS/Debian/macOS to give time to migrate: FileWave Server on CentOS End of Life

The following features have been removed from FileWave 15.2.1 :

• 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

• FWRD-11264 Fixed an issue where Central Admin side bar could not be made larger
• FWRD-11344 Fixed an issue where expand arrow and status indicator color become white and not visible properly for row selection in License Management view
• FWRD-11750 Fixed an issue where logs could be incorrectly be filled by entries related to errors when synchronizing VPP apps metadata after 9646 error
• FWRD-11867 Fixed a potential issue where invalid request could be made to VPP service, leading to error 9602
• FWRD-11879 Improved how VPP errors 9646 are handled
• FWRD-11882 Fixed an issue where iOS fileset status would incorrectly be "Associated" instead of "Available in Kiosk.."
• FWRD-11975 Fixed various issues related to communication with Google EMM service
• FWRD-11991 Improved speed of VPP License synchronization
• FWRD-12006 Fixed an issue where error related to VPP event could break event handling
• FWRD-12009 Fixed an issue where VPP sync process could create too many entries in database, leading to subsequent syncs require full sync

3rd party opensource components have been upgraded. Most relevant, but not only:

• OpenSSL 3.0.12
• Apache 2.4.58
• Postgres 12.16
• Python 3.10.13
• Qt 5.15.15
• ZLib 1.3
• Various library upgrades for bug and security issue fixes

Bug fixes:

• FWRD-982 Fixed an issue where fileset status could incorrectly be "Deleted" when changing deployed revision
• FWRD-1805 Fixed category for Command Policy Payload (Central Admin)
• FWRD-2101 Made sure Custom Field internal name can't end with underscore
• FWRD-2342 Fixed an issue where UseComputerNameForComputerRecordName key would incorrectly be added to Login Window Profile (Central Admin)
• FWRD-3102 Fixed an issue where it would not be possible to remove a fileset being a dependency of another fileset
• FWRD-3510 Fixed an issue where RSR updates would not be visible for macOS
• FWRD-3551 Fixed various issues related to dialogs Z-Order
• FWRD-3643 Fixed an issue where main window would come foreground after closing client monitor from client info dialog
• FWRD-3742 Fixed an issue where search would not work properly for scheduled report queries
• FWRD-3828 Fixed inconsistent button focus in Central Preferences dialog
• FWRD-4011 Fixed incorrectly formatted log entry related to smart group evaluation in fwxadmin.log
• FWRD-4442 Fixed Payload Description behaviour in FileWave Anywhere to match FileWave Central.
• FWRD-4776 Fixed an issue where signing out of FileWave would prevent from login into Grafana Dashboard
• FWRD-11270 Fixed an issue where global Content-Filter or DNS proxy profiles would not be applied (only per-app versions) 
• FWRD-11340 Fixed an issue where Setup Assistant section in DEP Profile dialog would not show all options
• FWRD-11343 Fixed an issue where inactive text contrast would be too low (FileWave Central)
• FWRD-11353 Fixed Passcode Lock Grace Period field for Shared iPad Command Policy (FileWave Central)
• FWRD-11365 Central Admin windows too small for Default Scale / Resolution (1440x900) 
• FWRD-11387 Fixed an issue where model update decision when two filesets for the same iOS application are associated via Fileset group to the same device would not be consistent
• FWRD-11402 Fixed Passcode Lock Grace Period field for Shared iPad Command Policy (FileWave Anywhere)
• FWRD-11495 Fixed an issue where duplicating a profile created outside FileWave would prevent from updating the model
• FWRD-11583 Fixed an issue on macOS Sonoma where Client Assistant would not use the same device name as the one used during enrollment
• FWRD-11610 Reduced required database disk space for revoked certificates
• FWRD-11613 Fixed an issue where the ampersand symbol would not be displayed in Clients View or Fileset View
• FWRD-11615 Fixed an issue where clone icons would be too hard to identify
• FWRD-11625 Fixed an issue where association timing fields would be to narrow (Central Admin)
• FWRD-11638 Fixed an issue where ampersand characters would not always be displayed in tabs or column headers
• FWRD-11641 Fixed margin on default revision picker dialog
• FWRD-11670 Fixed an issue where revert model could prevent subsequent update model
• FWRD-11692 Fixed an issue where group clone icon would be missing (Central Admin)
• FWRD-11264 Fixed an issue where Central Admin side bar could not be made larger
• FWRD-11344 Fixed an issue where expand arrow and status indicator color become white and not visible properly for row selection in License Management view

macOS Installers DMG (md5: 67a134acf540818408478ef622c7ca65)
macOS Upgrade Fileset (md5: 90d62f2b03e16b000d5d87bf871f1889)
macOS Admin (md5: f22936cbf0da9aba4b1c1bc7fa818ec0)
macOS Booster (md5: 3fef3dc0a30646d93cad17e3b62d69d2)
macOS Server (md5: edd3d36f5152fd62126f9dd86646b5d5)
macOS Client (md5: 0b30aa13e67d0ecdd1bfdc2b48140e90)

Remember that to upgrade macOS FileWave clients you should use the Upgrade Fileset. Never deploy the macOS Client listed above to an existing device. It is intended only for manual initial installs, and even for those you are better off creating an installer at https://custom.filewave.com 

Windows Upgrade Fileset (md5: 6f31766efa4407751f036aaf5b5a30bf)
Windows Admin (md5: 37bd4149f9165b34a4a1470a947d85f8)
Windows Booster (md5: 573c75a5060cae6563d480e4c4dd6feb)
Windows Client (md5: a4d72382a24fc74ec93283f8744543b9)

Remember that to upgrade Windows FileWave clients you should use the Upgrade Fileset. Never deploy the Windows Client listed above to an existing device. It is intended only for manual initial installs, and even for those you are better off creating an installer at https://custom.filewave.com 

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.

Note: version 15.2.2 has been released to renew 15.2.1 provisioning profile, which expires in April 2024.

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

https://fwdl.filewave.com/15.2.2/filewave/App%20Portal%2015.2.2.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: 8499c99d0f3769fdecac685616bbe382)

Debian Linux Installers (md5: 14219b62592bf7c279e8fbe38a4ddea2)
Debian Linux Server (md5: a935fe33ca3b3461a6fcd7b93b64007d)
Debian Linux Booster (md5: 534236bec74be2011a757d0202eb2f89)

Upgrading the FileWave Server

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

# Login via SSH as root or ensure you're using sudo for the commands

# 1. OS Upgrades:
sudo apt update -y
sudo DEBIAN_FRONTEND=noninteractive apt-get upgrade -y -o Dpkg::Options::="--force-confold"

# 2. Install Essential Tools:
sudo apt install -y zip net-tools gdebi-core

# 3. Download the FileWave Server package:
wget https://fwdl.filewave.com/15.2.1/fwxserver_15.2.1_amd64.deb -P /tmp

# 4. Install the FileWave Server using gdebi:
sudo gdebi -n /tmp/fwxserver_15.2.1_amd64.deb

# 5. Reboot the system to complete the installation:
sudo reboot

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

# Login via SSH as root or ensure you're using sudo for the commands

# 1. OS Upgrades:
sudo apt update -y
sudo DEBIAN_FRONTEND=noninteractive apt-get upgrade -y -o Dpkg::Options::="--force-confold"

# 2. Install Essential Tools:
sudo apt install -y zip net-tools gdebi-core

# 3. Download the FileWave Booster package:
wget https://fwdl.filewave.com/15.2.1/fwbooster_15.2.1_amd64.deb -P /tmp

# 4. Install the FileWave Booster using gdebi:
sudo gdebi -n /tmp/fwbooster_15.2.1_amd64.deb

# 5. Reboot the system to complete the installation:
sudo reboot

Please note that the IVS for Debian is first included in 15.3.1.

CentOS Linux:
VMware and VirtualBox (OVA) Server Appliance (md5: 7733c433cd6624e64955c1a1c2c827e0)
VMware and VirtualBox (OVA) Booster Appliance (md5: 16c6e5076b780d484baf8761ce17ddf2)
VMware and VirtualBox (OVA) Imaging Appliance (md5: 3c19d11f4b3742598a0fd3f4551e26db)

Debian Linux: It is preferred that you use this for a new server or booster. IVS is coming soon.
VMware and VirtualBox (OVA) Server Appliance (md5: c6f38b957e692c19e4934c98abf7fd32)
VMware and VirtualBox (OVA) Booster Appliance (md5: 3b05e55bd916cf99bf01ef790fbfadef)

To get started with the FileWave Server appliance please see: 1. Installation and Setup | FileWave KB
For a Booster you would setup networking just like you do with Server and then: Booster Installation | FileWave KB
For more information about importing the IVS appliance please see: Importing FileWave Appliances

CentOS Linux:
Hyper-V (VHD) Server Appliance (md5: 22c7d26c71142d16413db97cc2c56149)
Hyper-V (VHD) Booster Appliance (md5: 2c7836170a722ace54fb68f2f605236d)
Hyper-V (VHD) Imaging Appliance (md5: ab24bcdd2e756871e7efc148e326201a)

Debian Linux: It is preferred that you use this for a new server or booster. IVS is coming soon.
Hyper-V (VHD) Server Appliance (md5: a87eafd4e905026569b432bf8a497bac)
Hyper-V (VHD) Booster Appliance (md5: cecd30e3aa1256cee893b01f88063128)

To get started with the FileWave Server appliance please see: 1. Installation and Setup | FileWave KB
For a Booster you would setup networking just like you do with Server and then: Booster Installation | FileWave KB
For more information about importing the IVS appliance please see: Importing FileWave Appliances

CentOS is EOL in 2024. Migrating to Debian is highly recommended.

CentOS Linux Installers (md5: 28e9290912de67acafc21909aa1d367c)
CentOS Linux Server (md5: 2f9cedff2dc3f9b6a611d67e8df16343)
CentOS Linux Booster (md5: c62960f9fa4655a2adc691bdcf182893)

If when doing yum update or upgrade you get a note that no updates are available it may be that you block access to some countries. yum clean all can clear the cache so that the upgrades can happen.

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

# login via ssh / root or put sudo at the start of each line
sudo yum update -y
sudo yum upgrade -y
sudo yum install -y --nogpgcheck https://fwdl.filewave.com/15.2.1/fwxserver-15.2.1-1.0.x86_64.rpm
sudo reboot

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

# login via ssh / root
sudo yum update -y
sudo yum upgrade -y
sudo yum install -y --nogpgcheck https://fwdl.filewave.com/15.2.1/fwbooster-15.2.1-1.0.x86_64.rpm
sudo 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
sudo yum update -y
sudo yum update -y filewave-IVS
sudo yum upgrade -y
sudo 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
sudo yum install -y filewave-IVS
sudo yum upgrade -y
sudo 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.

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 12) 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 13, 14 (Intel and Apple Silicon)
• Linux CentOS 7.9 x86_64
• Debian 12.2 x86_64 (Note that any Debian 12.x is expected to work, and applying security updates may move you to a higher version.)
  

Expected to work

• macOS 11, 12 (Intel and Apple Silicon)

Fully Tested by QA

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

Expected to work

• macOS 11, 12 (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
  
• macOS 10.15 → Legacy Version 15.0.1

Fully Tested by QA

• iOS 16.1, 17
• iPadOS 16, 17
• tvOS 16, 17
• Android 13, 14 (EMM Client)
• Chromebook
  

Expected to work

• iOS 14, 15
• iPadOS 14, 15
• tvOS 14, 15
• Android 8 to 12 (EMM)
  

Legacy

• iOS 13 → Legacy Version 15.0.1
• iOS 10, 11, 12 → Legacy Version 13.1.5

Fully Tested by QA

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

Expected to work

• macOS 11, 12 (Intel and Apple Silicon)

Fully Tested by QA

• macOS 13, 14 (Intel and Apple Silicon)
• Windows 10 (Ent/Pro 21H1 and above), 11 (Ent/Pro 21H2 and above)
• Linux CentOS 7.9 x86_64
• Debian 12.2 x86_64 (Note that any Debian 12.x is expected to work, and applying security updates may move you to a higher version.)
  

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.

Note that a Debian version of IVS will be coming soon.

FileWave Central User Interface has been refreshed ; FileWave Central is adopting FileWave Anywhere more modern look and feel. We hope you’ll love as much as we do the new FileWave Central !

Support for macOS Sonoma (macOS 14):

Testing macOS 14, we found that some changes are required to properly restart FileWave Desktop agent (fwcld) after upgrade. These changes have been added to version 15.1.

This means that:
* It is recommended to upgrade macOS clients to FileWave 15.1 prior to upgrade to macOS 14 ;
* As the changes are related to permissions and are solved by automatically deploying a TCC profile, it is recommended to MDM-enroll macOS devices. This issue can be worked around by making upgrade fileset a reboot fileset.

FileVault 2 enforcement:

It is now possible to enforce Full Disk Encryption (FileVault 2) at enrollment time to increase security in your organization.

Return to Service (iOS / iPadOS 17): Learn More...

Parameterized WiFi profiles are now support with Return To Service.

Profile is delivered to the device at the time EraseDevice command is issued, and parameterization is done by FileWave server ; this means that parameterization happens at the time the command is sent to the device, and uses current values, including user-based values.
As WiFi profile is required prior to the enrollment, it can't use new enrollment credentials for parameterization.

New profiles or profile modifications:

• Managed Domains: new setting to configure urls to relax cross-site tracking prevention
• Dock: new settings to configure persistent items in the dock, and enforce settings like Auto-Hide or Show-Indicator, as well as new option for “Dock Fixup Override”.
• Security & Privacy : new “App Data” System Policy to pre-approve apps to access other app’s data (TCC)
• VPN Profile :
  • Extend DNS options with encryption options
  • Support for Transparent Proxy for Cisco AnyConnect, Cisco AnyConnect Legacy, Juniper SSL, F5 SSL, SonicWALL Mobile Connect, Aruba VIA
  • new options to exclude Cellular Services or APNS
• Network Relays can now be configured using corresponding profiles
• Extensible Singled Sign On profile extended with Platform SSO options
• Network Profile : New setting to configure TLS Trusted Certificates, settings to specify AD or OD credentials, HESSID

Network Relays:

• Applications can be configure to automatically use Network Relays as defined in the newly supported Network Relays profile

Shared iPads:

• Passcode policy and Auto Lock time can now be configured for Shared iPads ; these settings are deployed using Command Policy profile.

VPP API : “v2” is now enabled by default (15.1)

VPP v2 API is not compatible with legacy VPP tokens (created before Apple School or Business Manager but with legacy vpp.itunes.apple.com service). Transferring licenses to Location-based token is highly recommended.

MSI properties:

It is now possible to specify MSI properties to be applied during installation and, for installers supporting it, during uninstallation.

Default script:

Default script type is now PowerShell instead of Python (Central).

FileWave Networking Imaging 15.1.x brings compatibility with FileWave 15.2.x.

• PXE Kernel: 6.5.5
• Buildroot: 2023.08.01
  

The transition from version 1.0 to version 2.0 of our app signifies a major leap forward in terms of user experience and visual appeal, much like the transformation seen when comparing the Android Play Store and the App Store. In this upgrade, the primary focus has been on completely revamping the user interface (UI) to provide a sleek, modern, and highly intuitive platform that caters to our users' evolving expectations.

Version 1.0 laid the foundation for the app's functionality and introduced users to a diverse array of features and content. However, user feedback and industry trends have illuminated the need for a more sophisticated and streamlined UI that aligns with contemporary design principles and enhances the overall user journey.

With version 2.0, the app undergoes a stunning visual makeover, drawing inspiration from the aesthetic excellence of both the Android Play Store and the App Store:

1. Unified Design Paradigm: Our new UI design unifies elements from both the Android Play Store and the App Store, creating a harmonious blend of familiarity and innovation. This design consistency ensures that users across various platforms feel comfortable while navigating the app.

2. Intuitive Navigation: Building on the success of version 1.0, version 2.0 introduces a reimagined navigation system. Users can effortlessly explore and discover content thanks to intuitive menus, recognizable icons, and seamless navigation flows, akin to the ease of navigation in both app marketplaces.

3. Visual Delight: The new UI is not just about functionality; it's a visual treat. Engaging animations, subtle transitions, and tastefully curated visuals combine to make every interaction with the app a delightful experience, echoing the immersive nature of the Android Play Store and the App Store.

4. Enhanced Customization: Version 2.0 introduces enhanced customization options, allowing users to personalize their interface just as they would within the Android Play Store and the App Store. Users can arrange and prioritize content according to their preferences, granting them a sense of ownership over their app experience.

5. Responsive Design: Much like the Android Play Store and the App Store's responsiveness across devices, our app now adapts seamlessly to various screen sizes and orientations. This ensures a consistent and optimized experience whether users are browsing on smartphones, tablets, or desktops.

By transitioning from version 1.0 to version 2.0 with a UI overhaul reminiscent of the Android Play Store and the App Store, our app solidifies its commitment to delivering an unparalleled user experience. This transformation isn't just about aesthetics; it's a testament to our dedication to meeting the evolving needs of our users in an engaging, intuitive, and visually striking manner. As we bridge the gap between the old and the new, version 2.0 sets the stage for a future where our app continues to evolve in tandem with user expectations and industry trends.

Kiosk 2.0 (Technical Preview) Enterprise app can be downloaded here : https://fwdl.filewave.com/15.2.0/App_Portal_Beta_15.2.0.ipa

More: Kiosk 2.0 for iOS (Technical Preview)

The following features have been removed from FileWave 15.2.0 :

• 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

3rd party opensource components have been upgraded. Most relevant, but not only:

• OpenSSL 3.0.12
• Apache 2.4.58
• Postgres 12.16
• Python 3.10.13
• Qt 5.15.15
• ZLib 1.3
• Various library upgrades for bug and security issue fixes

Bug fixes:

• FWRD-982 Fixed an issue where fileset status could incorrectly be "Deleted" when changing deployed revision
• FWRD-1805 Fixed category for Command Policy Payload (Central Admin)
• FWRD-2101 Made sure Custom Field internal name can't end with underscore
• FWRD-2342 Fixed an issue where UseComputerNameForComputerRecordName key would incorrectly be added to Login Window Profile (Central Admin)
• FWRD-3102 Fixed an issue where it would not be possible to remove a fileset being a dependency of another fileset
• FWRD-3510 Fixed an issue where RSR updates would not be visible for macOS
• FWRD-3551 Fixed various issues related to dialogs Z-Order
• FWRD-3643 Fixed an issue where main window would come foreground after closing client monitor from client info dialog
• FWRD-3742 Fixed an issue where search would not work properly for scheduled report queries
• FWRD-3828 Fixed inconsistent button focus in Central Preferences dialog
• FWRD-4011 Fixed incorrectly formatted log entry related to smart group evaluation in fwxadmin.log
• FWRD-4442 Fixed Payload Description behaviour in FileWave Anywhere to match FileWave Central.
• FWRD-4776 Fixed an issue where signing out of FileWave would prevent from login into Grafana Dashboard
• FWRD-11270 Fixed an issue where global Content-Filter or DNS proxy profiles would not be applied (only per-app versions) 
• FWRD-11340 Fixed an issue where Setup Assistant section in DEP Profile dialog would not show all options
• FWRD-11343 Fixed an issue where inactive text contrast would be too low (FileWave Central)
• FWRD-11353 Fixed Passcode Lock Grace Period field for Shared iPad Command Policy (FileWave Central)
• FWRD-11365 Central Admin windows too small for Default Scale / Resolution (1440x900) 
• FWRD-11387 Fixed an issue where model update decision when two filesets for the same iOS application are associated via Fileset group to the same device would not be consistent
• FWRD-11402 Fixed Passcode Lock Grace Period field for Shared iPad Command Policy (FileWave Anywhere)
• FWRD-11495 Fixed an issue where duplicating a profile created outside FileWave would prevent from updating the model
• FWRD-11583 Fixed an issue on macOS Sonoma where Client Assistant would not use the same device name as the one used during enrollment
• FWRD-11610 Reduced required database disk space for revoked certificates
• FWRD-11613 Fixed an issue where the ampersand symbol would not be displayed in Clients View or Fileset View
• FWRD-11615 Fixed an issue where clone icons would be too hard to identify
• FWRD-11625 Fixed an issue where association timing fields would be to narrow (Central Admin)
• FWRD-11638 Fixed an issue where ampersand characters would not always be displayed in tabs or column headers
• FWRD-11641 Fixed margin on default revision picker dialog
• FWRD-11670 Fixed an issue where revert model could prevent subsequent update model
• FWRD-11692 Fixed an issue where group clone icon would be missing (Central Admin)
• FWRD-11264 Fixed an issue where Central Admin side bar could not be made larger
• FWRD-11344 Fixed an issue where expand arrow and status indicator color become white and not visible properly for row selection in License Management view

macOS Installers DMG (md5: 4fd2cfa4eb141708ce511b346aa8085a)
macOS Upgrade Fileset (md5: 273da58d7f671b8992edad084dc69beb)
macOS Admin (md5: 1fbaf4ab193ae78d6bdf2e12ee07439f)
macOS Booster (md5: 0a41426a07d60d59360270b758176c24)
macOS Server (md5: 13dde953b67eb72407a03265a918054e)
macOS Client (md5: 46675cffe452215e8609867506f2d9c1)

There is a patch for VPP that is important to install on your FileWave Server. If you run FileWave Server on macOS you can apply the patch with the below commands in Terminal.app when opened on the server or by SSHing to the server. For other platforms these same commands are listed in the install instructions as well:

# Apply patches to get the VPP patch that was done after 15.2.0 was finished
sudo /usr/local/filewave/python/bin/python /usr/local/filewave/django/manage.pyc apply_patch
sudo /usr/local/bin/fwcontrol apache restart
# Flush the scheduler in FileWave
sudo /usr/local/filewave/python/bin/python /usr/local/filewave/django/manage.pyc flush_scheduler
sudo reboot

Windows Upgrade Fileset (md5: ad3c6c1a23bb02968f9cd2820ef2e9c8)
Windows Admin (md5: 42542116485175fee18caeb15f3ff49c)
Windows Booster (md5: 28086cf9336da0f08cb458a20242ef25)
Windows Client (md5: a03017b73683cce7c5bf271eb1a5dda5)

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: fad3d73e0509ff20372972b1ac4e9ff8)
Static CDN URL :

https://fwdl.filewave.com/15.2.0/filewave/App%20Portal%2015.2.0.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: b35b1e0b6c728021ab88b9427291ed6a)

CentOS Linux Installers (md5: d8a8f2550735bba130030f8b49ea6e7a)
CentOS Linux Server (md5: 7e80216613d117f2f28a35666d997f47)
CentOS Linux Booster (md5: a0db0a5cb09aec0bec1dce78e2b6742f)

If when doing yum update or upgrade you get a note that no updates are available it may be that you block access to some countries. yum clean all can clear the cache so that the upgrades can happen.

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

# login via ssh / root or put sudo at the start of each line
sudo yum update -y
sudo yum upgrade -y
sudo yum install -y --nogpgcheck https://fwdl.filewave.com/15.2.0/fwxserver-15.2.0-1.0.x86_64.rpm
# Apply patches to get the VPP patch that was done after 15.2.0 was finished
sudo /usr/local/filewave/python/bin/python /usr/local/filewave/django/manage.pyc apply_patch
sudo /usr/local/bin/fwcontrol apache restart
# Flush the scheduler
sudo /usr/local/filewave/python/bin/python /usr/local/filewave/django/manage.pyc flush_scheduler
sudo reboot

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

# login via ssh / root
sudo yum update -y
sudo yum upgrade -y
sudo yum install -y --nogpgcheck https://fwdl.filewave.com/15.2.0/fwbooster-15.2.0-1.0.x86_64.rpm
sudo 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
sudo yum update -y
sudo yum update -y filewave-IVS
sudo yum upgrade -y
sudo 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
sudo yum update -y
sudo yum install -y filewave-IVS
sudo yum upgrade -y
sudo 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.

Debian Linux Installers (md5: 5b0b3444c95340b455f70350f05a3c1d)
Debian Linux Server (md5: 93f12c9bb8545db3b40ff3a288e78823)
Debian Linux Booster (md5: 89be5ef39b3b780ba5c77b6bbe829013)

Upgrading the FileWave Server

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

# login via ssh as root or use sudo for every line below
# OS Upgrades:
sudo apt update -y
sudo apt upgrade -y
# Download and Install:
wget https://fwdl.filewave.com/15.2.0/fwxserver_15.2.0_amd64.deb
sudo dpkg -i ./fwxserver_15.2.0_amd64.deb
# If dependencies are not met then the below will install them allowing for the FW server to install:
sudo apt-get install -f
# Apply patches to get the VPP patch that was done after 15.2.0 was finished
sudo /usr/local/filewave/python/bin/python /usr/local/filewave/django/manage.pyc apply_patch
sudo /usr/local/bin/fwcontrol apache restart
# Flush the scheduler in FileWave
sudo /usr/local/filewave/python/bin/python /usr/local/filewave/django/manage.pyc flush_scheduler
sudo reboot

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

# login via ssh as root or use sudo for every line below
# OS Upgrades:
sudo apt update -y
sudo apt upgrade -y
# Download and Install:
wget https://fwdl.filewave.com/15.2.0/fwbooster_15.2.0_amd64.deb
sudo dpkg -i ./fwbooster_15.2.0_amd64.deb
# If dependencies are not met then the below will install them allowing for the FW server to install:
sudo apt-get install -f
sudo reboot

Please note that the IVS for Debian will be released soon. At that time the download page will be updated and you will be able to replace your CentOS based IVS with a Debian one.

CentOS Linux:
VMware and VirtualBox (OVA) Server Appliance (md5: c27bee1a0f062b6fc3530d72bd5c1d96)
VMware and VirtualBox (OVA) Booster Appliance (md5: 74da6ac1163265a87748466d9d19dc68)
VMware and VirtualBox (OVA) Imaging Appliance (md5: 5a7d1512281de275e9a82c8916a11fb6)

Debian Linux: It is preferred that you use this for a new server or booster. IVS is coming soon.
VMware and VirtualBox (OVA) Server Appliance (md5: 32ffed46159fec2200afcf1877e1ad4b)
VMware and VirtualBox (OVA) Booster Appliance (md5: a5a9c2da28bfc83be947a6a021fb80f6)

There is a patch for VPP that is important to install on your FileWave Server that you can apply in a terminal session:

# Apply patches to get the VPP patch that was done after 15.2.0 was finished
sudo /usr/local/filewave/python/bin/python /usr/local/filewave/django/manage.pyc apply_patch
sudo /usr/local/bin/fwcontrol apache restart
# Flush the scheduler in FileWave
sudo /usr/local/filewave/python/bin/python /usr/local/filewave/django/manage.pyc flush_scheduler
sudo reboot

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

CentOS Linux:
Hyper-V (VHD) Server Appliance (md5: 3a2abef9410f1f327ccd78144c9f51d6)
Hyper-V (VHD) Booster Appliance (md5: 44bc6ff328c7773bf586abda596989a7)
Hyper-V (VHD) Imaging Appliance (md5: e6cc770040f9c82d4ca704253bfba156)

Debian Linux: It is preferred that you use this for a new server or booster. IVS is coming soon.
Hyper-V (VHD) Server Appliance (md5: 128687f2d74027222e75541412c2f9a5)
Hyper-V (VHD) Booster Appliance (md5: 96a3251057f1d7d5bdcbd1fb8a0a19ac)

There is a patch for VPP that is important to install on your FileWave Server that you can apply in a terminal session:

# Apply patches to get the VPP patch that was done after 15.2.0 was finished
sudo /usr/local/filewave/python/bin/python /usr/local/filewave/django/manage.pyc apply_patch
sudo /usr/local/bin/fwcontrol apache restart
# Flush the scheduler in FileWave
sudo /usr/local/filewave/python/bin/python /usr/local/filewave/django/manage.pyc flush_scheduler
sudo reboot

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 13, 14 (Intel and Apple Silicon)
• Linux CentOS 7.9 x86_64

Expected to work

• macOS 11, 12 (Intel and Apple Silicon)

Fully Tested by QA

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

Expected to work

• macOS 11, 12 (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
  
• macOS 10.15 → Legacy Version 15.0.1

Fully Tested by QA

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

Expected to work

• iOS/iPadOS 14, 15
• tvOS 14, 15
• Android 8 to 11 (APK/EMM)
  

Legacy

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

Fully Tested by QA

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

Expected to work

• macOS 11, 12 (Intel and Apple Silicon)

Fully Tested by QA

• macOS 13, 14 (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.

FileWave Central User Interface has been refreshed ; FileWave Central is adopting FileWave Anywhere more modern look and feel. We hope you’ll love as much as we do the new FileWave Central !

Support for iOS 17, iPadOS 17, tvOS 17

FileWave 15.1 introduces support for Apple new 2023 Operating Systems for iPhones, iPads and Apple TVs.

Basic Support for macOS Sonoma (macOS 14):

• macOS Sonoma is now reported

• MDM enrolled macOS devices now automatically deploy a TCC profile to grant FileWave client permissions to manage the device

Testing macOS 14, we found that some changes are required to properly restart FileWave Desktop agent (fwcld) after upgrade. These changes have been added to version 15.1.

This means that:
* It is recommended to upgrade macOS clients to FileWave 15.1 prior to upgrade to macOS 14 ;
* As the changes are related to permissions and are solved by automatically deploying a TCC profile, it is recommended to MDM-enroll macOS devices. This issue can be worked around by making upgrade fileset a reboot fileset.

Minimum OS version enforcement: Learn More...

Starting from iOS 17, iPadOS 17 and macOS 14, it is now possible to enforce a minimum OS version at enrollment time on supported devices.

Return to Service (iOS / iPadOS 17): Learn More...

Erase Device command (Remote Wipe) is now capable to keep a Wi-Fi profile and use it after device has been wiped to automatically bring the device back on the network.

DEP devices will then automatically start Automated Device Enrollment. Non DEP devices will be provided MDM profile and will then automatically be re-enrolled.

New profiles or profile modifications:

• LoginWindows (macOS) has now new options for auto login

• Passcode (macOS) has now a Regex based validation option

• System Settings is now part of Restriction (macOS) profile

• DNS Settings (iOS, macOS) can now define a client certificate

• TLS 1.3 can now be defined as minimum or maximum version in Network profile

• Login Items profile (macOS) can now specify Team Identifier for each allowed item

• tvOS now supports VPN profile

• SetupAssistant profile (iOS) can skip "Intended User" Pane

Inventory:

• Inventory Fields description related to Apple MDM has been updated following Apple documentation update
  

DEP changes:

• "Intended User" Pane can be skipped during enrollment

VPP API : “v2” is now enabled by default

FileWave Networking Imaging 15.1.x brings compatibility with FileWave 15.1.x.

• PXE Kernel: 6.4.7
• Buildroot: 2023.05.01
  

The transition from version 1.0 to version 2.0 of our app signifies a major leap forward in terms of user experience and visual appeal, much like the transformation seen when comparing the Android Play Store and the App Store. In this upgrade, the primary focus has been on completely revamping the user interface (UI) to provide a sleek, modern, and highly intuitive platform that caters to our users' evolving expectations.

Version 1.0 laid the foundation for the app's functionality and introduced users to a diverse array of features and content. However, user feedback and industry trends have illuminated the need for a more sophisticated and streamlined UI that aligns with contemporary design principles and enhances the overall user journey.

With version 2.0, the app undergoes a stunning visual makeover, drawing inspiration from the aesthetic excellence of both the Android Play Store and the App Store:

1. Unified Design Paradigm: Our new UI design unifies elements from both the Android Play Store and the App Store, creating a harmonious blend of familiarity and innovation. This design consistency ensures that users across various platforms feel comfortable while navigating the app.

2. Intuitive Navigation: Building on the success of version 1.0, version 2.0 introduces a reimagined navigation system. Users can effortlessly explore and discover content thanks to intuitive menus, recognizable icons, and seamless navigation flows, akin to the ease of navigation in both app marketplaces.

3. Visual Delight: The new UI is not just about functionality; it's a visual treat. Engaging animations, subtle transitions, and tastefully curated visuals combine to make every interaction with the app a delightful experience, echoing the immersive nature of the Android Play Store and the App Store.

4. Enhanced Customization: Version 2.0 introduces enhanced customization options, allowing users to personalize their interface just as they would within the Android Play Store and the App Store. Users can arrange and prioritize content according to their preferences, granting them a sense of ownership over their app experience.

5. Responsive Design: Much like the Android Play Store and the App Store's responsiveness across devices, our app now adapts seamlessly to various screen sizes and orientations. This ensures a consistent and optimized experience whether users are browsing on smartphones, tablets, or desktops.

By transitioning from version 1.0 to version 2.0 with a UI overhaul reminiscent of the Android Play Store and the App Store, our app solidifies its commitment to delivering an unparalleled user experience. This transformation isn't just about aesthetics; it's a testament to our dedication to meeting the evolving needs of our users in an engaging, intuitive, and visually striking manner. As we bridge the gap between the old and the new, version 2.0 sets the stage for a future where our app continues to evolve in tandem with user expectations and industry trends.

Kiosk 2.0 (Technical Preview) Enterprise app can be downloaded here : https://fwdl.filewave.com/15.1.0/App_Portal_Beta_15.1.0.ipa

More: Kiosk 2.0 for iOS (Technical Preview)

The following features were deprecated in FileWave 15.0.1 and will be removed in a future version:

• 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

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

3rd party opensource components have been upgraded. Most relevant, but not only:

• OpenSSL 3.0.12
• Apache 2.4.58
  

Changes to FileWave:

• FWRD-11264 Fixed an issue where Central Admin side bar could not be made larger
• FWRD-11344 Fixed an issue where expand arrow and status indicator color become white and not visible properly for row selection in License Management view
• FWRD-11750 Fixed an issue where logs could be incorrectly be filled by entries related to errors when synchronizing VPP apps metadata after 9646 error
• FWRD-11867 Fixed a potential issue where invalid request could be made to VPP service, leading to error 9602
• FWRD-11879 Improved how VPP errors 9646 are handled
• FWRD-11882 Fixed an issue where iOS fileset status would incorrectly be "Associated" instead of "Available in Kiosk.."
• FWRD-11975 Fixed various issues related to communication with Google EMM service
• FWRD-11991 Improved speed of VPP License synchronization
• FWRD-12006 Fixed an issue where error related to VPP event could break event handling
• FWRD-12009 Fixed an issue where VPP sync process could create too many entries in database, leading to subsequent syncs require a full sync
  

3rd party opensource components have been upgraded. Most relevant, but not only:

• OpenSSL 3.0.10
• Postgres 12.16
• Python 3.10.13
• Qt 5.15.15
• ZLib 1.3
• Various library upgrades for bug and security issue fixes

Changes to FileWave:

• FWRD-323 Fixed issue so now Apple .mobileconfig profile can be imported in FileWave Anywhere.
• FWRD-956 Fixed and improved information accuracy in "Command history data" (Devices tab) in FileWave Anywhere.
• FWRD-987 Fixed an issue where scripts from duplicated fileset would still be deployed in a folder based on the ID of the original fileset
• FWRD-1394 Fixed an issue Software Update links would be we displayed for Android devices in client info
• FWRD-1407 Fixed an issue where fileset size could be incorrect after reordering scripts
• FWRD-1409 Fixed an issue where Location information text would not be entirely visible on Windows (Central Admin)
• FWRD-1412 Fixed a potential issue where scripts could be removed from fileset after adding an empty script
• FWRD-1421 Fixed an issue where "Setup Mode" field visibility would not be correct
• FWRD-1425 Fixed an issue where permissions would not be properly respected in "Solve Conflict" dialog
• FWRD-1437 Fixed an issue where importing fileset from a temporary mounted location would fail
• FWRD-1520 Fixed an issue where dependencies would not be properly refreshed after changing dependency revision
• FWRD-1521 Fixed a cosmetic issue where "Conflict Details" dialog would not show the same title bar as other dialogs on macOS
• FWRD-1759 Fixed and improved behavior of "Save button" in Deployments edit mode in FileWave Anywhere.
• FWRD-2061 Fixed and improved behavior of "Cancel" button in the Script editor" in FileWave Anywhere.
• FWRD-2124 Fixed an issue where editing an inventory report in FileWave Central using double click would error
• FWRD-2128 Fixed import of Apple profiles from Windows or Linux host in FileWave Anywhere.
• FWRD-2375 Fixed behaviour of "Deploy to selected group" button and icon that is showing if group is deployed in FileWave Anywhere.
• FWRD-2385 Fixed Inventory query: It now can be set as false (Smart Group, Workflow, Report) in FileWave Anywhere.
• FWRD-2562 Fixed error handling: Error is displayed when removing device from pending devices in FileWave Anywhere.
• FWRD-2564 Fixed error message that is being shown when adding devices in FileWave Anywhere.
• FWRD-2689 Fixed an issue where license expiration date could be before purchase date in license purchase order dialog
• FWRD-2735 Fixed inconsistency between Chrome and Safari browsers: user can not select text while using Safari browser in Devices view in FileWave Anywhere.
• FWRD-2775 Fixed discard changes notification to be shown in Deployments edit mode in FileWave Anywhere.
• FWRD-2888 Fixed an issue where importing twice the same script would not work properly
• FWRD-3029 Fixed status count values to be aligned with the grid and grid is filtering clients according to the status in FileWave Anywhere.
• FWRD-3247 Fixed an issue where EMM devices excluded from a deployment could still receive filesets if they have been excluded via a smart group
• FWRD-3266 Fixed domain data-testid's to be unique in FileWave Anywhere.
• FWRD-3521 Fixed an issue where Desktop devices excluded from a deployment would not properly reported "Excluded" status for corresponding filesets
• FWRD-3630 Fixed an issue where "Excluded" status for excluded fileset would require some time to be properly reported
• FWRD-3631 Fixed an issue where iOS devices excluded from a deployment could still receive filesets if they have been excluded via a smart group
• FWRD-3827 Fixed (shortened) loading time for Fonts table in Device Info Details in FileWave Anywhere.
• FWRD-3878 Fixed an issue where DEP issues would not be properly marked as resolved in Grafana Dashboard
• FWRD-4014 Fixed Japanese translations (Central Admin)
• FWRD-4057 Fixed an issue where "When" information would be incorrect in fileset status for excluded filesets
• FWRD-4059 Fixed an issue where fileset status could be missing for iOS devices in case of complex deployment setup
• FWRD-4077 Fixed an issue where fileset status could be missing for Desktop devices in case of complex deployment setup
• FWRD-4079 FIxed permissions for showing Location Information in FileWave Anywhere.
• FWRD-4217 Fixed an issue where applications available on macOS and iPadOS but not marked as Universal in the App Store would be considered as iPadOS Only
• FWRD-4324 Fixed configuration of WiFi Windows profiles when configuring 2 WiFi Windows profiles in FileWave Anywhere.
• FWRD-4582 Fixed an issue where FileWave Central could crash when editing Parental Control profile
• FWRD-4725 Fixed an issue where search in "Clone to same groups as" dialog would not work
• FWRD-4871 Fixed an issue where --lang option would not overwrite Query Builder language
• FWRD-11156 Fixed an issue where VPP synchronization scheduled task would not restart in case of serious networking issue
• FWRD-11170 Fixed an issue where FileWave central would crash when closing all Inventory Query tabs
• FWRD-11173 Fixed a potential Central Admin crash when renaming scripts
• FWRD-4119 Improved fileset status report related to deployment exclusions
• FWRD-4206 Fixed an issue where Model Update would take significantly longer than on previous versions
• FWRD-4337 Fixed an issue on FileWave Central where Client Info dialog could open with incorrect client if it has been once opened from Inventory Query result
• FWRD-4496 Fixed one issue where excluding Smart Group from deployment would not work
• FWRD-11156 Fixed an issue where VPP synchronization scheduled task would not restart in case of serious networking issue 

macOS Installers DMG (md5: 8d1c145a1fe5eadea3ecbec8a03b3ab1)
macOS Upgrade Fileset (md5: 333a2eaa46c26f0b0a84f4f3465de5df)
macOS Admin (md5: a3e719cdc78059b3e74f12c37ba32bbe)
macOS Booster (md5: 51a4890133555cb8f3c713c2bfeda186)
macOS Server (md5: 0aedfcb6f5c76c0cbe3d826a9e384603)
macOS Client (md5: 78c964a57a4939bcfa61238eb46f07e1)

Remember that to upgrade macOS FileWave clients you should use the Upgrade Fileset. Never deploy the macOS Client listed above to an existing device. It is intended only for manual initial installs, and even for those you are better off creating an installer at https://custom.filewave.com 

Windows Upgrade Fileset (md5: 45e2a64cf87d2f4539020e60007de752)
Windows Admin (md5: 3f833de5539445b8e64e449c16c850a4)
Windows Booster (md5: 038481b5cbf0078cc646aa997859a0b2)
Windows Client (md5: a2853f36803334eece364f133bec79db)

Remember that to upgrade Windows FileWave clients you should use the Upgrade Fileset. Never deploy the Windows Client listed above to an existing device. It is intended only for manual initial installs, and even for those you are better off creating an installer at https://custom.filewave.com 

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: 833a4ae5db19f250ff3f5e7c03fa7833)
Static CDN URL :

https://fwdl.filewave.com/15.1.1/filewave/App%20Portal%2015.1.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: 890188fb5dbd8c8aadbde41fb0c88b3d)

Linux Installers (md5: 39d242e8c474700fd0b31d0384572eca)
Linux Server (md5: 75ecdae903ac2d4de59d4c67dbcb8192)
Linux Booster (md5: ca28806e18ac51a6e706e020b2540438)

If when doing yum update or upgrade you get a note that no updates are available it may be that you block access to some countries. yum clean all can clear the cache so that the upgrades can happen.

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

# login via ssh / root
yum update -y 
yum upgrade -y
yum install -y --nogpgcheck https://fwdl.filewave.com/15.1.1/fwxserver-15.1.1-1.0.x86_64.rpm
reboot

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

# login via ssh / root
yum update -y
yum upgrade -y
yum install -y --nogpgcheck https://fwdl.filewave.com/15.1.1/fwbooster-15.1.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 filewave-IVS
yum upgrade -y
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 install -y filewave-IVS
yum upgrade -y
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: ed7866db920d356d76be838ced7a8b43)
VMware and VirtualBox (OVA) Booster Appliance (md5: 1d2662e42044f03cc154acc9602ebf8b)
VMware and VirtualBox (OVA) Imaging Appliance (md5: 2e96fb5371730955a89ba8356053c0a1)

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

Hyper-V (VHD) Server Appliance (md5: 0936d1124843d12491740bd635f30476)
Hyper-V (VHD) Booster Appliance (md5: cac531a484d89dc634bd4ce6264af7b6)
Hyper-V (VHD) Imaging Appliance (md5: 35fb1f9548a78d1b77f8858b9bb3ffc5)

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 13, 14 (Intel and Apple Silicon)
• Linux CentOS 7.9 x86_64

Expected to work

• macOS 11, 12 (Intel and Apple Silicon)

Fully Tested by QA

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

Expected to work

• macOS 11, 12 (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
  
• macOS 10.15 → Legacy Version 15.0.1

Fully Tested by QA

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

Expected to work

• iOS/iPadOS 14, 15
• tvOS 14, 15
• Android 8 to 11 (APK/EMM)
  

Legacy

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

Fully Tested by QA

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

Expected to work

• macOS 11, 12 (Intel and Apple Silicon)

Fully Tested by QA

• macOS 13, 14 (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.

FileWave Central User Interface has been refreshed ; FileWave Central is adopting FileWave Anywhere more modern look and feel. We hope you’ll love as much as we do the new FileWave Central !

Support for iOS 17, iPadOS 17, tvOS 17

FileWave 15.1 introduces support for Apple new 2023 Operating Systems for iPhones, iPads and Apple TVs.

Basic Support for macOS Sonoma (macOS 14):

• macOS Sonoma is now reported

• MDM enrolled macOS devices now automatically deploy a TCC profile to grant FileWave client permissions to manage the device

Testing macOS 14, we found that some changes are required to properly restart FileWave Desktop agent (fwcld) after upgrade. These changes have been added to version 15.1.

This means that:
* It is recommended to upgrade macOS clients to FileWave 15.1 prior to upgrade to macOS 14 ;
* As the changes are related to permissions and are solved by automatically deploying a TCC profile, it is recommended to MDM-enroll macOS devices. This issue can be worked around by making upgrade fileset a reboot fileset.

Minimum OS version enforcement: Learn More...

Starting from iOS 17, iPadOS 17 and macOS 14, it is now possible to enforce a minimum OS version at enrollment time on supported devices.

Return to Service (iOS / iPadOS 17): Learn More...

Erase Device command (Remote Wipe) is now capable to keep a Wi-Fi profile and use it after device has been wiped to automatically bring the device back on the network.

DEP devices will then automatically start Automated Device Enrollment. Non DEP devices will be provided MDM profile and will then automatically be re-enrolled.

New profiles or profile modifications:

• LoginWindows (macOS) has now new options for auto login

• Passcode (macOS) has now a Regex based validation option

• System Settings is now part of Restriction (macOS) profile

• DNS Settings (iOS, macOS) can now define a client certificate

• TLS 1.3 can now be defined as minimum or maximum version in Network profile

• Login Items profile (macOS) can now specify Team Identifier for each allowed item

• tvOS now supports VPN profile

• SetupAssistant profile (iOS) can skip "Intended User" Pane

Inventory:

• Inventory Fields description related to Apple MDM has been updated following Apple documentation update
  

DEP changes:

• "Intended User" Pane can be skipped during enrollment

VPP API : “v2” is now enabled by default

FileWave Networking Imaging 15.1.x brings compatibility with FileWave 15.1.x.

• PXE Kernel: 6.4.7
• Buildroot: 2023.05.01
  

The transition from version 1.0 to version 2.0 of our app signifies a major leap forward in terms of user experience and visual appeal, much like the transformation seen when comparing the Android Play Store and the App Store. In this upgrade, the primary focus has been on completely revamping the user interface (UI) to provide a sleek, modern, and highly intuitive platform that caters to our users' evolving expectations.

Version 1.0 laid the foundation for the app's functionality and introduced users to a diverse array of features and content. However, user feedback and industry trends have illuminated the need for a more sophisticated and streamlined UI that aligns with contemporary design principles and enhances the overall user journey.

With version 2.0, the app undergoes a stunning visual makeover, drawing inspiration from the aesthetic excellence of both the Android Play Store and the App Store:

1. Unified Design Paradigm: Our new UI design unifies elements from both the Android Play Store and the App Store, creating a harmonious blend of familiarity and innovation. This design consistency ensures that users across various platforms feel comfortable while navigating the app.

2. Intuitive Navigation: Building on the success of version 1.0, version 2.0 introduces a reimagined navigation system. Users can effortlessly explore and discover content thanks to intuitive menus, recognizable icons, and seamless navigation flows, akin to the ease of navigation in both app marketplaces.

3. Visual Delight: The new UI is not just about functionality; it's a visual treat. Engaging animations, subtle transitions, and tastefully curated visuals combine to make every interaction with the app a delightful experience, echoing the immersive nature of the Android Play Store and the App Store.

4. Enhanced Customization: Version 2.0 introduces enhanced customization options, allowing users to personalize their interface just as they would within the Android Play Store and the App Store. Users can arrange and prioritize content according to their preferences, granting them a sense of ownership over their app experience.

5. Responsive Design: Much like the Android Play Store and the App Store's responsiveness across devices, our app now adapts seamlessly to various screen sizes and orientations. This ensures a consistent and optimized experience whether users are browsing on smartphones, tablets, or desktops.

By transitioning from version 1.0 to version 2.0 with a UI overhaul reminiscent of the Android Play Store and the App Store, our app solidifies its commitment to delivering an unparalleled user experience. This transformation isn't just about aesthetics; it's a testament to our dedication to meeting the evolving needs of our users in an engaging, intuitive, and visually striking manner. As we bridge the gap between the old and the new, version 2.0 sets the stage for a future where our app continues to evolve in tandem with user expectations and industry trends.

Kiosk 2.0 (Technical Preview) Enterprise app can be downloaded here : https://fwdl.filewave.com/15.1.0/App_Portal_Beta_15.1.0.ipa

More: Kiosk 2.0 for iOS (Technical Preview)

The following features were deprecated in FileWave 15.0.1 and will be removed in a future version:

• 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

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

3rd party opensource components have been upgraded. Most relevant, but not only:

• OpenSSL 3.0.10
• Postgres 12.16
• Python 3.10.13
• Qt 5.15.15
• ZLib 1.3
• Various library upgrades for bug and security issue fixes

Changes to FileWave:

• FWRD-323 Fixed issue so now Apple .mobileconfig profile can be imported in FileWave Anywhere.
• FWRD-956 Fixed and improved information accuracy in "Command history data" (Devices tab) in FileWave Anywhere.
• FWRD-987 Fixed an issue where scripts from duplicated fileset would still be deployed in a folder based on the ID of the original fileset
• FWRD-1394 Fixed an issue Software Update links would be we displayed for Android devices in client info
• FWRD-1407 Fixed an issue where fileset size could be incorrect after reordering scripts
• FWRD-1409 Fixed an issue where Location information text would not be entirely visible on Windows (Central Admin)
• FWRD-1412 Fixed a potential issue where scripts could be removed from fileset after adding an empty script
• FWRD-1421 Fixed an issue where "Setup Mode" field visibility would not be correct
• FWRD-1425 Fixed an issue where permissions would not be properly respected in "Solve Conflict" dialog
• FWRD-1437 Fixed an issue where importing fileset from a temporary mounted location would fail
• FWRD-1520 Fixed an issue where dependencies would not be properly refreshed after changing dependency revision
• FWRD-1521 Fixed a cosmetic issue where "Conflict Details" dialog would not show the same title bar as other dialogs on macOS
• FWRD-1759 Fixed and improved behavior of "Save button" in Deployments edit mode in FileWave Anywhere.
• FWRD-2061 Fixed and improved behavior of "Cancel" button in the Script editor" in FileWave Anywhere.
• FWRD-2124 Fixed an issue where editing an inventory report in FileWave Central using double click would error
• FWRD-2128 Fixed import of Apple profiles from Windows or Linux host in FileWave Anywhere.
• FWRD-2375 Fixed behaviour of "Deploy to selected group" button and icon that is showing if group is deployed in FileWave Anywhere.
• FWRD-2385 Fixed Inventory query: It now can be set as false (Smart Group, Workflow, Report) in FileWave Anywhere.
• FWRD-2562 Fixed error handling: Error is displayed when removing device from pending devices in FileWave Anywhere.
• FWRD-2564 Fixed error message that is being shown when adding devices in FileWave Anywhere.
• FWRD-2689 Fixed an issue where license expiration date could be before purchase date in license purchase order dialog
• FWRD-2735 Fixed inconsistency between Chrome and Safari browsers: user can not select text while using Safari browser in Devices view in FileWave Anywhere.
• FWRD-2775 Fixed discard changes notification to be shown in Deployments edit mode in FileWave Anywhere.
• FWRD-2888 Fixed an issue where importing twice the same script would not work properly
• FWRD-3029 Fixed status count values to be aligned with the grid and grid is filtering clients according to the status in FileWave Anywhere.
• FWRD-3247 Fixed an issue where EMM devices excluded from a deployment could still receive filesets if they have been excluded via a smart group
• FWRD-3266 Fixed domain data-testid's to be unique in FileWave Anywhere.
• FWRD-3521 Fixed an issue where Desktop devices excluded from a deployment would not properly reported "Excluded" status for corresponding filesets
• FWRD-3630 Fixed an issue where "Excluded" status for excluded fileset would require some time to be properly reported
• FWRD-3631 Fixed an issue where iOS devices excluded from a deployment could still receive filesets if they have been excluded via a smart group
• FWRD-3827 Fixed (shortened) loading time for Fonts table in Device Info Details in FileWave Anywhere.
• FWRD-3878 Fixed an issue where DEP issues would not be properly marked as resolved in Grafana Dashboard
• FWRD-4014 Fixed Japanese translations (Central Admin)
• FWRD-4057 Fixed an issue where "When" information would be incorrect in fileset status for excluded filesets
• FWRD-4059 Fixed an issue where fileset status could be missing for iOS devices in case of complex deployment setup
• FWRD-4077 Fixed an issue where fileset status could be missing for Desktop devices in case of complex deployment setup
• FWRD-4079 FIxed permissions for showing Location Information in FileWave Anywhere.
• FWRD-4217 Fixed an issue where applications available on macOS and iPadOS but not marked as Universal in the App Store would be considered as iPadOS Only
• FWRD-4324 Fixed configuration of WiFi Windows profiles when configuring 2 WiFi Windows profiles in FileWave Anywhere.
• FWRD-4582 Fixed an issue where FileWave Central could crash when editing Parental Control profile
• FWRD-4725 Fixed an issue where search in "Clone to same groups as" dialog would not work
• FWRD-4871 Fixed an issue where --lang option would not overwrite Query Builder language
• FWRD-11156 Fixed an issue where VPP synchronization scheduled task would not restart in case of serious networking issue
• FWRD-11170 Fixed an issue where FileWave central would crash when closing all Inventory Query tabs
• FWRD-11173 Fixed a potential Central Admin crash when renaming scripts
• FWRD-4119 Improved fileset status report related to deployment exclusions
• FWRD-4206 Fixed an issue where Model Update would take significantly longer than on previous versions
• FWRD-4337 Fixed an issue on FileWave Central where Client Info dialog could open with incorrect client if it has been once opened from Inventory Query result
• FWRD-4496 Fixed one issue where excluding Smart Group from deployment would not work
• FWRD-11156 Fixed an issue where VPP synchronization scheduled task would not restart in case of serious networking issue 

macOS Installers DMG (md5: acc9dcf3d622fc939547172a6c1693b8)
macOS Upgrade Fileset (md5: 77fa068c9c00a1ac81dbef7af71740a4)
macOS Admin (md5: 2a933c118f3df7c87ffecba2906962c9)
macOS Booster (md5: 5f33cf1088d553db4808cc0f95efafb9)
macOS Server (md5: d77d4c14511bafff3940a5976c403e95)
macOS Client (md5: fa94220791d5d75fcde54728a88cd126)

Windows Upgrade Fileset (md5: 926a88e844fc8ecc3dd010f4f12477aa)
Windows Admin (md5: 12f97693d4dd716b3f691a19b71e8a0a)
Windows Booster (md5: 0f26b28e3bb5cc5311b3fd6773008d3e)
Windows Client (md5: 34aee36afc6d4c9ba9b7edf70569f734)

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: 7dbb26e47e1dd418ae8da15591425abe)
Static CDN URL :

https://fwdl.filewave.com/15.1.0/filewave/App%20Portal%2015.1.0.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: 602ce436f2515e4c9093bd3b99f7ea0f)

Linux Installers (md5: 3bf03f249f3a560dcf9988db599915ff)
Linux Server (md5: 0fe4214ccc7d8834acc7731474fbb7f4)
Linux Booster (md5: b10aa9c6bf540a3d6be74f1392b944f5)

If when doing yum update or upgrade you get a note that no updates are available it may be that you block access to some countries. yum clean all can clear the cache so that the upgrades can happen.

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

# login via ssh / root
yum update -y 
yum upgrade -y
yum install -y --nogpgcheck https://fwdl.filewave.com/15.1.0/fwxserver-15.1.0-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 upgrade -y
yum install -y --nogpgcheck https://fwdl.filewave.com/15.1.0/fwbooster-15.1.0-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 filewave-IVS
yum upgrade -y
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 filewave-IVS
yum upgrade -y
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: 1f037e59f5343872318b87a59952aced)
VMware and VirtualBox (OVA) Booster Appliance (md5: 0e7365aef910910ce8576174e70cb2f1)
VMware and VirtualBox (OVA) Imaging Appliance (md5: 8e218491bc7d85e0aeb6cf670d098a81)

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

Hyper-V (VHD) Server Appliance (md5: 24fc168282798fa9aa0c405b667141b7)
Hyper-V (VHD) Booster Appliance (md5: df9e7195f5840b408784b19f24463087)
Hyper-V (VHD) Imaging Appliance (md5: 66bcba85f252d7cf1de31adddbb9610c)

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.1
• 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.

FileWave Anywhere is now considered fully implemented!

• For the power-admin, FileWave Anywhere is a great companion tool to use while you are on-the-go, but FileWave Central will still likely be your primary tool
• For the field-engineer who primarily:
  • works with individual devices
  • is super-mobile
  • manages groups and assigns content
  • FileWave Anywhere will likely become your everyday tool of choice!

Deployments in FileWave Central! 

• We are thrilled to announce that Deployments can now be fully managed from both FileWave Central and FileWave Anywhere.

  • This change means that FileWave Central and Anywhere are now fully compatible using Deployments
  • Deployments are the next-generation of Associations, and will eventually become the only supported method for assigning content
  • Best practice would be to start use them going forward so you'll have less to convert in later
    • And if you are not aware, there is an Associations → Deployments conversion tool in FIleWave Anywhere

Exclusions (revised):

• The meaning and the impact of exclusions in deployments have been revisited to be clearer and more predictable.
• In general terms, exclusions have been updated so that they more properly exclude devices from the singular deployment only, and not content from the device more globally (as could sometimes be the case before)
• Effectively with this change, devices are just "ignored" now in a deployment when they are set to be excluded

Context menu on inventory query result:

• Warning! Game-changing, awesome enhancement follows!
• When an inventory query returns device information, it is now possible to directly perform actions on devices in the report, without the extra "Reveal Client" step!
  
  

  

  
  

Default tracking state:

• There is a new option in Preferences to define what is the default tracking state for devices
  

  

  
  
• This change allows you to set the device to "Tracked" for instance before it even enrolls.  Then, when enrolled it will automatically be set.

Duplicate profile filesets:

• Warning! Game-changing, awesome enhancement follows!

• Profile filesets (Apple, Google, Windows and FileWave Policy) can new be duplicated both from FileWave Central and FileWave Anywhere admin consoles

  

  
  

  Notes:

  • New UUIDs are re-generated for Apple Profiles to ensure unicity of duplicated profiles
  • As changing UUIDs would break profile signature, signed profiles can't be duplicated

Windows Imaging associations can be managed in FileWave Anywhere

• Windows images (once created) can now be assigned to devices from FileWave Anywhere

Updated Dashboard Content (FileWave Anywhere)

• A new dashboard for NATS has been added to the FileWave dashboard in FileWave Anywhere
• The NATS notification system, introduced with FileWave 14.8.0, is a critical system component: notifications are used to synchronize all admin consoles, and by all other components to quickly interact.
• Monitoring how the NATS sub-system is utilized/working is useful for maintaining your overall FileWave installation health
  

  

  
  

Updated Translations (FileWave Central & FileWave Anywhere)

• Each new release of FileWave automatically includes updated translations
• Version 15 additionally has had some housekeeping done for German translations based on feedback from customers

FileWave 15 brings official support for the Apple 2023 Spring release, and more 

• More detail for VPP License Usage (FileWave Central):
  • License report shows more details related to Apple VPP license consumption. This is a significant improvement over earlier versions of this detailed report.
    

    

    
    

• Profile changes:
  • Content Caching Payload has a new ListenWIthPeersAndParents setting
  • Proxy Payload has new FallBackAllowed and ProxyCaptiveLoginAllowed settings
  • eMail Payload has a new allowMailDrop setting
  • Security And Privacy Payload  Firewall setting is not limited to currently installed apps and now allows to enter any bundle id
  • Web Content Filter payload has new filtering options

• Shared iPad
  • There is a new setting (added to Command Policy Profile) to skip language and locale setup for new users

• DEP
  • There is a new option to skip "Safety" setting panel ; the option is also available in Setup Assistant payload for upgrade setup

• Device information
  • Devices are now reporting the following data:
    • EACSPreflight (macOS)
    • HasBattery (macOS)
    • ModelNumber (iOS/iPadOS)
    • RecommendationsCadence for SoftwareUpdate (iOS/iPadOS)
    • SupplementalBuildVersion and SupplementalOSVersionExtra
    • SkipLanguageAndLocaleSetupForNewUsers (Shared iPads)

• Tap to Pay Screen Lock
  • There is a new setting to enable Tap To Pay Screen Lock for a specific iOS application

• FileWave Networking Imaging 14.10.x brings compatibility with FileWave 15.0.x.
• PXE Kernel: 6.2.6
• Buildroot: 2023.02
• FileWave Windows Imaging is now supported in FileWave Anywhere, as mentioned above

The following features have been removed from FileWave 15.0.1:

• 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 

Some features relying on notifications require the same notification library. This means that the following features will stop working for devices running FileWave 14.7 or earlier versions:

Clients:

• CRL update handling
• TeamViewer sessions
• Reboot command (Windows devices)
• Personal Recovery Key updates (macOS)
• Verify Command from FileWave Anywhere
• Client Monitor from FileWave Anywhere

Boosters:

• CRL update handling
• Handle server certificate renewal
• Automatic Upgrade from FileWave Central
• Discovery Scan from FileWave Central (Discovery is anyway decommissioned)

Other device management and inventory report features are not impacted by ZMQ removal.

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

• 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

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

• FWRD-227 Fixed an issue where fixing enrollment conflict would cause FileWave Central to incorrectly remove "(root") item from the screen, requiring admin restart
• FWRD-3799 Improved the error messaging when selecting a device without an Imaging MAC address.
• FWRD-3882 Fixed an issue where Model Update could fail when updating "Excluded" Status for devices excluded via SmartGroup in multiple deployments

• Qt has been upgraded to 5.15.14
• OpenSSL has been upgraded to 3.0.9
• Apache has been upgraded to 2.4.57

• FW-17271 Fixed a potential issue where changing Imaging association would not be properly applied
• FW-20764 Fixed a potential issue where fileset properties dialog "take control" would not work properly
• FW-20771 Fixed an issue where a failed preflight script would not be executed again after modifying it
• FWRD-73 An security issues has been adressed
• FWRD-276 A security issue regarding TeamViewer has been fixed
• FWRD-302 A critical bug has been fixed in profile editor, where SCEP certificates where not shown in trust tab
• FWRD-303 The search function in Profile Editor has been optimised.
• FWRD-307 A bug has been fixed in profile editor, where the add button in trusted certificates did not act correct.
• FWRD-588 Fixed internal issue when creating webclip profile in FileWave Central
• FWRD-675 New filewave logos have been implemented
• FWRD-719 A bug has been fixed, while converting  associations to the existing deployment, the user has not been warned about possible issues.
• FWRD-957 we now show a warning, that you might overwrite data in case you save an empty value
• FWRD-1017 A bug has been fixed, where Software Update Permissions are not honored.
• FWRD-1283 Command history search function has been improved.
• FWRD-1297 Extension of Profile Editor Items - you can now for example Allow Air Drop
• FWRD-1300 A bug has been fixed, where DEP profile where not validated.
• FWRD-1314 Fixed several issues in Per-App VPN profile in FileWave Central
• FWRD-1318 Fixed and issue where we can't distinguish different SCEP profiles for reference in FileWave Central
• FWRD-1319 Fixed the list of available settings for Per-App-VPN profile in FileWave Central
• FWRD-1321 Fixed an issue related Airplay Mirroring Profile
• FWRD-1378 An security issues has been addressed
• FWRD-1393 Fixed an issue where FileWave Central would report an un-informative error "-1" when importing incorrect fileset
• FWRD-1408 Fixed an issue where FileWave Central would crash when moving Inventory Queries
• FWRD-1411 Fixed an issue where size and position of Fileset Report Window would not be restored in FileWave Central
• FWRD-1414 Fixed an issue where Serial Number field could be edited for real devices in FileWave Central
• FWRD-1419 Fixed an issue where "Reveal Client" would not work in Imaging section in FileWave Central
• FWRD-1426 Fixed an issue where Filesets could not be visible in Fileset view of Association section in FileWave Central
• FWRD-1427 Fixed an issue where it would be possible to edit serial number for Groups in FileWave Central
• FWRD-1433 Fixed internal issue where FileWave Central would check too frequently if EMM is enabled, which could lead to server load increase
• FWRD-1434 Fixed incorrect error when re-ordering queries in FileWave Central
• FWRD-1444 Fixed an issue where Synchronize EMM would be possible even if EMM is disabled in FileWave Central
• FWRD-1445 Fixed an issue where it would be possible for an admin to modify EMM Enterprise setup without Configure Enterprise permission
• FWRD-1562 Fixed an issue where IVS rpm would not include kernel changes, forcing upgrading kernel separately
• FWRD-1710 A bug in Single Sign-On Extensions, where the "Value" field in "Custom Configuration" table is not shown after saving the profile has been fixed. 
• FWRD-1731 Fixed an issue related to Command Policy profile validation for Wallpaper
• FWRD-1738 You can not add multiple times the same field during edit devices anymore.
• FWRD-1742 A bug has been fixed, where the internal name was missing in different areas
• FWRD-1757 A bug has been fixed, where locking modus for Smart Groups and Deployments where not working correctly.
• FWRD-1758 A bug has been fixed, where a clone of a group could be moved in its own group.
• FWRD-1760 A bug has been fixed in profile editor, where error message behaviour was misleading
• FWRD-1796 Fixed an issue where FileWave Central could crash when moving files between filesets
• FWRD-1809 Fixed an issue where it would be possible to import any file for Windows Client Package in FileWave Central
• FWRD-1982 Renamed Client package upload permission to clarify it covers both macOS and Windows
• FWRD-1983 Fixed various cosmetic issues in FileWave Central Apple Profile Editor
• FWRD-1997 Implemented auto-refresh feature for Command History of Apple MDM devices in Anywhere Admin, ensuring up-to-date information.
• FWRD-2023 Help links have been updated.
• FWRD-2044 Added validation for mac addresses in Imaging.
• FWRD-2097 Fixed an issue where Fileset Report in Client Info would incorrectly filter results when switching between devices
• FWRD-2296 Fixed an issue where FRP Email template could be modified without corresponding permission
• FWRD-2434 Fixed an ordering issue in the "Choose Dependency" dialog
• FWRD-2598 Optimized payload loading performance in Anywhere for specific clients, resulting in faster load times.
• FWRD-2616 Fixed an issue where upload progress bar would not be displayed properly if uploaded file is larger than 2GB
• FWRD-2666 Fixed an issue where notification component of desktop clients (NATs) would not reconnect to booster if it ever has to connect directly to the server
• FWRD-2711 Fixed an issue in Inventory Extension for Chromebooks where additional windows would appear when retrieving geolocation.
• FWRD-2777 Fixed an issue where scheduler internal data would not be properly purged after restart
• FWRD-2841 Fixed an issue where multiple admins could run model update concurrently
• FWRD-2862 Fixed an issue where script would be considered as modified without changing any option
• FWRD-2900 Fixed an issue where imaging-control increase harddrive command would fail due to incorrect partition name
• FWRD-2927 Ensured reboot deadline is properly displayed in Anywhere when "Force reboot" is set in Payloads revisions.
• FWRD-2997 Fixed an issue where model update could be blocked due to concurrent smart group evaluation
• FWRD-3104 Fixed an issue where Model Update could be blocked due to auto-enrolled devices management
• FWRD-3288 Fixed an issue where external links would not be opened in default browser by iOS Native App Portal
• FWRD-3320 Fixed issues related to status filtering for Software Updates
• FWRD-3350 Fix: Resolved 500 error by correctly sending Smart Group criteria values as integers instead of strings.
• FWRD-3405 In Grafana, user profiles (e.g., "fwadmin" on Chrome and "rudi" on Safari) display non-unique values when logging out and back in.
• FWRD-3408 Fixed an issue where Traditional Chinese translations would not load (FileWave Central)

• Qt has been upgraded to 5.15.14
• OpenSSL has been upgraded to 3.0.9
• Apache has been upgraded to 2.4.57

macOS Installers DMG (md5: 3799823817ffb7f30742864d2d78ba7b)
macOS Upgrade Fileset (md5: 3a4e2bb5b0c181680d6d5489ea41f328)
macOS Admin (md5: 950e3dab63b71a7a146d66e2da4772d7)
macOS Booster (md5: 50793509311d8379371bcba7f7808a4c)
macOS Server (md5: b62c7ba9de4f3bb988de5be4fcfe98f5)
macOS Client (md5: 5d0c1e28c72f345bd446d997310169ca)

Windows Upgrade Fileset (md5: 88c9c061a8614815c22d95b1720a5bae)
Windows Admin (md5: 8f67bc30f7eaf851123dd4a0eadaae5e)
Windows Booster (md5: 4aa51881beddcaab602b1df6ddf0efa6)
Windows Client (md5: 0b6f8dbce16be7ed34be47c7e50a287c)

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: 4c0fde7dcf915bdaed61ebc7e86a595c)
Static CDN URL :

https://fwdl.filewave.com/15.0.1/filewave/App%20Portal%2015.0.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: 09973507a90f57c15c416aaff8dfaecf)

Linux Installers (md5: c05dac3a4ba5974ad2f2618c61602cb0)
Linux Server (md5: 55053e80cb505fbb10a40c4da6d89d85)
Linux Booster (md5: c19db76c70c1647f25c4836fdd1f75d6)

If when doing yum update or upgrade you get a note that no updates are available it may be that you block access to some countries. yum clean all can clear the cache so that the upgrades can happen.

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

# login via ssh / root
$ yum update -y 
$ yum upgrade -y
$ yum install -y --nogpgcheck https://fwdl.filewave.com/15.0.1/fwxserver-15.0.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 upgrade -y
$ yum install -y --nogpgcheck https://fwdl.filewave.com/15.0.1/fwbooster-15.0.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 filewave-IVS
$ yum upgrade -y
$ 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 filewave-IVS
$ yum upgrade -y
$ 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: 30805c06862ad6d6b938d04db18d3739)
VMware and VirtualBox (OVA) Booster Appliance (md5: 309b5b492cc826108c56bcf544b97416)
VMware and VirtualBox (OVA) Imaging Appliance (md5: 9d60a7d7416468f45cecc985e70b30c2)

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

Hyper-V (VHD) Server Appliance (md5: 6afb21d54373c84a94c2cc395342c211)
Hyper-V (VHD) Booster Appliance (md5: 867bd0b6cefcd20b06b19cdc758a111d)
Hyper-V (VHD) Imaging Appliance (md5: f8bf72b3fce277c254d67001190ff9e1)

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.

14.10.2 is a security and bug fix release:

• Apache upgraded to 2.4.56
• Fixed Issues related to Model Update
• Fixed issues related to Wallpaper Overlay

• 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.2 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.

• FWRD-3092 Fixed an issue where setting empty text in FileWave Central would still lead to text overlay processing
• FWRD-3112 Fixed an issue where Wallpaper command would not be sent to newly re-enrolled device
• Fixed issues which could lead to Model Update being stuck

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: ff08183a9b3ed2b1b8d953d45ffcf665)
macOS Upgrade Fileset (md5: 3df1a645dec67bcd0ea7c2fc0a18ccfd)
macOS Admin (md5: bc4de1f80d3cf77753663f4157fc41f2)
macOS Booster (md5: 6d47fe11e774c684bbe1218ba682fd2d)
macOS Server (md5: ddc5a361df45de3b79f5739037e7d61d)
macOS Client (md5: 1e5bfe9567bfede795bccee6d1647f8e)

Windows Upgrade Fileset v14.10.3 (md5: 74e005a73b0255fb84747f113d8b6ed2)
Windows Admin (md5: 51491c672d24d9229eb6426bee627936)
Windows Booster (md5: 8a77b2a5ff0d978843e1e6f893003364)
Windows Client v14.10.3 (md5: 2cdbcbe8f28e31cf843ededd9f89abae)

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

Windows Upgrade Fileset v14.10.2 (md5: b7bc07fbee70cb42add03cbc662fa9c1)
Windows Client v14.10.2 (md5: 06d681f89150e46b0a541afdbf60ec06)

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: 69b100eb59075381596507df5a26929e)
Static CDN URL :

https://fwdl.filewave.com/14.10.2/filewave/App Portal 14.10.2.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: e979b2a2ac3d877eafe233f901876674)
Linux Server (md5: c9ff1ca5fbf439ac80e2637c71c16b07)
Linux Booster (md5: 320ade4c12f74540b919fc79eda392e6)
Linux IVS (md5:06691ea1e8b5388ebfb608eca1002bf2)

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.2/fwxserver-14.10.2-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.2/fwbooster-14.10.2-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.2/filewave-IVS-14.10.2-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.2/filewave-IVS-14.10.2-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: 980963f14722f6055d297d8278f6af84)
VMware and VirtualBox (OVA) Booster Appliance (md5: 8c9c023f1d33ea044e16f3e5f1661416)
VMware and VirtualBox (OVA) Imaging Appliance (md5: 70fe2f04bb0116b8ef3cab1f353de209)

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

Hyper-V (VHD) Server Appliance (md5: abc4485c52620afff2c0af4f298c10d2)
Hyper-V (VHD) Booster Appliance (md5: d4019985118fca34db69c835ff8e6359)
Hyper-V (VHD) Imaging Appliance (md5: 18b765c0d09a7dc0395504d2282c03c0)

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)