Nomad Installation Guide

Nomad 2012 v5.2.
100 Installation Guide

Copyright and Trademark Notices
All rights reserved. No part of this document or of the software (the software) to which it relates shall
be reproduced, adapted, stored in a retrieval system, or transmitted by any means, electronic,
mechanical, photocopying, recording, or otherwise, without permission from 1E Ltd. It is the
responsibility of the user to use the software in accordance with this document and 1E Ltd shall not be
responsible if the user fails to do so. Although every precaution has been taken in the preparation of this
document, 1E Ltd and the authors assume no responsibility for errors or omissions, nor shall they be
liable for damages resulting from any information in it.
Trademarks
1E, the 1E device, APPCLARITY, ACTIVEEFFICIENCY, NIGHTWATCHMAN, NOMAD ENTERPRISE, PXE
EVERYWHERE, DROWSY and DROWSY SERVER are trademarks belonging to 1E Ltd. 1E is registered in
the UK, EU and the US. The 1E device is registered in the UK, EU, Australia and the US.
NIGHTWATCHMAN is registered in the EU and the US. Nomad is registered in the EU and the US.
DROWSY is registered in the UK. DROWSY SERVER is registered in the US.
MICROSOFT, WINDOWS 8, WINDOWS 7, WINDOWS VISTA, WINDOWS XP, SMS, CONFIGURATION
MANAGER, INTERNET EXPLORER are all trademarks of Microsoft Corporation in the United States and
other countries.
Macintosh is a trademark of Apple Inc., registered in the U.S. and other countries.
Nomad 2012 v5.2.100 Installation Guide Page ii

Table of Contents
1. Welcome ......................................................................................................... 5
1.1 What is new in Nomad 2012 v5.2.100 ................................................................... 5
2. Introduction ................................................................................................... 6
2.1 Introduction ...................................................................................................... 6
Who is this guide for? ......................................................................................... 6
Key benefits ...................................................................................................... 6

How Nomad works ............................................................................................. 7
Installing Nomad ............................................................................................... 7
2.2 Nomad Features ................................................................................................ 7

New in Nomad 2012 v5.2.100 .............................................................................. 7
Nomad 5.1 Features ........................................................................................... 7
Nomad 5.0 Features ........................................................................................... 7

Nomad 4.1.100 Features ..................................................................................... 8
Nomad 4.1 Features ........................................................................................... 8
Nomad 4.0 Features ........................................................................................... 8

Key features of Nomad ..................................................................................... 10
3. Prerequisites ................................................................................................ 12
3.1 PXE Everywhere .............................................................................................. 16

4. Installation ................................................................................................... 17
4.1 Nomad Installers ............................................................................................. 17
4.2 Installing Nomad ............................................................................................. 19

Installing Nomad ............................................................................................. 19
Install Nomad interactively ................................................................................ 19
Install Nomad Silently ...................................................................................... 22

Repair the Nomad Service ................................................................................. 23
Uninstall Nomad .............................................................................................. 23
License Nomad ................................................................................................ 24

4.3 Installing the Nomad download monitor .............................................................. 24
Nomad download monitor interactive installation steps .......................................... 25
Silent Installation ............................................................................................. 25

Nomad download monitor installer properties ....................................................... 25
4.4 Installing the ConfigMgr Admin Console GUI extensions ......................................... 25
Prerequisites ................................................................................................... 25
ConfigMgr OSD tools and configuration files ......................................................... 25
Upgrading ConfigMgr ........................................................................................ 26
ConfigMgr with Multiple or Remote SMS Providers ................................................. 27
4.5 NomadBranch Installer Properties ...................................................................... 29
Nomad 2012 v5.2.100 Installation Guide Page iii

NomadBranch Installer Property Categories ......................................................... 29
NomadBranch Alphabetic Installer Properties ....................................................... 30

4.6 Upgrading Nomad ............................................................................................ 45
Upgrade best practices ..................................................................................... 45
Upgrading ConfigMgr ........................................................................................ 46
Nomad 2012 v5.2.100 Installation Guide Page iv

Section 1 - Welcome
1. Welcome
Welcome to the Nomad 2012 v5.2 on-line documentation. Here you can learn about how Nomad 2012
works, the new features it supports and how the Nomad 2012 components fit together to provide
enterprise-wide, efficient and secure content download.
Installation Engineers can find out about the prerequisites for installing Nomad 2012 and check the
installation steps .
Systems administrators can find out how to: configure Nomad 2012 for use with Configuration Manager
2012, configure Nomad 2012 for OS deployments, monitor Nomad 2012 downloads, manage the Nomad
2012 cache and find information on the Nomad 2012 command-line switches, return codes, status
message events and registry entries .
Enterprises interested in providing bare metal OS deployment in branch scenarios can find out how to
install and configure PXE Everywhere v2.1 .
1.1 What is new in Nomad 2012 v5.2.100

This maintenance release provides the following additions:
Support for ConfigMgr 2012 R2, Windows 8.1 and Windows Server 2012 R2
Pre-stage content using Nomad custom task sequence action now supports the use of custom
ports in ConfigMgr 2012 and ConfigMgr 2007 when using Nomad for OS Deployment
The main release provides the following features:

Single Site Peer Backup Assistant - Peer Backup Assistant can make use of single site data to
locate potential PBA data stores at the local site not just the local subnet.
High-Availability Peer Backup Assistant - Peer Backup Assistant now supports the creation of
multiple backups of USMT data to minimize risk and maximize success for OS migration.
App-V Streaming - Nomad integrates with App-V streaming applications, recognizing that the
initial download is only partial enabling full download at a later date.
Nomad 2012 v5.2.100 Installation Guide Page 5

Section 2 - Introduction
2. Introduction
2.1 Introduction
Welcome to Nomad, the key software from 1E that increases the efficiency of software and patch
distribution and saves you money in the process. It maximizes WAN availability during download by
providing features such as: Central Multicast, download once to branch, and download resumption with
built-in consistency checking.
Click here to find out what is new in Nomad .

Now in its fifth generation Nomad integrates with Microsoft System Center Configuration Manager
(ConfigMgr), to provide increased resilience and bandwidth throttling and maximize use of advanced
features like Remote Differential Compression to make optimal use of any type of network connection
with minimal impact on network users. Using Nomad with ConfigMgr you can enable software update
capabilities for machines which would have previously been unmanaged.
Nomad reduces the load on the central Distribution Points and eliminates the necessity for local
Distribution Points. This allows the ConfigMgr infrastructure to be simplified while still retaining coverage
of the entire network and reducing maintenance costs.
Nomad consists of two main components:

Nomad, the content transfer utility that helps deliver large content efficiently, safely and
securely.
PXE Everywhere v2.1, a tool that helps deliver OS updates to bare metal computers
Who is this guide for?

This online help is aimed at administrators who intend to deploy and use Nomad across their software
distribution network.
Key benefits
Nomad solves problems in key areas of distributing large amounts of data across a distributed network.
In particular Nomad provides the following benefits:
Significantly reduces the bandwidth required for delivering software.
Small offices or sites connected via poor network links can receive software updates more
reliably.
Reduces the need for large numbers of ConfigMgr servers.
Faster ConfigMgr implementations because fewer servers are required.
Distribute software to home, mobile and remote office users

Low cost easy to deploy
No new infrastructure or skills required

Reduces software distribution costs

How Nomad works

Nomad provides an efficient file transfer mechanism that integrates with ConfigMgr. Its support for
multicast and local re-distribution of data enables the reduction of dedicated ConfigMgr servers,
particularly in branch office scenarios where reducing WAN traffic is a critical consideration.
More details on how Nomad integrates with and enhances ConfigMgr can be found here.
Installing Nomad
Full details on the prerequisites required for installing Nomad can be found here and the steps for
installing the Nomad components can be found here.
2.2 Nomad Features

This page shows the historical features for Nomad listed by release.
New in Nomad 2012 v5.2.100

This maintenance release provides the following additions:
Support for ConfigMgr 2012 R2, Windows 8.1 and Windows Server 2012 R2
Pre-stage content using Nomad custom task sequence action now supports the use of custom
ports in ConfigMgr 2012 and ConfigMgr 2007 when using Nomad for OS Deployment
The main release provides the following features:

Single Site Peer Backup Assistant - Peer Backup Assistant can make use of single site data to
locate potential PBA data stores at the local site not just the local subnet.
High-Availability Peer Backup Assistant - Peer Backup Assistant now supports the creation of
multiple backups of USMT data to minimize risk and maximize success for OS migration.
App-V Streaming - Nomad integrates with App-V streaming applications, recognizing that the
initial download is only partial enabling full download at a later date.
Nomad 5.1 Features

Usability and feature enhancements for Operating System Deployments, including:
New Nomad Peer Backup Assistant Task Sequence actions.
Peer Backup Assistant supported across subnets.
Peer Backup Assistant supports redundant backups.
Multicast support added to Install and configure Nomad in WinPE and Pre-stage content using
Nomad Task Sequence actions.
Pre-stage content using Nomad Task Sequence action no longer requires the use of LSZ
Delegation for non-site server distribution points.
Pre-stage content using Nomad Task Sequence action now displays progress information in the
Task Sequence User Interface.
Streamlined OSD Task Sequence Nomad integration.
Nomad 5.0 Features

