Peer to Peer Software Distribution with 1E Nomad

To offer an alternative peer distribution system, Omnissa Workspace ONE UEM partners with 1E Nomad. This integration does not require any configuration in the Omnissa Workspace ONE UEM console. When you install the Nomad client on a UEM-enrolled device, the Software Distribution agent detects it and uses Nomad to download the application packages. If previously activated, deactivate BranchCache or Adaptiva P2P technologies to ensure successful downloads using the Nomad.

Architecture of Nomad

The Nomad uses several customer-facing components that connect to provide its content download functionality.

The basic architecture and port configuration for Nomad is as shown in the diagram. For a full description of Tachyon Platform Stacks, its components, the clients, and how the connection is made to provide Tachyon Platform features, refer to the Tachyon Platform 8.1 documentation.

The ports used for basic Nomad communications are listed in the table. This data was obtained from the Nomad documentation.

Considerations for 1E Client Deployment

Review the list before proceeding with the deployment to determine whether you already have the 1E Client setup in your environment with the Nomad enabled or are performing a clean installation.

• If you have a supported version of the 1E Client installed, with Nomad enabled, there should be no further configuration required. The Workspace One client automatically detects the presence of the NomadBranch service and calls it accordingly. Please contact your 1E account team if you have any questions.
• If you do not have the 1E Client with Nomad enabled deployed in your environment, you must follow the instructions outlined in the Deploy 1E Client for Nomad section.
• If you currently have the 1E Client deployed in your environment but do not have Nomad enabled, please contact your 1E account team for assistance.

Note: The advanced features of the 1E Client, such as Single Site Download (SSD) and Client Health, require the 1E Platform. If you want to take advantage of these features, contact your 1E account team for assistance.

Deploy 1E Client for Nomad

Before you begin the deployment process, ensure you meet the prerequisites. After you complete the prerequisites, launch the 1E Client Deployment Assistant to install the 1E Client with Nomad enabled for use with Workspace One and enter the necessary deployment details.

Prerequisites:

• Download the 1E Client Deployment Assistant ZIP from https://1eportal.force.com/s/article/1EClient81.
• Create a folder to store the client installer files that are produced by the 1E Client Deployment Assistant. For example, use D:\Temp\Output.

Procedure:

1. Create the 1E Client content source.

   a. Right-click the installer file ClientDeploymentAssistant.exe and select Run as administrator.

   b. On the Welcome screen, select Next.

   c. Select the I accept the license terms check box and then click Next.

   d. On the Configuration Manager connection screen, select Do not connect to Configuration Manager. Click Next.

   e. On the General Settings screen, enter the output directory or browse to the directory path you created earlier. Click Next.

   f. On the Agent selection screen, deselect the 1E NightWatchman Agent check box and select 1E Client. Click Next.

   g. On the Tachyon and other client settings screen, do not select any of the check boxes. Click Next.

   h. On the Nomad client settings screen, activate the following settings:

   Settings	Description
   Enable Nomad	Select the check box.
   Log Path	Change the log path to C:\ProgramData\1E\NomadBranch. If you have another preferred location for agent log files, enter the path in this field, if the System account has the write access to the location.
   Hidden Nomad Share Fanout Prevent Failing Over to BITS Use FIPS Encryption	Select only the check boxes for these settings.
   P2P Protocol	Select the protocols appropriate for your environment based on the allowed protocols and ports. HTTPS uses a self-signed certificate. If you want to use your own PKI certificates for P2P authentication, refer to the Nomad documentation.

   i. On the PXE Everywhere settings screen, deselect the EnablePXE Everywhere check box. Click Next.

   j. The Summary screen displays a preview of the content sources created by the 1E Client Deployment Assistant. Click Create to continue or Previous to go back and change the values.

   k. On the Progress screen, once the Status is shown as Successful, review the results and then click Next.

   l. Click Finish.

2. Review the output from the 1E Client Deployment Assistant.

   a. In your output folder, you can see both x64 and x86 subfolders. These folders contain an MSI installer, an MST transform file, an Install.txt, and an Uninstall.txt file.

   b. The Install.txt and Uninstall.txt files contain the command lines for installing and uninstalling the 1E Client. You can change the log path, but by default, it is set to the %TEMP% path of the account or context under which the install is running.
   Here is an example of the Install.txt command line.

   `msiexec /i 1E.Client-x64.msi REBOOT=ReallySuppress /l*v %TEMP%\1E.Client-x64-Install-8.1.2.62.log /qn TRANSFORMS="1E.Client-x64-8.1.2.62.mst"`
   

3. Deploy the 1E Client.

   After you complete the steps, you can use the output of the 1E Client Deployment Assistant in the deployment tool in your environment.