1E 8.1 (on-premises)

Enable Tachyon

Check this box to enable Tachyon.

Switch

Sets the name and port of the server where the Tachyon Switch is located. The default port is 4000.

If Tachyon and Nomad client features are not required then the connection to Tachyon platform is not required, and both Switch and BackgroundChannelUrl settings must be set to none when doing a non-interactive (silent/quiet) install using installer properties on a command-line or in a MST transform file. When doing an interactive install then you must uncheck the Enable Tachyon checkbox.

Client features are not required if the 1E Client is being installed only to support PXE Everwhere, Shopping, or WakeUp. They are only required for Nomad if using Nomad features of the Tachyon platform.

To connect to the Tachyon platform then Switch will have one or more entries in the format:

Switch=<SwitchName>:<SwitchPort>

<SwitchName> is the DNS Name FQDN for one or more Switches. This is the same as the following except in a custom configuration where the Switch is installed on its own:

<SwitchPort> is the Port number, which has default value of 4000. Any other port number is used only in a complex configuration if advised by 1E.

In systems where there are multiple DNS Names, there will be multiple entries using a semi-colon (;) as the delimiter between entries. For example:

Switch=tachyon.acme.local:4000;tachyon.acme.com:4000

Background Channel URL

Sets the fully qualified URL that the 1E Client will use to connect to the Tachyon background channel used to transfer large content. If the Tachyon server has been installed to use a custom port for the background channel, the port number must be specified in the URL, for example https://tachyon.acme.local:8443/Background.

If Tachyon and Nomad client features are not required then the connection to Tachyon platform is not required, and both Switch and BackgroundChannelUrl settings must be set to none when doing a non-interactive (silent/quiet) install using installer properties on a command-line or in a MST transform file. When doing an interactive install then you must uncheck the Enable Tachyon checkbox.

Client features are not required if the 1E Client is being installed only to support PXE Everwhere, Shopping, or WakeUp. They are only required for Nomad if using Nomad features of the Tachyon platform.

To connect to the platform then BackgroundChannelUrl will have one or more entries in the format:

BackgroundChannelUrl=https://<BackgroundChannelServer>:<BackgroundChannelPort>/Background/

<BackgroundChannelServer> is the DNS Name FQDN of the server, which is the same as the:

<BackgroundChannelPort> is the Port number, which is the same as:

In systems with multiple server and multiple DNS Names, there will be multiple entries on one line using a semi-colon (;) as the delimiter between entries. For example:

BackgroundChannelUrl=https://tachyon.acme.local:443/Background/;https://tachyon.acme.com:443/Background/

Default Stagger Range Seconds

Sets the scope for the random delay used by the 1E Client to prevent overburdening the Tachyon Background Channel.

Some operations (including HTTPS downloads from the BackgroundChannel) are randomly time-staggered across Tachyon platform clients. This property dictates the upper-limit on the default randomization period in seconds.

Range is 0 to 3600. Default is 300.

Use 0 to instruct Tachyon platform client not stagger operations by default.

Enable Nomad

Check this box to enable Nomad.

Nomad is used to support efficient content download for Configuration Manager and Tachyon. For Tachyon, its Nomad content download feature is enabled by default but only used if Nomad is enabled.

Enable 1E Platform features

Check this box to let you configure the Single-Site Download (SSD) options and WakeUp integration.

If you need to enable reporting but prevent the Nomad client from acting as an SSD provider, then use installer properties or mst transform files to configure MODULE.NOMAD.SSDENABLED and MODULE.NOMAD.CONTENTREGISTRATION.

For more information about SSD, please refer to Single Site Download.

Use FIPS encryption

Checking to Use FIPS Encryption configures the Nomad module to use FIPS-encrypted encrypted communications.

You must ensure that Nomad is configured with the same FIPS encryption setting on all your 1E Client.

Enable PXE Everywhere

Check this box to enable PXE Everywhere Agent client module.

Other fields are only enabled if this checkbox is checked.

PXE Everywhere Central URL

URL for the PXE Everywhere Central web service in the format: http://SERVER/PXELite/PXELiteConfiguration.asmx

where <SERVER> is the name of the server (or FQDN) where the PXE Everywhere Central web service is installed.

Use FIPS Encryption