This release provided the following capabilities:
Peer Backup Assistant configuration during Nomad installation - The Peer Backup Assistant can
now be configured using dedicated Nomad installer properties.
ConfigMgr 2012 SP1 support

Windows 8 and Windows Server 2012 support
Nomad FanOut - this feature enables more Nomad Peers to be updated with the download from
the Nomad Master by allowing the machines directly connected to the Nomad Master to
themselves share out the download.
Single Site Download - this feature ensures that downloads are performed only once per branch
site, not per branch subnet - thereby maximizing the efficient distribution of downloads without
using the WAN more than once.
Nomad 4.1.100 Features

This release of Nomad provides custom Task Sequence actions for integrating Nomad with OS
Deployments, PXE Everywhere to reduce costly management of PXE servers and new 64-bit versions of
Nomad for integrating with ConfigMgr 2012.
Custom Task Sequence Actions this feature improves OS deployment performance enabling
Nomad to maximize content download efficiency by integrating Nomad into Task Sequences.
PXE Everywhere v2.1 - PXE Everywhere is a new feature in Nomad that lets you configure branch
networks to allow bare metal OS deployment efficiently in a scalable way that requires minimal
resources.
ConfigMgr 2012 support Nomad now integrates closely with the ConfigMgr 2012 Application
Model to support content download for Packages, Task Sequences, Driver Packages, Operating
System Images, Boot images, Applications and Software Updates.
Nomad 4.1 Features

This release of Nomad provides an onrequest shared cache mechanism, Nomad WinPE 3x support and
sensitive server weighting.
Peer Backup Assistant this feature is designed to help backup user files and settings data
during Operating System deployments, though it is not limited to this. Enabling backups of user
data to a peer computer on a branch site minimizes WAN usage and increases deployment
efficiency. By default this feature is disabled but can be enabled for any computer with Nomad
4.1 installed where you intend to store data.
Nomad WinPE 3x support Nomad now improves bare metal and refresh OSD capabilities in
branch scenarios by running under WinPE 3x. Nomad can then be used as a local store for OS
images, reducing bandwidth usage over the WAN and supporting local multicast to enable
simultaneous deployments without greatly impacting the branch network.
Sensitive Server Weighting Election weighting now takes a special case value that prevents a
business critical server from becoming a master.
OSD Migration Tools Nomad is now bundled with the NomadPackageLocator and TSEnv2 OSD
support tools. These help to support the new Peer Backup Assistant and Nomad WinPE 3x
features. 32- and 64-bit variants of these tools, which were previously bundled with the PXE
Everywhere installer, are now installed as part of the NomadBranchAdminUIExt.msi installer.
Nomad 4.0 Features

Version 4.0 improves on the previous version's extensive list of transfer efficiency and reliability features
to provide: remote differential compression integration, connection type awareness, support for
additional platforms and Internet protocols, and increased resilience.
Remote Differential Compression Integration Nomad RDC integration further minimizes the
amount of data sent across the WAN. Nomad integrates its existing features such as bandwidth
throttling and dynamic elections with parts of the ConfigMgr 2007 RDC feature to produce a
more efficient and reliable mechanism for transferring content.
Earlier versions of Nomad have always been aware of the filelevel differences between different
versions of a package, so that only the changed files are downloaded. Nomad 4.0 now has the
ability to focus in and download just the differences between individual files.

Mobile data connection awareness The increased usage of mobile devices operating over
various standards and technologies has also increased the need for awareness of the connection
type. This is essential in order not to incur cost and performance penalties when transferring
large amounts of systems management content or data, especially as many mobile providers
limit data usage with large cost penalties for exceeding the limits.
Nomad provides a mechanism for identifying and managing the connection type. If the agent
connection type matches a locally configured list of known devices it is determined to be a
mobile data connection and only Packages specifically configured to use a mobile data connection
will be transferred.
Wireless stability provides extra stability by managing a machine's connections as they move
between wired and wireless LAN. Often once an SMB or HTTP session is running on wireless it
will remain on wireless even when a wired LAN becomes available. The wired LAN connection is
normally deemed to be faster, more stable and reliable, so if Nomad is presented with a scenario
where a session is running on wireless but a wired LAN becomes available, it will drop the
wireless connection and seamlessly resume on the wired LAN.
LSZ delegation This feature supports distribution point server shares where ConfigMgr 2007
and Nomad 2012 are not installed and, as a result, the required .LSZ file cannot be produced. A
DP server share can be created on a Windows Server or NAS device. A file called
DelegatedLSZ.txt must be manually created upon the NAS DP. This provides a pointer to the
location of an alternate DP (usually the upstream DP). The client agent will then contact the
alternate location for its package LSZ files, and download the package content from the DP
server share.
P2P enhancements v4 has some new peertopeer connection options that enable it to work in
a wider range of scenarios than previously.
Internet Protocol Version 6 support Internet Protocol version 6 (IPv6) is the successor to
Internet Protocol version 4 (IPv4). The main driver to support IPv6 has been a recent directive
for all US federal organizations to move to this protocol. By providing support for IPv6
environments v4.0 also supports distribution to clients connected to the corporate network using
DirectAccess.
Distribution Point Resilience ConfigMgr provides a list of DPs to support failover capabilities
should access to a DP encounter problems. Nomad v4 supports cycling through this list of
available DPs until one can be reached and will now attempt to do this multiple times until a
configurable timeout has been reached.
Windows 7 Embedded support is now available on Windows Embedded Standard 2011
(formerly known as Windows 7 Embedded). As long as a fully working ConfigMgr 2007 client is
present all existing functionality can be fully utilized.
Permitted LSZ Shares enhancement the PermittedLszShares registry entry can now take
wildcards to provide flexible naming convention support.
Dynamic election weighting v4 now dynamically weights the chances of a computer
successfully winning a master election. Computers running Server Operating Systems are
favored whereas computers with a chassis type of mobile or with a connection type of wireless
are negatively weighted. This dynamic adjustment happens in addition to any locally configured
settings.
Domain Controller support v4 can now be deployed on Domain Controllers to allow them to
use Nomad features to get any locally required content, while ensuring as they perform mission
critical functions that they never have to provide any services to other computers on the
network.

Key features of Nomad

Full control over WAN link usage
Nomad minimizes the impact of software downloads on other business critical communications,
keeping the WAN link traffic flowing even when large packages, such as OS images, are being
downloaded to the branch.
Nomad Software distributions and downloads are throttled to ensure that a configurable
percentage of the WAN link remains free regardless of the Nomad traffic. Nomad recalculates the
available end-to-end bandwidth continuously and adjusts transfer speeds to keep within the
determined percentage. If other services or PCs start using the same WAN link, Nomad will back-
off automatically.
You can set an overall cap on the percentage of bandwidth used by Nomad WAN traffic using the
--wr switch and you can set hourly work rates for each day of the week. See Nomad Registry
Entries heading See Setting intra-day work rates for more details.
Maximum efficiency with significantly lower deployment and ongoing costs Nomad
enables server consolidation and maximizes operational efficiency. Very few ConfigMgr servers
are required, i.e. thousands of PCs can be served by a single ConfigMgr server. The
implementation costs will be significantly lower as will the ongoing management costs.
Additionally as only a few, centrally located, servers have to be deployed ConfigMgr
implementations will be rapid.
Download once to branch Nomad ensures that the software package is downloaded only once
to the branch. When a software package is advertised to the branch PCs, an election is held per
subnet in the branch to determine a master, this master PC then downloads the software. With
the Single Site Download feature introduced in Nomad 5.0, all such subnet masters then select a
site master amongst themselves, enabling a single machine to download from the WAN link
rather than having multiple downloads by every subnet master in the site. The subnet masters
copy from the site master and all other branch PCs copy the package directly from the elected
master in their respective subnets. If any of the masters is switched off, or becomes unavailable,
another PC is elected. This process is completely dynamic and does not require any management
in normal operation.
Download resumption and consistency checking
Nomad can restart downloads at the Byte level if there is an intermittent network link. It ensures
that the locally cached package is consistent with the ConfigMgr Package source and if the source
is changed during the copy process Nomad will automatically only update the changed files.
Local Multicast support Nomad provides multicast functionality that supports the local
distribution of Packages using multicast. multicast significantly improves the efficiency and
scalability of distributing ConfigMgr packages to branch offices. Once the download has reached
the branch using standard Nomad functionality, it is distributed locally using multicast
technology. This greatly reduces both the LAN network traffic and the load on the elected Nomad
masters. Multicast support enables Nomad to scale to branches with large numbers of local
machines.
The Multicast functionality is enabled by a specific product license. Please contact Sales for more
details.

Key benefits
Significantly reduces the bandwidth required for delivering software.
Small offices or sites connected via poor network links can receive software updates more
reliably.
Reduces the need for large numbers of ConfigMgr servers.
Faster ConfigMgr implementations because fewer servers are required.
Distribute software to home, mobile and remote office users
Low cost easy to deploy
No new infrastructure or skills required
Reduces software distribution costs

Section 3 - Prerequisites
3. Prerequisites
This section describes prerequisites needed to ensure a successful deployment of Nomad.
Requirements Notes
General The following requirements should be met before installing Nomad on your network.
When upgrading we recommend that you update all versions of Nomad
running on a single subnet at the same time. It is also highly recommended
that all the Site Servers and Distribution Points are updated first with Nomad
5.x before updating versions of Nomad running on the clients to avoid
known compatibility issues between Nomad 5.x clients and Distribution
Points running earlier versions of Nomad.
Ensure DNS is working properly
Ensure client side firewalls allow exceptions to be made for

