Understanding how 1E Client settings are managed

1E Client modules are enabled or disabled using the 1E.Client.exe -reconfigure command line interface described in Example command-lines for reconfiguring the 1E Client below. Once enabled, additional configuration is likely to be required.

• All Tachyon and Shopping configuration settings can be modified using the 1E.Client.exe -reconfigure command line interface. 
• All Nomad and most of WakeUp configuration settings are managed in the registry, so must be addressed in addition to enabling the module using the 1E.Client.exe -reconfigure command. 

The table below summarizes which settings can be modified after installation using 1E.Client.exe -reconfigure and which require modification in the registry. If you are using Configuration Manager, registry settings are best managed using Configuration Baselines. 1E provide template Configuration Items for Nomad and WakeUp that configure settings with their default values. These can be imported, modified to meet your requirements then added to a Configuration Baseline and deployed to clients as described in Using Configuration Manager to enable and reconfigure the 1E Client after installation.

Using Configuration Manager to enable and reconfigure the 1E Client after installation

The 1E Client can be configured after installation using a Configuration Manager Configuration Baseline. The following template Configuration Items have been prepared and are available to be downloaded and imported into Configuration Manager.

You can download the set of template Configuration Items available here 1EClientCIs.zip and unzip to a working directory accessible from a CM console.

To configure the 1E Client after installation:

1. Import template Configuration Items

   1. Download the set of template Configuration Items available here 1EClientCIs.zip and unzip to a working directory accessible from a CM console

   2. Start the CM console and open the Assets and Compliance workspace
   3. Expand the Compliance Settings folder, right-click Configuration Items and select Import  Configuration Data to start the Import Configuration Data Wizard
   4. From the Import Configuration Data Wizard Select Files page, click Add... and browse to the files extracted from 1EClientCIs.zip. You can select to import all files, or select only those relevant to the modules you want to enable and configure right now, using the above table for reference. Click Open to import the selected files
   5. As the Configuration Items have not been signed you will be prompted to confirm that you want to import them - click Yes to import each file, then click Next
   6. On the Summary page click Next to import the Configuration Items

   7. On the Confirmation page click Close.

      After importing the Configuration Items, double-click each in turn to view the CI properties and review the Supported Platforms tab to ensure all Operating Systems you currently manage are selected. For example, if you are managing Windows Server 2019 with CM CB 1902 or later, you will need to select Windows Server 2019.

      
      

2. If you want to configure Tachyon
   1. Double-click the Configure Tachyon client in 1E Client Configuration Item to edit its properties
   2. Click on the Settings tab, then double-click the Configure Tachyon client in 1E Client setting
   3. From the General tab of the Configure Tachyon client in 1E Client Properties dialog box, select the Edit Script button under Remediation Script (optional)
   4. In the script editor, replace <SERVERFQDN> with the FQDN of your Tachyon server for both the Switch and BackgroundChannelUrl. If you are using custom ports, then modify these accordingly too, then click OK to save and close the script editor.
   5. Click OK on the remaining dialog boxes to save the updated CI and return to Configuration Items in the CM console.
    
3. If you want to configure Shopping
   1. Double-click the Enable and Configure Shopping module in 1E Client Configuration Item to edit its properties
   2. Click on the Settings tab, then double-click the Enable and Configure Shopping module in 1E Client setting
   3. From the General tab of the Enable and Configure Shopping module in 1E Client Properties dialog box, select the Edit Script button under Remediation Script (optional)
   4. In the script editor, replace <<FQDN>> with the FQDN of your Shopping web server (typically this is a DNS alias for the Shopping website host header), then click OK to save and close the script editor
   5. Click OK on the remaining dialog boxes to save the updated CI and return to Configuration Items in the CM console.
    
