Space Index

Total number of pages: 196

0-9 ... 1 A ... 5 B ... 2 C ... 15 D ... 10 E ... 12
F ... 5 G ... 2 H ... 1 I ... 14 J ... 0 K ... 2
L ... 3 M ... 20 N ... 27 O ... 2 P ... 26 Q ... 0
R ... 19 S ... 15 T ... 7 U ... 1 V ... 0 W ... 7
X ... 0 Y ... 0 Z ... 0 !@#$ ... 0    

0-9

Page: 1E WSA Actions
The WSA Actions step is an essential component of the WSA deployment task sequence. Its positioning and configuration within the task sequence is critical to ensuring the task sequence completes successfully. The step performs several different functions

A

Page: Advanced features
Summary Nomad provides a number of advanced features that deal with specific scenarios and enhancements, including: the Nomad dashboard, client health, Office 365 updates, single-site download, peer-backup assistant and Nomad Fanout. These features and m
Page: Alphabetic NomadBranch registry values
The following table shows the supported NomadBranch registry value and any associated installer properties. Installer properties must be upper-case and those that use numeric values must be set using decimal integers on the command-line. Registry value De
Page: App-V support
Summary Nomad supports application virtualization (App-V) applications which are deployed as streamed content by Configuration Manager 2012. On this page App-V support Nomad only handles App-V applications that use Configuration Manager as the App-V serve
Page: AssumedLinkSpeed
This registry value is deprecated. It is no longer used in Nomad 6.3. Instead Nomad now relies only on the actual content being download to gauge link speed. Value (in bits per second) to for the link speed calculations at the beginning of a download. Thi
Page: AuthenticatedUsers
Determines which of the built-in security groups is granted read-only permissions to the Nomad cache. Registry value Default value Notes Installer property AuthenticatedUsers 1 Grants read-only access to the Nomad cache as follow: 0 – Everyone built-in se

B

Page: Basic Nomad behavior in a simple environment
admin_guide_nmd_scenarios.pngIn order to understand how Nomad behaves in a simple environment, we have provided some examples. All the scenarios use the illustrated network setup. The likely scenarios are: Basic Nomad behavior in a simple environment Basi
Page: BlockSize
Value (in bytes) for the minimum size of each block of data Nomad copies from the package source folder. Any change to this value requires a manual service restart before it can take effect. Registry value Default value Notes Installer property BlockSize

C

Page: Cache management
Summary The cache mechanism is essential to Nomad's download once to branch feature. The cache enables Nomad to hold its downloaded content so that it can be distributed locally to other Nomad peers. The Nomad cache contains downloaded content (such as pa
Page: CacheCleanCycleHrs
Determines the number of hours between automatically running the Nomad cache cleaner. Registry value Default value Notes Installer property CacheCleanCycleHrs 0 (turned off) The first automatic cache clean runs randomly between 10 to 60 mins of service st
Page: CachePath
This value holds the location of the base peer backup assistant (PBS) share where user data is copied to. Registry value Default value Notes Installer property CachePath <NomadCachePath>\NMDS This REG_SZ registry value is found under the PBA registry key
Page: CentralMCastExtraDelayMins
An integer value that sets the delay for receiving Central Multicast. Normally you would not need to set this value. Registry value Default value Notes Installer property CentralMCastExtraDelayMins This registry value does not exist until a successful c
Page: CertIssuer
Determines the certificate issuer for the following. SCCM Client certificate used when downloading over HTTPS from internet facing distribution points and when communicating with management points during pre-caching. Nomad Server certificate used to share
Page: CertSubject
Determines the client certificate subject to use when downloading over HTTPS from internet facing distribution points. It is also used when communicating with management points as part of the Nomad pre-caching feature. Registry value Default value Notes I
Page: Client health
Summary Client health is a background service that monitors Nomad clients to ensure that they are running as expected and where it encounters issues, it will attempt a self-heal or remediation. It is installed as a 1E Client Health service and like NomadB
Page: ClientHealth registry values
The Nomad ClientHealth registry values are held under the HKEY_LOCAL_MACHINE > SOFTWARE > 1E > ClientHealth key, as shown in the picture opposite. Client Health Registry.png Each of the registry entries is described in the following table: Registry value
Page: Cloud Support
Summary Nomad now supports the following Configuration Manager on Azure scenarios: IaaS (Infrastructure as a Service) scenario where you host your Configuration Manager infrastructure servers in Azure virtual machines; cloud-based distribution points, whe
Page: Communication ports
Networking From Nomad 6.2, peer copy can be enabled over HTTP (default 5080) or HTTPS (default 5443). You can customize the ports for this feature in the host registry but a change to the default impacts Nomad's peer backup assistant which is used to capt
Page: CompatibilityFlags
Determines different compatibility settings which relate to specific customer related functionality and should not generally be changed from the defauvalue under normal conditions, unless advised. Registry value Default value Notes Installer property Comp
Page: ContentProviderOnWifi
Determines whether a device on a WLAN can become content provider. By default, only devices connected to a LAN can become content providers when using Single Site Download (SSD). This setting is only applicable to SSD and has no effect on P2P content tran
Page: ContentRegistration
Determines if content in Nomad's cache (packages, applications, software updates, boot images, etc.) is registered with ActiveEfficiency. Content registration is necessary if a host is to be available as a Single-site download (SSD) provider or can be wok
Page: Core features
Summary Nomad provides a number of key features that maximize download efficiency in branch network deployment scenarios. It integrates closely with Configuration Manager, assists with WAN link usage efficiency during downloads, copes with different netwo
Page: Create Nomad application policy
This custom task sequence creates a Nomad application policy and is used during an OSD task sequence during the provisioning phase prior to any applications being installed. It uses the NomadPackageLocator tool to enable Nomad to be used as an alternative

D