NomadBranch.exe, NomadPackageLocator.exe and
PackageStatusRequest.exe. See Windows Security Settings for more
details.
Ensure the ConfigMgr Client is healthy and functioning properly
OS Nomad and Nomad Multicast should install and be configurable on any workstation
running the following Microsoft operating systems:
Windows 8.1 (Professional, Enterprise)
Windows 8 (Professional, Enterprise)
Windows 7 (Embedded*, Professional, Enterprise, Enterprise x64 and

Ultimate)
Windows Vista (Business, Enterprise, Enterprise x64 and Ultimate)
Windows XP 32-bit with SP3 applied

Note
*Windows Embedded versions are customizable Windows OS, best suited for
embedded or kiosk usage. Hardware manufacturer and operating system
customizations can vary greatly, and therefore 1E cannot provide full support
when certain OS components have been removed from the full image.
Nomad and Nomad Multicast should install and be configurable on any server
running the following Microsoft operating systems:
Windows Server 2012 R2
Windows Server 2012

Windows Server 2008 R2 RTM, SP1
Windows Server 2008 x64 SP1, SP2
Windows Server 2008 SP1, SP2

Windows Server 2003 SP2
Systems The following versions of ConfigMgr are supported:

Management
Configuration Manager 2012 R2
Configuration Manager 2012 RTM, SP1
Configuration Manager 2007 SP2, R2, R3

Nomad installers Nomad has two sets of installers one for 32-bit systems and the other for 64-bit
systems. The set that should be used depends on the ConfigMgr client installed on
the local machine.
ConfigMgr 2007 clients are always 32-bit so only the 32-bit Nomad installers
should be regardless of whether the target computer is 32-bit or 64-bit.
ConfigMgr 2012 clients may be either 32-bit or 64-bit client so the Nomad
installers used must match the local client.
The Nomad 32-bit installers are in the NomadBranch.v5.x.x.x.zip file:
NomadBranch.msi (in both the ConfigMgr2007 and ConfigMgr2012
directories)
NomadBranchAdminUIExt.msi (in ConfigMgr2007)
NomadBranchGui.msi (in DownloadMonitor)
The Nomad installers for 64-bit systems are in the ConfigMgr2012 directory in the
NomadBranch.v5.x.x.x.zip file:
NomadBranchAdminUIExt2012.msi (32-bit installer for ConfigMgr 2012

console)
NomadBranchTools.msi
NomadBranch-x64.msi
Distribution Point To support enhanced Package consistency checking, Nomad requires that the Nomad
agent is installed on each ConfigMgr Distribution Point (DP). This agent enables file-
level consistency checking by creating a manifest file on the DP for every version of
each Package created.
This allows Nomad to check that each file it downloads is consistent with the version
available on the DP.
Note
On ConfigMgr 2012 systems LSZ generation using HTTP/HTTPS is not enabled by
default on standalone Distribution Points. You will need to manually enable it on
the Nomad agent running on the standalone DP by configuring the
SpecialNetShare registry entry to include the 0x4000 value.
If the DP is not installed on a Primary or Secondary Site server you must ensure that
the Nomad registry setting PermittedLsZShares on the DP is updated to contain the
local share name(s) used on the server (e.g. SMSPKGF$; SMSPKGG$; etc) to host
ConfigMgr packages
To support Nomad RDC integration the Remote Differential Compression Feature
must also be installed using the Windows Server Manager. You will also need to set
the SigsFolder registry entry to point to the ConfigMgr RDC signatures folder. If the
DP is installed on a site server this step is not required as Nomad retrieves the DP
share name information directly from WMI.
For more details please refer to the description of the PERMITTEDLSZSHARES and
SIGSFOLDER installer command-line properties.
System Center For each ConfigMgr Site Server where you intend to administer Task Sequence
Configuration Packages to use Nomad as the alternate download Provider, you need to ensure the
Manager following conditions hold:

The Configuration Manager Admin Console must be installed as is the case

in a default Configuration Manager installation. This is a prerequisite for the
following:
The Nomad Admin Console GUI extensions must be
installed
When using ConfigMgr 2012 the Nomad Branch Tools must
also be installed.
If these conditions do not hold the Nomad settings for Task Sequences will not be
created correctly.
Note
This is the case even if you install a remote Configuration Manager Admin Console
with the Nomad Admin Console GUI extension, except for Nomad Branch Tools
which are required to be installed on ConfigMgr Site Server only.
Nomad Download The following components must be present prior to installing the Nomad Download
Monitor Monitor:
.NET Framework 2 or above

To use the Nomad Download Monitor to monitor remote machines the user
account will require DCOM permissions.
Nomad To install the NomadBranchTools for ConfigMgr 2012 the following needs to be
NomadBranchTool present:
s
A local installation of the System Center Configuration Manager 2012 Site
Server.
Nomad Admin To install the Admin Console GUI extensions the following needs to be present:
Console GUI
A local installation of the System Center Configuration Manager Admin
extensions
Console.
.NET Framework 3.5

If you want to install the Admin Console GUI Extensions on a remote ConfigMgr
console then you will need to ensure that the Admin Console GUI Extensions have
been installed on the site server first.
Nomad Multicast To use the Multicast functionality for Nomad you will need a specific multicast license
key available from 1E.
For more information on purchasing license keys contact Sales, details on contacting
1E are provided in Technical Support for Nomad.

ActiveEfficiency To support Single Site Download Functionality the following version of 1E

Server integration ActiveEfficiency Server must be installed:
1E ActiveEfficiency 1.2 or above must be installed and running
successfully - though we recommend using the latest version. Please refer
to ActiveEfficiency installation instructions relevant to the version you are
using for setting up an instance for use with Nomad.
To support Single Site Peer Backup Assistant Functionality the following version of 1E
ActiveEfficiency Server must be installed:
1E ActiveEfficiency v1.5 or above must be installed and running
successfully. Please refer to ActiveEfficiency installation instructions for
setting up an instance for use with Nomad.
Windows security File and Print Sharing

settings
The recommended way to facilitate Nomad peer-to-peer communications is to enable
Windows File and Print Sharing. If this is not feasible on your network environment
you can configure Nomad to use different means to access network shares, see Peer-
to-peer enhancements for more details on configuring this option.Nomad port
access
Nomad uses UDP port 1779, by default, to communicate during the election process
for determining the master on a subnet. The Nomad installer will automatically add
NomadBranch.exe, NomadPackageLocator.exe and
PackageStatusRequest.exe to the list of excepted programs.Manually
configuring Nomad port access
If you do need to open the Nomad port by hand, the following command-lines will
open the firewall for NomadBranch.exe UDP and TCP requests on Windows 7,
provided you run the command with sufficient privileges (you will need to run the
equivalent for the NomadPackageLocator.exe and PackageStatusRequest.exe
executables too):
> netsh advfirewall firewall add rule

name="NomadBranch.exe"
dir=in action=allow
program="NomadBranch.exe"
enable=yes profile=domain
protocol=udp
> netsh advfirewall firewall add rule

name="NomadBranch.exe"
dir=in
action=allow
program="NomadBranch.exe"
enable=yes
profile=domain protocol=tcp
The equivalent on Windows XP is:
> netsh firewall set portopening udp 1779 NomadBranch
Attention
If you change the default port, please ensure all Nomad clients are communicating
using the same port.

This command-line should be run on every machine where Nomad is installed, a

convenient way to do this would be to create a ConfigMgr Package and Program with
the above command line and advertise to all your Nomad machines.Using other
firewalls
If you are using other types of firewall on your systems you will need to open the
Nomad port in these. You should refer to the specific firewall documentation for
details on how to do this.
3.1 PXE Everywhere

If you are also implementing a PXE Everywhere solution using Nomad you will need to follow the PXE
Everywhere v2.1 Prerequisites.

Section 4 - Installation
4. Installation
Before attempting to install Nomad 2012 you should ensure that the Prerequisites have been met.
Here you can view:
Installers provided in the Nomad download zip file

Installation steps for Nomad
Installation steps for the Nomad download monitor
Installation steps for the ConfigMgr Admin Console GUI extensions.

Best practices for upgrading Nomad
Nomad installer properties.
4.1 Nomad Installers

The following tables describe the Nomad installers provided in the Nomad download ZIP file.
For ConfigMgr 2007:
Installer Description
ConfigMgr2007\NomadBranch.msi 32-bit installer for the main Nomad application.
This is used on all instances of the following 32-bit and

64-bit platforms:
Clients
Distribution Points
Site servers
ConfigMgr2007\NomadBranchAdminUIExt.msi Installer for Nomad ConfigMgr 2007 console extensions.

Also installs Nomad Tools for use with OS Deployments.
This is used on all instances of the following:
Site servers
Wherever the ConfigMgr Console is installed
For ConfigMgr 2012:
ConfigMgr2012\NomadBranch.msi 32-bit installer for the main Nomad application.

This is used on all instances of the following 32-bit
platforms:
Clients
Distribution Points.

ConfigMgr2012\NomadBranch-x64.msi 64-bit installer for the main Nomad application.

