Summary

Information that will help you design and plan deployment of 1E Client in your organization. Includes infrastructure dependencies for each 1E product supported by the 1E Client.

Please refer to the relevant 1E product documentation for more detail, links are provided below to relevant documentation spaces.

This page is part of the design phase of implementation.

1E Client is deployed as part of one or more 1E Solutions. You should review documentation for whichever 1E Solutions you are licensed to use, to help you decide which 1E Client features to configure, determined by which server systems are used. 






1E Client deployment

You will need to plan the deployment of 1E Client using whichever software deployment tools you have. For more detail, please refer to: 

CDA is the recommended method of deploying 1E Client on Windows if your organization uses Configuration Manager. It is a wizard that guides you through common settings for clients and deployments, and provides additional options that the installers do not. 


You must use CDA if you are deploying 1E Client with PXE Everywhere and you want to deploy it with the boot image at the same time.


1E Client features and modules

You will need to decide which client features and modules to enable and configure. Unless otherwise stated, modules are only available on Windows computers. Please refer to Supported Platforms for details of supported OS platforms.

All modules including the Tachyon client feature can be optionally enabled during deployment of the 1E Client or after deployment by enabling features in its configuration file.

Feature/moduleDescriptionInfrastructure dependencies
1E Client

This is the main service that determines which features and modules are enabled, including uninstallation of legacy versions of the 1E clients listed below.

Please refer to 1E Client settings for details of configurable options.


Tachyon client

1E Client feature which replaces Tachyon Agent to support Tachyon 4.1 and later but will work with earlier versions of Tachyon Server.

Must be enabled on each end-user device to provide Real-time and Inventory features to support the following Tachyon applications: Explorer, Experience, Guaranteed State, Patch Success, Application Migration, and AppClarity. Also required to support Tachyon integration with NightWatchman and Nomad.

Supports Windows and non-Windows devices.

Please refer to Tachyon client settings for details of configurable options.

Full Tachyon infrastructure including Master and Response Stacks.

See Tachyon infrastructure dependencies below.

Nomad client

1E Client module which replaces the NomadBranch client to support Nomad 7.0 and later, as well as Tachyon clients use of the Nomad content download feature.

Must be enabled on each end-user device to provide bandwidth efficient download of content for Tachyon clients, as well as Configuration Manager clients. It is optionally used by PXE Everywhere.

Please refer to Nomad client settings for details of configurable options.

ActiveEfficiency Server is required for several Nomad features, as described in Nomad infrastructure dependencies below.

PXE Everywhere Agent

1E Client module which replaces the PXE Everywhere Agent to support PXE Everywhere 4.0 and later.

Enabled on as may end-user devices as possible to provide a lightweight PXE service that responds to PXE requests on their local subnet.

Please refer to PXE Everywhere Agent settings for details of configurable options.

PXE Everywhere Central must be installed, as described in PXE Everywhere infrastructure dependencies below. You can also configure PXE Everywhere to support environments that use DHCP Snooping.
Shopping client

Must be enabled on each end-user device to support access to the Shopping web portal, and WSA features to support OS rebuilds and upgrades.

Please refer to Shopping client settings for details of configurable options.

Shopping Central website and Shopping Receiver services are required, as described in Shopping infrastructure dependencies below.
WakeUp client

1E Client module which replaces WakeUp Agent to support WakeUp Server 7.2.500 and later. This version contains hotfixes.

Must be enabled on each end-user device to support Wake-on-LAN and Configuration Manager policy refresh. Also integrates with the 1E NightWatchman Agent.

Please refer to WakeUp client settings for details of configurable options.

WakeUp Servers are required, as described in NightWatchman and WakeUp infrastructure dependencies below.


Upgrading the 1E Client

Upgrading from 1E Client 4.1 or 1E Client 5.0 to 1E Client 5.1 simply requires deploying the new version, using the same or different configuration settings.

If you are upgrading from Tachyon Agent, Shopping Agent, NomadBranch and/or 1E Agent (for NightWatchman and WakeUp) then please refer to Upgrading to 1E Client.

Tachyon infrastructure dependencies

Please refer to Tachyon 5.1 documentation for more details. 

If you intend using Tachyon for its Real-time, Inventory, Patch Success, or Guaranteed State features, then you require at least one Tachyon Server and a Tachyon license.

Organizations with less than 50000 devices will typically have a single-server system with one Tachyon Switch, but there may be reasons why a more complex configuration would be required. Key factors are the location of servers and how devices and users will connect to them.

