Deploying 1E Client on Windows

Multi-tenant SaaS platform Green checkmark | Single-tenant SaaS platform Green checkmark | On-premises platform Green checkmark

Guidance for deploying 1E Client onto Windows computers, including installation and uninstallation.

The 1E Client certificate auto-provision feature is not currently available as part of the interactive installation.

Requirements

1E Client does not have a license key. Even so, you must adhere to the terms of your license agreement.

Deployment choices

You must decide how you will configure the 1E Client and deploy to devices.

  • Use your existing software deployment tool: For example, Microsoft System Center Configuration Manager. Some organizations may require the 1E Client to be packaged prior to deployment.

  • Client Deployment Assistant: Designed to help install Windows versions of 1E Client and other 1E agents using Configuration Manager. It includes template transform files for each combination of client and agent for 32-bit and 64-bit platforms, and automatically creates collections and deployments in Configuration Manager, so that you only need to populate the collections. Refer to Client Deployment Assistant

For more information about configuring 1E Client properties during and after installation, refer to 1E Client configuration settings and installer properties.

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).

Preparation

1E Client installation files are available for download from the 1E Support Portal.

1E Client should be installed on all Windows clients. You must use the correct installer file according to the Windows architecture of the device.

Ensure you allow for a reboot, especially for mission-critical servers. After installing the 1E Client, the computer may request a reboot that appears to be caused by 1E Client, but is actually caused by a pending reboot from a previous software or patch installation.

Pending reboots and notifications can occur up to several hours after installation, depending on policies in your organization, such as Computer Restart settings for Configuration Manager clients.