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.

Lab Information
The lab environment consists of the following computers:

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 1.10.0.62 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

7. Log into 1ETRNCM as 1ETRN\SCCMAdmin
8. 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
9. Open the Config Mgr console and navigate to the Software Library Workspace
10. Expand Operating Systems – Select Task Sequences
11. Right Click on WSA Wipe and Load Non-Destructive and select Edit
12. Scroll down to the Install and Setup Operating System Group
13. Highlight Stage Nomad Package action and notice that the old Nomad package is selected

14. Close the Task Sequence without making any changes
15. Close the Config Mgr Console
16. Open an Administrative Command Prompt and change directory to c:\temp\NomadBranch.v7.0.0.205
17. Type in the following command line

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

18. On the Welcome page click Next
19. Accept the terms in the license agreement click Next
20. On the Nomad Pre-Caching page ActiveEfficiency URL field type in http://1etrnap/ActiveEfficiency click Next
21. On the Nomad Tachyon Integration page click Next
22. On the Ready to Install page click Install
23. When the Installation completes click Finish
24. In the Administrative Command Prompt type in the following command line

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

25. On the Welcome page click Next
26. Accept the terms in the license agreement click Next
27. On the Ready to Install page click Install
28. When the installation finishes click Finish

Verify the Installation of the Tools

29. Still logged into 1ETRNCM as 1ETRN\SCCMAdmin
30. Open the Config Mgr console
31. Navigate to the Software Library Workspace
32. Expand the Operating Systems node. Click Task Sequences
33. Right click the WSA Wipe and load Non-Destructive task sequence and select Edit
34. Scroll down to the Install and Setup Operating System group
35. Select the Stage Nomad Package step
36. 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.

37. 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.

38. Navigate to the Boot Images node
39. Right click the PXE Everywhere Boot Image and choose Update Distribution Points
40. Click Next. Click Next
41. 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.

42. Log into 1ETRNCM as 1ETRN\SCCMADMIN
43. 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
44. Launch the 1EClientDeploymentAssistant.exe
45. On the Welcome page click Next
46. On the License Terms page check I accept the license terms. Click Next
47. On the Configuration Manager Connection page click connect. Once it connects click Next
48. On the General settings page 1E License File field click browse and select the licenses.txt file in the 1EClientDeploymentAssistant folder

49. In the 1E ActiveEfficiency Server URL change default to *http://1etrnap/ActiveEfficiency*
50. On the Application and Package Content Sources fields type in \\1etrndc\ConfigMgrSource\Software
51. Check the Distribute Content box and select All Distribution Points from the drop-down. Click Next.
52. Uncheck all the boxes except for the 1E Client. Click Next
53. On the 1E Client 5.0.0.745 page change the Limiting Collection to All Desktop and Server Clients Click OK
54. On the Tachyon and other client settings page Switch field type in Tachyon.1etrn.local:4000
55. In the Background Channel field type in *https://Tachyon.1etrn.local:443/Background* 
56. 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.

57. On the Nomad Client Settings page check Enable Nomad Click Next
58. Once the Summary page activates the Create button click Create
59. Once that completes click Next
60. Click Finish
61. Launch the ConfigMgr console  from the taskbar

62. Navigate to Software Library – Application Management – Applications
63. Select the 1E Client 5.0.0.745 and click Deployment Types tab at the bottom
64. Right Click the 1E Client x64 deployment type and choose Properties
65. Click the Requirements tab. Click the Operating System requirement type and click the edit button
66. 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.

67. Navigate to Software Library – Application Management – Applications
68. Right Click 1E Client 5.0.0.745 select Properties
69. Click the Supersedence tab. Click Add. Click Browse and select 1E Nomad 6.3.201.6 and Click Ok
70. In the New Deployment Type fields select 1E Client for both the x86 and the x64 new deployment type.

71. Click Ok. Click Apply. Click Ok

Deploy the 1E Client Application

71. Navigate to Assets and Compliance workspace and click on Devices
72. Multi-select all the devices in the Lab except for 1ETRNDC and add them to an existing collection – 1E Client 5.0.0.745 – Required
73. Once the collection membership shows 6
74. Right Click on the 1E Client 5.0.0.745 – Required collection and choose Client Notification – Download Computer Policy.

Task Sequence Update for the 1E Client

75. Navigate to Software Library workspace
76. Expand Operating Systems Node Select Task Sequences
77. Right click on the WSA Wipe and load Non-Destructive Task Sequence and select Edit
78. Scroll down to the Install and Setup Operating System Group
79. Select the Stage Nomad Package action. Click Browse Select the 1E Client 5.0.0.745 x86 Package. Click Ok
80. Click Apply to save the Task Sequence. Close the Task Sequence

Validate the 1E Client Install

81. On the client computer, launch the Services console from the desktop
82. Confirm the 1E Client service has been installed and is running
83. Navigate to c:\programdata\1E\Client
84. Double- click the 1E.Client.log file and review the log
85. Note the uninstall of 1E Nomad Branch 6.3.201
86. Review the other settings in the log
87. Navigate to c:\program files\1E\Client and review the content
88. Right-click 1E.Client.conf and select Open With and open with Notepad++
89. 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
90. Scroll down to the bottom section Module Settings
91. Notice that the WakeUp Module is not enabled

92. 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

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

Create the Baseline and add the Imported CI

99. Right click on Configuration Baselines and choose Create Configuration Baseline
100. In the Name field type in Enable WakeUp in the 1E Client
101. Click Add choose Configuration Items. Select our Enable WakeUp in the 1E Client CI that we just imported
102. Click Add then click Ok
103. Click OK

Deploy the Baseline to Enable the WakeUp Module

104. Navigate to Configuration Baselines – Select the Enable WakeUp in the 1E Client baseline and Right Click and select Deploy
105. Check the box to Remediate noncompliant rules when supported
106. Check the box to Allow remediation outside the maintenance window
107. In the Collection Field click Browse and Select Device Collections – Lab Workstations
108. Click Ok. Click Ok
109. 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

110. Log into 1ETRNW101 as 1ETRN\User
111. Launch the Config Mgr applet from the desktop
112. Click the Configurations Tab. Select the Enable WakeUp Baseline and click evaluate
113. Click Refresh until it shows compliant
114. Navigate to c:\ProgramData\1E\Client and launch 1E.Client.Log
115. Search the log for Module 'WakeUp' has been installed
116. 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.
117. Launch c:\Program Files\1E\Client\1e.Client.conf
118. Scroll down to the bottom and see that WakeUp Module has been enabled

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.