Common client requirements
Prerequisites and dependencies that are common to all client features and modules of the 1E Client.
Tip
1E Client contains client features and modules for 1E, Shopping/WSA, WakeUp, Content Distribution and PXE Everywhere clients. You can optionally enable and configure clients during and after installation.
Installation account for Windows
The 1E Client installer installs a service as local system, therefore the installation account for Windows clients must be capable of being elevated in order to run the installer. The simplest way of achieving this is for the account to have full local administrator rights (as a member of the localgroup administrators, either directly or indirectly).
Installation account for non-Windows
To install the 1E Client on a non-Windows client the installation account must have privileges to run the sudo command.
1E Client supports only 1E platform client features on non-Windows devices.
Supported Platforms
A list of all the platforms supported by 1E Client, and the software required to allow 1E Client to be installed or to work.
Windows client
Category | Product | Notes |
|---|---|---|
| The zip for 1E Client for Windows is available for download from the support.1e.com/. 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. NoteThis list shows only those OS versions in mainstream support by Microsoft, and therefore supported by 1E, and by 1E Client . Please refer to Constraints of Legacy OS regarding the end of mainstream support. For Microsoft product lifecycle details, please refer to https://support.microsoft.com/en-us/lifecycle/search. Refer to Support for Microsoft Rapid-Release Cycle on https://support.1e.com/ for details of which Current Branch versions are supported by 1E products, and known issues regarding specific versions. For installation guidance on Windows, please refer to Deploying 1E Client on Windows. The following 1E Client features and modules are supported on Windows OS:
| |
| .NET Framework is required only for the following features of 1E Client:
NoteThis list shows only those .NET Framework versions in mainstream support by Microsoft, and therefore supported by 1E, and by 1E Client . For Microsoft product lifecycle details, please refer to https://support.microsoft.com/en-us/lifecycle/search. 1E Client installer includes the Visual C++ 2015-2019 Redistributable package. | |
| 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. For more details please refer to Content Distribution client requirements. 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. For useful information about PowerShell versions please refer to ???. | |
| 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, CD, WakeUp, and Application Migration have Configuration Manager Console extensions which are available separately. NoteThis list shows only those Configuration Manager versions in mainstream support by Microsoft, and therefore supported by 1E, and by 1E Client . For Microsoft product lifecycle details, please refer to https://support.microsoft.com/en-us/lifecycle/search. Please refer to the Support for the Microsoft Rapid-Release Cycle on https://support.1e.com/ for details of which Current Branch versions are supported by 1E products, and known issues regarding specific versions. (Microsoft Endpoint Configuration Manager - MECM - is also known as Configuration Manager, ConfigMgr, Config Man, CM, and SCCM among other names. Version names include 2012 and Current Branch or CB.) |
macOS clients
Category | Product | Notes |
|---|---|---|
| Other versions of these non-Windows OS should work but have not been tested by 1E. 1E Client package for macOS is included in the non-Windows zip available for download from the support.1e.com/. For installation guidance, please refer to Deploying 1E Client on macOS. | |
| 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. Therefore, 1E recommends testing custom Bash scripts on each supported OS. |
Linux clients
Category | Product | Notes |
|---|---|---|
| Other versions of these non-Windows OS should work but have not been tested by 1E.
| |
| 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. Therefore, 1E recommends testing custom Bash scripts on each supported OS. |
Solaris clients
Category | Product | Notes |
|---|---|---|
| Note1E Client is no longer available for Solaris, but 1E may reintroduce it, if there is sufficient demand. |
Feature dependencies
Products and Features with dependencies on the 1E Client.
Supported versions of 1E companion products with features that depend on 1E Client .
Products and features that depend on 1E Client | Supported versions of companion products | |
|---|---|---|
1E | 1E requires the 1E Client (with 1E Client platform features enabled) to be installed on all client computers. This replaces the legacy Tachyon Agent. 1E platform features:
# not supported on non-Windows, ## partially supported on non-Windows Clients can optionally use the Content Distribution client module of 1E Client to more efficiently download content. |
|
Content Distribution | Content Distribution requires the 1E Client (with Content Distribution client module enabled) to be installed on all client computers, and on Distribution Points if Configuration Manager is used. |
|
Content Distribution | Content Distribution Download Pause is an optional feature of Content Distribution. It requires the 1E Client (with Content Distribution client module enabled) to be installed on all client computers, and a 1E server infrastructure. |
|
PXE Everywhere | PXE Everywhere requires the 1E Client (with PXE Everywhere Agent client module enabled) to be installed on all client computers. |
|
Shopping | Shopping requires the 1E Client (with Shopping client module enabled) to be installed on all client computers. This replaces the legacy Shopping Agent. |
|
Shopping | Windows Servicing Assistant (WSA) is an optional feature of Shopping that supports OS Deployment. Please refer to Shopping 6.1 - Preparation: Windows Servicing Assistant (WSA) for WSA features in different versions of 1E Client. |
|
WakeUp | WakeUp requires the 1E Client (with WakeUp client module enabled) to be installed on all client computers, and WakeUp Servers. This replaces the WakeUp component of the 1E Agent. |
|
Supported versions of 1E companion products that 1E Client features depend on.
Products and features that 1E Client depends on | Supported versions of companion products | |
|---|---|---|
1E | 1E real-time and other features require a full 1E infrastructure including a 1E Server and a 1E license. |
|
Content Distribution | 1E platform clients can optionally use Content Distribution (1E Client with Content Distribution client features enabled) to provide more efficient downloading of content. |
|
Firewall ports
1E does not provide a combined diagram showing all components and features. Please refer to the communications reference page for each product:
1E platform Communication Ports.
Content Distribution Communication ports — Diagrams and tables with lists of all the Content Distribution communication ports.
PXE Everywhere communication ports — A list of communication ports used by PXE Everywhere. Useful, if needed, for network and device firewalls.
Shopping communication ports — A diagram and a table with a list of all the Shopping communication ports.
NightWatchman Enterprise communication ports — Tables with lists of all the NightWatchman Enterprise components and their communication ports.
Anti-Virus and Malware
The following should be excluded from scans to prevent file locking and resource deletion.
1E log files. See Log files.
The 1E Client temporary directory. We recommend modifying the TemporaryDirectory 1E Client configuration setting to %programdata%\1E\Client\Temp and excluding that directory. See 1E Client settings.
Note
TemporaryDirectory must be specified as an absolute path. The directory is not automatically created by 1E Client. It must be created before being set otherwise 1E Client will use its default.
Digital signing certificates
On Windows computers, the installation MSIs, executables and DLLs of the 1E software are digitally signed by 1E using the 1E Limited SHA1 and SHA256 signature certificates.
These signing certificates are issued by the Symantec Class 3 SHA256 Code Signing CA, which in turn is issued by the root CA VeriSign Class 3 Public Primary Certification Authority - G5.
The SHA1 and SHA256 signature certificates are each countersigned with the same Timestamp signature certificate Starfield Timestamp Authority - G2, itself issued by Starfield Secure Certificate Authority - G2, in turn issued by the root CA Starfield Root Certificate Authority – G2.
The root CA certificates (for signing and countersigning) must exist in the Third-Party Root Certification Authorities store (which is replicated in the Trusted Root Certification Authorities store). These root CA certificates are normally automatically provided by Microsoft's Update Root Certificates feature, however for legacy OS computers in a lab environment that are not connected to the Internet, see Common client requirements.
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. For details, refer to Supported Platforms