This is used on all instances of the following 64-bit
platforms:
Clients (see note)
Distribution Points
Site servers
Note
When installing on 64-bit clients, it is required that
the 64-bit ConfigMgr 2012 client is present on the
machines prior to running this installer
ConfigMgr2012\NomadBranchAdminUIExt2012 Installer for Nomad ConfigMgr 2012 console extensions.

.msi
This is used on all instances of the following:
Wherever the ConfigMgr Console is installed
ConfigMgr2012\NomadBranchTools.msi Installer for Nomad Tools for use with OS Deployments

in ConfigMgr 2012.
This is used on on all instances of the following:
Site servers
Nomad Download Monitor:
DownloadMonitor\NomadBranchGUI.msi Installer for Nomad Download Monitor.
PowerShell scripts:
Scripts\PostADSitesandSubnets.ps1 Sample script for populating the ActiveEfficiency

database for the Nomad Single Site Download (SSD) and
High-Availability Peer Backup Assistant (HAPBA)
features.

4.2 Installing Nomad

Installing Nomad
Nomad should be installed on each client computer at a remote branch. The install can be interactive or
silent.
Using the Nomad installer you can perform the following tasks:
Install Nomad Interactively
Install Nomad Silently
Repair the Nomad Service
Uninstall Nomad
License Nomad
After installing Nomad you may also want to install the Nomad Download Monitor and the Nomad Admin
Console GUI extensions.
Note
Before starting the installation you should check and ensure that all the Prerequisites have been met.
Install Nomad interactively

The following headings describe the installer steps for Nomad.
Welcome the first screen in the installer is the Welcome page. Click Next to continue.
License Agreement the License Agreement for the Nomad product must be accepted by clicking on
the I accept the terms in the license agreement option before the Next button is enabled.
License Key enter your license key and then click Next to continue. A default 30-day license key is
provided to allow the easy evaluation of the Nomad product. To run Nomad for any longer period the
product needs to be licensed. The license key should have been provided with your purchase. If this is
not present you can contact 1E Sales to obtain a suitable key. There are three types of licensing available
for Nomad and Multicast.
The standard Nomad license. This provides unlimited use of the standard Nomad functionality.
You will not be able to use multicast, any multicast settings you make in the multicast
configuration page will be ignored.
The Multicast license. This provides unlimited use of both the standard Nomad and multicast
functionality.
The default evaluation license. This provides a 30 day trial period of both the Nomad and
multicast functionality, where multicast is limited to 100 machines.
Setup Type here you select the type of installation you want to perform.
Custom option installer screens

This heading describes the installer screens shown after selecting the Custom Setup Type:
Selecting the Custom option lets you choose the Components you want to install and lets you define
custom settings for multicast, ActiveEfficiency connection and Single Site Download configuration.

Destination Folder - Click Next to accept the default installation directory or click the Change... button
to change this.
The defaults for the Destination Folder for the various systems and installers are shown in the
following boxes:
32-Bit System NomadBranch.msi
C:\Program Files\1E\NomadBranch\
64-bit System NomadBranch.msi

C:\Program Files (x86)\1E\NomadBranch\
64-bit System NomadBranch-x64.msi

C:\Program Files\1E\NomadBranch\

Multicast Configuration - This screen configures the Nomad use of multicast as described below:
Information
This screen will always appear even if you have entered a standard Nomad license without
the Multicast option. If this is the case ensure the No Multicast option is selected and click
Next on the page to go to the next phase of the installation. All machines in a single branch
must be configured using the same setting for this option.
No Multicast this option turns off multicast mode.
Data Only Multicast data refers to the contents of the downloaded Package. Select this
option for standard Nomad Multicast.
Control Only Multicast control information refers to the communications between Nomad
enabled machines, especially the election information.
Control and Data Multicast selecting this option enables the multicasting of both control
and data information
The use of MADCAP is configured by entering the scope description in the MADCAP Scope Name field.
This field is disabled when the No Multicast option is selected. The scope description may be either of
the following formats:
<ScopeName>
where <ScopeName> is the name of a scope defined on the DHCP (if you are using the Microsoft
implementation of MADCAP). You should use this format if you have multiple MADCAP servers.
or
<MADCAP_ServerIP>, <MADCAP_Scope_IP>, <TTL>
where
<MADCAP_ServerIP> is the IP address of a specific MADCAP server.
<MADCAP_ScopeIP> is the IP base address for the multicast defined on the DHCP (if you are using
the Microsoft implementation of MADCAP).
<TTL> (time to live) specifies the number of routers that multicast packets will pass through on
the network.

ActiveEfficiency URL - Here you configure the connection between Nomad and ActiveEfficiency for use
with the Single Site Download and Single Site PBA feature.
The Enable ActiveEfficiency checkbox must first be checked in order to make any configuration
changes.
Once enabled, you must provide a URL to a valid ActiveEfficiency instance in the ActiveEfficiency URL
field.
You can then go through the options for Single Site Download
Option Description
Disabled SSD will be turned off, the Nomad machine will take no part in the SSD
functionality on the site.
Consume SSD will be turned on but the Nomad machine will only fetch downloads
using SSD and will not serve downloads to other machines. This setting
should be used for sensitive servers or WinPE installations.
Provide SSD will be turned on but the Nomad machine will only provide downloads.
Consume + Provide SSD will be turned on and the Nomad machine will both provide and fetch
downloads using SSD.
Ready to Install the Program - Having entered all the appropriate configuration details click Install to
begin the installation.
Typical Option Installer Screens

This heading describes the screens shown after selecting the Typical Setup Type:
Selecting the Typical option configures the installer to install all the components to the local computer.
Ready to Install the Program - Having entered all the appropriate configuration details click Install to
begin the installation.
Install Nomad Silently

Windows Installer enables you to install and configure silently. All the configuration options can be
controlled using the installation switches described below.
To install Nomad silently, execute the following example command-line:
> msiexec /i NomadBranch.msi PIDKEY=ABCD-1234-5678-8765-4321 /qn
where ABCD-1234-5678-8765-4321 is a place holder for a valid license key obtained from 1E.
Information
The Nomad executable will be installed either to "Program Files\1E\NomadBranch" or
"Program Files (x86)\1E\NomadBranch" and the appropriate path will be included on the
PATH variable. The ConfigMgr client is not aware of updates to the PATH until after a machine
reboot.
To install Nomad silently with Nomad FanOut and Single Site Download and features enabled, execute
the following example command-line:> msiexec /i NomadBranch.msi PIDKEY=ABCD-1234-5678-8765-
4321 SPECIALNETSHARE=64 SSDENABLED=3 PLATFORMURL="http://<server>/ActiveEfficiency" /qn
where "SpecialNetShare=64" enables Nomad Fanout and "SSDEnabled=3" along with PlatformURL
information enables Single Site Download feature. "<server>" in the PlatformURL is a place holder for the
hostname/FQDN of a valid ActiveEfficiency Platform server.
The list of available command-line switches can be seen in Installer Switches.

Repair the Nomad Service

In certain valid circumstances it may become necessary to repair the Nomad service. This may occur, for
example, if Nomad program files have been deleted.
To repair Nomad you re-run the NomadBranch.msi or NomadBranch-x64.msi over an existing
installation. This provides the options to Repair or Remove the existing components.
Uninstall Nomad
When uninstalling Nomad you should take the following points into account:
Before uninstalling NomadBranchAdminUIExt.msi, NomadBranchAdminUIExt2012.msi or
NomadBranchTools.msi you will need to close the Configuration Manager Admin Console.
If you are using the Nomad Download Monitor, you should uninstall this prior to Nomad itself.
Before uninstalling the Nomad service you should ensure that there are no running jobs using
Nomad.
To uninstall Nomad use the Add/Remove Programs applet in the Control Panel.
Information
Files which have been retained in the Nomad cache will not be deleted when Nomad is
uninstalled. This is usually a good idea as any .msi files in the Nomad cache may be
required for repair at some point. These must be deleted manually or by running
CacheCleaner.exe -deleteall prior to uninstalling Nomad.

License Nomad
Nomad and Nomad Multicast must be configured with their own unique license key. Please contact Sales
to obtain any keys. Nomad and Nomad Multicast can be licensed in the following ways.
Licensing methods Notes
Using Windows Installer You can enter a valid license key in the interactive Windows Installer setup
interactively wizard when prompted.
Evaluation licenses If you leave the License Key field blank, the product will be installed with a
time limited license for evaluation purposes only. This will give you full
functionality, including Multicast, for 30 days from the date of initial
installation. If you require an extension to your evaluation period, please
contact 1E Sales.
Using the Windows Include the property PIDKEY=<License Key> on the Windows Installer
Installer command-line command-line.
For example, to register the Nomad executable and service you would run the
following command:
> msiexec /i NomadBranch.msi PIDKEY=ABCD-1234-5678-8765-4321 /qn
where ABCD-1234-5678-8765-4321 is the license key you obtained from 1E.
Using the Nomad You can also relicense the product from the command-line:
command-line
> NomadBranch.exe -relicense=ABCD-1234-5678-8765-4321
where ABCD-1234-5678-8765-4321 is the license key you obtained from 1E.
4.3 Installing the Nomad download monitor

