Microsoft General Info

The Microsoft General Info section is a valuable resource for topics related to FileWave and managing Microsoft devices that don't fit into other categories. It covers a range of subjects, including tips, insights, and updates on Microsoft products, services, and device management. Discover helpful information to optimize your Microsoft device management strategies and stay informed about the latest developments in the Microsoft ecosystem.

Windows 11 Compatible Devices

Description

Microsoft have provided their list of supported Windows 11 requirements:

https://www.microsoft.com/en-gb/windows/windows-11-specifications

https://docs.microsoft.com/en-gb/windows-hardware/design/minimum/windows-processor-requirements

The variety of machines that could be either complaint or non-compliant is vast.  The recipe here allows for a scripted method to confirm the status of compliance and is based upon Microsoft's Readiness PowerShell script, details of which are highlighted in the following documentation: 

https://techcommunity.microsoft.com/t5/microsoft-endpoint-manager-blog/understanding-readiness-for-windows-11-with-microsoft-endpoint/ba-p/2770866

Two of the methods provided are edited versions of the original supplied Microsoft script.  One is a straight forward Custom Field, whilst the other uses a more advanced method to achieve the same result.  The script for both methods will provide an output of Pass or Fail in the Custom Field value.  Please choose as desired.

Custom Field values may be added to the Client View:

windows_11_compliance_list.png

Unaltered Version

Unaltered version of the Microsoft supplied readiness script.  Output will include all text as dictated by Microsoft.  As a Custom Field, this information can be lengthy, but inventory Queries may be configured to identify the word 'Fail'.

Ingredients
↓ Windows

Windows 11 Readiness Unaltered.customfields
Directions
  1. Download the provide Custom Field: 'Windows 11 Readiness Unaltered'
  2. Open the Custom Field Editor: FileWave Admin > Assistants > Custom Fields > Edit Custom Fields
  3. Select Import and choose the downloaded Custom Field from step 1
  4. Change Name if desired
  5. Save

Example failed value:

{"returnCode":1,"returnReason":"TPM, Processor, ","logging":"Storage: OSDiskSize=98GB. PASS; Memory: System_Memory=4GB. PASS; TPM: TPMVersion=False. FAIL; Processor: {AddressWidth=64; MaxClockSpeed=2494; NumberOfLogicalCores=4; Manufacturer=GenuineIntel; Caption=Intel64 Family 6 Model 70 Stepping 1; }. FAIL; SecureBoot: Capable. PASS; ","returnResult":"NOT CAPABLE"}

Simplified Method

The information output by the default script is lengthy and can be considered as inappropriate as a single Custom Field value.  This method alters the script, which when used as a Custom Field will return either Pass or Fail.  However the details of why it failed will not be provided.

Ingredients

↓ Windows

Windows 11 Readiness.customfields

Directions

  1. Download the provide Custom Field: 'Windows 11 Readiness'
  2. Open the Custom Field Editor: FileWave Admin > Assistants > Custom Fields > Edit Custom Fields
  3. Select Import and choose the downloaded Custom Field from step 1
  4. Change Name if desired
  5. Save

Advanced Method 

Since the hardware of the device will rarely change, it is unnecessary to have the Custom Field script run on every inventory.  Additionally, the information output by the default script is lengthy and can be considered as inappropriate as a single Custom Field value.  The following method involves building an Administrator Custom Field and the script will be added as a Fileset instead.  This Fileset will update the Custom Field value when ran, the details will be stored in a local log file on the device, yet the Custom Field will merely show Pass or Fail once the script has ran on a Windows device.

As a Fileset, the script will run only once without intervention, preventing the script from unnecessarily running over and over again.

Ingredients

↓ Windows

Windows 11 Compatible.customfields
↓ Windows

Windows 11Compliance.fileset.zip

Directions

Custom Field
  1. Download the provided Custom Field: 'Windows 11 Compliance'
  2. Open the Custom Field Editor: FileWave Admin > Assistants > Custom Fields > Edit Custom Fields
  3. Select Import and choose the downloaded Custom Field from step 1
  4. Change Name as desired, but ensure the Internal Name is not altered and association is to all devices
  5. Save
  6. Once configured, the Fileset may then be associated and pushed to devices

