Version: 2
restore

Contents

A list of prerequisites and dependencies you need to meet in order to run the 1E Client Deployment Assistant, and eventually install each of the 1E clients/agents.

1E Client Deployment Assistant 1.5

The following are required in order to run the 1E Client Deployment Assistant.

CategoryProductNotes

OS

  • Windows Server 2019
  • Windows Server 2016
  • Windows 10 CB 2004
  • Windows 10 CB 1909
  • Windows 10 CB 1809
  • Windows 10 CB 1803
  • Windows 10 CB 1709
CDA can be run on these OS.

Runtime libraries

  • .NET Framework 4.8
  • .NET Framework 4.7.2
  • .NET Framework 4.7.1
  • .NET Framework 4.7
CDA requires one of these versions of .NET Framework.

Configuration Manager

  • SCCM CB 2103
  • SCCM CB 2010
  • SCCM CB 2006
  • SCCM CB 2002
  • SCCM CB 1910
  • SCCM CB 1906
  • SCCM CB 1902
  • SCCM CB 1810

CDA requires one of these versions of Microsoft Systems Center Configuration Manager.

Other


Please see:

1E Client

The following are required in order to install 1E Client on client computers. Some are only required for particular client modules and features. The Tachyon client features of 1E Client are also supported on non-Windows platforms, however the 1E Client Deployment Assistant does not support using Configuration Manager to deploy 1E Client to non-Windows computers. Instead, please refer to Common client requirements.

CategoryProductNotes

OS

  • Windows Server 2022
  • Windows Server 2019
  • Windows Server 2016
  • Windows 10 CB 21H2
  • Windows 11 CB 21H2
  • Windows 10 CB 21H1
  • Windows 10 CB 20H2
  • Windows 10 CB 2004
  • Windows 10 CB 1909
  • Windows 10 CB 1903
  • Windows 8.1

CDA only creates deployment types for workstations. The deployment types can be fine-tuned and manually amended to include server OS.

The zip for 1E Client for Windows is available for download from the 1E Support Portal .

Professional and Enterprise editions of Windows 10 are supported.

All versions are provided with 32-bit & 64-installers, and can be installed on physical and virtual computers.

This list is automatically updated to show only those OS versions in mainstream support by Microsoft, and therefore supported by 1E, and by 1E Client 5.1. However the following OS continue to be supported as exceptions to help customers during their migration to the latest OS:

  • Windows Server 2012 R2
  • Windows 7 SP1

Please refer to Constraints of Legacy OS regarding end of mainstream support.

For Microsoft product lifecycle details, please refer to https://support.microsoft.com/en-us/lifecycle/search.

Please refer to https://1eportal.force.com/s/support-for-msft-rapid-release-cycle for details of which Current Branch versions are supported by 1E products, and known issues regarding specific versions.

Runtime libraries

  • .NET Framework 4.8
  • .NET Framework 4.7.2
  • .NET Framework 4.7.1
  • .NET Framework 4.7
  • .NET Framework 4.6.2
  • .NET Framework 4.6.1

.NET Framework is required only for the following features of 1E Client:

  • The 1E Client User Interaction (UI) component of the Interaction module, which supports the notification and survey features
  • Windows Servicing Assiatant (WSA) feature of the Shopping client module, which supports OS deployment, upgrades and migrations

Other Windows Software

  • Visual C++ 2013 Redistributable
  • PowerShell 3.0 (or later)
  • Nomad 7.0 (or later)

Visual C++ 2013 - 1E Client installer includes the redistributable package for Visual C++ 2013.

PowerShell - PowerShell is not a prerequisite for installation of the 1E Client.

PowerShell 3.0 or later (included in Windows 8.0 and later) is required if you are using Tachyon real-time features. Some Tachyon instructions use PowerShell (commands are embedded or scripts are downloaded).

PowerShell 4.0 or later (included in Windows 8.1 and later) is required if you are using Application MigrationThe Application Migration Task Sequence step executes in a Configuration Manager OS deployment task sequence after the new OS is installed. If you are deploying Windows 7 images, upgrade PowerShell in the image or install it using a task sequence step before executing the Application Migration step.

Nomad - 1E Client includes the Nomad client module (disabled by default) which optionally replaces the legacy Nomad Branch client. Tachyon real-time features can optionally use Nomad to download content (feature enabled by default).

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.

CategoryProductNotes

OS

  • Windows 10 CB 21H2
  • Windows 11 CB 21H2
  • Windows 10 CB 21H1
  • Windows 10 CB 20H2
  • Windows 10 CB 2004
  • Windows 10 CB 1909
  • Windows 10 CB 1903
  • Windows 10 CB 1809
  • Windows 10 CB 1803

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

  • SCCM CB 2111
  • SCCM CB 2107
  • SCCM CB 2103
  • SCCM CB 2010
  • SCCM CB 2006
  • SCCM CB 2002
  • SCCM CB 1910
  • SCCM CB 1906
  • SCCM CB 1902
  • SCCM CB 1810

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 OS unless the OS is explicitly listed as being supported for a specific 1E product or product feature. This is because Microsoft has ended mainstream support for these OS or they are not significantly used by business organizations.

  • 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
1E Client 8.1 and later will not install on Windows XP and Windows Server 2003. Please 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.

For Microsoft product lifecycle details, please refer to https://support.microsoft.com/en-us/lifecycle/search.