Nomad provides an additional Download Monitor that comes with its own installer
NomadBranchGUI.msi. The download monitor is optional. The monitor may be installed in one of two
modes, basic or advanced.
In basic mode the system tray icon only appears when an active download is taking place. Clicking on the
icon displays simple progress bars that show the status of the download. This mode is designed for
environments where users require the ability to see the progress of software downloads.
In advanced mode, the Nomad download monitor can be used for monitoring local machine activity or
used to connect to a remote machine. You can remotely connect to any Nomad client machine receiving a
download providing you have sufficient Remote Activation DCOM permissions on the remote machine.
This mode is designed for Administrators and trouble shooting.
You can install the Nomad download monitor interactively or silently.

Nomad download monitor interactive installation steps

The Welcome Screen - No interaction required here, just click Next .
License Agreement - You should read the license information displayed here and then choose to
continue with the installation by selecting the I accept the license agreement option and clicking on
Next .
Destination Folder - Click Next to accept the default installation directory of C:\Program
Files\1E\NomadBranch\, or C:\Program Files\1E\NomadBranch (x86)\, or click the Browse button to
change this.
UI Mode - This screen configures the complexity of the Nomad download monitor interface. The options
are described below:
Basic displays Progress Bars only.
Advanced displays the current download and status bars, shown in the basic mode, along with
controls to modify the work rate, pause/resume the download and cancel the download.
Ready to Install the Program - Click Next to begin the installation.
Silent Installation
The following example shows how to silently install the Nomad Download Monitor in basic mode:
> msiexec.exe /i NomadBranchGUI.msi /qn
The following example shows how to silently install the Nomad Download Monitor in advanced mode:
> msiexec.exe /i NomadBranchGUI.msi UI=1 /qn
Nomad download monitor installer properties

The following table shows the supported installer properties for the Nomad download monitor:
Property Description
UI Sets the mode for the Nomad download monitor. This may be set to one of
the following values:
Value Description
0 Sets the Nomad download monitor to basic mode. This is the

default value.
1 Sets the Nomad download monitor to advanced mode.
4.4 Installing the ConfigMgr Admin Console GUI extensions

The Admin Console GUI extensions for ConfigMgr 2007 are installed using the
NomadBranchAdminUIExt.msi installer and for ConfigMgr 2012 by
NomadBranchAdminUIExt2012.msi, both provided in the Nomad download zip file. The only option
provided in the installers is to read and accept the license agreement before continuing.
Prerequisites
The prerequisites for installing the ConfiMgr Admin Console GUI extensions are described here.
ConfigMgr OSD tools and configuration files

The NomadBranchAdminUIExt.msi installer also copies six files to the ConfigMgr 2007 OSD directories
and modifies the osdinjection.xml file to add those files to any WinPE image that gets created or
updated. The equivalent for ConfigMgr 2012 is done by the NomadBranchTools.msi. More details can
be found in Nomad WinPE Support .

Installing NomadBranchTools.msi
The only option when running NomadBranchTools.msi is to read and accept the license agreement
before continuing.
The ConfigMgr OSD tools

The OSD tools installed are described in the following table:
Tools Description
NBCacheActions.exe Performs specific functions on the Nomad Cache.
NomadPackageLocator.exe Locates content in local Nomad caches.
TSEnv2.exe Sets environment variables in the Task Sequences.
NomadBranch.exe Nomad service.
SMSNomad.exe Nomad executable.
SnoItfPS.dll Nomad Enterprise COM/DCOM interface.
Upgrading ConfigMgr
Note
If you upgrade ConfigMgr 2012 to ConfigMgr SP1 after installing the ConfigMgr Admin Console GUI
extensions you will need to reinstall the extensions as the upgrade overwrites the osdinjection.xml
and TaskSequenceProvider.mof files.

ConfigMgr with Multiple or Remote SMS Providers

NomadBranch v5.1.xx.xxx and above support custom Task Sequence actions that enable Nomad
functionality to be integrated directly into OSD task sequence actions in ConfigMgr 2007 with remote SMS
Provider or ConfigMgr 2012 with multiple SMS Providers. However, in order to complete installation of the
Nomad Task Sequence actions, the following post installation steps must be performed.
1. Copy the NomadBranch_TSActions.mof from the ConfigMgr site server to a location on the site
system hosting the remote SMS Provider
(typically the file is located on the site server in C:\Program Files\Microsoft Configuration
Manager\bin\X64\NomadBranch_TSActions.mof)
2. On the remote site system run the following from a command shell, making sure there are no
errors:
> mofcomp NomadBranch_TSActions.mof
Note
When using a NomadBranch_TSActions.MOF file, created on one ConfigMgr site server to

support an SMS Provider on another, the SiteCode must be changed. This is because the
installer sets the SiteCode for the machine that it is installed on:
In the following snippets from the NomadBranch_TSActions.MOF file, the %SITECODE%
variables are replaced by the installer
instance of __Namespace { Name = "site_%SITECODE%"; };
#pragma namespace(\\\\.\\root\\SMS\\site_%SITECODE%)
3. Whenever changes are made to a WinPE Boot Image and distribution points are updated, the
OSDInjection.xml controls which files get injected into the boot wim. This file needs to be
updated on the remote SMS Providers to ensure the Nomad binaries are also replaced.
Locate the OSDInjection.xml on the remote provider server (typically located in
C:\SMSPROV\bin\x64\osdinjection.xml)
4. Make a backup of the file before editing it in Notepad

a. Place the following under <Architecture imgArch="i386"> Find the line <FileList
source="SCCM"> and add:
<File name="NBCacheActions.exe">
<Destination>sms\bin\i386</Destination>
<LocaleNeeded>false</LocaleNeeded>
<Source>bin\i386</Source>
</File>
<File name="NomadBranch.exe">
<Destination>windows\system32</Destination>
</File>
<File name="NomadPackageLocator.exe">
</File>
<File name="SMSNomad.exe">
</File>
<File name="SnoItfPS.dll">

</File>
<File name="TSEnv2.exe">
</File>
b. Place the following under <Architecture imgArch="x64"> Find the line <FileList
source="SCCM"> and add:
<File name="NBCacheActions.exe">
<Destination>sms\bin\x64</Destination>
<Source>bin\x64</Source>
</File>
<File name="NomadBranch.exe">
</File>
<File name="NomadPackageLocator.exe">
</File>
<File name="SMSNomad.exe">
</File>
<File name="SnoItfPS.dll">
</File>
<File name="TSEnv2.exe">
</File>

4.5 NomadBranch Installer Properties

NomadBranch Installer Property Categories
The following headings describe the Nomad installer properties associated with each particular area of
functionality available in Nomad:
Basic Nomad Configuration

COMPATIBILITYFLAGS, DEBUG, GENERATEWEREVENTS, INSTALLDIR, LOGNAME, LOGPATH,
MAXLOGSIZE, P2PENABLED, P2PPORT, PIDKEY, SPECIALNETSHARE
Peer Backup Assistant

The following properties relate to the PBA functionality:
ENFORCEQUOTAS, HAACKTIMEOUTMINS, MAXALLOCREQUEST, MAXCONCURRENCY,
MAXIMUMMEGABYTE, POSTCOMPLETETIMEOUTHOURS, PRECOMPLETETIMEOUTHOURS, SSPBAENABLED
Connection and Download

The following installer properties relate to configuring the connection Nomad uses to download packages:
ASSUMEDLINKSPEED, BLOCKSIZE, DOWNLOADTIMEOUT, KNOWNMOBILEDEVICES, MAXPACKAGEFAST,

MAXPACKAGERAS, MAXPACKAGESLOW, PERMITUNCACHED, WLANBLIPSECS, WLANPROFILELIST
Nomad Cache
The following installer properties relate to configuring the Nomad Cache:
AUTHENTICATEDUSERS, MAXCACHESIZEMB, NOHARDLINK, NOMADINHIBITEDADSITES,
NOMADINHIBITEDSUBNETS, PERCENTAVAILABLEDISK
Internet Facing Client

CERTISSUER, CERTSUBJECT
Distribution Point Related

DPNOTAVAILABLECODES, PERMITTEDLSZSHARES, RECYCLEDPDELAY, SIGSFOLDER
Status Message
MAXSTATUSFREQUENCY, STATUSMSGEVENTS
Single Site Features

SSDENABLED, PLATFORMURL
Multicast
MADCAPSCOPE, MAXPACKETSPERSECOND, MULTICASTSUPPORT

NomadBranch Alphabetic Installer Properties

The following table shows the supported Nomad installer properties. Installer properties that use numeric
values must be set using decimal integers on the installer command-line.
Registry Entry Description
ASSUMEDLINKSPEED Specifies a value in bits per second to be used for the link speed
calculations at the beginning of a download. This value should only be
modified if requested by 1E support.
When this value is set to 0, an unreliable IPv4 ping test is performed
to gauge the bandwidth of the WAN link before starting a download.
By default the value is set to 100 so as to disable the ICMP test and
calculate the end-to-end bandwidth based on actual data blocks.
The default value is 100
AUTHENTICATEDUSERS Controls Nomad share permissions.
1 uses Authenticated Users

0 uses Everyone
BLOCKSIZE Integer defining the size of each block of data copied by Nomad in
bytes. Each file is downloaded from the package source folder in
segments of this size.
Must be between 4096 to 65536 inclusive. We recommend
32768 as a minimum amount, and it must be set to this value
when using multicast.
Attention
All Nomad machines in the enterprise must be configured using the

