End of Life Statements

Windows 32bit Client - EOL
What
As the new desktop kiosk for Windows is based on 64bit libraries, FileWave 15.3.0 will not be supported on Windows 32bit platforms. FileWave Agent (fwcld) is currently still a 32bit executable, meaning there is no change in how Filesets are deployed, and scripts are executed with this initial change. 
When/Why
Windows 32bit has long been on the way out. Because it can only handle 3.5Gb of RAM there has long been a lot of progress to get away from it by customers. 
How
At first the Kiosk in FileWave 15.3.0 will be 64bit, and in a future release the entire agent will transition. Moving to a 64bit application is expected to happen later this year.
Related Content
Windows Enrollment

FileWave Kiosk 1.0 for macOS and Windows (EOL)
What
FileWave Kiosk 2.0 replaced the original desktop Kiosk for macOS and Windows in FileWave 15.3.0. Kiosk 2.0 is 64-bit. During the 15.3.x and 15.4.x transition, the client also included Kiosk 1.0.
Transition history
Kiosk 1.0 remained temporarily available for older workflows and rollback during that transition. It is now end of life and should not be used for new deployments.
Current guidance
Use Kiosk 2.0 for current macOS and Windows deployments. If an existing workflow still calls Kiosk 1.0, contact FileWave Technical Support before changing it so the dependency can be identified.
Related Content
FileWave Kiosk for macOS and Windows overview (15.3+)

macOS Imaging with IVS - EOL
What
macOS Imaging: Apple changes such as APFS, T2 chips, and Apple silicon moved macOS setup away from traditional imaging. With Compatibility mode deprecated, FileWave no longer keeps macOS imaging options in IVS.
When/Why
Apple has discouraged macOS imaging for years. This EOL change should not affect current workflows because modern macOS deployment uses enrollment and management workflows instead of imaging.
How
FileWave 15.4.0 removed macOS imaging from the IVS solution. Removing it also removed the NetBoot configuration warning tied to that retired workflow.
Related Content
Network Imaging / IVS

