1E Client requirements
You can plan the deployment of 1E Client using the software deployment tools you choose. In addition the Client Deployment Assistant provides a wizard that simplifies deployment of 1E Client for Windows. It also integrates with Configuration Manager to create deployments. Refer to Client Deployment Assistant.
-
For more information about configuring the 1E Client properties during and after installation, refer to 1E Client configuration settings and installer properties.
-
For details of interactive and command-line installation, refer to Deploying 1E Client.
-
1E, Content Distribution, and Shopping require client certificates, refer to Certificate requirements.
Installation accounts
1E Client Windows installation account
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).
1E Client non-Windows installation account
To install the 1E Client on a non-Windows client the installation account must have privileges to run the sudo command.
Supported device platforms
Refer to Common client requirementsand Constraints of legacy operating systems, which applies to server and client OS.
Scripting requirements
You must ensure the appropriate scripting environment is present on client devices. DEXCode supports running native PowerShell on Windows and bash on non-Windows devices, which can be script files downloaded when an instruction runs, or command text.
-
Windows 1E clients can use PowerShell scripts. Ensure your client devices have an appropriate version of PowerShell installed to support any custom scripts you may develop. Refer to PowerShell on Windows OS.
-
Non-Windows clients use bash as their scripting medium. This should be present on all non-Windows 1E Client devices. Refer to Bash on non-Windows OS.
PowerShell on Windows OS
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, although some scripts will support PowerShell 2.0. PowerShell scripts are supported only on Windows OS.
If installing or upgrading PowerShell, it is best to install the latest version available. However, do not expect full forward or backward compatibility between PowerShell versions.
To determine the version of PowerShell on a computer, start PowerShell (command prompt or ISE) and enter one of the following commands: $PSVersionTable.PSVersion or $PSVersionTable for more detail.
The table below shows which versions of PowerShell are supported on each OS version and Service Pack, and if it is built-in or needs to be installed.
|
OS Version |
PowerShell Version |
Notes |
|
|
|
|
|
|---|---|---|---|---|---|---|---|
|
Windows Server 2022 |
|
|
|
|
|
RTM (Notes 3,4) |
Note 1 |
|
Windows 11 |
|
|
|
|
|
RTM (built-in) |
|
|
Windows Server 2016, 2019, 2022 |
|
|
|
|
RTM (Note 2) |
RTM (Notes 3,4) |
Note 1 |
|
Windows 10 |
|
|
|
|
RTM (built-in) |
Anniversary Update (built-in) |
|
-
PowerShell is not installed by default on these OS but is an optional feature that should be enabled using Server Manager.
-
PowerShell 5.0 is part of WMF 5.0 without any other prerequisites. Refer to https://www.microsoft.com/en-us/download/details.aspx?id=50395.
-
PowerShell 5.1 is part of WMF 5.1 with prerequisite of .NET Framework 4.6 or later. Refer to https://www.microsoft.com/en-us/download/details.aspx?id=54616.
-
In these Server OS, PowerShell 5.1 is referred to as the Desktop Experience. You can use the PowerShell Core version if you prefer.
Please refer to https://support.microsoft.com/en-gb/help/17455/lifecycle-faq-net-framework for details of Microsoft support for .NET Framework.
-
Support for 4, 4.5, and 4.5.1 ended on January 12, 2016.
-
Support for 4.5.2, 4.6 and 4.6.1 ended on April 26, 2022.
Bash on non-Windows OS
Bash and perl are required for installation of all non-Windows 1E Client.
-
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 the Scripting.Run method. 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.