same value for this parameter.
CACHEPATH Location of local package cache. The path will be created if it does not
exist.
If the drive letter does not exist, and it is not possible to create the
specified path, %TEMP% will be used instead.
Default values are dependent on OS.
The default values are:
C:\ProgramData\1E\NomadBranch
C:\Documents and Settings\All Users\Application

Data\1E\NomadBranch
CERTISSUER Defines the client certificate issuer. For use with internet facing
clients, for example, CERTSVR01
Configure either CERTISSUER or CERTSUBJECT.
The default value is ""

CERTSUBJECT Defines the client certificate subject. For use with internet facing
clients, for example, machine.ashby.com
Configure either CERTISSUER or CERTSUBJECT.
COMPATIBILITYFLAGS Configures various compatibility settings. These relate to specific

customer related functionality and should not generally be changed
under normal conditions, unless advised.
Bit Hex Decimal Description
0 0x0001 1 Never check hash values
1 0x0002 2 Enable longer values for

hashes. This value is auto
enabled when the ConfigMgr
2012 client is detected
2 0x0004 4 Calculate CRCs as files are

downloading
3 0x0008 8 Do not start Job Manager in

Alternate Content Provider
mode.
4 0x0010 16 Determines compatibility with

Nomad v3.x caches. Set this
option once all Nomad v3.x
installations have been
upgraded.
5 0x0020 32 Disable all RDC data

generation.
6 0x0040 64 Keep Packages that failed the

CRC test during download.
7 0x0080 128 Prevent computers using

wireless connections from
becoming fill-in multicast
masters.
8 0x0100 256 Include LinkLocal IPv4

addresses.
9 0x0200 512 Include LinkLocal IPv6

addresses.
11 0x0800 2048 Adds users license name to

the key seed.
12 0x1000 4096 Do not automatically jump

from HTTP to HTTPS.
13 0x2000 8192 Always use HTTPS.
16 0x10000 65536 Disable IIS 7.5 filtering

workaround.

17 0x20000 131072 Disable DelegatedLSZ checks

and errors.
18 0x40000 262144 Disable partial download

when App-V streaming, i.e.
download entire application
The installer property must be set to sum of the integer values for the
required bits.
For example, the following installer command-line would disable hash
value checking (1) and DelegatedLSZ checks and errors (131072):
> msiexec /i NomadBranch.msi COMPATIBILITYFLAGS=131073 /qn
DEBUG Sets the debug level.

The following table shows the customer supported values for Debug:
0 0x01 1 Minimal logging.
3 0x08 8 Registry changes.
4 0x10 16 Additional debugging (should

only be used if requested by
1E support).
The default value for this entry is 0x09 (9), which is a combination
of 0x01 (Minimal logging) and 0x08 (Registry changes).
required bits.
For example, the following would set all three supported levels of
debug on the NomadBranch.msi installer command-line:
> msiexec /i NomadBranch.msi DEBUG=25 /qn
DOWNLOADTIMEOUT Sets the timeout in seconds after which a job will be canceled if the
download has not been successful.
This parameter is associated with the DP resilience feature and is used

in conjunction with the RecycleDPDelay registry entry.
If a value greater than zero is set the download timeout will either use
this or the ConfigMgr setting depending on which is the smaller value.
When the timeout has been reached the job Package download will be
canceled and a success will be sent to the ConfigMgr client with the
ERROR_MAXDURATION timeout error sent as the Package status
message.
The default for the timeout is 0 which sets the download to use the
ConfigMgr setting, which has a default of 28 days.

DPNOTAVAILABLECODES This registry entry contains a comma-separated list of error codes

which, if encountered by Nomad during download, cause a retry of the
download using an alternative Distribution Point, as provided by
ConfigMgr.
The default value is 0x205A, 0x205D
For example, the following would set Nomad to the default value on
the NomadBranch.msi installer command-line:
> msiexec /i NomadBranch.msi

DPNOTAVAILABLECODES="0x205A,0x205D" /qn
ENFORCEQUOTAS This value determines whether Quotas are enforced on the PBA share.
Setting the value to 0x1 limits the access to the share using disk
quotas.
The default value is 0x0 (0)
GENERATEWEREVENTS Enables Windows Error Reporting memory dumps to be sent to

Microsoft Winqual. Should Nomad experience an unexpected failure,
the user will be presented with a pop up dialog asking them if they
wish for the debug information to be sent to Winqual. This is then
automatically forwarded to 1E for continued quality improvements.
0 disables this feature.
HAACKTIMEOUTMINS This value sets a timeframe in minutes within which if the machine
running the Task Sequence does not receive an acknowledgement
message from the PBA Host performing the additional backups, the
PBA-HA Task Sequence step will fail.
This setting applies to synchronized backups only and the PBA Host
sends the acknowledgement messages back to the machine running
the Task Sequence approximately every 5% of the synchronized copy.
INSTALLDIR Location of Nomad. The path will be created if it does not exist. This
installation directory should be added to the path or included in the
ConfigMgr Program command line.
The default value is %PROGRAMFILES%\1E\NomadBranch
KNOWNMOBILEDEVICES Set this to a list of mobile devices to restrict delivery of Packages to

only those that contain the --mobok Nomad command-line switch.
The default value is VNClite*,Vodafone*
LOGNAME Location of the Nomad log file. The path will be created if it does not
exist. This value is preserved upon upgrade.

C:\ProgramData\1E\NomadBranch\LogFiles\NomadBranch.log

Data\1E\NomadBranch\LogFiles\NomadBranch.log

The log file name is set by two properties in the installer, LOGNAME
sets the log file name component and LOGPATH sets the path
component.
LOGPATH Location of the Nomad log file. The path will be created if it does not
exist. This value is preserved upon upgrade.
C:\ProgramData\1E\NomadBranch\LogFiles\NomadBranch.log

Data\1E\NomadBranch\LogFiles\NomadBranch.log
The log file name is set by two properties in the installer, LOGPATH
sets the path component andLOGNAME sets the log file name
component.
MAXALLOCREQUEST This value sets the maximum amount of space in MB that can be
requested by each PBA client.
The default value is 0xC8 (200)
MAXCACHESIZEMB Sets the value in bytes for the maximum size the cache is allowed to
grow to, before automatic cache cleaning starts to take place.
Attention
This setting is provided for backwards compatibility only. It is
recommended that PercentAvailableDisk is used for future
implementations.
There is no maximum value for this property.

This method for determining the maximum size of the cache is
provided as an alternative to PercentAvailableDisk:
If PercentAvailableDisk has a value greater than zero set

its method will be used to control the cache size.
If MaxCacheSizeMB is set to a value greater than zero and
PercentAvailableDisk is set to zero then MaxCacheSizeMB
will be used as the method for determining the maximum size
of the Nomad cache.
MAXCONCURRENCY This value sets the maximum number of concurrent PBA sessions that
may be in use on the host.
MAXLOGSIZE Size (in bytes) of Nomad log file. When this size is reached, the file is
renamed with a .LO_ extension and a new .LOG file is created. The
.LO_ file is overwritten each time.
MAXIMUMMEGABYTE This value sets the maximum amount of space in MB that can be used
for all the PBA shares combined on the host.

Setting this value to a non-zero value turns the PBA feature on.
MAXPACKAGEFAST Maximum size (in bytes) of a package that Nomad will attempt to
cache on a Fast LAN (>500 kbps) connection.
This registry entry works in conjunction with the
RunUncachedPermittedFastLAN registry entry.
Attention
This setting is only used in stand-alone mode and does not work
with Configuration Manager.
MAXPACKAGERAS Maximum size (in bytes) of a package that Nomad will attempt to
cache on a RAS (<55 kbps) connection.
MAXPACKAGESLOW Maximum size (in bytes) of a package that Nomad will attempt to
cache on a Slow LAN (55-500 kbps) connection.
MAXPACKETSPERSECOND Used to set the rate at which Multicast will proceed - if packets are
sent too fast then machines will drop packets and Multicast will not be
affective - too slow and Multicast will only work slowly.
MAXSTATUSFREQUENCY This parameter sets the maximum frequency for transfer progress
status messages.
This property works in conjunction with the SMSNomad.exe

command-line switches Nomad command-line switch.
The default value is 3600 (1 hour)
MADCAPSCOPE Configure the MADCAP scope for multicast. This may either of the
following formats:
Format Description
<ScopeName> Where <ScopeName> is the name of a

scope defined on the DHCP (if you are
using the Microsoft implementation of
MADCAP). You should use this format if
you have multiple MADCAP servers.
This method will use the time to live
settings for the specified scope.
<MADCAP_ServerIP>, Where <MADCAP_ServerIP> is the IP

<MADCAP_Scope_IP>, address of a specific MADCAP server.
<TTL> <MADCAP_ScopeIP> is the starting IP
address for a MADCAP scope defined on
the DHCP (if you are using the Microsoft

implementation of MADCAP). <TTL> is the

time to live for the multicast packets.
Attention
Using a TTL greater than 1 is not
recommended unless you have ensured
that MultiCast traffic cannot leak back
upstream through any intervening
routers.
Nomad is also capable of performing
control multicast without a MADCAP server
installation on the network. In order to use
this feature the <MADCAP_ServerIP> should
be set to 0.0.0.0.
For example, the following supports