Checking to Use FIPS Encryption configures the PXE Everywhere Agent module to use FIPS encrypted communications.

You must ensure that PXE Everywhere is configured with the same FIPS encryption setting on all your 1E Client.

Enable DHCP Snooping support

Enable this option if your network uses DHCP Snooping. You will also need to implement one or more PXE Everywhere Responders as described in Design Considerations.

Enable Shopping and WSA

Check this box to enable Shopping Integration and the Windows Servicing Assistant.

Shopping must be enabled so that users of a computer can use the 1E Shopping self-service portal, the Windows Servicing Assistant, and the 1E Virtual Assistant.

Shopping Web Site URL

This field is only enabled if the Enable Shopping and WSA checkbox is checked.

Example: https://shopping.acme.local/Shopping

This is the URL of the Shopping Central website, comprising:

The URL is not verified by the installer, so you will need to ensure that the correct URL is entered.

Enable loopback for Edge and Windows App browsers

Enable this option if users will connect to the Shopping website using Edge or other Metro-style browsers.

When users connect to the Shopping Portal, the website needs to get the latest details about the local computer. Shopping may already have details from the Configuration Manager database, but these need to be confirmed and updated.

Browser standards only allow websites to get limited information about the user and computer, therefore the website needs to make loopback calls to the local computer via the Shopping client. The following browsers permit loopback calls by default:

If your Shopping users are using Edge and Metro Internet Explorer browsers, you must enable a Loopback Exemption to allow these browsers to make loopback calls. Exemption affects the browser as a whole and is not just restricted to the Shopping website. Before enabling this option, check your corporate security policy and be aware of the implications of allowing access between browsers and the local machine. By enabling loopback, you are only setting the Edge/Metro Internet Explorer browsers to the same level of security as other browsers which allow this setting already.

If you are running an unattended install, you can use MODULE.SHOPPING.LOOPBACKEXEMPTIONENABLED for all OS but it only works on Windows 8, 8.1, 10 and Windows Server 2012 R2 and later.

Shopping client only allows inbound connections to localhost (127.0.0.1) which prevents remote access.

Enable WakeUp

Check this box to enable WakeUp integration. WakeUp integration is required to enable 1E WakeUp capabilities on this device.

Use FIPS encryption

Checking Use FIPS Encryption configures the WakeUp module to use FIPS encrypted communications.

You must ensure that the NightWatchman Management Center, WakeUp Server and 1E NightWatchman Agent components are all set to the same option.

Enable HTTP reporting

Check this box if the NightWatchman Management Center Web Service is configured to use HTTP and you want communications from the WakeUp module to use HTTP. Do not use this option when installing on a WakeUp Server.

When checked you must set the DNS Name FQDN for the server hosting the NightWatchman Management Center Web Service in the edit field provided.

Enable HTTPS reporting

Check this box if the NightWatchman Management Center Web Service is configured to use HTTPS and you want communications from the WakeUp module to use HTTPS. Do not use this option when installing on a WakeUp Server.

When checked you must set the DNS Name FQDN for the server hosting the NightWatchman Management Center Web Service in the edit field provided.

Use client certificate (from local certificate store) for HTTPS reporting

This checkbox is only enabled when the Enable HTTPS reporting checkbox is checked. You will need to check this option if the NightWatchman Management Center Web Service has been configured to request a client certificate.

The certificate is retrieved from the local certificate store and is found by providing a certificate issuer or certificate subject search text. The first certificate found that matches the text will be used to authenticate the client with the NightWatchman Management Center Web Service.

Match Certificate Issuer

This option is only enabled when the Use client certificate for HTTPS reporting checkbox is checked.

When selected this option sets the search in the local certificate store to match against the certificate issuer field of the certificate.

Match Certificate Subject

This option is only enabled when the Use client certificate for HTTPS reporting checkbox is checked.

When selected this option sets the search in the local certificate store to match against the certificate subject field of the certificate.

Search Text

This option is only enabled when the Use client certificate for HTTPS reporting checkbox is checked.

When enabled this edit field should be set to the search text used to locate and retrieve the client certificate from the local certificate store. This will be matched against either the certificate issuer or the certificate subject, depending on which option has been selected above.

Sets the installation folder.