IPA-based FileWave Kiosk for iOS/iPadOS - EOL
The IPA-based FileWave Kiosk / App Portal distribution method for iOS and iPadOS is end of life. FileWave 16.3.0 and later use the Apple App Store version of FileWave Kiosk, delivered through Apps and Books / VPP from Apple School Manager or Apple Business Manager.
What changed
Starting with FileWave 16.3.0, FileWave moved iOS/iPadOS Kiosk delivery to the Apple App Store version of FileWave Kiosk. This is the standard managed-app distribution model for iOS and iPadOS: acquire the app in Apple School Manager (ASM) or Apple Business Manager (ABM), sync Apps and Books / VPP licenses into FileWave, and let FileWave deploy the App Store Kiosk to managed devices.
FileWave no longer ships new IPA packages for Kiosk in FileWave 16.3.0 or later, and older IPA packages will not be re-signed or refreshed. The older enterprise IPA path should be removed from managed deployments.
Who is affected
Customers managing iOS or iPadOS devices with FileWave 16.2.x or earlier.
Customers that still have an old 
iOS App - FileWave Kiosk fileset, IPA fileset, or IPA association in FileWave.
Customers that have not yet acquired the free FileWave Kiosk app in ASM/ABM Apps and Books.
Customers already running FileWave 16.3.x or later, with FileWave Kiosk acquired through ASM/ABM and no legacy IPA association, are already using the current deployment model.
Required action
Upgrade FileWave Server and related components to FileWave 16.3.x or later. Use a currently supported FileWave release where possible.
In ASM or ABM, acquire the free FileWave Kiosk app through Apps and Books / VPP.
Confirm FileWave is syncing Apps and Books / VPP licenses from ASM/ABM.
Delete the legacy 
iOS App - FileWave Kiosk fileset or any older IPA-based Kiosk/App Portal fileset if it exists.
Remove any remaining associations to the old IPA-based Kiosk/App Portal fileset.
Run a Model Update, then run an Apps and Books / VPP sync so FileWave recalculates available licenses.
Verify affected iOS/iPadOS devices, or allow them to check in during their normal verification cycle.
Do not create a new IPA fileset or keep an existing IPA association to make the FileWave 16.3.0+ Kiosk workflow function. The current workflow uses the App Store Kiosk app and VPP licensing instead.
Timing and risk
FileWave cannot provide an exact date when an older IPA installation might stop working in a particular environment. The legacy IPA path depends on enterprise IPA signing and the associated distribution account, and those older IPA signatures are time-limited. FileWave will not be issuing refreshed Kiosk IPA packages for this retired workflow.
Because this depends on Apple platform trust and app-signing behavior, the exact user-visible error may vary or may not appear until an app launch, install, update, or redeployment attempt. The safe operational guidance is to move iOS/iPadOS Kiosk deployment to the FileWave 16.3.0+ App Store / VPP workflow before the old IPA path becomes a problem.
Verify the transition
FileWave Server is running 16.3.x or later.
FileWave is syncing Apps and Books / VPP licenses from ASM/ABM.
The free FileWave Kiosk App Store app has enough available licenses for the managed iOS/iPadOS fleet.
No legacy 
iOS App - FileWave Kiosk fileset or old Kiosk IPA association remains in FileWave.
Managed devices receive the App Store version of FileWave Kiosk and users can open Kiosk normally.
FAQ
Can we keep using the old IPA until it stops?
That is not recommended. The old IPA workflow is retired, the IPA signature is time-limited, and FileWave will not refresh Kiosk IPA packages for this method. Upgrade to FileWave 16.3.x or later and use the App Store / VPP workflow.
Do we know the exact date the old IPA will stop working?
No. Treat the old IPA method as an end-of-life deployment path and remove it proactively rather than waiting for a device-side failure.
Do we need to buy the FileWave Kiosk app?
No. The FileWave Kiosk app is free, but it still needs to be acquired in ASM/ABM Apps and Books so FileWave can receive and assign VPP licenses.
What if our older FileWave version automatically deployed Kiosk?
FileWave 15.3.0 through 16.2.x used the older automatic Kiosk deployment behavior. Customers with iOS/iPadOS devices should upgrade to FileWave 16.3.x or later so Kiosk can be distributed through the current App Store / VPP workflow.
Related Content
Automatic updating of iOS/iPadOS Kiosk
FileWave Kiosk for iOS/iPadOS overview
Apple’s Volume Purchase Plan and License Management
FileWave Version 16.3.0 release notes
FileWave Official Version Support Statement

FileWave Compatibility Mode - EOL
What
Compatibility Mode was removed with FileWave 15.4.0.
When/Why
Communication between FileWave components has relied on TLS certificates for years. Compatibility Mode existed to help older clients, specifically clients older than 13.1, stay managed by a newer server even though they did not support the newer encrypted communication model. Removing Compatibility Mode enforced secured communication between FileWave components.
How
FileWave 15.4.0 and later require macOS and Windows clients to be version 13.1 or higher to continue communicating with the server.
For those legacy clients, the minimum enrolled operating system versions were macOS 10.11 and Windows 7 SP1. Those operating systems are now end of life, so use current supported operating systems whenever possible.
Related Content
FileWave Version 15.4.2