For more detail about client certificates, please refer to Tachyon client requirements: Client Certificates.

Downloading Tachyon client content and Nomad integration 

 

Nomad infrastructure dependencies

Please refer to Nomad 7.0.200 documentation for more details.

In addition to deploying 1E Client (with Nomad client module enabled) on all computers and on Configuration Manager Distribution Points, the following are also required:

  • Nomad tools installed on Configuration Manager sites and SMS Providers
  • Nomad Configuration Manager Console extensions on Configuration Manager site servers any other computer that has the Configuration Manager Console installed

As explained above, Nomad can be used for downloading content for Tachyon clients, as well as Configuration Manager clients.

PXE Everywhere infrastructure dependencies

PXE Everywhere helps with OS Deployment. The PXE Everywhere Agent is a lightweight PXE service deployed throughout the network, responding to PXE requests on local subnets. Local Agents elect which one will respond to the original PXE request, and communicate with PXE Everywhere Central to determine what to do next, by asking Configuration Manager. If the original PXE client has been assigned a Task Sequence, then the Agent provides the associated boot image to the local PXE client, which can then start the Task Sequence. Boot images will have been previously deployed to Agents, providing the reassurance there will always be a local Agent capable of quickly responding with the relevant boot image. It also means you can deploy a PXE solution without needing to configure routers to support DHCP forwarding to a central PXE server. Please refer to PXE Everywhere 4.0 documentation for more details.

PXE Everywhere does not depend on Nomad but is often used with Nomad, which helps with distribution of PXE boot images via Configuration Manager, which further reduces the impact of network traffic on the WAN.

1E Client Deployment Assistant (CDA) is the recommended method of using Configuration Manager to deploy 1E Client to client computers. CDA is necessary if you want to include a boot image in the same deployment as the 1E Client. 

PXE Everywhere also works in environments that use DHCP Snooping, as described in PXE Everywhere 4.0 - Design Considerations: DHCP Snooping. This requires the following configuration changes:

  • install of one or more PXE Everywhere Responders, typically on server OS in the central network - Responders only communicate with Agents, they do not communicate with the PXE Everywhere Central server or with Configuration Manager 
  • authorize the Responders to respond to PXE requests
  • configure DHCP Relays (IP helpers) on routers to forward DHCP/PXE request packets to the PXE Everywhere Responder(s) in addition to any DHCP Relays you already have configured for the DHCP server(s)
  • configure PXE Everywhere Agents to listen on port 2067 (default) instead of port 67.


Shopping infrastructure dependencies

Please refer to Shopping 6.0 documentation for more details.

Shopping requires an ActiveEfficiency Server, and ActiveEfficiency Scout to import data from Configuration Manager into ActiveEfficiency.

A Shopping solution requires a Shopping Central server on a web server, and a Shopping Receiver installed on each Configuration Manager Site server that has client reporting to it, and on a CAS if using Shopping for OS Deployment.

If users are using Edge or Metro browsers then you must enable the loopback feature. This feature implements a mechanism for passing information between the Shopping client, the browser's secure sandboxed environment and the local machine. This mechanism affects these browsers as a whole and is not just restricted for use by Shopping.

Before enabling the loopback feature, check your security policy on enabling loopback and be aware of the implications of allowing access between browsers and the local machine.



NightWatchman and WakeUp infrastructure dependencies

Please refer to NightWatchman Enterprise 7.3 documentation for more details.

A NightWatchman Management Center server is required if implementing NightWatchman or WakeUp solutions. 

If implementing WakeUp, or Nomad integration with WakeUp, then you require at least one WakeUp Server. If you have Configuration Manager you require a WakeUp Server on each Site server that has clients reporting into it. If you do not have Configuration Manager you require one or more independent WakeUp Servers.

1E NightWatchman Agent is a separately installed client agent, that can optionally be used to help with power management of computers. It is not included in 1E Client, but is included in the 1E Client Deployment Assistant (CDA) which assists with deploying Windows versions of 1E clients via Configuration Manager. When 1E NightWatchman Agent is installed alongside the WakeUp client it will optionally manage the computer returning to its original power state after being woken using 1E WakeUp and the computer is not busy, for example installing patches.

Web WakeUp is an optional server component that is typically installed on the NightWatchman Management Center server. It is a web portal for users and administrators to search for computers to wake. It optionally provides a remote desktop link to the woken computer.

Constraints of Legacy OS