On this page:

Document Purpose and Conventions

This document has the following aims:

  • To provide instructions to delegates to enable completion of the practical training labs
  • Where relevant, provide guidance which can be used during real world implementations

The following conventions are used to highlight important information.

Hot Tip
Best practice
Discussion point
Indicates the virtual machine that should be used for the exercise or task.


Lab Information

The lab environment consists of the following computers:




AD Site


Domain controller for the 1ETRN.LOCAL domain. The ConfigMgr package source folder is located on this server.



ConfigMgr server with a local SQL instance. All ConfigMgr roles are installed in this server.



Application server that hosts ContentDistribution and other databases. SQL is installed locally.



Windows 10 client computer

Remote Office - Floor 1


Windows 10 client computer

Remote Office - Floor 2


Windows 10 client computer

Remote Office - Floor 1


Windows 10 client computer

Remote Office - Floor 1


Windows 10 client computer

Remote Office - Floor 2

The password for all accounts used in the lab environment is: Passw0rd

Ignore any patching popups on our servers. We have deliberately left them unpatched to show patching via Patch Success and/or Nomad


Unless otherwise indicated, logon to the lab VMs using the following accounts



















Upgrading the 1E Client

The lab environment already has Tachyon, Nomad, Shopping, Wakeup, and Windows Servicing Suite Installed. In this lab you will learn how to upgrade the 1E Client and how to enable a module of the 1E Client after you have deployed to the device.

Upgrading Nomad Backend

This exercise will teach you how to upgrade your Nomad infrastructure to 7.0 to support using the 1E Client on your devices.

Upgrade ActiveEfficiency

Nomad version 7.0 needs ActiveEfficiency at least v with hotfix Q20481. We already have AE 1.10 installed in our lab. We will apply the hotfix.

  1. Log into 1ETRNAP as 1ETRN\AppInstaller
  2. Open OneDrive Shortcut on the desktop and download the contents of 1E Client Upgrade Course Content\ActiveEfficiency.v1.10.0.62 and copy Q20481-activeefficiencyserver.v1.10.0.62.msp to c:\temp
  3. Right click on Q20481-activeefficiencyserver.v1.10.0.62.msp and click Apply
  4. On the Welcome page click Update
  5. Once the installation completes click Finish
  6. Click yes to restart 1ETRNAP

Install the Console Extensions and the Nomad Tools

  1. Log into 1ETRNCM as 1ETRN\SCCMAdmin
  2. Open the OneDrive Shortcut and download 1E Client Upgrade Course Content\NomadBranch.v7.0.0.205.zip to c:\temp right click and extract the contents
  3. Open the Config Mgr console and navigate to the Software Library Workspace
  4. Expand Operating Systems – Select Task Sequences
  5. Right Click on WSA Wipe and Load Non-Destructive and select Edit
  6. Scroll down to the Install and Setup Operating System Group
  7. Highlight Stage Nomad Package action and notice that the old Nomad package is selected
Once we install the Nomad 7.0 console extensions this will change to 1E Client (instead of Nomad package). It will still be pointed to the current Nomad package – so nothing will break. You will need to go into your Task Sequences and repoint this step (which will be changed to Stage 1E Client) to your new 1E Client package that will be created with the Client Deployment Assistant.
  1. Close the Task Sequence without making any changes
  2. Close the Config Mgr Console
  3. Open an Administrative Command Prompt and change directory to c:\temp\NomadBranch.v7.0.0.205
  4. Type in the following command line

MSIEXEC /I NomadBranchAdminUIExt.msi /l*v NomadBranchAdminUIExt.log

  1. On the Welcome page click Next
  2. Accept the terms in the license agreement click Next
  3. On the Nomad Pre-Caching page ActiveEfficiency URL field type in http://1etrnap/ActiveEfficiency click Next
  4. On the Nomad Tachyon Integration page click Next
  5. On the Ready to Install page click Install
  6. When the Installation completes click Finish
  7. In the Administrative Command Prompt type in the following command line

MSIEXEC /I NomadBranchTools.msi /l*v NomadBranchTools.log

  1. On the Welcome page click Next
  2. Accept the terms in the license agreement click Next
  3. On the Ready to Install page click Install
  4. When the installation finishes click Finish

Verify the Installation of the Tools

  1. Still logged into 1ETRNCM as 1ETRN\SCCMAdmin
  2. Open the Config Mgr console
  3. Navigate to the Software Library Workspace
  4. Expand the Operating Systems node. Click Task Sequences
  5. Right click the WSA Wipe and load Non-Destructive task sequence and select Edit
  6. Scroll down to the Install and Setup Operating System group
  7. Select the Stage Nomad Package step
  8. Notice that it now shows 1E Client Package (instead of Nomad Package) in the details of the action (right pane). The action name is still called Stage Nomad Package. Notice that the old 6.3 Nomad Package is still selected.
Nothing will break if we do not edit out task sequences after we create our new 1E Client Package – the older version of Nomad will be installed instead of the 1E Client.
  1. Close the Task Squence without making any changes

Update the Boot Images on the DP