MADCAP server not being present, with a
scope of 239.0.9.0 and a time to live of 3.
0.0.0.0,239.0.9.0,3
Note
The valid range for TTL is a number
between 1 and 255
The default value is SMSNomad
MULTICASTSUPPORT Defines the behavior of local multicast.
Attention
All machines in a single branch must be configured using the same
value for this parameter.
0 no Multicast.
1 data Multicast. Selecting this option enables the
multicasting of data only (Package contents). Nomad control
communications will be broadcast as normal on the local
subnet. Select this option for standard functionality.
2 control Multicast. Selecting this option enables the
multicasting of control information only. This may be used if
there is more than one subnet in a single location to enable a
single Nomad master to be elected for all the subnets.
3 control and Data Multicast. Selecting this option enables
the multicasting of both data and control information. Select
this option if a branch has multiple subnets connected by high
speed routers.
NOHARDLINK Sets the use of hard links between the Nomad cache and the
ConfigMgr cache.

0 hard links will be used. The Nomad cache will link to the
ConfigMgr cache so only a single copy of a package is held
locally.
1 hard links will not be used. This results in the content
being double-cached
NOMADINHIBITEDADSITES Prevents Nomad from caching data when it is connected to specified

AD sites. This can be used in sites with a local DP.
This is a comma-separated list of each AD site to be inhibited. For
example the following string shows the format for inhibiting three AD
sites called site1, site2 and site3:
site1,site2,site3
NOMADINHIBITEDSUBNETS Prevents Nomad from caching data when it is connected to specified

IP subnets. This can be used in sites with a local DP.
This is a comma-separated list of each subnet to be inhibited in CIDR
notation, as in the following example showing two subnet definitions
separated by a comma:
10.2.0.0/16,192.168.9.0/24
Note
Only IPv4 subnets are supported, not IPv6.
P2PENABLED Controls the peer-to-peer communications used by Nomad. It is

possible to set more than one option at the same time by combining
the bit values.
To enable connectionless P2P in most cases this should be set to

0x0006. Only use this if file and print sharing is turned off.
The following table shows the supported values:
0 0x0001 1 P2P enabled. This is the

default value and should
remain set to allow Nomad to
work correctly.
1 0x0002 2 Enable connectionless P2P

server.
2 0x0004 4 Enable connectionless P2P

client.

3 0x0008 8 Use Net literal names when

connecting to P2P shares.
This causes Nomad to use the
Nomad master's IP address
when connecting to the share
and is recommended when
running wirelessly.
4 0x0010 16 Use FQDN when connecting to

P2P shares. Recommended
when using a multi-forest
environment where
computers from different
forests may be present in the
same subnet. This requires
that reverse lookup for IP
addresses is correctly
configured and running. If
this is not available Nomad
will revert to using the IP
address for connecting to the
P2P shares.
required bits.
For example, the following would set Nomad to use connectionless
P2P on the NomadBranch.msi installer command-line:
> msiexec /i NomadBranch.msi P2PENABLED=6 /qn
P2PPORT Port used to broadcast election messages.
PERCENTAVAILABLEDISK This sets a limit on the Nomad cache. Specified as a percentage of the
available disk space it controls the automatic cache cleaning to ensure
that the cache does not grow to a size whereby the percentage of
available disk space is less than this value.
The value of the registry entry is not altered by using the
PercentAvailableDisk cache cleaner command-line switch, any
settings made there only apply for the duration of the command. If
you want to change the default maximum size for the cache you will
need to change this registry entry by hand.
The default value is 10. The cache will not grow such that less that
10% of total disk space is available.
The maximum value is 80. The cache will not grow beyond 20% of the
total available disk space.
This method for determining the maximum size of the cache is
provided as an alternative to MaxCacheSizeMB:
If PercentAvailableDisk has a value greater than zero set
its method will be used to control the cache size.

If MaxCacheSizeMB is set to a value greater than zero and

PercentAvailableDisk is set to zero then MaxCacheSizeMB
will be used as the method for determining the maximum size
of the Nomad cache.
PERMITTEDLSZSHARES This enables increased security and is only used by the Nomad
Distribution Point agent. It contains a comma-separated list of
Package source locations. Nomad LSZ file generation requests will
only be completed if the content location is listed. If you are using
additional package source locations then you will need to manually
add these to this registry value.
PermittedLSZShares can incorporate wildcard characters to provide
flexible naming convention support.
The default value for this registry entry is:
SMSPKG*$,SMS_DP_SMSPKG*$
which is equivalent to the value:
SMSPKGC$,SMS_DP_SMSPKGC$,SMSPKGD$,SMS_DP_SMSPKGD$
If you leave the registry value blank, no security checks upon package
source location are performed.
The default value is SMSPKG*$,SMS_DP_SMSPKG*$
PERMITUNCACHED Determines where the download Package is run from under certain
conditions.
To ensure that the un-cached mode works correctly you will need to
set the Program Environment Properties to include the Drive
mode/Require drive letter option.
This works in conjunction with MaxPackageSizeFastLAN which will
need to be set to a value greater than zero.
Attention
This should not be set to 1 if you are using Nomad with
Configuration Manager.
0 do not run Package from the Distribution Point.

1 run package directly from the Distribution Point if there is
either insufficient disk space to create the cache, or the
maximum package threshold is exceeded but the connection
is fast (>500kbps).
PIDKEY Set the Nomad license key. This value should be set to a valid license
key obtained from Sales.
The default behavior if this property is not set on the installer

command-line is to generate a 30 day evaluation license key.
There are three types of licensing available for Nomad and Multicast.

The standard Nomad license. This provides unlimited use of

the standard Nomad functionality. You will not be able to use
multicast, any multicast settings you make in the multicast
configuration page will be ignored.
The Multicast license. This provides unlimited use of both the
standard Nomad and multicast functionality.
The default evaluation license. This provides a 30 day trial
period of both the Nomad and multicast functionality, where
multicast is limited to 100 machines.
To set a license key during installation you would use a command
similar to the following example:
> msiexec /i NomadBranch.msi PIDKEY=ABCD-1234-5678-8765-4321
where ABCD-1234-5678-8765-4321 is an example place holder for a

valid license key obtained from 1E.
PLATFORMURL This parameter determines the URL of the ActiveEfficiency web

service, usually of the form http://server/ActiveEfficiency or
http://server:port/ActiveEfficiency depending on how the
ActiveEfficiency Web Service is configured.
If a change is made to the PlatformURL registry entry post-
installation, the NomadBranch service must be restarted.
Note
The PlatformURL parameter does not support HTTPS.
POSTCOMPLETETIMEOUTHOURS This value sets the duration in hours after which PBA share will be
deleted from the host. This value only applies to an PBA share after
the NMDS_COMPLETE command has been run for it, otherwise the
PreCompleteTimeoutHours value will apply.
The intention is that an incomplete share will only be available for a
short period of time, as defined by the PreCompleteTimeoutHours
value; once the NMDS_COMPLETE command has been sent it will be
fixed for this longer time.
When the share is deleted the folder and associated user will be
removed.
The default value is 0xA8 (168)
PRECOMPLETETIMEOUTHOURS This value sets the duration in hours after which PBA share will be
deleted from the host. This value only applies to an PBA share after
the NMDS_POLL command has been run for it, but not the
NMDS_COMPLETE command.
The intention is that an incomplete share will only be available for a
short period of time, as specified in this value.
When the share is deleted the folder and associated user will be
removed.

RECYCLEDPDELAY Sets the delay in seconds for retrying from the first DP after all the
available DPs have been cycled through.
Must be between 600 and 3600 inclusive
The default value is 600 (10 minutes)
SIGSFOLDER This relates to RDC integration and needs to be set on Distribution

Points that are not Primary or Secondary ConfigMgr servers. It must
be set to the folder path for the ConfigMgr signature files. (Wildcards
cannot be used in this value)
For example the following value sets the path to the signature folder
on the C drive:
C:\SMSSIG$
SPECIALNETSHARE This parameter is used to set multiple special feature options for
Nomad. It is possible to set more than one option at the same time by
combining the bit values.
So to use the Machine account for access to the Nomad share, and
have custom share permissions you would set the value for the
SpecialNetShare registry entry to 129 (0x81 hex).
0x0000 0 No special features are turned

on
0 0x0001 1 Custom Share Permissions.

Administrators can configure
and manage custom share
permissions. The service
doesn't create the share
NomadSHR on startup so that
the Administrator can
manually create the
NomadSHR with required
permissions. Also, the share
NomadSHR is not deleted
when the service stops and
therefore existing share
permissions are retained.
1 0x0002 2 Enable support for IPv6. If

the network supports both
IPv6 and IPv4 it is
recommended that you
enable support for both. This
is done by setting bit 1 but
not bit 2.
2 0x0004 4 Disable support for IPv4. If

the network supports only
IPv6 you should disable IPv4
and set both bit 1 and bit 2.
4 0x0010 16 Hidden Share. The Nomad

share is hidden and named

NomadSHR$. When using a

