Plan FileWave Compatibility for Windows Enterprise LTSC
What is Windows LTSC?
Enterprise LTSC is
PersonalWindows ComputersEnterprise areLong-Term notServicing theChannel only(LTSC) hardwareis intended for special-purpose devices that may runperform a copyfixed oftask, Windows.such Examples could includeas medical equipment,systems, digital signs, cashor machines, etc.kiosks.
EachThese ofsystems theseusually examples, require dedicated hardware, which may be high precision and very expensive. When purchasingneed a cataractstable surgeryfeature solution,set for example, the expectation is it will last many years and itshould won'thave golittle wrongdependence duringon anapps eyethat operation!change frequently.
Since the hardware's shelf live is much greater than that of a standard PC and reliability is of upmost concern, it requires the OS driving that hardware to provide that same support, without compromising the product.
This is where Microsoft's Long Term Service Channel comes into play. Unlike their mainstream OS versions, LTSC isreceives lockedmonthly inquality timeupdates, andincluding security fixes, but does not receive the sameregular newfeature updates delivered to the general availability channel. New feature sets arrive in later LTSC releases.
Microsoft's Windows Enterprise LTSC overview lists each LTSC release, its equivalent general availability release, and the servicing model.
App and feature availability differs by LTSC release. Check the documentation for the exact release instead of relying on a blanket list of included or missing apps.
Microsoft recommends the general availability channel for ordinary user PCs that need current Windows features and updatesbroad thatthird-party wouldapplication besupport.
Microsoft does not recommend LTSC for most or all PCs in an organization. Use it for a defined special-purpose workload with mainstreama versionstested ofapplication theirand OS.management Theplan.
Browser agreementavailability includedalso withdiffers by release. For example, Windows 11 Enterprise LTSC is2024 basedincludes uponMicrosoft securityEdge and actual issues reported by those using LTSC.
To provide some idea on scope, LTSC does not include the likes of Edge, Cortana, One Note, MSFT Store and many more applications and lacks inclusion of newer features. All of this is with the aim to ensure the hardware continues to function as it did the day it was produced.
This is a stark contrast to their mainstream Windows releases, which include many updates to applications and newer features.
For this reason, the LTSC version of Microsoft is not intended for PC use and should only be installed on devices that have these specific restraints.
For example, LTSC versions include Internet Explorer, since it is no longer receiving updates (beyond security). This could lead to websites not being viewable as designed.Explorer.
How does this impact FileWave?
Microsoft offergives thethis followingcompatibility statementwarning for their LTSC releases:
"Since the feature set for LTSC doesn't change for the lifetime of the release, over time there might be some external tools that don't continue to provide legacy support."
As expected, FileWave must reactsupport changes in current Windows releases and in the third-party components used by FileWave Client.
An LTSC release can remain under Microsoft support after an external library or management component stops supporting that Windows generation. Microsoft lifecycle support therefore does not guarantee compatibility with every FileWave Client release.
Security or supplier support may require FileWave to thereplace newera featuresdependency, introduced intoand the mainstreamreplacement may not run on an older LTSC release.
Check the exact LTSC release ofagainst anythe Operatingplatform-support System.table As Microsoft introduce these new features,for the FileWave Developerversion Teamyou beaver away, sometimesplan to utilisedeploy. theseDo newnot features, whilst other times having to react to changes and enhancements in OS updates, forcing theinfer FileWave products to also move forward.
This is in no way limited to FileWave code, but to any code that FileWave leverages, e.g. 3rd party code. Since FileWave does not have full control over the newer features introduced by Microsoft or support of all included 3rd party code, it is foreseeable, that an LTSC version may fall far enough behind the mainstream versions and no longer function as intended with FileWave.
There are times when 3rd party code must be replaced with alternate code, which could be driven by lack of supportcompatibility from thatMicrosoft's supplier, particularly where security is involved. When transitioning to newer 3rd party tools, there could be limitations regarding end-of-support ofdate older OS versions.
Due to the design of Long Term Service OS for Windows, FileWave cannot guarantee the same timeframe of support as Microsoft offer. The very nature of LTS Windows releases, avoids fundamental code changes that is seen in their mainstream releases. To ensure product efficiency, security and features, it can be necessary to include newer FileWave code which will no longer be appropriate for LTS versions, where the LTS version no longer falls inline with its mainstream equivalent.alone.
Taking a look at some lifetime examples, Windows 10 2016 LTSB was Microsoft's offering, pre-dating LTSC:
| Release Date | Mainstream End Date | Long Term End Date | |
| Windows 10 2016 LTSB (1607 equivalent) | Aug 2, 2016 | Oct |
Oct 13, 2026 |
DespiteMicrosoft thelists mainstream endsupport datefor ofWindows 10 2016 LTSB beingthrough 2016,October it12, was2021 seenand thatextended support through October 13, 2026. FileWave Client versionsbehavior were still functioning up tooutside the beginningtested ofplatform 2025.list However,may itchange was entirely plausible that this impact could have been sooner andbefore Microsoft's expectationextended-support is migration to LTSC.date.
AsFileWave's seenDownloads inpages ourlist downloadsoperating page,systems wethat are unable to test all possible versions of every OS. We highlight the versions fully tested and then list some versions which would bethose expected to work,work basedfor uponeach release.
If an LTSC release is absent from those tested.tables, treat it as unverified and test it before changing either the FileWave Server or Client.
Yet, due toRecord the aboveWindows details,edition, itLTSC release, FileWave Client version, and required device workflow in the test plan. The word LTSC alone is not possiblea tocompatibility suggestresult.
Plan upgrades
Before upgrading FileWave, pilot the target Server and Client combination on representative LTSC devices. Older FileWave willClients becan ableoften tocommunicate function,with eithernewer entirelyServers, but feature support and minimum-version requirements still need verification.
If the newest Client is not compatible, hold the Client version only on the affected LTSC devices while you test an operating-system or inapplication part,replacement on older Microsoft code.plan.
InReview essence,the whentarget FileWave release page for minimum Client and Server compatibility before production rollout. Test inventory, Fileset deployment, remote actions, and any device-specific workflow the LTSC equivalentsystem versionmust iskeep noperforming.
Do not prevent this code from being legacy.
What Options Exist?
Typically, older versions of FileWave Client still function with newer versions of FileWave Server. Where newer versions of FileWave software is released, products that are no longer in mainstream release should be tested thoroughly before considering upgrading. If satisfied the Client still functions, it is by internal choice whetherleave the FileWave ClientServer isunpatched upgradedsolely to preserve an old LTSC endpoint. Escalate the compatibility decision to FileWave Technical Support and plan isolation or not.replacement It may be just certain features are lost, rather thanfor the wholeaffected client no longer functioning.device.
If unsure, it may be prudent to cease upgrades ofRetest the FileWaveLTSC Clientworkflow softwarebefore for those dedicated devices.
There are times whenevery FileWave mustupgrade. makePrior somesuccess crucialproves change,only which will prevent certain olderthe versions ofand Clientfunctions fromthat communicatingwere any further with the FileWave Server. These changes are always stressed in our downloads documentation. If this is likely to impact devices from being managedtested at all, then rigorous testing should be attempted, before upgrading a production environment. The outcome may therefore mean it is no longer possible to upgrade FileWave appliances at all, until these older clients are no longer of concern.
Not upgrading FileWave appliances, in particular the FileWave Server, could have security concerns.
In the main, history has shown it is likely that these LTSC versions that are no longer in mainstream support, will still be able to function as hoped, however this cannot be relied upon as the FileWave product advances.time.