FileWave Server on CentOS - EOL
As FileWave continues to develop our industry-leading multi-platform solution, our primary goal is to make it as simple, stable, and scalable as possible. With the End of Life of CentOS on June 30th, 2024, beginning with 15.2.0, the FileWave Server will be shipped for Debian Linux and macOS. Although we will produce FileWave Server for CentOS 7 with 15.2, 15.3, and 15.4, we will not continue to produce new versions of CentOS installers for Server or Boosters after the June 30th EOL date. When we released 15.4.1 in July 2024 it did not officially support CentOS, and the announcement email and Download page reflect this. 
Want to get an email when this FAQ is updated? Using Email to stay updated on KB updates.
Easy URL to articles: https://go.filewave.com/debian 
FAQ
Q: Does this change affect me?
My FileWave Server is:
⚙️ Managed by me on CentOS: You will be able to follow the migration documentation where we have step-by-step guidance. The entire process can take about an hour, but copying all the data from the old server to the new one can take a longer time if there is a lot to copy so plan for your server to be offline for the day you do the migration.
Additional help is available on Discord. We have Debian-specific sessions every Thursday at 9:30am Eastern US time that are open for anyone, and monthly Open Office Hours for all questions in North American, European, and Asia Pacific time zones.
For those who need someone to walk through this step by step, please contact Professional Services. However, if you are already working with PS, please ask your Engineer to check, as they may be able to give you the help you need under an existing project.
You may also want to consider migrating to our Hosted offering, which would allow FileWave to manage and care for the server. Contact Customer Success for more information on Hosting. 
If something goes wrong in the migration process, please contact Customer Technical Support unless you are a Community Edition customer, in which case you would want to go to Discord for help.
✅ Managed by FileWave (Hosted): 100% handled by FileWave, so no action is needed, but make sure to check your Boosters and/or IVS.
✅ Managed by me on macOS: We continue to support FileWave Server on macOS, and no action is required for your Server. But make sure to also check your Boosters and/or IVS.
I Have Boosters:
⚙️ Running on CentOS: CentOS boosters will need to be switched over to Debian. The simplest process is to shut down each CentOS Booster, bring online a Debian Booster using the same IP address, and complete the setup process to enroll that Booster. Doing this will allow you to not need to worry about updating Firewall rules or Superprefs. 
If something goes wrong in the migration process, please contact Customer Technical Support unless you are a Community Edition customer, in which case you would want to go to Discord for support.
✅ Booster running on macOS or Windows will continue to be supported. No action is required for macOS or Windows Boosters.
I have FileWave IVS:
⚙️ Running on CentOS will need to be switched over to Debian. The simplest process is to shut down each CentOS IVS and then set up and enroll Debian replacements using the same IP address as the prior IVS. Setting up the IVS (Imaging Virtual Server)
FileWave 15.3.1 and beyond includes a Debian IVS server.
You can run a CentOS IVS with a Debian FileWave Server, so the order in which you migrate does not matter.
Q: Does this affect the Admin Console or Clients?
A: No. The FileWave Server, Boosters, and IVS are changing over to Debian, but all Windows and macOS components are still fully supported and will continue to be.
Q: Will FileWave help me with FileWave Server migration?
A: We are publishing and updating our documentation to help this process be as simple as possible. 
Q: What if I don't want to run a FileWave Server On-Premise anymore?
A: Please connect with Customer Success because we offer Hosting options and will migrate your data to our Amazon infrastructure.
Q: What if I would like someone to walk me through the whole migration?
A: Please connect with Professional Services & Training about our Migration services. 
Q: I have questions and just would like to speak with someone?
A: Please check out our Discord. We have sessions every month for Open Office Hours. If you are in a time zone where that doesn't work, use Discord channels to ask about alternatives pr reach out to Professional Services & Training. 
Related Content
End of Life of CentOS
Migrating your On-Premise FileWave Server to new Hardware
Upgrading your On-Premise FileWave Server
Updating CentOS Repo Files After Mirrorlist End of Life

FileWave Appliances on HyperV Gen 1 - EOL
FileWave no longer produces Hyper-V Generation 1 appliance images. Starting with FileWave Version 16.1.1, newly posted Hyper-V Server, Booster, and IVS appliances use Generation 2.
No action is required for an existing Generation 1 Server, Booster, or IVS appliance. The change only affects new Hyper-V appliance setup. Mixed Generation 1 and Generation 2 FileWave appliances can coexist, and this change does not affect VMware OVA images.
Related Content
End of Life Statements

FileWave Server on Windows - EOL
FileWave Server for Windows reached end of life with FileWave 14. FileWave Server packages are provided for Linux and macOS, while Windows remains supported for FileWave Central, Boosters, and Clients where those components are listed on Downloads.
If you still have a historical FileWave Server on Windows, plan a migration to a supported Linux or macOS server. Windows Server builds were supported through FileWave 13.3 and are not available for FileWave 14 or later.
FAQ
Q: Does this change affect me?
A: If you already run your FileWave Server on Linux or Mac this change does not affect you.
To check your server OS, click the blue status text in the bottom-right corner of the admin console.
A Windows-based server reports "FileWave Windows Server" in the Status box.
Q: Does this affect FileWave Central, Boosters, or Clients?
A: No. The end-of-life notice applies to FileWave Server on Windows. FileWave Central on Windows, Windows Boosters, and Windows Clients remain separate supported components when listed for the release you are using.
Q: Can I still use my Windows hardware?
A: Yes. You can host a supported FileWave virtual appliance on Windows hardware through a compatible virtualization platform, such as Hyper-V or VirtualBox.
Q: Will FileWave assist me with the migration?
A: Yes! Please contact Professional Services & Training.
Related Content
Upgrading your On-Premise FileWave Server
Migrating your On-Premise FileWave Server to new Hardware