hidden share, all Nomad
installations must be
configured to use this option.
This cannot be used in
conjunction with Custom
Share Permissions ((0x1).
6 0x0040 64 Enable Nomad FanOut

behaviour.
7 0x0080 128 Use Machine Account. The

machine account is used
when connecting to a peer
agent. The SMSNomadP2P&
account is not created. This is
only supported on Windows
XP and above.
12 0x1000 4096 Allows a computer to become

Nomad master even when the
Nomad traffic has been
inhibited by either a VPN,
wireless connection or a
firewall.
13 0x2000 8192 SMB and HTTP Connectivity.

Enables the Nomad agent to
download content from the
Distribution Point using HTTP
or SMB depending on the
content location provided by
ConfigMgr. This parameter
should be used on clients
when following setting has
been enabled on the
Distribution Point(s): Allow
clients to transfer content
from this distribution point
using BITS, HTTP, and HTTPS
(required for device clients
and Internet-based clients):
Allow intranet-only client
connections.
14 0x4000 16384 Web LSZ Generation. Enables

the Nomad Distribution Point
agent to handle LSZ file
generation requests coming
from HTTP/HTTPS enabled
clients. This parameter should
be used on Nomad
Distribution Point agents
when either of the following
parameters are enabled on
the clients: (0x2000) SMB
and HTTP connectivity
(0x8000) Web Connectivity
Only. On enabling this

registry entry, the Nomad

Distribution Point agent
creates a virtual folder called
LSZFILES. The permissions
for this are copied from the
ConfigMgr
SMS_DP_SMSPKGX$ share.
By default, it is assumed that
access to the LSZFILES folder
will require SSL to be
enabled. This is the case for
Internet facing scenarios
where local client access
certificates will ensure
authentication. If you are
using HTTP, instead of HTTPS,
you will need to manually
disable SSL on the LSZFILES
web folder in order for the
Nomad LSZ file generation
process to work.
15 0x8000 32768 Web Connectivity Only.

Enables the Nomad agent to
download content from the
Distribution Point using HTTPs
or HTTP depending on the
content location provided by
ConfigMgr. The Nomad agent
will not use SMB to download
content from the Distribution
Point when this registry entry
is enabled. This parameter
should be used on the clients
when either of the following
settings have been enabled
on the Distribution Point(s):
Allow clients to transfer
content from this distribution
point using BITS, HTTP, and
HTTPS (required for device
clients and Internet-based
clients): Allow Internet-only
client connections.Allow both
intranet and Internet client
connections.
required bits.
For example, to use the Machine account for access to the Nomad
share, and have custom share permissions you would set the value for
the SpecialNetShare registry entry to 129 (0x81 hex).
This is shown in the following NomadBranch.msi installer command-
line:

> msiexec /i NomadBranch.msi SPECIALNETSHARE=129 /qn
SSDENABLED This registry entry determines the status of the Single Site Download
(SSD) feature. It is configured by the installer and defaults to a value
of 0 which sets the SSD feature off.
To turn on SSD post-installation for normal usage you will need to set
both Bit 0 and Bit 1 (0x3).
0x0 0 SSD will be turned off, the

Nomad machine will take no
part in the SSD functionality
on the site.
0 0x1 1 SSD will be turned on but the

Nomad machine will only
fetch downloads using SSD
and will not serve downloads
to other machines. This
setting should be used for
sensitive servers or WinPE
installations.
1 0x2 2 SSD will be turned on but the

Nomad machine will only
provide downloads. In
practice this is unlikely to be
used on its own.
required bits.
For example, the following will turn the complete SSD functionality on.
> msiexec /i NomadBranch.msi SSDENABLED=3 /qn
SSPBAENABLED Configures the use of the Single Site option for PBA data stores.
Value Description
0 Turns Single Site integration for PBA off
1 Turns Single Site integration for PBA on
Note
To turn Single Site PBA feature on you will also need to set
SSDEnabled=0x3 in order to enable ActiveEfficiency integration
required for Single Site PBA feature to work.

STATUSMSGEVENTS Set to a 64-bit value that determines which Nomad events are
reported via ConfigMgr status messages. The full list of events is listed
in Nomad status message events .
WLANBLIPSECS Sets a time for disabling a wireless LAN when a wired LAN connection
becomes available. To enable this feature set the value for
WLanBlipSecs to 20 seconds or more.
WLANPROFILELIST This parameter should be set to a comma-delimited list of SSID profile

names. It enables switching from wireless to wired LAN connections
when the wireless connection's SSID profile name appears on the list
and a wired LAN connection becomes available.
4.6 Upgrading Nomad

When upgrading Nomad we recommend that you follow these general points:
Update all versions of Nomad running on a single subnet at the same time. This will avoid the
possibility of hybrid installations where multiple versions are installed on a subnet making it
difficult to troubleshoot problems.
Update all the Site Servers and Distribution Points first before updating versions of Nomad
running on the clients to avoid known compatibility issues between Nomad clients and
Distribution Points running earlier versions of Nomad.
Upgrade best practices

When upgrading your Nomad system across your entire network, we recommend that you follow these
steps in order:
1. Request a new licence key from 1E Support if you are upgrading to a major release of Nomad
2. Install the latest version of Nomad on all ConfigMgr Distribution Points
3. Install the latest version of Nomad Tools on the site servers and latest version of Nomad Admin
UI Extensions on machines that have the ConfigMgr Console installed
4. Update the source of the ConfigMgr Package / Application used to deploy Nomad on clients with
the latest version of Nomad and re-deploy to the clients
5. Check the Nomad installer logs and Nomad client logs
6. In Task Sequences, check the Install Package / Application step used to deploy Nomad is using
the updated Nomad Package / Application
7. Reapply the Nomad steps used in Task Sequences to ensure latest updates in the Nomad custom
Task Sequence actions are being reflected
8. Update the new license key in "Install and configure Nomad in WinPE" Task Sequence step
9. Update Distribution Points for any relevant boot images
10. Distribute a test package to a subset of clients to ensure Nomad downloads the package
To upgrade from versions earlier than 4.1.100 please contact 1E support for details of the upgrade
process.

Upgrading ConfigMgr
When upgrading ConfigMgr you may need to restart the Nomad service:
Note
If you upgrade the ConfigMgr 2007 client to ConfigMgr 2012 client or the ConfigMgr 2012 RTM client
to ConfigMgr 2012 SP1 client you will need to restart the Nomad service otherwise Nomad will not be
used as the alternate download provider for downloading content.

Nomad Installation Guide

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Nomad Installation Guide

Загружено:

Авторское право:

Доступные форматы

Nomad 2012 v5.2.

100 Installation Guide

Nomad 2012 v5.2.100 Installation Guide Page ii

Key benefits ...................................................................................................... 6

2.2 Nomad Features ................................................................................................ 7

Nomad 5.0 Features ........................................................................................... 7

Nomad 4.0 Features ........................................................................................... 8

3.1 PXE Everywhere .............................................................................................. 16

4.1 Nomad Installers ............................................................................................. 17

4.2 Installing Nomad ............................................................................................. 19

Install Nomad Silently ...................................................................................... 22

License Nomad ................................................................................................ 24

Nomad download monitor interactive installation steps .......................................... 25

Silent Installation ............................................................................................. 25

Nomad 2012 v5.2.100 Installation Guide Page iii

NomadBranch Alphabetic Installer Properties ....................................................... 30

Nomad 2012 v5.2.100 Installation Guide Page iv

1.1 What is new in Nomad 2012 v5.2.100

The main release provides the following features:

Nomad 2012 v5.2.100 Installation Guide Page 5

Click here to find out what is new in Nomad .

Nomad consists of two main components:

Who is this guide for?

Distribute software to home, mobile and remote office users

No new infrastructure or skills required

Nomad 2012 v5.2.100 Installation Guide Page 6

How Nomad works

2.2 Nomad Features

New in Nomad 2012 v5.2.100

The main release provides the following features:

Nomad 5.1 Features

Nomad 5.0 Features

Nomad 2012 v5.2.100 Installation Guide Page 7

Windows 8 and Windows Server 2012 support

Nomad 4.1.100 Features

Nomad 4.1 Features

Nomad 4.0 Features

Nomad 2012 v5.2.100 Installation Guide Page 8

Nomad 2012 v5.2.100 Installation Guide Page 9

Key features of Nomad

Nomad 2012 v5.2.100 Installation Guide Page 10

Nomad 2012 v5.2.100 Installation Guide Page 11

Ensure client side firewalls allow exceptions to be made for

Windows 7 (Embedded*, Professional, Enterprise, Enterprise x64 and

Windows XP 32-bit with SP3 applied

Windows Server 2012

Windows Server 2008 x64 SP1, SP2

Windows Server 2008 SP1, SP2

Systems The following versions of ConfigMgr are supported:

Nomad 2012 v5.2.100 Installation Guide Page 12

NomadBranchAdminUIExt2012.msi (32-bit installer for ConfigMgr 2012

Nomad 2012 v5.2.100 Installation Guide Page 13

The Configuration Manager Admin Console must be installed as is the case

.NET Framework 2 or above

.NET Framework 3.5

Nomad 2012 v5.2.100 Installation Guide Page 14

ActiveEfficiency To support Single Site Download Functionality the following version of 1E

Windows security File and Print Sharing

> netsh advfirewall firewall add rule

> netsh advfirewall firewall add rule

The equivalent on Windows XP is:

> netsh firewall set portopening udp 1779 NomadBranch

Nomad 2012 v5.2.100 Installation Guide Page 15

This command-line should be run on every machine where Nomad is installed, a