Fileset

  1. Download the provided Fileset
  2. Edit the Fileset's script Environment Variables (details below)
  3. Associate to devices for testing and then once satisfied push to all devices
Fileset Editing

windows_11_compliance.png

Additional Information

The Fileset will use the FileWave API to report back the current status of the device's compatibility during Fileset activation.  If devices are addressed to change their compatibility status, it is possible to run a 'Reinstall Fileset' which will cause the API to update the current information, refreshing the Custom Field.

The full output of the script will be available in the script log, accessible from the right click menu item of a Fileset's script status view from Client Info (local network between Admin device and selected machine is required).  A failure example:

{"returnCode":1,"returnReason":"TPM, Processor, ","logging":"Storage: OSDiskSize=98GB. PASS; Memory: System_Memory=4GB. PASS; TPM: TPMVersion=False. FAIL; Processor: {AddressWidth=64; MaxClockSpeed=2494; NumberOfLogicalCores=4; Manufacturer=GenuineIntel; Caption=Intel64 Family 6 Model 70 Stepping 1; }. FAIL; SecureBoot: Capable. PASS; ","returnResult":"NOT CAPABLE"}

Self-Signed Certs

The Fileset Activation Script 'HardwareReadiness.ps1' must be edited to allow for Self-Signed Certificates.  The following section should have the mentioned lines updated to remove the leading hashes.  After removal it should look like the following:

#####################################################
# Beginning of ammendment for FileWave Custom Field report

# REMOVE HASHES FROM FOLLOWING 12 LINES IF USING A SELF-SIGNED CERTIFICATE
add-type @"
using System.Net;
using System.Security.Cryptography.X509Certificates;
public class TrustAllCertsPolicy : ICertificatePolicy {
public bool CheckValidationResult(
ServicePoint srvPoint, X509Certificate certificate,
WebRequest request, int certificateProblem) {
return true;
}
}
"@
[System.Net.ServicePointManager]::CertificatePolicy = New-Object TrustAllCertsPolicy

The client must be able to reach the server on port 443 to be able to post the API update back to the server.

Result

The Custom Field for the Simplified and Advanced methods actually provides 3 possible values:

Notes

These options are by no means the only options available.  The script could be used within an Upgrade Fileset for Windows 11, for example, and the script may run prior to confirm if the device satisfies the requirements.  However, requirement scripts should only be used where they will eventually become true, to prevent them from running forever and being a constant draw on the server.


Windows 11 support in FileWave 14.7+

What

Windows 11 was released by Microsoft on October 5, 2021. 

When/Why

As an administrator, it is important to know if this new OS is supported, and about the end of life of older versions of Windows.

How

The FileWave client running on Windows 11 is fully supported.  We will also continue to support Windows 10 because it is still a supported OS by Microsoft.

Related Content

Using Native Windows Tools to Troubleshoot

What

Things break, thank goodness!  If they didn't all IT engineers would be out of work.  But what do you do when things break?  Specifically, if a FileWave client on a Windows device isn't working right, what tools are available to help?  Turns out there are tons of options!

When/Why

We'll turn to other tools whenever we need an alternate method of confirming things with remote machines.  This list isn't meant to be all-inclusive, but is a great "starter pack" of tools you can use!

Note that access to remote Windows tools is always reliant on being logged in with a MSFT account that has rights to perform those actions. 

How

Here is a list of super-helpful tools:

image.png

image.png

image.png


image.png

image.png

Related Content

Transitioning to 64-bit Architecture in FileWave 15.5 for Windows

What

With the release of FileWave 15.5, significant changes have been made to enhance security and performance on Windows platforms. FileWave now relies on updated open-source components, notably Qt 6, which supports only 64-bit operating systems. This shift means that FileWave Client, FileWave Booster, and FileWave Central are now exclusively 64-bit applications on Windows. As a result, FileWave 15.5 and later cannot run on Windows 32-bit editions.

This transition impacts how filesets are delivered and managed on Windows devices. Administrators need to understand these changes to ensure a smooth migration and maintain the functionality of their deployments.

In 15.5, Custom Fields and Blocker Scripts are forced to run in 32bit mode, and these two areas are the only parts of FileWave that have not been updated to run in 64bit on Windows. 

