FileWave Version 13.0.3 (Unsupported)
These downloads are provided for the purposes of migrations and should not continue to be used in production. You should upgrade to either the most recent release or the one prior. They can always be found here: Supported FileWave Versions
FileWave Management Suite
Included in the Installer
- Admin
- Server
- Booster
- Client
Compatibility
Server
- macOS 10.12 through 10.14 (binaries are 64 bit only)
- Windows Server 2012 R2 and Server 2016
- Linux CentOS 6.10 x86_64, and 7.5 x86_64 (binaries are 64 bit only)
Booster
- macOS 10.12 through 10.14 (binaries are 64 bit only)
- Windows 10, Windows Server 2012 R2 and Server 2016
- Linux CentOS 6.10 x86_64 and 7.5 x86_64 (binaries are 64 bit only)
Clients
- macOS 10.11 through 10.14 (binaries are 64 bit only)
- Windows 7 SP1, Windows 10, Windows Server 2008 R2, Windows Server 2012 R2 and Server 2016
Admin
- macOS 10.12 through 10.14 (binaries are 64 bit only)
- Windows 7 SP1 and Windows 10
Mobile Clients
- iOS 9 through iOS 12
- tvOS 10 through tvOS 12
- Android 4.1, 4.2 *known issues, 4.3 (Jelly Bean), 4.4 (KitKat), 5, 6 and 7
- Chromebook: ChromeOS 43+
Compatibility Chart
New Features (13.0.3)
Changes and New Features
MDM Profile removal
By default, FileWave is no longer answering with HTTP 401 when an unknown MDM Apple device checks in. This allows FileWave to recover data from a previous backup without un-enrolling devices, which could lead to data loss if applications were removed. For 13.0.3, a new option was added in "FileWave Admin / Preferences / Mobile / Apple" that reverts to previous behavior.
Desktop Client and Booster Affinity
FileWave 13.0.0 introduced a behavioral change related to how desktop clients are communicating with boosters. Before 13.0.0, clients would always contact the first booster, unless the booster is not reachable (off network or offline). This could lead to very long delay for fileset deployment if first configured booster would be overloaded. Starting with 13.0.0, clients will try to stay on a given upstream booster instead of changing frequently. This provides better load balancing as the connections are more stable. Clients will also fallback to the server if none of the boosters are reachable.
13.0.3 ensures that a client will retry boosters regularly if it fell back to the server.
Memory Footprint
During model update, a large amount of data is processed to determine which fileset will be deployed to which device. Fileset statuses are also processed and updated, so deleted filesets are removed, newly-associated filesets are marked as "Associated" and so on. Starting with FileWave 13.0.0, iOS fileset statuses are now properly reported, which can create a large number of entries in the database, increasing the memory consumption during model update.
The Linux operating system is more sensitive to memory fragmentation (very summarized: it is not able to to recover memory with a frequent and high number of allocations, even if the process is not using this memory anymore), and the additional features brought to FileWave in the previous versions made the Linux version consume more memory over time, which could lead to Out-Of-Memory management.
FileWave 13.0.3 is now using a more efficient memory allocation system, more efficient, and a special attention has been paid to reducing memory usage during model update to avoid memory fragmentation as much as possible.
VPN on Demand Option
IKEv2 VPN allows very granular configuration, based on VPN provider rules. For 13.0.3, VPN profile allows entering raw XML provided by VPN vendors.
New Features (13.0.2)
Changes and New Features
- Upgrade OpenSSL to 1.0.2q
- Several improvements related to performance during model update and "Database deadlocks":
- Internal changes to decrease model update duration
- Made sure iOS devices could not interfere with Model Update and cause database issues
- iOS App portal speed improvements
- Improved updating DEP associations to workaround potential issues on DEP Web service
New Features (13.0.1)
Changes and New Features
- Added DEP_FORCE_FULLSYNC settings to force DEP full sync to workaround possible issues with Apple DEP API
New Features (13.0.0)
Changes and New Features
- Discover the initial version of FileWave Admin Web Console
- Additional security internal changes:
- fwxserver and MDM/Inventory server share the same SSL certificate
- admin console and clients are checking SSL certificate validity
- helpers for self-signed certificates (usage of trusted CA issued certificate is recommended)
- Please read this Self-Signed Certificates KB article
- This version adds support for iOS 12, tvOS 12, macOS 10.14 (see below)
- Service Now integration
- Dependency failures are better displayed in client information
- Updated Observe Client component on macOS.
Apple 2018 Fall release support
Device Enrollment Program:
- New skip items for Setup Assistant:
- Screen Time
- Software Update
- iMessage and FaceTime
- Appearance
- Change default settings according to Apple Guidelines (Non supervised devices will be deprecated).
MDM Commands:
- Lock device on macOS can now display additional message
- VPP app installation is now supported on tvOS 12
Profile changes:
- Exchange and Email profiles have additional settings for S/MIME options
- Notification profile has additional settings
- Restriction profiles (iOS, tvOS and macOS) have additional settings
- VPN profile (IKEv2) has additional settings (Profiles: VPN IKEV2 changes)
- Xsan profile has additional settings
- New profile: Time server
- Smart Card profile has additional settings
- Privacy profile has additional entries for Transparency and Consent Control
- Energy profile has addition setting
Push Notification changes:
- New Apple APN server is now used by FileWave, using HTTP/2 protocol. Please make sure your FileWave server can contact https://api.push.apple.com (port 443).
Additional Information
Included Open Source Software
Click here for an extensive list of Open Source Software included in the FileWave products.
Fixes
- CT-1027 Fixed issues where error 500 would be raised when accessing Filesets tab
- FW-22432 VPP users and VPP codes management are not based on the same permission anymore
- FW-22442 Fixed an issue where, on Windows, restarting client service would prevent client monitor from working
- FW-22502 Fixed an issue where MDM enrolled macs would not report correctly profile fileset status
- FW-22543 Fixed invalid Privacy and Consent payload generation when defining Apple Events
- FW-22593 Fixed an issue where using drag and drop to import a .webloc file would create an invalid file in fileset, which could lead to containing folder deletion
- FW-22608 Fixed several issues where FileWave services could consume high level of memory
- FW-22723 Fixed an issue where a high number of connections to the server/booster would prevent the server/booster from processing further requests
- FW-22730 Fixed an issue where client not able to reach any booster would always use server without retrying boosters
- FW-22799 Fixed an issue where a fileset that could not be downloaded due to network issues will never be downloaded again and stay with "Fileset Error" status
- FW-22800 Fixed a performance issue where boosters would send useless requests to server
- FW-22819 Fixed an issue where MDM enrolled macOS would not send required MDM commands
- FW-22884 Fixed an issue where file on disk would get corrupted if booster unreachable during file transfer
- FW-22895 Fixed an issue where multiple "Insufficient licenses available" dialogs would show up when device count exceeds license count
- FW-22904 Fixed an issue where deploying profiles to MDM enrolled macs could cause database deadlocks
- FW-22927 Fixed an issue where model update would fail due to fileset status update
- FW-22930 Fixed an issue where enrollment would fail due to database deadlocks
- FW-22941 Fixed an issue where booster not able to contact upstream would not be able to reconnect
- FW-23032 Fixed an issue where shared iPad reporting invalid MaximumResidentUsers value would prevent device management
- FW-23035 Fixed incorrect behavior when internal id are larger than maximum signed int
- FW-23038 Fixed an issue where model update could hang due to high load on server
- FW-23044 Fixed an issue where synchronizing Chromebook data from Google could time out
- FW-23070 Fixed a possible security issue due to dynamic loading of DLLs
Downloads
Your existing FileWave Server must be version 12.0.3 or higher before you can upgrade to FileWave 13.0+.
Upgrading
Please read: https://kb.filewave.com/display/KB/Upgrading+your+FileWave+Server
This article contains important information that will help ensure your upgrade runs smoothly. It is strongly advised that you review this for each release, since new notes or instructions may have been added.
Please make sure you have a recent backup before upgrading your server.
Upgrading FileWave requires the FileWave Imaging Appliance (IVS) is upgraded to a compatible version to ensure communication continues. Example: FileWave 12.9.0 requires the 5.9 IVS to image your computers.
The FileWave Engage Server must be version 1.2.0 or greater for compatibility.
In order to avoid problems with migrating database internal structures please make sure that you use a local administrator account, not domain administrator, when performing FileWave Server upgrade on Windows platform.
Location Tracking
The location reporting feature in FileWave is disabled by default.
It is recommended that you verify that this feature is in accordance with your organization’s policies and AUP (Acceptable Use Policy). Notify your end users before activating location reporting, as enabling the feature will prompt for permission to location information.
Read more... The Location Tracking KB (https://kb.filewave.com/display/KB/Location+Tracking)
Before Upgrading
Version 13.0.x introduces higher security standards which have impact on self-signed certificate usage.
While it is recommended to use Trusted-CA issued certificates, you can still use self-signed certificate with FileWave ; please make sure you follow the upgrade steps described in this KB article.
Following upgrade steps is important to make sure your FileWave setup works properly !
FileWave 13.0.x uses new Apple Push Notifications service with HTTP/2 protocol ; make sure your FileWave server can contact https://api.push.apple.com (port 443).
Web admin console
With version 13.0.x comes the first iteration of FileWave web-based admin console. It will be installed automatically and uses default HTTPS port (443).
Upgrade to 13.0.x will fail if port 443 is not available (upgrade will fail without upgrading your server, leaving it with the previous version running).
It is recommended to use a dedicated server for FileWave ; if you want to share the server with other services that require HTTPs port, follow the following steps:
- stop other service using 443
- install FileWave 13.0.x
- change FileWave admin port to an unused as described in /wiki/spaces/DRAFT/pages/4327696 KB article
- restart FileWave 13.0.x
- restart other service
macOS Downloads
Windows Downloads
In order to avoid problems with migrating database internal structures please make sure that you use a local administrator account, not domain administrator, when performing FileWave Server upgrade on Windows platform.
Linux Downloads
Note: Use the following command to download and unzip the installers:
wget https://fwdl.filewave.com/13.0.3/FileWave_Linux_13.0.3.zip
unzip FileWave_Linux_13.0.3.zip
Since v11+ only has one installer (that installs both mdm and server), the old standalone mdm will be removed automatically when doing an upgrade. This does not delete any mdm data.
To install or upgrade the FileWave Server, use the following :
yum install -y --nogpgcheck fwxserver-13.0.3-1.0.x86_64.rpm
To install or upgrade the FileWave Booster, use the following :
yum install -y --nogpgcheck fwbooster-13.0.3-1.0.x86_64.rpm
iOS Downloads
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 highly recommended for iOS 9 devices (required for location information).
iOS 9+ : FileWave Enterprise.ipa
Static CDN URL :
https://fwdl.filewave.com/13.0.3/app_kiosk/filewave/App%20Portal%2013.0.3.ipa
Android Downloads
This is the Android APK, and can be downloaded and associated to update already enrolled Android Devices.
FileWaveClient-13.0.3.apk
Skeleton for Android white-boxing
Chrome
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
Skeleton for Chromebook white-boxing
Virtual Appliance Downloads
VMware and VirtualBox (OVA) Server Appliance
VMware and VirtualBox (OVA) Booster Appliance
For more information about importing the appliances please see: Importing Virtual Appliances
Hyper-V Appliance Downloads