4. If you want to configure WakeUp, there are no changes required to the Enable WakeUp module in 1E Client CI, but you will need to modify the WakeUp 7.3 Registry Settings CI as follows:
   1. Double-click the WakeUp 7.3 Registry Settings Configuration Item to edit its properties
   2. Click on the Compliance Rules tab and review the values defined for each of the registry values. To modify any of these, double-click the item and in the Edit Rule dialog box, define the value that should be used:
      
      • If the AFWebService website is using HTTP, replace the <SERVERFQDN> in the ServiceUrl (HTTP) setting with the FQDN of the web server and ensure the ServiceUrl (HTTPS) value is blank
      • If the AFWebService website is using HTTPS, blank the ServiceUrl (HTTP) value and replace the <SERVERFQDN> in the ServiceUrl (HTTPS) setting
      • When using HTTPS you must also define either CertIssuer or CertSubject setting.
   3.  Click OK to save the properties and return to Configuration Items in the CM console.
    
5. If you want to configure Nomad, there are no changes required to the Enable Nomad module in 1E Client CI, but you will need to modify the Nomad 7.0 Registry Settings CI as follows:
   1. Double-click the Nomad 7.0.200 Registry Settings Configuration Item to edit its properties
   2. Click on the Compliance Rules tab and review the values defined for each of the registry values. To modify any of these, double-click the item and in the Edit Rule dialog box, define the value that should be used. If you are using ActiveEfficiency you will need replace the <<AEServerFQDN>> in the PlatformUrl setting with the FQDN of the ActiveEfficiency web server
   3.  Click OK to save the properties and return to Configuration Items in the CM console.
    
6. Create a baseline to configure the 1E Client to include the required Configuration Items as follows:
   1. Right-click Configuration Baselines and select Create Configuration Baseline. Enter a suitable name and description.
   2. Click the Add button and select Configuration Items from the drop-down list. Select the Configuration Items as follows:
      • To configure Tachyon with this baseline, select the Configure Tachyon Client in 1E Client CI and click Add
      • To configure Shopping, select the Enable and Configure Shopping module in 1E Client CI and click Add
      • To configure WakeUp, select the Enable WakeUp module in 1E Client and WakeUp 7.3 Registry Settings CIs and click Add
      • To configure Nomad, select the Enable Nomad module in 1E Client and Nomad 7.0.200 Registry Settings CIs and click Add
   3. When you have added all the CIs you want to include, click OK to save and close the Add Configuration Items dialog box, then click OK to close the Create Configuration Baseline dialog box.
    
7. Deploy the Configuration Baseline to systems with the 1E Client installed
   1. Right-click the Configuration Baseline created in the previous step and select Deploy
   2. In the Deploy Configuration Baselines dialog box check the option Remediate noncompliant rules when supported
   3. Click the Browse... button and select a Collection to deploy the baseline to (typically you would use the same Collection that was targeted with the initial 1E Client installation deployment)
   4. Modify the scheduling according to your preferences and click OK.

Clients in the targeted Collection will start to apply the Configuration Baseline after the next machine policy refresh. You can check the compliance status periodically Configuration Baselines view in the console.

Example command-lines for reconfiguring the 1E Client

After installing the 1E Client, it may be necessary to enable additional modules, disable modules, or change configuration settings. For example, the 1E Client may have been initially installed just for the Shopping or WakeUp modules and you now want to use the full 1E Client with the Tachyon Platform, or conversely you may have deployed the 1E Client without the Shopping module enabled and subsequently implemented Shopping v5.5 and therefore need to enable the Shopping module. These scenarios can be managed using the 1E.Client.exe -reconfigure command-line interface, so it is easy to implement using software distribution tools such as Configuration Manager.

Please refer to  1E Client command-line parameters if you would like to see details of other CLI commands.

Reconfiguring on Windows devices

The -reconfigure command-line option changes the settings in the 1E.Client.conf configuration file. These changes are only available from Tachyon instructions when the 1E Client service is running. Use the -restart option on the command line to restart the service after the configuration changes have been made. Note that the restart will be delayed by a random duration (based on the Tachyon client reconnection interval) to disperse the load as clients connect to Tachyon, ActiveEfficiency, NightWatchman or Shopping servers on startup.

Reconfiguring on non-Windows devices

Please refer to 1E Client command-line parameters if you would like to see details of other CLI commands.

Starting and Stopping the 1E Client from the command line

On Windows devices, you can start, stop and restart the 1E Client from the command-line, as an alternative to using the Windows Services console UI. Please refer to 1E Client command-line parameters for more details.

On Linux, Solaris and macOS devices, you can start, stop and restart the 1E Client from the command-line, but this is not supported on Android.