Now that we have installed Nomad 7.0, we need to update our Boot Image content on the DPs so that the new binaries will be injected to our boot images. Make sure you update all the boot images that you will use in our environment. We are only using our PXE Everywhere Boot Image in this lab.

  1. Navigate to the Boot Images node
  2. Right click the PXE Everywhere Boot Image and choose Update Distribution Points
  3. Click Next. Click Next
  4. When the update completes click Close

Using the 1E Client Deployment Assistant

Now that the Nomad back end has been installed, it is time to get our clients installed. In this exercise, we will deploy the 1E Client with multiple modules installed first. The next exercise will teach you how to enable modules after the installation of the 1E Client (no need to redeploy if you purchase another 1E Product later).  In most enterprises, there will be a Systems Management platform to manage devices in the environment. In our lab we will use ConfigMgr, but the concept of deploying the 1E Client as a piece of software will apply to any Systems Management platform.

  1. Log into 1ETRNCM as 1ETRN\SCCMADMIN
  2. Launch the OneDrive shortcut from the desktop and download the contents of 1E Client Upgrade Course Content\1EClientDeploymentAssistant.v1.4.0.27 folder to c:\temp
  3. Launch the 1EClientDeploymentAssistant.exe
  4. On the Welcome page click Next
  5. On the License Terms page check I accept the license terms. Click Next
  6. On the Configuration Manager Connection page click connect. Once it connects click Next
  7. On the General settings page 1E License File field click browse and select the licenses.txt file in the 1EClientDeploymentAssistant folder
You will need to have your license numbers for PXE Everywhere and NightWatchman if you are going to use the Client Deployment Assistant to create your objects.
  1. In the 1E ActiveEfficiency Server URL change default to *http://1etrnap/ActiveEfficiency*
  2. On the Application and Package Content Sources fields type in \\1etrndc\ConfigMgrSource\Software
  3. Check the Distribute Content box and select All Distribution Points from the drop-down. Click Next.
  4. Uncheck all the boxes except for the 1E Client. Click Next
  5. On the 1E Client page change the Limiting Collection to All Desktop and Server Clients Click OK
  6. On the Tachyon and other client settings page Switch field type in Tachyon.1etrn.local:4000
  7. In the Background Channel field type in *https://Tachyon.1etrn.local:443/Background* 
  8. Check Enable Inventory  and Enable Shopping. Type in  http://Appstore/Shopping in the Shopping Web URL field and check Enable Edge/Windows App Browser support. click Next.
Leave Enable Wakeup unchecked as we are going to enable that in a later exercise using a Configuration Item.
  1. On the Nomad Client Settings page check Enable Nomad Click Next
  2. Once the Summary page activates the Create button click Create
  3. Once that completes click Next
  4. Click Finish
  5. Launch the ConfigMgr console  from the taskbar
Our lab is configured to create our applications and packages for only workstation class devices. You can modify this by editing your AppImport.xml in your 1E Client Deployment Assistant folder. We will edit our application to include the servers.
  1. Navigate to Software Library – Application Management – Applications
  2. Select the 1E Client and click Deployment Types tab at the bottom
  3. Right Click the 1E Client x64 deployment type and choose Properties
  4. Click the Requirements tab. Click the Operating System requirement type and click the edit button
  5. Scroll down and select all the x64 Server Operating Systems also. Click Ok. Click Apply. Click Ok

Add Supersedence for the 1E Client

You will need to either disable your current deployments for any of the products you are upgrading or, if you are deploying using the Application Model (for both the old and new versions), you can configure supersedence. If you do not configure supersedence or disable any deployments the device will be reverted to the prior version.

  1. Navigate to Software Library – Application Management – Applications
  2. Right Click 1E Client select Properties
  3. Click the Supersedence tab. Click Add. Click Browse and select 1E Nomad and Click Ok
  4. In the New Deployment Type fields select 1E Client for both the x86 and the x64 new deployment type.
No need to select to uninstall as the 1E Client module, once it starts up, will look for and remove any prior versions.
  1. Click Ok. Click Apply. Click Ok

Deploy the 1E Client Application

  1. Navigate to Assets and Compliance workspace and click on Devices
  2. Multi-select all the devices in the Lab except for 1ETRNDC and add them to an existing collection – 1E Client – Required
  3. Once the collection membership shows 6
  4. Right Click on the 1E Client – Required collection and choose Client Notification – Download Computer Policy.
At this stage, the 1E Client has been deployed to all the clients in the lab environment, including our Distribution Point. We will move onto the next exercise and validate that the clients have installed a bit later, as the deployment will take a few minutes.

Task Sequence Update for the 1E Client

  1. Navigate to Software Library workspace
  2. Expand Operating Systems Node Select Task Sequences
  3. Right click on the WSA Wipe and load Non-Destructive Task Sequence and select Edit
  4. Scroll down to the Install and Setup Operating System Group
  5. Select the Stage Nomad Package action. Click Browse Select the 1E Client x86 Package. Click Ok
  6. Click Apply to save the Task Sequence. Close the Task Sequence