Page: Debug
The level of messages logged in the Nomad logs for debugging purposes. Registry value Default value Notes Installer property Debug 0x09 (9) See the table below for customer supported values. The default is a combination of 0x01 (Minimal logging) and 0x08
Page: DebugDynamicBlock
The level of messages related to the Dynamic Block Size (DBS) feature logged in the Nomad logs for debugging purposes. This DWORD registry value does not exist by default and must be created under HKLM\SOFTWARE\1E\NomadBranch if you want to enable debuggi
Page: Delete Nomad application policy
This custom task sequence deletes a Nomad application policy previously created using the Create Nomad application policy custom task sequence action. It uses the NomadPackageLocator tool to remove the previously created Nomad application policy. Actions
Page: Deploying Office 365 updates
Summary Configuration Manager introduced support for Office 365 agents in Current Branch 1602. There are no additional steps to perform when you configure Office 365 update deployments and in the way you configure Software Updates and Applications in Conf
Page: Disable Run from distribution point
This custom task sequence is used to revert the task sequence variables set using the Enable Run from distribution point custom task sequence action to their default values. Actions Notes When run, this task: Sets the task sequence to download on-demand.
Page: Distributing software with Nomad and Configuration Manager
Summary Nomad integrates tightly with Configuration Manager, acting as an alternate download provider on a per-package basis for software distribution, per-task sequence or per-site for applications and software updates. The Configuration Manager client r
Page: Download once to branch
Summary Nomad ensures that software packages are only ever copied once per branch over the WAN – utilizing local computers as temporary file caches to distribute the software locally. This reduces the bandwidth required for delivering software updates and
Page: Download resumption and consistency checking
Summary To minimize repeated downloads of the same content from the Distribution Point Nomad supports download resumption and consistency checking. On this page Download resumption Nomad downloads include checkpoint recovery, so if the connection to the d
Page: DownloadTimeout
Sets the timeout in seconds after which a job will be cancelled if the download has not been successful. Registry value Default value Notes Installer property DownloadTimeout 0 This parameter is associated with the distribution point resilience feature an
Page: DPNotAvailableCodes
Determines which error codes will cause Nomad to retry a download using an alternative distribution point. Registry value Default value Notes Installer property DPNotAvailableCodes 0x205A, 0x205D This registry entry contains a comma-separated list of retu

E

Page: Enable Run from distribution point
This custom task sequence can be used in the following instances: In conjunction with the pre-stage content using Nomad action to avoid making a local copy of the Nomad share. It is used during the provisioning phase, prior to any package being installed,
Page: Enabling Nomad on Windows embedded devices
Windows embedded OS provide a subset of the functionality normally available in the standard variants of the OS. These are generally supported with the following caveat: Windows Embedded versions are customizable Windows OS, best suited for embedded or ki
Page: EncryptionType
Determines the type of encryption used by Nomad to encrypt its license key and communications between Nomad peers. Registry value Default value Notes Installer property EncryptionType 0x0 (0) Value are: 0 – standard Nomad encryption 1 – FIPS encryption US
Page: EnforceQuotas
Determines whether Windows Disk Quotas (if configured) are enforced on the PBA share defined in CachePath . Registry value Default value Notes Installer property EnforceQuotas 0x0 (0) Enables quotas to be enforced but requires Windows Disk Quotas to be co
Page: Ex 1 - Nomad 6.3 - Installing the Nomad Components
Installing the Nomad Components In this lab, you will install ActiveEfficiency on the Application server, the Nomad Components on the ConfigMgr server, and the Nomad client on the Distribution Point and the workstations. Install ActiveEfficiency Server Ac
Page: Ex 2 - Nomad 6.3 - Deploying Software using Nomad
Deploying Software using Nomad Nomad can be used to deploy content associated with both legacy Packages and Applications in ConfigMgr. In this lab, you will enable Nomad for Application Management and then observe how Nomad obtains the content when the Ap
Page: Ex 3 - Nomad 6.3 - Deploying Software Updates with Nomad
Deploying Software Updates with Nomad In this lab, you will use Nomad to distribute content for ConfigMgr Software Updates. Deploying Software Updates with Nomad In this exercise, you will enable Nomad for Software Updates and set up a Software Update dep
Page: Ex 4 - Nomad 6.3 - Using Single Site Download and FanOut
Using Single Site Download and FanOut So far, you have observed Nomad with its default configuration where a master is elected in each subnet. This lab environment has been configured to represent two distinct locations (a datacenter and a remote office),
Page: Ex 5 - Nomad 6.3 - Preparing for OS Deployments
Preparing for OS Deployments Preparing OSD objects for use with Nomad In this exercise, you will prepare the existing boot image, create a new package for the ConfigMgr client, and make a copy of the task sequence template that will be used to leverage No
Page: Ex 6 - Nomad 6.3 - Using Nomad for an OSD Refresh
Using Nomad for an OSD Refresh In this lab, you will see how Nomad integrates with the ConfigMgr OS Deployment process to enable workstations to be refreshed in remote locations that do not have a local server. In the next lab, you will extend this to sup
Page: Ex 7 - Nomad 6.3 - Using Nomad for OSD 'bare metal'
Using Nomad for OSD 'bare metal' In the previous lab, you have seen how a Task Sequence is set up to refresh an operating system using Nomad to obtain content locally throughout the build process. In this lab, you will learn how PXE Everywhere enables 'ba
Page: ExtraReplyDelayMs
Time by which PBA peer reply window should be extended to avoid network spikes. When a machine sends a PBA message like POLL all peers do not reply at the same time. They spread their replies out across a time window. This is done to avoid network spikes

F