ZeroMQ replacement with NATS - EOL
What
ZeroMQ is being replaced with NATS in a process starting with v14.8.
When/Why
This move will naturally occur when upgrading FileWave components where eventually NATS will replace ZMQ everywhere it is used.  This article and release notes will explain what is migrated in each new version.  
This does have an impact on what network ports are used in FileWave.
How
 Please observe our TCP ports KB for additional and deprecated ports.
As of FileWave 14.8, NATS will be implemented instead of ZeroMQ for Admin to Server communication.
In 14.9 the ZeroMQ features for clients is removed. NATS is used for all notifications between clients and servers as well as boosters.
In 15.0 ZeroMQ is entirely removed and no longer used.
Related Content
Default TCP and UDP Port Usage

Android device management pre-EMM - EOL
What
This notice explains that Android device management pre-EMM, also known as APK delivery, was deprecated as of FileWave v14.9.0.
When/Why
Android EMM is the replacement for the much older method of managing Android devices. This change does not affect environments that already manage Android devices with Android EMM in FileWave.
How
FileWave v14.9.0 was released in November 2022, and the pre-EMM APK delivery function was removed in FileWave 15.2.0. Use Android EMM for current Android enrollment and app-management workflows. 
Related Content
Quickstart Guide for Android EMM

Device Discovery - EOL
What
Device Discovery is retired. FileWave deprecated Device Discovery in FileWave 14.9.0 and removed it in FileWave 15.0.
When/Why
Device Discovery was not effective enough for production environments and saw little use. If you need basic network scanning outside FileWave, use a dedicated network scanner such as Angry IP Scanner or another tool approved for your environment.
How
Do not plan new workflows around Device Discovery. For FileWave 15.0 and later, use another network-discovery process and enroll or manage discovered devices through the normal FileWave workflows.

Observe Client - EOL
FileWave removed the Observe Client feature from the computer client in FileWave 14.8.0. TeamViewer replaced it for remote-control sessions.
TeamViewer provides the current cross-platform remote-control workflow for FileWave-managed devices.
FAQ
Q: How does this impact older clients?
A: After the FileWave Server is upgraded to 14.8 or later, Observe Client is no longer available, regardless of client version.
Q: How does this impact Client Preferences?
A: The admin console and Superprefs Editor no longer provide VNC port options. The Privacy Preferences for 'Managed Remote Control' and 'Prompt client for remote control access' are still used by TeamViewer.
Remove Superpref Filesets that only define VNC ports; those settings no longer have any effect.
For current remote-control guidance, see the TeamViewer KB articles.

FileWave Official Version Support Statement
What
FileWave supports the two latest major versions at any time. For example, if the current version is 15.5.x, we support versions 15.5.x and 15.4.x. Major releases occur roughly every quarter.
What does “officially support” mean?
We will investigate and patch significant issues in these versions. We do not produce patches for versions older than N-1, focusing instead on current versions and future improvements. If an issue is found in an older version, remediation will be in the form of an upgrade or a patch to a more recent version.
You can still contact our support teams about earlier versions. They will assist you to the best of their ability but won’t escalate tickets to our development teams. Upgrading is recommended to access the latest features and bug fixes.
Related Content
Downloads

