Supported platforms
Multi-tenant SaaS platform 
| Single-tenant SaaS platform 
| On-premises platform 
A list of supported platforms, and the software required to allow them to be installed or to work.
For more support and lifecycle information refer to Microsoft Rapid-Release Cycle on 1E Support for details of which Current Branch versions are supported by 1E products, and known issues regarding specific versions, and refer to Microsoft Product and Services Lifecycle Information.
This section shows only those OS versions in mainstream support by Microsoft, and therefore supported by 1E, and by 1E Client. For details refer to Constraints of legacy OS.
Platform1E portal
|
Category |
Product |
Notes |
|---|---|---|
|
Browsers |
Latest version of:
|
These browsers are supported on all OS platforms which the browser vendor supports. refer to Whitelisting connections to 1E Cloud for details of URL that must be whitelisted for administrator browsers. The Portal and any API should be added as a trusted site. This is especially important when running scripts that may produce unexpected errors. Microsoft legacy browsers Support has been withdrawn for Internet Explorer 11 and legacy Microsoft Edge (non-Chromium version) because Microsoft no longer supported them since 2021. We recommend you use Google Chrome, Firefox, or Microsoft Edge Chromium browser. |
1E Toolkit
Configuration Manager console extensions
|
Category |
Product |
Notes |
|---|---|---|
|
Client OS |
|
For OS supported by Configuration Manager Current Branch (CB) refer to Supported configurations for Configuration Manager. |
|
Configuration Manager console |
|
These are the versions of Configuration Manager that 1E has tested and therefore support, but later versions are assumed to work also. Refer to Preparing for the ConfigMgr extensions for 1E Endpoint Troubleshooting. |
|
Runtime libraries |
|
1E Toolkit installer includes the Visual C++ 2015-2019 Redistributable package. |
TIMS
|
Category |
Product |
Notes |
|---|---|---|
|
Windows OS |
|
Professional and Enterprise editions of Windows 10 and 11 are supported. All versions are provided with 32-bit & 64-installers. TIMS is currently only available for Windows OS. |
|
Runtime libraries |
|
One of these versions of .NET Framework is required. 1E supports .NET Framework versions that are in mainstream support by Microsoft. For Microsoft product lifecycle details, refer to Search Product and Services Lifecycle Information. TIMS installer includes the Visual C++ 2015-2019 Redistributable package. |
|
Other Windows Software |
|
PowerShell 3.0 or later is required when testing instructions that have PowerShell commands embedded or scripts that are downloaded. |
1E Client
A list of all the platforms supported by 1E Client, and the software required to allow 1E Client to be installed or to work. 1E Client software for Windows, macOS and Linux is available for download from the 1E Support Portal.
Windows client
|
Category |
Product |
Notes |
|---|---|---|
|
Operating System |
|
Professional and Enterprise editions are supported for Windows 10 and Windows 11. All versions are provided with 32-bit & 64-installers, and can be installed on physical and virtual computers. For installation guidance on Windows, refer to Deploying 1E Client on Windows. The following 1E Client features and modules are supported on Windows OS:
|
|
Runtime libraries |
|
.NET Framework is required only for the following features of 1E Client:
The 1E Client now uses Microsoft Visual C/C++ Runtime Library (MSVCRT) version 14.42.34438.0. If a device has an older version installed, it may cause other services that depend on the runtime to restart during the 1E Client installation. |
|
Other Windows Software |
|
1E Client provides real-time client features. It also includes the CD client module. Real-time client features can optionally use CD to download content (feature enabled by default) if the CD client module in 1E Client is enabled (module disabled by default) or CD 7.0 or later is running. PowerShell is not a prerequisite for installation of the 1E Client. PowerShell is used by some 1E instructions (that have PowerShell commands embedded or scripts that are downloaded) and some of these require PowerShell 3.0 or later. |
|
Microsoft Endpoint Configuration Manager Client |
|
The following client features work with these versions of Configuration Manager on Windows computers:
Configuration Manager is not a prerequisite for installation of the 1E Client, and except for above features, the 1E Client, its features and modules, have no dependency on Configuration Manager. 1E Platform, Content Distribution, WakeUp, and Application Migration (unavailable for SaaS) have Configuration Manager Console extensions which are available separately. This list shows only those Configuration Manager versions in mainstream support by Microsoft, and therefore supported by 1E Platform, and by 1E Client. |
macOS client
For installation guidance, refer to Deploying 1E Client on macOS.
|
Category |
Product |
Notes |
|---|---|---|
|
Operating System |
|
Other versions of these non-Windows OS should work but have not been tested by 1E Platform. 1E Client for macOS is written for Intel and supported on Apple devices using Intel processors. It is also supported on Apple devices using the M1 chip, provided you have installed Rosetta 2, which is included with Big Sur and later. 1E Client is a daemon (not an app), therefore, during installation or running it will not prompt for Rosetta 2, which does not get installed on-demand. You only need to install Rosetta 2 once, using one of the following commands, but repeating the command will safely reinstall it. The second version of the command requires root permission. Attempting to install on an Intel device will issue a harmless unrecognized option usage message. Copy
|
|
Other Software |
|
Bash and perl are required for installation of 1E Client on all non-Windows OS. 1E instructions support the use of Bash scripts on all supported non-Windows OS. To see if an Instruction requires a Bash script, look in its Instruction Definition XML file for Bash script resources defined under the <Resources> tag. Bash is the preferred choice when developing custom instructions for non-Windows OS. There are slight differences between OS implementations of Bash, particularly on the Mac. 1E recommends testing custom Bash scripts on each supported OS. Rosetta 2 must be installed before installing 1E Client for macOS on an Apple device using a non-Intel processor such as M1 chip, see above details about installing Rosetta 2. |
Linux client
For installation guidance on the following OS, refer to Deploying 1E Client on Linux.
|
Category |
Product |
Notes |
|---|---|---|
|
Operating System |
|
Other versions of these non-Windows OS should work but have not been tested by 1E.
|
|
Other Software |
|
Bash and perl are required for installation of 1E Client on all non-Windows OS. 1E instructions support the use of Bash scripts on all supported non-Windows OS. To see if an Instruction requires a Bash script, look in its Instruction Definition XML file for Bash script resources defined under the <Resources> tag. Bash is the preferred choice when developing custom instructions for non-Windows OS. There are slight differences between OS implementations of Bash, particularly on the Mac. 1E recommends testing custom Bash scripts on each supported OS. |
Content Distribution
1E Platform
Although not a requirement for generally using Content Distribution, the 1E Platform must be available in your environment before you can use certain features. The following features require 1E Platform and platform features of the 1E Client to be enabled.
-
Content Distribution app provides visibility of content distribution activity
-
Single Site Download (SSD)
-
Get Migration Settings task sequence action used to manage computer associations
The following features were provided in earlier versions of Content Distribution:
-
1E Client Health - now provided by the Endpoint Automation feature of the platform
-
Content Distribution Dashboard - now provided by Content Distribution app feature of the platform
Content Distribution Administration Tools
|
Category |
Product |
Notes |
|---|---|---|
|
Windows OS |
OS versions supported by Configuration Manager versions are listed below. |
|
|
Microsoft Endpoint Manager Configuration Manager |
|
For each Configuration Manager site server where you intend to administer task sequence packages to use 1E as the alternate download provider, you need to ensure that:
If these conditions are not met, the 1E settings for task sequences will not be created correctly. This is the case even if you install a remote Configuration Manager Admin Console with the Content Distribution Admin Console GUI extension, except for Content Distribution Branch Tools, which are required to be installed on Configuration Manager Site Server only. |
|
Runtime libraries |
|
.NET Framework is required for the Admin Console GUI extensions, the Download Monitor, and NomadBranch GUI. It is not a requirement for other features of Content Distribution. |
|
Antivirus |
Content Distribution is able to work with antivirus systems provided they have certain exclusions configured. |
It is likely that performance will be impaired by antivirus programs. To mitigate this, we have detailed suggested antivirus exclusions you can implement. Refer to Nomad post-installation tasks. |
Content Distribution client
The 1E Client (with Content Distribution enabled) must be installed on client devices and Configuration Manager Distribution Points.
|
Category |
Product |
Notes |
|---|---|---|
|
Windows OS |
|
For installation guidance on Windows refer to Deploying 1E Client on Windows. |
|
Runtime libraries |
|
.NET Framework is required only for the following features of 1E Client:
|
|
Other Windows Software |
|
1E Client installer includes the redistributable package for Visual C++ 2013. 1E Client provides client features. It also includes the Content Distribution client module which replaces the legacy branch client. 1E client features can optionally use Content Distribution to download content (feature enabled by default) if the Content Distribution client module in is enabled (module disabled by default) or Content Distribution Branch 7.0 or later is running. PowerShell is not a prerequisite for the installation of the 1E Client. PowerShell is used by some 1E instructions (that have PowerShell commands embedded or scripts that are downloaded) and some of these require PowerShell 3.0 or later. Rrefer to Downloading client content and Content Distribution integration. |
|
Microsoft Endpoint Manager Configuration Manager Client |
|
1E maintains a testing cycle for our products relative to the Current Branch release cycle. Refer to Support for Microsoft Rapid-Release Cycle in the Support Portal for the latest information on future releases of CM Current Branch, and any advisories related to these releases. If IIS filtering is enabled on Distribution Points, you may encounter problems during downloads if certain types of content are present in the download. Refer to IIS Request Filtering. (Microsoft Endpoint Configuration Manager is also known as Configuration Manager, ConfigMgr, Config Man, CM and SCCM among other names. Version names include 2012 and Current Branch or CB.) |
|
Antivirus |
Content Distribution is able to work with Antivirus systems provided they have certain exclusions configured. |
It is likely that 1E performance will be impaired by antivirus programs. To mitigate this, we have detailed suggested antivirus exclusions you can implement. Refer to Nomad post-installation tasks. |
PXE Everywhere
The table below lists all the platforms supported by PXE Everywhere and the software required to allow PXE Everywhere Central and Responders to be installed or to work. Refer to Common client requirements for details of the PXE Everywhere Agent module of the 1E Client.
|
Category |
PXE Everywhere Central |
PXE Everywhere Responder |
Notes |
|---|---|---|---|
|
Windows OS |
|
|
Will only install on computers running one of these operating systems. Installing PXE Everywhere Central on domain controllers is not a supported configuration. A server operating system is recommended for PXE Everywhere Responder. |
|
Web servers |
|
Not applicable. |
For PXE Everywhere Central:
|
|
Runtime libraries |
|
Visual C++ 2013 Redistributable |
|
|
Boot Image OS |
|
Not applicable. |
UpdateBootImage.exe is supported only on these client operating systems. The Admin Tools feature of the PXE Everywhere Central installer installs UpdateBootImage.exe, which uses the native Configuration Manager API used to generate boot media. |
|
Configuration Manager |
|
Not applicable. |
You can install PXE Everywhere Central on a Configuration Manager site server, or on any other server with IIS installed and good connectivity to the Configuration Manager database, ideally equivalent to the connection the site server has to its database. |
Certificate limitations
Expired root certificates
Ensure that your Root CA Certificates are up-to-date on clients and servers. The Automatic Root Certificates Update feature is enabled by default, but its configuration may have been changed or restricted by Group Policy Turn off Automatic Root Certificates Update.
If this GPO is enabled, then you will see DisableRootAutoUpdate = 1 (dword) in HKLM\Software\Policies\Microsoft\SystemCertificates\AuthRoot.
Signing certificates missing
On Windows computers, the installation MSI files, and binary executable and DLL files of 1E software are digitally signed. The 1E code signing certificate uses a timestamping certificate as its countersignature. 1E occasionally changes its code signing certificate, and uses it for new releases and patches for older versions, as shown in the table(s) below.
Root Certificate Authorities are implicitly trusted to validate certificates, and their certificates must be correctly installed to do this. Your computers should already have the necessary root CA certificates installed, however this may have been prevented by your organization's security policies, or inability to connect to the Internet, or they are legacy operating systems. In general this is not an issue because by default Windows allows software to be installed and run without validation, although you may see a warning or experience a delay. However, you must have relevant CA certificates installed if you are using 1E Client (which self-validates its own files), or your organization has applied more secure polices (for example UAC, AppLocker or SmartScreen).
Typical reasons for issues with signing certificate are:
-
If your organization has disabled Automatic Root Certificates Update then you must ensure the relevant root CA certificates are correctly installed on each computer.
-
If computers do not have access to the Internet then you must ensure the relevant root and issuing CA certificates are correctly installed on each computer, numbered in the table(s) below.
The signature algorithm of the 1E code signing certificate is SHA256RSA. In most cases, the file digest algorithm of an authenticode signature is SHA256, and the countersignature is a RFC3161 compliant timestamp. The exception is on legacy operating systems (Windows XP, Vista, Server 2003 and Server 2008) which require the file digest algorithm of an authenticode signature to be SHA1, and a legacy countersignature.
Client Deployment Assistant
A list of prerequisites and dependencies you need to meet in order to run the Client Deployment Assistant, and eventually install each of the 1E Client/agents.
|
Category |
Product |
Notes |
|---|---|---|
|
Client OS |
|
CDA can be run on these OS. |
|
Runtime libraries |
|
CDA requires one of these versions of .NET Framework. |
|
Configuration Manager |
|
CDA optionally supports these versions of Microsoft Systems Center Configuration Manager. |
|
Other |
|
Refer to:
|
1E Client
For prerequisites and dependencies that are common to all client features and modules of the 1E Client, refer to Common client requirements.
Some real-time client features of 1E Client are also supported on non-Windows platforms, however, the Client Deployment Assistant does not support using Configuration Manager to deploy 1E Client to non-Windows computers. Instead, refer to Installation account for Windows.
1E NightWatchman Agent
The following are required in order to install 1E NightWatchman Agent on client computers. NightWatchman is also supported on macOS, however the 1E Client Deployment Assistant does not support using Configuration Manager to deploy NightWatchman Agent to non-Windows computers.
|
Category |
Product |
Notes |
|---|---|---|
|
OS |
|
Installs on these OS. 1E NightWatchman Agent does not install on server OS. CDA only creates deployment types for workstations which can be fine-tuned. Does not require .NET Framework. |
|
Configuration Manager |
|
1E NightWatchman Agent feature MonitorJobs works with these versions of Configuration Manager. |
Constraints of legacy OS
1E does not provide support for 1E products on the following operating systems unless the operating system is explicitly listed as being supported for a specific 1E product or product feature. This is because Microsoft has ended mainstream support for these operating systems or they are not significantly used by business organizations.
For Microsoft product lifecycle details, refer to Search Product and Services Lifecycle Information. For details of which Current Branch versions are supported by 1E products, and known issues regarding specific versions, refer to Support for Microsoft Rapid-Release Cycle.
-
Windows XP
-
Windows Vista
-
Windows 7
-
Windows 8.0
-
Windows 8.1
-
Windows Server 2003
-
Windows Server 2008
-
Windows Server 2008 R2
-
Windows Server 2012
-
Windows Server 2012 R2
-
Windows Server 2016
1E Client 24.5 and later will not install on Windows XP and Windows Server 2003. Contact 1E if you intend to continue using any of the other legacy OS. If you experience an issue, then please try replicating the issue on a supported OS.