Page: Feature Reference
Summary This section describes each feature of Nomad, there are two main categories: Core features and Advanced features. In this section
Page: Features by release
New in This maintenance release introduces the following features: Windows Service Assistant (WSA) support - to support WSA a new 1E WSA Actions Task Sequence step has been added. Changes have also been made to the Get Migration Settings, Peer backup assi
Page: FIPS compliant communication encryption
Summary Nomad has always provided encryption for most of its communications. Now, In Nomad version 6.0, an advanced FIPS compliant encryption algorithm has been made available. The United States Federal Information Processing Standard (FIPS) http://en.wik
Page: Frequently asked questions
Summary Answers to some frequently asked questions related to Nomad. On this page FAQ list What happens to the 1E Nomad client during an upgrade? Does it halt its processes? Yes, if a deployment is in place then it can affect the LSZ generation process on
Page: Full control over WAN link usage
Summary Nomad dynamically analyzes the overall WAN traffic to ensure that it only uses a percentage of the total. It uses dynamic block sizes to allow it to take full speed advantage of high-bandwidth links while retaining its low impact on low-bandwidth

G

Page: GenerateWEREvents
Determines whether Windows Error Reporting memory dumps should be sent to Microsoft Winqual. Registry value Default value Notes Installer property GenerateWEREvents 1 If enabled and if Nomad experiences an unexpected failure, a dialog is displayed prompti
Page: Get migration settings
Provides support for encryption in PBA. Also enables PBA to be used for computer replace scenarios. This task can be configured to run under either the capture phase or the restore phase. Its behavior differs depending on which phase it's run under. It is

H

Page: HAACKTimeoutMins
The time-out period in minutes for the Peer Backup Assistant - High Availability (PBA-HA) task sequence action. If a machine running this action does not receive an acknowledgement message within this period from the PBA host performing the additional bac

I

Page: Implementing Nomad
Summary Everything you need to know about getting Nomad installed and running in your network. This section is structured in a way that leads you through a typical implementation project. In this section
Page: Index
Page: Install and configure Nomad in WinPE
This custom task sequence action is used specifically to install and configure Nomad in WinPE – typically done in order to support the use of pre-staged content. Actions Notes When run, this task: Creates the Nomad registry values and sets the parameters
Page: Install Nomad
This task sequence action is used to install Nomad. Actions Notes When run, this task: Reads the NomadinstallPath task sequence variable (set by the Stage Nomad package task sequence) for the location of the installer to run the Nomad installation If an .
Page: InstallationDirectory
The installation directory for Nomad. Registry value Default value Notes Installer property InstallationDirectory %PROGRAMFILES%\1E\NomadBranch The path is created if it does not exist. The installation directory must be added to the path or included in t
Page: Installing and upgrading
Summary How to install, uninstall, licence repair and upgrade Nomad. On this page In this section ActiveEfficiency Supported Platforms If you plan to use any of these Nomad features you must install or upgrade to the latest version of ActiveEfficiency fi
Page: Installing Nomad tools for operating system deployment
Summary A step-by-step guide to installing the Nomad OSD tools. Installing the Nomad OSD tools The tools required for integrating Nomad with OSD task sequences in Configuration Manager 2012 are installed by running NomadBranchTools.msi. These Nomad OSD to
Page: Installing the Configuration Manager console extensions
Summary A step-by-step guide to installing the Configuration Manager console extensions. On this page Installing the Nomad Configuration Manager console extensions In order to enable the Configuration Manager client to interpret Nomad settings and ensure
Page: Installing the Nomad client interactively
Summary A step-by-step guide to interactively installing the Nomad client. On this page Installing Nomad Before attempting to install Nomad please ensure that the Prerequisites are present. The installer MSI used to install Nomad is provided in 32-bit and
Page: Installing the Nomad client using Configuration Manager
Summary A step-by-step guide to installing the Nomad client to all Configuration Manager client machines using Configuration Manager. On this page Using Configuration Manager to deploy Nomad Using Configuration Manager to deploy Nomad to all the Configura
Page: Installing the Nomad download monitor
Summary A step-by-step guide to interactively installing the Nomad download monitor. On this page Installing the Nomad download monitor The Nomad branch download monitor is a tool for observing Nomad activity on either the local or a remote client. Genera
Page: Integrating with WakeUp
Summary Nomad integration with WakeUp enables Nomad to share content from its machines that are holding particular content, even if those machines are shut down. On this page This feature requires an ActiveEfficiency server and a NightWatchman infrastruct
Page: Introducing Nomad 6.3
Summary An overview of Nomad; what it does and how it can benefit your organization. An introduction to the features of Nomad is provided, alongside a high-level explanation of the Nomad architecture. On this page Why use Nomad? Conventional methods of so
Page: IPv6 and DirectAccess support
Summary By providing support for IPv6 environments, Nomad supports distribution to clients connected to the corporate network using the DirectAccess feature. On this page IPv6 and DirectAccess support overview Internet Protocol version 6 (IPv6) is the suc

J

K

Page: Known issues
Summary Lists of the current known issues when installing Nomad and using the Nomad features. Installing and working with Nomad Issues Description Nomad is not able to download from CCMTOKENAUTH_SMS_DP_SMSPKG$ content location virtual directory on Distrib
Page: KnownMobileDevices
This feature is retired. We are currently working on a new feature to replace this which will be made available in a future release. Mobile device connections known to Nomad. When a device running the Nomad client uses a mobile connection whose identifier

L

Page: Licenses
3rd Party Licenses The following are the licenses for the 3rd party components used by Nomad: JSON.NET zlib LZMA SDK
Page: LocalCachePath
The location of local Nomad package cache. Registry value Default value Notes Installer property LocalCachePath %ALLUSERSPROFILE%\1E\NomadBranch\ There are two registry values called LocalCachePath that are used by Nomad. The LocalCachePath REG_SZ registr
Page: LogFileName
The path and filename of the Nomad log file. Registry value Default value Notes Installer property LogFileName %ALLUSERSPROFILE%\1E\NomadBranch\LogFiles\NomadBranch.log The location and name of the Nomad log and preserved when you upgrade Nomad. If Nomad

M