Clever Integration - EOL
This is the FAQ for the email that was sent out to customers on October 29, 2021, about Clever integration being discontinued. Please check back here over time as our answers may evolve over time as we work with customers. 
FAQ
Q: When will the Clever integration stop working?
A: On December 31, 2021 it will stop syncing and you will no longer see updates from Clever. 
Q: What if I do nothing?
A: On December 31, 2021, you will see Clever stop syncing. Existing associations between devices and people will be unaffected in your FileWave but future changes will not sync.
Q: I don’t use Engage or Apple Classroom associations through FileWave. What should I do?
A: If you open the Native Admin you can go to Preferences -> Education and switch your server from Clever to None. Then login to Clever and pick to Disconnect or book a meeting with us and we will disconnect it with you.
Q: What are my alternatives to Clever integration?
A: There are two. You can either work with ASM (recommended) or import CSV data.
Q: How would I connect my SIS to ASM?
A: See this Apple article: https://support.apple.com/en-us/HT207409 
Q: What SIS are supported by ASM?
A: See this Apple article: https://support.apple.com/en-us/HT210156 
Q: How do I setup ASM integration in FileWave?
A: See this FileWave article: Classroom – SIS Data and utilize the complimentary consulting time mentioned in the email you received.
Q: I have questions about ASM integration that I couldn’t answer after reading this and connecting with FileWave Pro Services.
A: If you do not know who your Apple account executive or system engineer is then call Apple's EDU support line (800-800-2775) to determine who they are. They will be best to help you with deep ASM questions.
Q: I’m already using ASM to sync to FileWave. Is there something I need to do?
A: Login to Clever and pick to Disconnect or book a meeting with us and we will disconnect it with you.
This was the original email sent to customers who have Clever integration enabled:
Good afternoon,
 If we haven’t spoken then I wanted to first introduce myself. I joined FileWave earlier this year to run Professional Services and Training. I wanted to reach out to you because you appear to be using Clever integration in FileWave to assign devices to students and teachers. Clever was originally only added to support Engage, but then started to be used by some customers to support Apple Classroom. In your case, you may be using it for that or you may have simply left it configured after Engage went away. 
Clever integration is something that we will be discontinuing at the end of this calendar year, but there is a free alternative that has similar functionality and we want to help you migrate to it. 
 To meet the need of creating relationships of devices to individuals I wanted to let you know about our Apple School Manager (ASM) integration. ASM is free to use with Apple and supports SIS integration. By December 31st, 2021 we would like to help you with making the switch from Clever over to either CSV imports or ASM integration. After that date, Clever will no longer sync changes to your FileWave server so we recommend working with us as soon as you are able to so that you are not rushed. 
 I have created the Calendly link below for you to create a meeting with a Professional Services engineer to discuss the process and the migration. There will be no cost to you for either this meeting or the complementary 2 hours of support with the same engineer to work through the migration process. I encourage you to setup a meeting as soon as possible after you have reviewed the FAQ below. The FAQ will help you understand what help you may or may not need in this process.

FileWave Engage EOL
What
This is a notice that as of FileWave v14.8+ Engage will no longer be supported.
When/Why
FileWave v14.8 should release in Spring 2022. Engage has been at end of life earlier than this, but this will be the first release that will remove the functionality. 
How
In 14.8.0 the supporting features will be removed. Inventory queries related to Engage will not work anymore. There are 2 fields specifically: EngageProfile and EngageProfileStatus will be removed. We have also already removed EngageX from the app store.