When/Why

When to Be Aware

Why This Change Matters

However, this change necessitates adjustments in how filesets are configured and deployed, particularly concerning file system paths and registry entries on Windows devices.

How

Impact on Fileset Delivery and Management

On Windows systems, the installation paths differ between 32-bit and 64-bit architectures:

To maintain compatibility with legacy 32-bit applications, Windows uses a system called WOW64 (Windows On Windows 64). This system automatically redirects file system calls from 32-bit applications attempting to access C:\Program Files\ to C:\Program Files (x86)\, ensuring that older applications function correctly on 64-bit systems.

Previous Behavior with FileWave 15.4 and Earlier

Configuring Filesets in FileWave 15.5

When creating or editing a fileset:

  1.  Access the Fileset Properties: In the FileWave Central console, select the fileset and open its properties.
  2. Specify the Architecture:
    • Choose between 32-bit or 64-bit based on the application’s requirements. New Filesets will default to 64-bit.
    • This setting affects file system paths, registry keys, and the environment in which scripts run.
    • The Disable Windows 32-Bit on Windows 64-Bit redirection option in the same area was the setting that existed previously to allow a Fileset to behave as if the FileWave Client were 64-Bit. This setting remains for compatibility and will remain in the state it was in before you upgraded to FileWave 15.5. 
      image.png
  3. Understand the Effects:
    • File Deployment: Determines whether files are installed in C:\Program Files\ (64-bit) or C:\Program Files (x86)\ (32-bit).
    • Registry Entries: Ensures registry modifications are made in the appropriate 64-bit or 32-bit sections.
    • Script Execution: Scripts will execute in the designated architecture environment, impacting how commands are processed

Migration Considerations

To facilitate the transition:

It may be necessary to alter some of the script when transitioning between 32 and 64 bit

Before wide deployment, test filesets to ensure they install correctly on target Windows devices with the appropriate architecture settings.

Impact on FileWave Booster and Central

The transition also affects FileWave Booster and FileWave Central on Windows:

Careful planning and testing are essential to ensure a smooth transition and to prevent deployment errors on Windows devices.

Related Content

Microsoft Long Term Service Channel

What is Windows LTSC?

Personal Computers are not the only hardware that may run a copy of Windows.  Examples could include medical equipment, digital signs, cash machines, etc.

Each of these examples, require dedicated hardware, which may be high precision and very expensive.  When purchasing  a cataract surgery solution, for example, the expectation is it will last many years and it won't go wrong during an eye operation!

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 is locked in time and does not receive the same new features and updates that would be expected with mainstream versions of their OS.  The support agreement included with LTSC is based upon security 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.

How does this impact FileWave?

Microsoft offer the following statement 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 react to the newer features introduced into the mainstream release of any Operating System.  As Microsoft introduce these new features, the FileWave Developer Team beaver away, sometimes to utilise these new features, whilst other times having to react to changes and enhancements in OS updates, forcing the 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 support from that supplier, particularly where security is involved.  When transitioning to newer 3rd party tools, there could be limitations regarding support of 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.

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
LTSB (1607 equivalent) Aug 2016 Oct 2016 Oct 2026

Despite the mainstream end date of LTSB being 2016, it was seen that FileWave Client versions were still functioning up to the beginning of 2025.  However, it was entirely plausible that this impact could have been sooner and Microsoft's expectation is migration to LTSC.

As seen in our downloads page, we are unable to test all possible versions of every OS.  We highlight the versions fully tested and then list some versions which would be expected to work, based upon those tested.

Yet, due to the above details, it is not possible to suggest FileWave will be able to function, either entirely or in part, on older Microsoft code.

In essence, when the LTSC equivalent version is no longer in mainstream support, it is now effectively legacy code still.  Microsoft's agreement plan does 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 whether the FileWave Client is upgraded or not.  It may be just certain features are lost, rather than the whole client no longer functioning.

If unsure, it may be prudent to cease upgrades of the FileWave Client software for those dedicated devices.

There are times when FileWave must make some crucial change, which will prevent certain older versions of Client from communicating any further with the FileWave Server.  These changes are always stressed in our downloads documentation.  If this is likely to impact devices from being managed 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.