Page: Managing large package distribution with multicast
Summary If you want to make more efficient use of your network when distributing the same data to many end-points, you may want to consider using multicast – it may already be used in your environment for multi-media tasks such as providing video content.
Page: MaxAllocRequest
Sets the maximum amount of space in MB that can be requested by each PBA client. Registry value Default value Notes Installer property MaxAllocRequest 0xC8 (200) Located under the PBA registry key NomadBranch\NMDS. MAXALLOCREQUEST
Page: MaxAllowedLinkSpeed
(Optional setting) If set, defines the maximum possible link speed in bits per second. Registry value Default value Notes Installer property MaxAllowedLinkSpeed 0 If greater than 0, a fixed cap method is implemented where Nomad's bandwidth usage cannot ex
Page: MaxBusyBackOffSecs
The maximum duration (in seconds) that Nomad backs-off between blocks of data. Registry value Default value Notes Installer property MaxBusyBackOffSecs 20 Governs Nomad's multicast and peer-to-peer behaviour. None
Page: MaxCacheDays
When the Nomad cache cleaner runs, delete any application or package content that last triggered Nomad elections before the specified number of days ago. Registry value Default value Notes Installer property MaxCacheDays 0 (turned off) Set to delete appli
Page: MaxCacheSizeMB
Provided for backward compatibility only – use PercentAvailableDisk instead. The value (in bytes) for the maximum size the cache is allowed to grow to, before automatic cache cleaning takes place. Registry value Default value Notes Installer property MaxC
Page: MaxConcurrency
Sets the maximum number of concurrent PBA sessions that may be in use on the host. Registry value Default value Notes Installer property MaxConcurrency 0x3 (3) Located under the PBA registry key NomadBranch\NMDS. MAXCONCURRENCY
Page: MaxDevicesFromAE
The maximum number of devices with the content that Nomad can retrieve from ActiveEfficiency server in one call. Registry value Default value Notes Installer property MaxDevicesFromAE 10 The maximum number of devices (i.e. machines) with the content (pack
Page: MaximumMegaByte
The maximum amount of space (in MB) that can be used for all the PBA shares combined on the host. Registry value Default value Notes Installer property MaximumMegaByte 0 A non-zero value enables PBA share. This registry value is located under the PBA regi
Page: MaxLogFileSize
The maximum size (in bytes) of the Nomad log file. Registry value Default value Notes Installer property MaxLogFileSize 1048576 When the log file reaches this size, it is renamed with a .LO_ extension and a new .LOG file is created. The .LO file is overwr
Page: MaxPackageSizeFastLAN
The maximum size (in bytes) of a package that Nomad attempts to cache on a Fast LAN (>500 kbps) connection. Registry value Default value Notes Installer property MaxPackageSizeFastLAN 0 Works in conjunction with the RunUncachedPermittedFastLAN registry va
Page: MaxPackageSizeRAS
The maximum size (in bytes) of a package that Nomad will attempt to cache on a RAS (<55 kbps) connection. Registry value Default value Notes Installer property MaxPackageSizeRAS 0 MAXPACKAGERAS
Page: MaxPackageSizeSlowLAN
Maximum size (in bytes) of a package that Nomad attempts to cache on a Slow LAN (55-500 kbps) connection. Registry value Default value Notes Installer property MaxPackageSizeSlowLAN 0 MAXPACKAGESLOW
Page: MaxPacketsPerSecond
The maximum rate at which multicast packets are sent. Registry value Default value Notes Installer property MaxPacketsPerSecond 800 Modify this value with caution. If packets are sent too fast, machines will drop packets and multicast will not be effectiv
Page: MaxPreCacheDays
When the Nomad cache cleaner runs, delete any pre-cached content that last triggered Nomad elections before the specified number of days ago. Registry value Default value Notes Installer property MaxPreCacheDays 0 (turned off) Set to delete pre-cached con
Page: MaxStatusFrequency
he minimum interval (in seconds) between sending transfer progress status messages, thereby governing the overall maximum frequency for sending the messages. Registry value Default value Notes Installer property MaxStatusFrequency 3600 Works in conjunctio
Page: MaxSUCacheDays
When the Nomad cache cleaner runs, delete any software updates that last triggered Nomad elections before the specified number of days ago. Registry value Default value Notes Installer property MaxSUCacheDays 0 (turned off) Set to delete software updates
Page: MaxWorkRates
A registry key, that must be created, to hold values for each day of the week where the hourly maximums for the variable work rates are set. Registry value Default value Notes Installer property MaxWorkRates Hourly variable workmates can be set througho
Page: MultiCastMADCAPScope
The MADCAP scope for multicast. Registry value Default value Notes Installer property MultiCastMADCAPScope SMSNomad Values may be set using either of the formats in the table below. MADCAPSCOPE Format Description <ScopeName> <ScopeName> is the name of a s
Page: MulticastSupport
The behavior of local multicast. Registry value Default value Notes Installer property MulticastSupport 0x1 (1) All machines in a single branch must be configured using the same value for this parameter. If you are not using multicast, deploy the Nomad br

N

Page: NMDS_COMPLETE
Peer Backup Assistant (PBA) The NMDS_COMPLETE argument is available on the NomadPackageLocator.exe (recommended) or NomadBranch.exe service argument-line. It indicates that all user data has been copied to the PBA share and the connection can be closed. W
Page: NMDS_DELETE
Peer Backup Assistant (PBA) The NMDS_DELETE argument is available on the NomadPackageLocator.exe (recommended) or NomadBranch.exe service argument-line. When run, it deletes the share, contents and user associated with the shared cache. It is only for use
Page: NMDS_FIND
Peer Backup Assistant (PBA) The NMDS_FIND argument is available on the NomadPackageLocator.exe (recommended) or NomadBranch.exe service argument-line. When run, it locates and connects to the share associated with it. It is only for use in a task sequence
Page: NMDS_HA
Peer Backup Assistant (PBA) The NMDS_HA argument is available on the NomadPackageLocator.exe (recommended) or NomadBranch.exe service argument-line. It creates additional backup copies of the user data that has been copied to the PBA share, so it must be
Page: NMDS_POLL
Peer Backup Assistant (PBA) The NMDS_POLL argument is available on either the NomadPackageLocator.exe (recommended) or NomadBranch.exe service command-line. When run, it places a request for a network share and size associated with it. It must only be use
Page: NoHardlink
Determines whether hard links are used between the Nomad cache and the Configuration Manager cache. Registry value Default value Notes Installer property NoHardlink 0 Values are: 0 – hard links are used. The Nomad cache will link to the Configuration Mana
Page: Nomad 6.3 - Implementing and Using Lab Guide
Lab Guide Multi ExcerptsLab Guide Multi ExcerptsLab Guide Multi ExcerptsLab Guide Multi Excerpts Command Lines and Queries All command lines and queries used throughout the lab exercises are available by accessing the SkyTap Shared Drive shortcut on the d
Page: Nomad client registry values and installer properties
Installer properties usually map to registry values. The following table shows the mappings though there are some that have no corresponding registry values. Installer properties that use numeric values must be set using decimal integers on the installer
Page: Nomad command-line switches
Nomad accepts configuration changes that can be specified on the command-line. The command-line options for Nomad should be denoted using double dashes (--) or double slashes (//) to distinguish them from the main install command-line. For Configuration M
Page: Nomad dashboard Latest Operations tiles
Latest deployment progress tile This tile shows the download progress for the latest deployment. dashboard_tile_deployment download_progress.png To view the progress for a different deployment and is associated packages: Click the Expand icon to run a new
Page: Nomad dashboard Status tiles
These tiles display information about the status of Nomad across your network. Client version distribution tile This tile displays the distribution of Nomad client versions across your environment. The red bar indicates the number of clients that do not h
Page: Nomad Download Pause
Summary Nomad integrates with Tachyon to enable pausing or resuming Nomad downloads throughout the estate. This feature provides a safety measure for situations when a faulty or harmful deployment is made by mistake. In such situations pausing Nomad downl
Page: Nomad FanOut
Summary Windows imposes a limit on the number of concurrent connections on the Nomad share. The FanOut feature compensates for this limitation by enabling peers connected to the master to themselves allow connections to other peers requiring the download
Page: Nomad features
Summary An overview of Nomad features and enhancements. On this page Distributing software with Nomad and Configuration Manager Distributing software with Nomad and Configuration Manager Full control over WAN link usage Full control over WAN link usage Ov
Page: Nomad installer properties
Summary Subject-oriented lists of Nomad installer properties. There are two Nomad installers that have usable installer properties: NomadBranch.msi and NomadBranchAdminUIExt.msi. NomadBranch installer properties The following headings describe the NomadBr
Page: Nomad local multicast
admin_guide_enterprise_downloads_local_multicast_download.pngNomad local multicast is designed to increase the efficiency and scalability of Nomad by allowing the download to be multicast on the branch LAN. This feature is provided in addition to the stan
Page: Nomad package locator command-line switches
NomadPackageLocator.exe is used by the Nomad custom task sequence actions, we recommend that these are used to perform the appropriate functions in preference to the command-line. So this documentation is for completeness only. The format of the NomadPack
Page: Nomad pre-caching
Summary Pre-caching lets you pre-load the Nomad caches of particular machines directly from the Configuration Manager console. This enables downloads to be available on the branch prior to a deployment taking place, which can be very useful in large-scale
Page: Nomad registry values
The two Nomad components that have registry values are NomadBranch and NomadBranchAdminUIExt. We have organized these into features in the sections below. For reference, we also provide a list of registry values and their associated installer properties (
Page: Nomad return codes
The following is a list of the Nomad return codes and their descriptions. This list is subject to change with each release of Nomad, and provided for reference only. Return Code Description Dec Hex ‭-1 0xFFFFFFFF Reserved 1 0x0001 Reserved 112 0x0070 Insu
Page: Nomad SECure
Summary SECure enables content to be signed, encrypted and compressed on the DP which clients can download – content is downloaded according to the data format (0 – original, 1 – compressed or 2 – encrypted+compressed) specified in the client policy. If y
Page: Nomad Upgrade Checklist
The following table provides a quick checklist for upgrading 1E Nomad. Main Step Step Outline 1 incomplete Upgrade ActiveEfficiency 37 incomplete Backup any customizations made to ActiveEfficiency as these will be overwritten during the upgrade 2 incomple
Page: 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. Installer property Description ASSUMEDLINKSPEED AssumedLinkSpeed AUTHENTICAT
Page: NomadBranch.exe command-line switches
The format of the Nomad service command-line is as follows: NomadBranch.exe [options]In contrast to the SMSNomad executable command-line switches, the service uses single dashes before the arguments. NMDS commands can only be used within a Configuration M
Page: NomadInhibitedADSites
Prevents Nomad from calling an election when it is connected to the specified AD sites, meaning that each Nomad client on the listed AD sites will automatically become a Nomad master. This prevents P2P sharing as each master downloads its own copy of the
Page: NomadInhibitedSubnets
Prevents Nomad from calling an election when it is connected to specified IP subnet, meaning that each Nomad client on the IP subnet automatically becomes a Nomad master. This prevents P2P sharing as each master downloads its own copy of the content. Regi
Page: NomadNeverUseSubnets
Prevents Nomad from using specific network adaptors based on the IP subnet. For example, this can be used to exclude Server backup subnets. Registry value Default value Notes Installer property NomadNeverUseSubnets " " A comma-separated list of each subne

O

Page: Operational best practices
Summary Some best practices tips for particular operational situations. On this page The combination of Nomad and Configuration Manager results in a complex set of behaviors related to package downloads and updating. We have some basic recommendations for
Page: OS deployment task sequences
Summary Nomad can integrate with OSD strategies to maximize the efficiency of distributing large OS content across the network. It does this by providing a number of Task Sequence steps that can be integrated directly into your OSD Task Sequences. On this

P

Page: P2P_Port
Port used to broadcast election messages, for connectionless cache access and package status broadcasts. Registry value Default value Notes Installer property P2P_Port 1779 P2PPORT
Page: P2PElectionWeight
Determines the outcome of Nomad elections. Registry value Default value Notes Installer property P2PElectionWeight Must be between 0 and 99. The higher the value, the greater the probability of winning the election. If not set, Nomad uses a default valu
Page: P2PEnabled
Determines how the Nomad cache is accessed. See Peer access to the Nomad cache for more details. Registry value Default value Notes Installer property P2Penabled 9 The default (Hex 0x0009) which enables SMB and NetLiteralNames. You can set more than one o
Page: P2PHttpPort
The HTTP port to use for peer copy. Registry value Default value Notes Installer property P2PHttpPort 5080 Default HTTP port to use for peer copy. If you are using a custom port, ensure that all agents use the same custom port. P2PHTTPPORT
Page: P2PHttpsPort
The HTTPS port to use for peer copy. Registry value Default value Notes Installer property P2PHttpsPort 5443 Default HTTPS port to use for peer copy. If you are using a custom port, ensure that all agents use the same custom port. P2PHTTPSPORT
Page: P2PSslSettings
Determines the type of certificate (self-signed or PKI) to use. Registry value Default value Notes Installer property P2PSslSettings 0 Type of certificate to used while sharing content between peers using HTTPS. Values are 0 – uses a self-signed certifica
Page: Peer access to the Nomad cache
Nomad uses peer-to-peer connections to enable Nomad peers to access the Nomad master's cache via the Nomad share. In Nomad this type of connection is commonly abbreviated to P2P. Due to the complexity of network environments Nomad provides some low-level
Page: Peer Backup Assistant (PBA)
Summary The Peer Backup Assistant (PBA) feature enables files and settings data to be backed-up to a peer computer so that they can be maintained when the computer is being migrated to a new Operating System. Using PBA, you can avoid the cost of specifica
Page: Peer backup assistant Close Nomad PBA data store
This custom task sequence has been replaced by Peer backup assistant Finalize Nomad PBA data store. Existing deployments will still work but you cannot modify them. Going forward, we recommend using its replacement. This custom task sequence action closes
Page: Peer backup assistant Finalize Nomad PBA data store
This custom task sequence action is used to close the connection to the PBA data store after user state is saved with USMT Capture User State. Peer backup assistant Finalize Nomad PBA data store replaces the Peer backup assistant Close Nomad PBA data stor
Page: Peer backup assistant High-availability
This custom task sequence is deprecated and you should use the Peer backup assistant Finalize Nomad PBA data store task sequence instead. Existing deployments will still work but you cannot modify them. Going forward, we recommend using using its replacem
Page: Peer backup assistant Locate existing Nomad PBA data store
This custom task sequence action is used to find saved user data, prior to restoring user state using USMT Restore User State. The Peer Backup Assistant: Close Nomad PBS Data Store and (usually) OS refresh or OS install on bare metal actions must be run f
Page: Peer backup assistant Provision Nomad PBA data store
This custom task sequence action is used to provision a PBA data store prior to saving user state using USMT. It is the first step of the Peer backup assistance sequence (USMT Capture User State follows). PBA supports the use of multiple backup data store
Page: Peer backup assistant Release Nomad PBA data store
This custom task sequence action is used to release saved user data in the Nomad cache, after restoring user state with USMT Restore User State. The USMT Restore User State action must have been run successfully. Actions Tasks When run, this task: Deletes
Page: Peer copy over HTTP or HTTPS
Summary Historically, Nomad content distribution required File and Print services to be enabled in order for it to share the content. From version 4, you could bypass these services and use the connectionless transfer protocol over the User Datagram Proto
Page: PercentAvailableDisk
The 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. Registry
Page: PermittedLSZShares
Restricts Nomad LSZ file generation requests to a list of permitted package source locations. Registry value Default value Notes Installer property PermittedLSZShares SMSPKG*$ SMS_DP_SMSPKG*$ A list of comma-separated package source locations. Enables inc
Page: PlatformURL
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. HTTP and HTTPS protocols are supported. Registry value
Page: Post-installation tasks
Summary Post-installation tasks that may be necessary to ensure that Nomad will work correctly in your environment. You may need to make some post-installation configurations to your environment to ensure that Nomad works effectively. There are two areas
Page: PostCompleteTimeoutHours
The duration (in hours) after which the PBA share is deleted from the host. Registry value Default value Notes Installer property PostCompleteTimeoutHours 0xA8 (168) Only applies to a PBA share after the NMDS_COMPLETE command has been run for it, otherwis
Page: Pre-stage content using Nomad
This custom task sequence action is used to pre-stage content using Nomad either in WinPE or a full Microsoft Windows operating system. It uses the NomadPackageLocator tool to locate any locally available copies of content, as set in the References in the
Page: PrecachePollBatchSize
The number of notifications a client processes in one pre-cache poll cycle. Registry value Default value Notes Installer property PrecachePollBatchSize 20 Range is 1 to 500. If the value is greater than 500, it defaults to 500. If you set the value to 0,
Page: PrecachePollMinutes
The interval (in minutes) between Nomad polling ActiveEfficiency for new pre-cache jobs. Registry value Default value Notes Installer property PrecachePollMinutes 0x5A0 (1440) Nomad clients normally start their polling cycle when the service starts-up, wi
Page: PreCompleteTimeoutHours
The duration (in hours) after which PBA share is deleted from the host. Registry value Default value Notes Installer property PreCompleteTimeoutHours 0x3 (3) Located under the PBA registry key NomadBranch\NMDS, it only applies to a PBA share after the NMD
Page: Preparation
Summary What you will need to prepare in advance of implementing Nomad in your network. Typically these are tasks that may take some time, depending on how your organization works. A more complete checklist of tasks is provided in Prerequisites. On this p
Page: Prerequisites
Summary A checklist of infrastructure prerequisites and dependencies that most organizations would require in order to install Nomad. On this page Installation account permissions Installer Rights required Nomad agent: NomadBranch-x64.msi, NomadBranch.msi

Q

R

Page: RecycleDPDelay
The delay (in seconds) before restarting retries from the first DP after the whole list of available DPs have been tried. Registry value Default value Notes Installer property RecycleDPDelay 600 It is associated with the distribution point resilience feat
Page: Redirect content location to the Nomad cache
This action is deprecated and is currently provided for backwards compatibility only, Use Pre-stage Content Using Nomad instead. This custom task sequence action was used to redirect the task sequence's content location to the Nomad cache on another host.
Page: Reference
Summary All reference material for . All the list and table type information, such as installer properties in alphabetical lists etc. In this section
Page: Release notes
release notes - last updated These release notes contain late-breaking information about Nomad. For the most up-to-date information, see the online release notes http://help.1e.com/display/NMD63/Release+notes and known issues http://help.1e.com/display/N
Page: Relicensing Nomad client
Summary The Nomad client must be licensed during the time of the initial installation or upgrade. There are three types of Nomad client license: Subscription - this type of license expires after the subscription period and must be renewed Project Based -
Page: Remote differential compression integration
Summary Not only is Nomad aware of the file level differences between different versions of a package so that only changed files are downloaded, it is also aware of the differences within individual files. This is sometimes known as binary differential re
Page: Resolving common issues
The most common issues are listed below. Late-breaking information can be found in the online Help. Communication issues From Nomad version 6.0, there are two methods for encrypting its communications. The default is compatible with earlier versions; the
Page: Resolving content integrity (hash checks) issues
How integrity checking works When an LSZ request is made and the request contains a hash, Nomad on DP computes a corresponding hash for the content on its disk. If the computed hash does not match the hash sent by the client, the content is considered cor
Page: Resolving dynamic pre-caching issues
Content not available on client machines If you find yourself in a position where content is not available on the client machine, take the following steps to validate the job. You will need: Access to the SQL server where the ActiveEfficiency database is
Page: Resolving hard link issues
Hard Links A hard link is the file system representation of a file by which more than one path references a single file in the same volume. To create a hard link, use the CreateHardLink https://msdn.microsoft.com/en-us/library/aa363860(v=vs.85).aspx func
Page: Resolving Nomad client health issues
Client Health Client Health is a Nomad feature which monitors the health of Nomad clients installed on DPs and client machines. It runs 13 checks for different resources and components and if it discovers something that is not running as expected, it atte
Page: Resolving Nomad Dashboard issues
You may come across different issues at different times when you working with the Nomad Dashboard. Some of the common errors are Error 500 The Nomad Dashboard, Nomad Sync and Nomad Pre-cache features rely on an SQL linked server connection between the Act
Page: Resolving Nomad peer election issues
There can be multiple reasons why a Nomad peer computer is disqualified from elections (and therefore unable to provide content to the requesting computer). It can be caused by mis-matched Nomad settings or network issues (such as the client firewall not
Page: Resolving PBA issues
The state of the Nomad log when PBA is working Peer Backup Assistant: Provision Nomad PBA Data Store PBA process typically starts with provisioning the Nomad data store to find the OSDStateStorePath variable to let the task sequence know where to store an
Page: Resolving peer copy over HTTP or HTTPS issues
How it works On start up, the Nomad service starts the HTTP server logs a list of URLs it listens to. Untitled 9.png When any Nomad agent wants to download content, it does an election and identifies a machine which has content in its cache (the Master ma
Page: Resolving remote differential compression issues
Things to note when working with RDC On Configuration Manager 2012, RDC will not be used for Applications. This is because an Application's content version always remains at 1, only the content revision gets updated with a new content ID and hence RDC for
Page: Resolving slow content transfer issues
Things that may cause slow content transfers If you encounter slow content transfers, we recommend you check the following: WAN accelerators can sometimes interfere with Nomad bandwidth utilization calculations making Nomad to back-off unnecessarily Netwo
Page: Restore Nomad cache
This custom task sequence action is used to restore the Nomad cache in the new Operating System during provisioning after Nomad has been installed. It only needs to be run if Save Nomad Cache is run prior to applying the new Operating System. The Nomad in
Page: RunUncachedPermittedFastLAN
Determines where the download package is run from under certain conditions. Registry value Default value Notes Installer property RunUncachedPermittedFastLAN 0 Works in conjunction with MaxPackageSizeFastLAN (which needs to contain a value value greater t

S

Page: Save Nomad cache
This custom task sequence action is used to save the Nomad cache either in WinPE or a full Microsoft Windows operating system. It copies, links or moves previously downloaded content to the protected task sequence runtime folder so that it is not deleted
Page: Secondary PBA backup data store
Support for this configuration is deprecated and is currently provided for backwards compatibility only. Use high-availability PBA instead. The PBA task sequence dialogs do not support this option, therefore some scripting would be required to achieve the
Page: Server sizing
Sizing and deployment considerations For optimum performance, we recommend the following: For a single-server deployment: ae_vms_single1.png Number of machines 5,000 25,000 50,000 Benchmark configuration Maximum downloads per hour 5,000 12,5000 25,000 Act
Page: Set Nomad as download program
This custom task sequence action is used to set SMSTSNomad.exe as the download program during a task sequence. This is accomplished by setting the SMSTSDownloadProgram task sequence variable to SMSTSNomad.exe.We recommend that this is the first action to
Page: SigsFolder
The path to the Configuration Manager signature files. Registry value Default value Notes Installer property SigsFolder C:\SMSSIG$ Relates to RDC integration and must point to the folder where the signature files are held for Configuration Manager. Wildca
Page: Single-site download
Summary Nomad's single-site download (SSD) feature ensures a download across the WAN only happens once per site. It does this by maintaining information about which subnets are neighbors of each other (accessible on LAN rather than WAN), so that when an e
Page: SMSNomad.exe command-line switches
The format of the Nomad command-line is as follows: SMSNomad.exe [switches] InstallCommandLine Where InstallCommandLine is the command-line required for the target installation. For example: SMSNomad.exe --wr=20 setup.exe SMSNomad.exe msiexec.exe /i insta
Page: SpecialNetShare
Sets various special feature options related to the Nomad share. Registry value Default value Notes Installer property SpecialNetShare 0 You can set more than one option at the same time by combining the bit values. For example, to have custom share permi
Page: SSDEnabled
Enables single-site download. Registry value Default value Notes Installer property SSDEnabled 0 If your network is running over a WLAN or have devices on a wireless network you want to be content providers, modify ContentProviderOnWifi=1. You can set mor
Page: SSPBAEnabled
Enables the use of single-site functionality for PBA data stores. See single-site peer backup assistant for more details. Registry value Default value Notes Installer property SSPBAEnabled 0 Has a dependency on the ActiveEfficiency PlatformURL. Values are
Page: Stage Nomad package
This custom task sequence downloads the Nomad package and is typically done in full OS in order to support the Install Nomad task sequence action. Actions Notes When run, this task: Downloads the Nomad package and sets the path in the task sequence NomadI
Page: Status messages for download events
Nomad can send status messages through Configuration Manager based on specific download events which appear in its deployment status. On this page These messages are controlled by the StatusMsgEvents registry value. This is a REG_SZ string data type and t
Page: StatusMsgEvents
Determines which Nomad events are reported via Configuration Manager status messages. Registry value Default value Notes Installer property StatusMsgEvents 0x0 Status messages for download events Status messages for download events The Nomad Dashboard Cli
Page: SuccessCodes
A list of Nomad return codes that are translated as success to the Content Transfer Manager (CTM) component of the Configuration Manager client. Registry value Default Notes Installer property SuccessCodes 0x206b, 0x2077, 0x103, 0xffffffff, 0x1, 0x70, 0x2
Page: Supported Platforms
Infrastructure prerequisites Category Product Notes Supported OS SELECT '* ' + os + CHAR(10) FROM [release] AS r INNER JOIN [product] AS p ON r.product_id = p.product_id INNER JOIN [version] AS v on r.version_id = v.version_id INNER JOIN [status] AS s on

T

Page: Technical support for Nomad
For customers with a maintenance contract Log-in to the 1E Support Web portal https://1eportal.force.com/s/ with the credentials from your maintenance contract – it provides issue tracking, product hotfixes and knowledge base articles for each product. B
Page: The Download Monitor
Summary If you installed the Download Monitor in basic mode, you will only see progress bars in the UI – useful for those who only need to see the status of the downloads. If you installed it in advanced mode, you will see an extended UI – useful for admi
Page: The Nomad Baseline Wizard
Summary The Nomad Baseline Wizard is used to create a Configuration Manager Baseline from the Configuration Manager console for settings related to Nomad and Client Health. On this page The Nomad Baseline Wizard Baselines are used in Configuration Manager
Page: The Nomad Dashboard
Summary The Nomad Dashboard is a collection of interactive tiles made available in the Configuration Manager console that provides you with a global view across your network of Nomad status and latest operation details. For the dashboard to function full
Page: The Nomad share
The Nomad cache is configured as a share that enables peer-to-peer distribution of downloaded content. Nomad provides control over the accounts that have access to the share and also provides an advanced Nomad FanOut mechanism that can overcome the connec
Page: Training
Summary Lab guides used in conjunction with the Nomad 6.3 training courses. Available training for This page provides links to the available training on. To access the training follow this link and select the course relevant for you and the version requir
Page: TSEnv2 command-line switches
TSEnv2 is an executable that can be used primarily to set or change task sequence environment variables (including "readonly" variables, those starting with an underscore, which cannot be changed with ConfigMgr's tsenv,exe tool), but it also has other rel

U

Page: Upgrading Nomad
Summary A step-by-step guide to upgrading 1E Nomad. This page describes how to upgrade to the latest version of the 1E Nomad suite (comprising ActiveEfficiency, PXE Everywhere and 1E WakeUp - all included with the purchase of Nomad) within the Configurati

V

W

Page: WakeUpBatchSize
The maximum number of machines to wake up in a single call. Registry value Default value Notes Installer property WakeUpBatchSize 10 Sets the maximum number of machines to wake up in one call, for subnet and site separately. (So up to twice this number of
Page: WakeUpEnabled
Enables WakeUp integration, see Integrating with WakeUp for more details. Registry value Default value Notes Installer property WakeUpEnabled 0 Determines the status of the WakeUp integration. If configured by the installer, it is disabled (0) by default.
Page: WakeUpMinPackageSizeMB
The minimum size of content (in megabytes) that will cause a request for a wakeup. See Integrating with WakeUp for more details. Registry value Default value Notes Installer property WakeUpMinPackageSizeMB 1024 Any content below this size is downloaded fr
Home page: Welcome
Welcome to the documentation space. Here we describe all aspects of configuring and using Nomad. Here is a quick overview of what the Nomad documentation pages will tell you. _Copyright
Page: WLanBlipSecs
The duration for temporarily disabling a wireless LAN when a wired LAN connection becomes available. Registry value Default value Notes Installer property WLanBlipSecs 0 For wireless stability, the value must be 20 seconds or more. WLANBLIPSECS
Page: WLanProfileList
A list of wireless SSIDs to enable switching from wireless to wired LAN connections. Registry value Default value Notes Installer property WLanProfileList A comma-delimited list of wireless SSIDs (* for any all) which enables Nomad to switch form wirele
Page: Working with Nomad
Summary How to administer, use and maintain Nomad, including: some typical worked scenarios, a feature reference organized into core and advanced features, operational best practices and frequently asked questions. In this section

X

Y

Z

!@#$