We only edited one Task Sequence in our lab – in your production environment you will need to edit all of the ones that have an install Nomad Step. No need to edit the Install and Configure Nomad in WinPE as we injected the binaries for the 1E Client into our boot image from the server. This is what will be used in WinPE.

Validate the 1E Client Install

  1. On the client computer, launch the Services console from the desktop
  2. Confirm the 1E Client service has been installed and is running
  3. Navigate to c:\programdata\1E\Client
  4. Double- click the 1E.Client.log file and review the log
  5. Note the uninstall of 1E Nomad Branch 6.3.201
  6. Review the other settings in the log
  7. Navigate to c:\program files\1E\Client and review the content
  8. Right-click 1E.Client.conf and select Open With and open with Notepad++
  9. Review the different sections of the config file, ensuring you  do not make any changes . Note that the settings displayed in the log file are all defined here
  10. Scroll down to the bottom section Module Settings
  11. Notice that the WakeUp Module is not enabled
The 1E Client settings are defined in the config file and loaded up when the service starts. In the next exercise we will enable the WakeUp Module using configuration items and a baseline.
  1. Close the config file, ensuring no changes were made. If asked to save it, click NO

Enabling a Module of the 1E Client after Initial Deployment

This exercise is to simulate how you would enable a module of the 1E Client after you have done your initial deployment. If you wanted to stay at Nomad version 6.3 while you were upgrading to Tachyon v5.0 you would deploy the 1E Client with the Nomad module not enabled. Later, once you are ready to upgrade Nomad (i.e. you have the backend upgraded and are ready to deploy to your workstations) you would then use a Configuration Item and deploy a baseline to enable the Nomad module of the 1E Client. In this exercise we are going to enable the WakeUp module using Configuration Items deployed in a Baseline. 1E provides all the Configuration Items for you to import into Config Mgr to enable any of the modules. The 1EClientCIs.zip can be downloaded from Reconfiguring 1E Client: Using Configuration Manager to enable and reconfigure the 1E Client after installation.

Import the Configuration Item

  1. Still logged into 1ETRNCM as 1ETRN\SCCMAdmin
  2. Launch OneDrive shortcut and copy the contents of 1E Client Upgrade Course Content\1EClientCIs to c:\temp
  3. Launch the Config Mgr Console and navigate to Assets and Compliance – Compliance Settings – Configuration Items
  4. Right Click Configuration Items and select Import Configuration Data
  5. Click Add and navigate to C:\temp\1EClientCis\Enable WakeUp Module in 1E Client.cab Click Open. Click Yes on the warning box
  6. Click Next. Click Next. When the import finishes click Close

The Configuration Items are setup to import without Server 2019 selected as a supported platform. This is to ensure that the Configuration Items will not fail the import if you are running a version older than 1902. In your production environment look at the properties of the Configuration Items – Supported Platforms to ensure that the platforms that are required for your environment are selected.

Create the Baseline and add the Imported CI

  1. Right click on Configuration Baselines and choose Create Configuration Baseline
  2. In the Name field type in Enable WakeUp in the 1E Client
  3. Click Add choose Configuration Items. Select our Enable WakeUp in the 1E Client CI that we just imported
  4. Click Add then click Ok
  5. Click OK

Deploy the Baseline to Enable the WakeUp Module

  1. Navigate to Configuration Baselines – Select the Enable WakeUp in the 1E Client baseline and Right Click and select Deploy
  2. Check the box to Remediate noncompliant rules when supported
  3. Check the box to Allow remediation outside the maintenance window
  4. In the Collection Field click Browse and Select Device Collections – Lab Workstations
  5. Click Ok. Click Ok
  6. Navigate to Device Collections – Right click on Lab Workstations and select Client Notification – Download Computer Policy – Click ok on the warning

Verify WakeUp is Enabled for the 1E Client

  1. Log into 1ETRNW101 as 1ETRN\User
  2. Launch the Config Mgr applet from the desktop
  3. Click the Configurations Tab. Select the Enable WakeUp Baseline and click evaluate
  4. Click Refresh until it shows compliant
  5. Navigate to c:\ProgramData\1E\Client and launch 1E.Client.Log
  6. Search the log for Module 'WakeUp' has been installed
  7. Read the lines below the installation. Notice that the 1E Client is checking for prior versions of WakeUp in order to uninstall it. In our case there was not a prior version installed on the device.
  8. Launch c:\Program Files\1E\Client\1e.Client.conf
  9. Scroll down to the bottom and see that WakeUp Module has been enabled
Notice that the Inventory Module, Shopping Module, and Nomad Modules are all also enabled. Those were enabled with the original installation of the 1E Client. Tachyon is not technically a module so no need to enable it. By default Tachyon is enabled when you install the 1E Client, so you are not able to remain at the 3.3 version of Tachyon if you are deploying the 1E Client, the other modules are able to be upgraded after the deployment of the 1E Client.

Lab Summary

In this lab, we learned how to upgrade to Nomad 7.0 and deploy the 1E Client. We then learned how to enable additional modules of the 1E Client for environments that have already deployed.