Apple EOL Advisory: Intel-Based Apps and Rosetta Dependencies on Apple Silicon
What
Apple is signaling the end of the Intel-to-Apple-silicon transition window for Mac software compatibility.
In macOS 26.4 beta, testers/reporters have observed user notifications such as:
Support Ending for Intel-based Apps
This version of "[App Name]" will not open in a future release of macOS. Learn how to update to an Apple silicon version.
This warning applies to two risk areas:
Intel-only apps without a native Apple silicon build
Workflows that still rely on Rosetta translation
Apple has also published official guidance confirming the broader direction and support timeline for Rosetta:
Using Intel-based apps on a Mac with Apple silicon (Apple Support)
When/Why
Apple announced the Apple silicon transition in 2020. The current messaging indicates that compatibility grace periods are narrowing.
Why this matters now:
Future macOS releases may prevent Intel-only apps from launching
Rosetta has an explicit support runway in Apple documentation:
Available through macOS 27
Beginning with macOS 28, limited to certain older, unmaintained games that depend on Intel-based frameworks
Organizations that have not mapped Intel app dependencies may see avoidable outages during OS upgrades
Important nuance (beta vs GA)
The notification wording/screenshots were first observed in macOS 26.4 beta.
Because 26.4 is still beta, exact final UI wording and placement in GA cannot be guaranteed.
However, Apple’s official support article confirms the strategic direction: Intel dependency retirement is real, and Rosetta availability is time-bounded.
How
FileWave 16.4 inventory workflow
FileWave 16.4 reports architecture for inventoried macOS applications as Intel, Apple Silicon, Universal, or iOS app. Use an Inventory Report to turn the general Rosetta risk into an application-and-device remediation list.
In FileWave Central > Reports, create a report with the application inventory component as the main component.
Return Application Name, Version, Path, Architecture, Client Name, OS Version, and CPU Type.
Filter the report to macOS applications whose architecture is Intel.
Group or export the results by application name and version to identify the vendors and business owners that need follow-up.
Validate each critical Intel application on representative Apple silicon Macs, then record whether the remediation is a native update, a replacement, a retired workflow, or a documented exception.
Repeat the report after remediation to measure the remaining Intel-only footprint.
Do not interpret a Universal result as proof that the complete workflow is Rosetta-free. Universal applications can still load Intel-only plug-ins, extensions, command-line tools, or helper processes. FileWave’s application architecture value identifies the inventoried application; critical workflows still require functional validation.
See Inventory Reports for the macOS and Windows architecture values and report patterns.
Rosetta usage-awareness restriction in FileWave 16.4
FileWave 16.4 adds the Apple Restrictions setting that controls Rosetta usage awareness. On supported macOS versions, the operating system can display an awareness dialog when a user launches software through Rosetta, explaining that the organization should plan for a native replacement before Rosetta support is removed.
Decide whether users should see Apple’s awareness dialog as part of the organization’s migration communication.
Review the setting with Checking Apple Profile Compatibility before deployment because availability depends on the macOS version.
Pilot both the restriction and the affected Intel application workflow. The restriction controls awareness messaging; it does not convert an Intel application, remove its Rosetta dependency, or prove that the application will keep working.
Keep the Inventory Report remediation workflow below as the source for identifying actual Intel exposure.
Recommended actions for endpoint, desktop engineering, and IT operations teams:
Inventory Intel exposure
Identify Intel-only apps across managed Macs
Identify Universal apps forced into Rosetta mode (for Intel plug-ins/extensions)
Assess operational impact
Classify apps by business criticality
Flag high-risk workflows with no known Apple silicon replacement
Engage software vendors
Request Apple silicon-native availability and timelines
Track vendor commitments and support statements in your internal app catalog
Pilot migration paths
Validate native replacements in a controlled pilot
Test critical workflows on current stable macOS and pre-release builds
Set upgrade guardrails
Block or defer major macOS upgrades for impacted groups until blockers are resolved
Communicate expected user impact and timelines before rollout
Update standards and procurement
Require Apple silicon-native support for new app approvals
De-prioritize tools with unresolved Intel-only dependency chains
Related Content
Using Intel-based apps on a Mac with Apple silicon (Apple Support)

macOS 12 Monterey Platform Support - EOL
What
Starting with FileWave 16.3.0, macOS 12 Monterey is no longer listed as an Expected to work platform for FileWave Clients, FileWave Server, FileWave Central, or FileWave Booster.
Customers who still need to manage macOS 12 devices should use the FileWave 16.2.5 client listed in the Legacy section of the FileWave 16.3 and later release notes.
When/Why
macOS 12 Monterey is no longer receiving current security updates from Apple. Apple's public security releases page lists macOS Monterey 12.7.6, released on July 29, 2024, as the final macOS Monterey security release.
FileWave 16.3 and later releases need to keep moving with current macOS frameworks, platform behavior, and security requirements. Removing macOS 12 from the expected-support matrix helps FileWave focus on supported macOS versions without keeping newer platform work constrained by an older Apple operating system.
Impact
macOS 12 is no longer listed under Expected to work for FileWave 16.3.0 and later.
FileWave does not recommend using macOS 12 for FileWave Server, FileWave Central, or FileWave Booster on FileWave 16.3 and later.
Customers who still need to manage macOS 12 devices should use the FileWave 16.2.5 client listed in the Legacy section of the release notes.
Support for macOS 12-specific issues is limited because the platform is no longer receiving current security maintenance from Apple.
Recommended action
Upgrade macOS 12 devices to a currently supported macOS version where possible. If macOS 12 must remain in the environment temporarily, use the FileWave 16.2.5 client and plan migration away from macOS 12.
Related Content
FileWave Version 16.3.0
FileWave Version 16.3.2
FileWave Version 16.4.0
FileWave Version 16.2.5
Apple security releases