1E 8.1 (on-premises)

Tachyon Platform

Tachyon and other client settings

Nomad client settings

If you intend to use Tachyon, the Tachyon client screen in the CDA wizard requires details of the Tachyon Switch and Background Channel. These are normally installed on a single Tachyon server and therefore use the same DNS Name. Large environments (over 50,000) may have a Tachyon Master Stack server and one or more separate Response Stack servers. These may share the same DNS Name or have different DNS Names. The names required by the Tachyon client screen will depend on the design of your Tachyon system.

The Tachyon Master Stack server requires a license obtained from 1E, but details of this are not required by the CDA wizard.

For 1E Client 5.2 onwards, Nomad client uses the Content Distribution feature of Tachyon platform, which replaces ActiveEfficiency Server used by earlier versions of Nomad client. You must enable the client if you want Nomad to use any of the following Nomad features.

Although not a requirement for generally using Nomad, Tachyon platform must be installed and available before you can use certain Nomad features.

The following Nomad features use Content Distribution and require Tachyon platform and Tachyon features of 1E Client to be enabled:

The following features were provided in versions of Nomad older than 7.1:

Nomad can also be used to provide content distribution features for clients, as well as Configuration Manager.

PXE Everywhere Central

PXE Everywhere settings

The CDA wizard requires the URL of the PXE Everywhere Central web service when deploying PXE Everywhere Local client. PXE Everywhere Central is installed on a Configuration Manager Site server, or other Windows server.

NightWatchman Management Center

Tachyon and other client settings

1E NightWatchman Agent settings

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

The CDA wizard requires the name of the NightWatchman web server (specifically the web server hosting the AFWebService).

WakeUp Server

Tachyon and other client settings

If implementing WakeUp, or Nomad integration with WakeUp, then you require a 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.

Ideally, you would install the WakeUp Server before deploying the 1E Client with the WakeUp client module enabled, but that is not a prerequisite for using the CDA wizard.

Shopping Central

Tachyon and other client settings

The CDA wizard requires the URL of the Shopping Central self-service portal when configuring the Shopping client module of the 1E Client. 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 a client reporting to it, and on a CAS if using Shopping for OS Deployment. You can deploy the 1E Client without Tachyon servers or Tachyon license.

If users are using Edge or Metro browsers, then you must enable the loopback feature option in the CDA wizard. 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.

Installation Files Directory

Mandatory

Tells the CDA wizard where to locate the 1E Client source files that you extracted when you unzipped the 1E Client Deployment Assistant (CDA) files. These are used to create Configuration Manager applications and packages.

Create Application

Optional

Determines if an application for the client is created in Configuration Manager.

You must check Create Application and/or Create Package option to enable and click on the Next button.

If this option is not checked, then the CDA Wizard will not copy files and create an MST transform in the Application Content Source specified in the General settings screen.

Create Application Deployment

Optional

Only enabled if you choose Create Application and determine whether a required deployment type for the application is created in Configuration Manager.

Create/Select Device Collection

Mandatory if Create Application Deployment is enabled

The device collection is used to deploy the application. If specified, then the CDA wizard will also create a deployment for the application's deployment types and the specified collection.

A default name is suggested, which you can change. If the name you entered for Create/Select Device Collection does not exist, one is created. You must manually populate the created device collection after running the CDA wizard.

You can click Browse to choose from a list of existing collections that you have access to using Configuration Manager RBAC. If you do this, you will not have the option to associate the device collection with a Limiting Collection.

Limiting Collection

Mandatory if Create Application Deployment is enabled

If you are creating a new device collection, you must also choose an associated Limiting Collection.

This limits administrators to populating the new device collection with devices only from the selected Limiting Collection. By default, this is All Systems, but you can click Browse to choose from a list of existing collections that you have access to using Configuration Manager RBAC.

Create Package

Optional

Determines if a legacy package and associated install and uninstall programs for the client are created in Configuration Manager.

You must check Create Application and/or Create Package options to enable and click on the Next button.

If this option is not checked, then the CDA wizard will not copy files and create an MST transform in the Package Content Source specified in the General settings screen.