This value is not stored in the 1E Client configuration file.

This value is stored as InstallationDirectory in the Windows registry under HKLM\SOFTWARE\1E\Client\ and must not be changed.

Some client modules that run on Windows store their registry settings under their own keys in HKLM\SOFTWARE\1E.

If Tachyon platform and Nomad client features are not required then the connection to Tachyon Platform is not required, and both Switch and BackgroundChannelUrl settings must be set to none when doing a non-interactive (silent/quiet) install using installer properties on a command-line or in a MST transform file. When doing an interactive install then you must uncheck the Enable Tachyon checkbox.

Tachyon client features are not required if the 1E Client is being installed only to support PXE Everwhere, Shopping, or WakeUp. They are only required for Nomad if using Nomad features of the Tachyon platform.

To connect to the Tachyon platform then BackgroundChannelUrl will have one or more entries in the format:

BackgroundChannelUrl=https://<BackgroundChannelServer>:<BackgroundChannelPort>/Background/

<BackgroundChannelServer> is the DNS Name FQDN of the server, which is the same as:

<BackgroundChannelPort> is the Port number, which is the same as:

In systems with multiple server and multiple DNS Names, there will be multiple entries on one line using a semi-colon (;) as the delimiter between entries. For example:

BackgroundChannelUrl=https://tachyon.acme.local:443/Background/;https://tachyon.acme.com:443/Background/

If Tachyon and Nomad client features are not required then the connection to Tachyon platform is not required, and both Switch and BackgroundChannelUrl settings must be set to none when doing a non-interactive (silent/quiet) install using installer properties on a command-line or in a MST transform file. When doing an interactive install then you must uncheck the Enable Tachyon checkbox.

Tachyon platform client features are not required if the 1E Client is being installed only to support PXE Everwhere, Shopping, or WakeUp. They are only required for Nomad if using Nomad features of the platform.

To connect to the Tachyon platform then Switch will have one or more entries in the format:

Switch=<SwitchName>:<SwitchPort>

<SwitchName> is the DNS Name FQDN for one or more Switches. This is the same as the following except in a custom configuration where the Switch is installed on its own:

<SwitchPort> is the Port number, which has default value of 4000. Any other port number is used only in a complex configuration if advised by 1E.

In systems where there are multiple DNS Names, there will be multiple entries using a semi-colon (;) as the delimiter between entries. For example:

Switch=tachyon.acme.local:4000;tachyon.acme.com:4000

Some operations (including HTTPS downloads from the BackgroundChannel) are randomly time-staggered across Tachyon clients. This property dictates the upper limit on the default randomization period in seconds.

Range is 0 to 3600. Default is 300.

Use 0 to instruct Tachyon client not stagger operations by default.

Nomad is used to support efficient content download for Configuration Manager and Tachyon. For Tachyon, the Nomad content download feature is enabled by default.

This installer property is no longer supported. The Nomad installer determines the location of servers from the platform client. Specifically, it communicates with Response Stack Switches and Background Channel.

Set to 1 to enable the Nomad client to act as a content provider across subnets when using Single Site Download.

Set to 1 to enable Single-site download, which requires Tachyon platform with Nomad.

If you enable both Single-Site Download and Content Registration then Nomad will make its own content available to other Nomad peers.

If you enable Single-Site Download but not Content Registration then Nomad will be able to fetch downloads from registered peers on other subnets but will not make its own content available.

Set to 1 to enable WakeUp integration, which requires an ActiveEfficiency Server.

If you enable WakeUp integration but not Single Site Download, any attempt to wake-up peers with particular content will only be on the local subnet. If Single Site Download is also checked, Nomad will try to wake peers with particular content in neighboring subnets on the site if peers on the local subnet do not wake.

Set to 1 to configure the Nomad module to use FIPS encrypted communications.

You must ensure that Nomad is configured with the same FIPS encryption setting on all your 1E Client.

Set this property to true to enable the PXE Everywhere Agent client module. The default value is false.

URL for the PXE Everywhere Central web service in the format: http://SERVER/PXELite/PXELiteConfiguration.asmx

where <SERVER> is the name of the server (or FQDN) where the PXE Everywhere Central web service is installed.

You must use the same FIPS encryption setting on all PXE Everywhere Agents.

Use of FIPS compliant encryption for communications.

This installer property is set to 2067 if Enable DHCP Snooping support is checked during an interactive installation of the 1E Client installer.

This is the UDP port on which the PXE Everywhere Agent will listen for PXE requests.

If DHCP Snooping is not being used, then this port must be 67 (default), and you do not need to install Responders.

When manually installing the PXE Everywhere Agent, if the DHCP Snooping option is enabled in the installer UI, the default port is changed from 67 (43 hex) to 2067 (813 hex). If the MODULE.PXEEVERYWHERE.DHCPPORT installer property is used to specify a port other than 67, the installer UI assumes the DHCP Snooping option is enabled.

If DHCP Snooping is being used, then DhcpPort on Agents must be the same value as AltPxeServerPort on Responders. The default value of AltPxeServerPort is 2067. If a value other than 2067 is specified as a custom port number on Agents, you will also need to manually create the AltPxeServerPort (and AltPxeClientPort) registry values on Responders, refer to AltPxeClientPort.

Shopping must be enabled so that users of a computer can use the 1E Shopping self-service portal, the Windows Servicing Assistant, and the 1E Virtual Assistant.

Example: https://shopping.acme.local/Shopping

This is the URL of the Shopping Central website, comprising:

Optional. Default value is false. Set this value to true if users are likely to use Microsoft Edge or other Metro browsers to access the Shopping website.

The Shopping client requests this value from the Shopping Central website (admin console setting: Loopback exemption enabled). If the client fails to connect to the website, it defaults to using this local setting and retries later.

Set this property to true to enable the WakeUp client module. The default value is false.

Enabling this will also cause any installation of the 1E Agent's WakeUp component to be uninstalled the first time the 1E Client is started, leaving the NightWatchman component if that was installed.

Set to 1 to force the WakeUp agent to use a FIPS-compliant algorithm for:

If enabled, then all components in the NightWatchman and WakeUp system must have FIPS enabled.

EncryptionLevel and FIPS settings used by WakeUp do not affect other 1E Client communications.

Enables WakeUp reporting. Sets whether the Agent sends reporting messages to the NightWatchman Management Center Web Service. May be set to one of the following values:

Set this parameter to the FQDN (recommended) or NetBIOS name of the server hosting the NightWatchman Management Center Web Service.

Set this parameter to the FQDN (required) or NetBIOS name of the server where the NightWatchman Management Center Web Service component secure site has been installed.

Specify the text used to search for a client certificate in the client certificate store.

Either MODULE.WAKEUP.CERTISSUER or MODULE.WAKEUP.CERTSUBJECT is mandatory when all the following are true:

If this property is used, it will use the first certificate it finds where the specified text matches the certificate's Issuer CN.

Specify the text used to search for a client certificate in the client certificate store.

Either MODULE.WAKEUP.CERTISSUER or MODULE.WAKEUP.CERTSUBJECT is mandatory when all the following are true:

If this property is used, it will use the first certificate it finds where the specified text matches the certificate's Subject CN.

Installation folder

None.

Logs folder

Log files remain.

Please refer to Log files for log file locations of 1E Client and its client modules.

The log files can be deleted or renamed. If not deleted, then a new installation that uses the same logs folder will continue to use the old log file.

Client\Persist folder remains.

Leave this folder which contains status information about current instructions.

The Persist folder should be deleted only if you do not intend re-installing the 1E Client with Tachyon enabled, or when preparing OS images, refer to Sysprep and OS images for details.

Tachyon client registry

HKLM\SOFTWARE\1E\Client\Persist

This registry exists if the Tachyon platform client feature of the 1E Client is enabled.

It is used to keep a record of hash values for its persistent storage files, which includes status information about current instructions.

This registry key should be deleted only if you do not intend re-installing the 1E Client with Tachyon enabled, or when preparing OS images, refer to Sysprep and OS images for details.

Nomad Cache

%ALLUSERSPROFILE%\1E\NomadBranch

The folder should be deleted only if you do not intend re-installing the 1E Client with Nomad enabled.

Downloaded content is retained so that if the Nomad client is re-enabled it will be scanned and re-registered, to make it available for peer sharing with other Nomad clients.