Summary

Lists of the current known issues when installing Nomad and using the Nomad features.Please also review Frequently asked questions.

On this page:

Installing 1E Client

IssuesDescriptionWorkaround
1E Client installer adds Nomad registry settings even when Nomad module is NOT enabled while installation. If someone deletes those registry settings and enables Nomad module later, Nomad won't function right.

The installer is currently creating the majority of Nomad registry values because the service doesn’t create them all and Nomad doesn’t tolerate the absence of all the settings that the service doesn’t create. If someone deletes those settings and enables Nomad module later, Nomad won't function right.


In such a scenario, we recommend reinstalling the 1E Client with a new set of properties / transform that enables the Nomad module.

This will be fixed in a future release of 1E Client.

On Windows XP, 1E.Client.log displays a warning "Unsupported OS version. Will not install Nomad." however the very next log lists that "Module 'Nomad' has been installed".Nomad is not support on Windows XP therefore when 1E Client is installed with Nomad module, the module is not enabled, and the Nomad Branch service is not installed.None.
Nomad may be downgraded by active Application deployments in CM, which may cause issues with behaviour of the 1E Client Nomad module.

If there is an active Application deployment in CM of an earlier version of Nomad, clients that have been upgraded with the 1E Client with the Nomad module enabled may be downgraded when the Application Enforcement cycle runs. In this scenario, if the 1E Nomad module is subsequently disabled in the 1E Client, the Nomad service will be removed. This is because once the Nomad module has been enabled, it is not aware nor does it check for older versions. If the Nomad module is subsequently disabled, the service is removed as the Nomad module believes it is not longer required.


To avoid this situation, always define Application Supersedence on the 1E Client Application such that it supersedes any Applications that install previous versions of Nomad (and the 1E Client when introducing new versions of the 1E Client).

To resolve this issue should it occur, first address the Application Supersedence to prevent it from recurring. Then run the following command from the 1E Client installation directory on the affected devices.

1E.Client.exe -reconfigure MODULE.NOMAD.ENABLED=false -restart & 1E.Client.exe -reconfigure MODULE.NOMAD.ENABLED=true -restart

This will disable the Nomad module and remove the Nomad service, then re-enable the Nomad module, which will in turn uninstall the earlier version of Nomad and install the Nomad module. The settings defined by the earlier Nomad install will be migrated - these may differ from the settings with which the Nomad module was initially configured with.

1E Nomad Branch and 1E Client Health services may be stopped if upgrading to Nomad 7.0 if previous version of Nomad installer is no longer in source folder or the Windows Installer cache.

The 1E Client installer stops the 1E Nomad Branch and 1E Client Health services if the Nomad module is enabled. The 1E Client installation completes successfully, after which the Nomad module attempts to uninstall the older version of Nomad. The uninstallation fails as Windows Installer cannot find the original source installer. The Nomad module is not enabled and the Nomad and Client Health services remains stopped.


In this scenario, to immediately restore Nomad functionality simply start the services. To fix completely you will need to remediate the installer source for the old version of Nomad on the affected client, then run the following command from the 1E Client installation directory to restart the 1EClient service.

1E.Client.exe -restart

Uninstalling 1E Client doesn't delete Nomad's P2P server certificate.When P2PEnabled value was set to 79 then NomadBranch server certificate does not get deleted after uninstallation.

Working with Nomad

IssuesDescriptionWorkaround
Nomad crashes while downloading an application in original content having source path greater than 290 length.

When the source path of an application is longer than 290 chars and Nomad starts downloading application in original format (that is format 0) then Nomad crashes in between but successfully downloads the content and passes the hash check as well.

Use Nomad SECure when a package has source path greater than 255 characters in length. Compressing and/or encrypting content results in a single file which the possibility of an overly long path.
PBA find will fail if P2PEnabled registry changes on host machineAfter PBA capture when data is sent to host over https, pause the task sequence and change the value of P2PEnabled=9 on the host machine. On resuming task sequence would get failed. None. This is as per design and so is not suggested to change the value of P2PEnabled in between.
Installer log file may not be launched after installation

In Windows Server 2019 when installation was initiated by the Built-in Domain Administrator and "Show the Windows Install log" option was selected after installation then log file does not get launched. However it works with other admin users.

Initiate the installation from elevated command prompt using /l*v properties to generate the log file, for example:

msiexec /i <installer.msi> /l*v <filename.log>

By default NomadBranchGui is upgraded into Basic modeIf previous version was setup in the Advanced mode and user upgrades it to the latest release then it does not recognize the previous setup mode and so gets upgraded into Basic mode by default.Reinstall NomadBranchGui.
Nomad is not able to download from CCMTOKENAUTH_SMS_DP_SMSPKG$ content location virtual directory on Distribution Point, which is created when Distribution Point is configured to communicate over HTTPS starting CM CB 1810.

Enhanced HTTP was first introduced in CM1806 as a pre-release feature and it became a standard feature in CM1810. It allows administrators to use secure communication between clients and DP without the need for PKI-generated certificates or a Network Access Account.

Nomad currently can’t use the new Enhanced HTTP features when downloading from the DP, but it will continue to work when there are still Network Access Accounts available to allow it to authenticate non-Domain joined machines (such as those in WinPE and Workgroup machines).

None.

We are working with Microsoft to determine the best approach to enabling download from the Enhanced HTTP virtual directory. You can upvote our request at https://aka.ms/AA63jc3

Nomad download halts for some time if block size is different on a machine acting as a master.Nomad may not be able to download whole content from the master and stuck in a loop for some time if the master has incomplete content and different block size.None.
Different block sizes on DP and Clients may leads to RDC failure.RDC may not work properly if distribution point and client has different block size. To fix this, have same block size on all Distribution Points and clients.
Nomad would fail to download content when client switches from Intranet to Internet DP having higher content version.Nomad may fail to download the content when switching from Intranet to Internet DP and Internet DP has higher version of content than required.None.
Nomad fails to use already precached content in secure format even if same content is requested in original format.Nomad won't convert the secure format content into the original format on the client side and downloads the content again.None.
Nomad settings on SCCM client policies don't replicate between CAS and primariesNomad settings do not replicate between CAS and Primary site, the user has to manually do settings on both the sites.Change the settings manually on both sites.
Nomad won't handle SUSPEND by CM when in PauseJobQueue stateWhen Nomad JobQueue is paused using Download Pause and during the pause if CM sends suspend for a job then Nomad won't honor that instruction and would continue to run that job once JobQueue resume.None.
NomadBranch GUI does not work when File sharing is connected with Remote machineWhen NomadBranch GUI is installed on machine and connected to remote machine then it may not show any download progress and remains in paused state.None.
NomadAdminUIExtension always give "stopped working" error but installs successfully on Windows Server 2012.Installing NomadAdminUIExtension on Windows Server 2012 would give error "stopped working" however installs successfully.Ignore the error message and click OK.
Incorrect protocol status download reported in the NomadBranch.log for SMB downloads in SSDThe NomadBranch.log erroneously logs a SMB download as SM_HTTP over SSD.Ignore the error message.
The correct installer may not be picked up by the Install 1E Client custom task sequence action if there are multiple installers in the content source for the Nomad package.The Install 1E Client custom task sequence action randomly selects a Nomad MSI if there are multiple installers in the content source for the Nomad package. We recommend having only one installer in the Nomad package source.
Job fails if disk space is low when compress/encrypted content is uncompressed.For compressed/encrypted content, Nomad reserves disk space equivalent to size of compressed/encrypted content only before download. When disk space is low the, job will fail when it uncompresses the content in the Configuration Manager cache.None.
Status messages are not sent when Nomad runs in WinPE mode.When Nomad is installed in WinPE and starts downloading packages, send status messages are not sent to CM server as it does not have SCCM client.None.
Peer-to-peer transfer fails if one of the machine name is longer than 50 characters.When on a subnet, machine1 has hostname longer than 50 characters with content A, and machine2 requests content A, P2P transfer fails and content will be downloaded from DP.

Do not use hostnames longer than 50 characters.

https://support.microsoft.com/en-us/help/909264/naming-conventions-in-active-directory-for-computers-domains-sites-and 

Attempting to downgrade nomad using SCCM puts the machine in such a state that any further upgrades would fail.When a downgrade is attempted using a ConfigMgr job, the rollback doesn’t happen cleanly and a few traces are left in the system leading to failure in future upgrades. To fix this, please contact 1E support.
Log files may contain a large number of error messages if a mixture of encryption methods is used for Nomad communications.It is possible to configure different installations of Nomad to use different encryption methods. Nomad 6.0 supports two options: the default encryption method and a new FIPs compliant encryption method. The error messages in the log files indicate that Nomad communications are being impacted and the fault should be rectified. 

This state is liable to occur if hybrid installations are allowed with unsupported versions of Nomad, because encryption is required in Nomad 6.0 owards.
You should ensure that all the installations of Nomad are set to the same encryption method.
Clients may not be able to download content using HTTP/HTTPS from the Distribution Point if the content URL contains hidden segments or double-escape sequences.This issue is specific to Distribution Points running IIS 7.0 and above and may occur when the requested content URLs contain hidden segments or double-escape sequences. When this happens the client displays HTTP error 404.8 (Hidden Namespace) and 404.11 (Double Escaping) in the NomadBranch.log file while processing the content.

Modify the IIS Request Filtering settings on the DP to allow download of such content.

Please refer to Post-installation tasks#installationtasks-IISrequestfiltering.

Using Nomad on multihomed machines results in extraneous network traffic.
Please contact 1E Support for a detailed workaround if you have multihomed machines in your environment.
Disk Full error retries with Configuration Manager ClientIf the Nomad job returns with the error Disk Full, the Configuration Manager Advanced Client regards this as a non-fatal error and will retry the deployment on a scheduled basis. None. This is by design.
Nomad Provider Settings overwrite Third party Provider settings in Task SequencesWhen making changes to Nomad Properties for a Task Sequence the settings are written to all the Task Sequence's reference Packages. This does not take into account any third party configurations that may already be in place. To avoid this you should set Nomad Provider settings for each of the reference Packages individually.
Nomad encounters problems when WebDAV is used to connect to a server.

Use of WebDAV is not supported by Nomad.

WebDAV may be present because older versions of Configuration Manager required it, but not any longer.

None. Remove WebDAV from the server. 
Uninstalling and reinstalling Nomad results in unverified cached data.When uninstalling Nomad, cache content is not deleted as files may still be required (for example for Windows Installer repairs). If you subsequently reinstall Nomad on the same machine, Nomad will enumerate the existing cache and will be aware that it has cached content for certain packages. It is not possible to verify that the package content has not been altered in the interim period, therefore these are referred to as zombie packages i.e. they have returned from the dead.


The Nomad client will be able to participate in elections for zombie packages, but will only win an election if other machines do not have verified content. This ensures minimum WAN utilization. Prior to execution, package content is verified by Configuration Manager.

To manually force verification of the cache after upgrading Nomad or uninstalling and reinstalling Nomad, please use the command:

NomadBranch.exe -activateall

If you wish to delete cache content, please use the CacheCleaner.exe utility prior to uninstall.

Nomad fails to download the content, which has one or more empty file (of zero file size), from a cloud distribution point.In this case, Nomad gets stuck in a loop and won't be able to download the content from cloud distribution point due to blocks mismatch errors.None.

Configuration Manager

IssuesDescriptionWorkaround
User cannot go back to Configuration Type page in the Create Nomad Baseline Wizard.If user moves forward with 'Configure settings using MSI Transform' option then he cannot go back to Configuration Type page in the Create Nomad Baseline Wizard without selecting MSI and MST files. A popup would be displayed with message: Please use valid MSI and MST files.Start again.
The Nomad Content Pause feature is not visible in the Configuration Manager console after upgrading the Nomad Admin UI extensions.

5.1When upgrading there is currently a known issue where the 5.1 Enable Tachyon Integration 5.1 setting, on the Nomad Tachyon Integration screen of the NomadBranchAdminUIExt.msi installer, is not picked up from the previous installation. You will need to ensure that this checkbox is checked in the installation wizard or that the ENABLETACHYONINTG=true installer property is set on the installer command-line 5.1if you want the Nomad Download Pause feature to work.

You will need to ensure that this checkbox is checked in the installation wizard or that the ENABLETACHYONINTG=true installer property is set on the installer command-line if you want the Nomad Download Pause feature to work.
The Nomad Content Pause feature is not working after installation.

If the site server does not have a local SMS Provider, the Nomad Branch Admin UI Ext installer does not create the Nomad Custom Role, required Instruction set and add the Nomad Core instructions in Tachyon.

All users require the following permissions to install and use the 1E Nomad Branch Admin Extensions:

  • Local administrator rights on the computer - to install the console extensions
  • Configuration Manager console installed on the computer - to install and use the console extensions
  • Configuration Manager user with Full Administrator rights - to be able to use the Download Pause feature
  • ActiveEfficiency 1.10

    (or later) installed and working - you must know and enter the full URL for the ActiveEfficiency website in the installer

Preparation in Tachyon required to support Nomad Download Pause

The Nomad Download Pause feature requires Tachyon to be installed with some manual configuration steps to create a Nomad consumer, upload some Tachyon instructions and configure permissions to allow CM administrators to execute them. These steps should be completed by a user that has Global Admin role in Tachyon. 

Upgrading

If you are upgrading Nomad or Tachyon and you have previously installed Nomad Download Pause then you can continue using your existing setup, you do not need to do anything further, and you can ignore the steps below. However...

  • You are recommended to rename the instruction set from Nomad Core Instructions to 1E Nomad to match the name used in the steps below for new installations. The renamed set will retain the permissions you previously configured.
  • You can optionally upload additional Nomad instructions included in the 1E-Nomad product pack, which you can download from Tachyon Exchange (tachyonexchange.1e.com/product-packs/1e-nomad).  A list of these instructions is provided below under the heading1E-Nomad product pack, which include the two instructions required by Nomad Download Pause.

In previous versions of Nomad, you were advised not to change the name of the instruction set. This was because the NomadBranchAdminUIExt.msi installer uploaded the instructions into an instruction set named Nomad Core Instructions. From version 7.0.200 onwards, this restriction no longer applies, because the instructions are no longer in the installer, and instead are only available in the 1E-Nomad product pack.

The installation steps below use the Settings app to create the 1E Nomad instruction set and upload instructions for a new installation. However, if you instead use the Tachyon Product Pack Deployment Tool to upload the 1E Nomad product pack, the tool will create an instruction set called 1E Nomad and place new instructions there. If the instruction set Nomad Core Instructions has not been renamed, any existing instructions in it will remain or be updated if they are new versions. You may end up with two instruction sets. You can keep both sets, or you can do the following which will retain the permissions you previously configured:

  • move the new instructions from 1E Nomad to Nomad Core Instructions
  • delete the now empty instruction set 1E Nomad
  • rename the old instruction set from Nomad Core Instructions to 1E Nomad
  1. Download the 1E Nomad Product Pack from Tachyon Exchange (tachyonexchange.1e.com/product-packs/1e-nomad). This will download 1E-Nomad.zip that you will upload to Tachyon in step 7.
  2. In the Tachyon Portal, select Switch App and navigate to Settings > Configuration > Consumers

  3. Click Add to open the Add consumer form
  4. Enter the following values then click Add to create the Nomad consumer

    ParameterValue
    NameNomad
    Consumer URL (optional)leave blank
    Maximum simultaneous instructions100
    Offload target URL (optional)leave blank
    Offload timeout seconds (optional)60
    Use Windows AuthenticationEnable
    EnabledEnable
  5. Navigate to Settings > Configuration > Instructions > Instruction Sets
  6. Click Add new set then enter the Name 1E Nomad on the Add new instruction set form and click Add
  7. Click the Upload button on the top right of the Instruction sets page and browse to the 1E-Nomad.zip file downloaded in step 1. This will upload the Nomad instructions to the Unassigned instruction set. 
  8. Select the Unassigned instruction set, select all the Nomad instructions and click Move
  9. On the Move instructions form, select 1E Nomad as the destination instruction set and click Move
  10. Navigate to Settings > Permissions > Users and add any Configuration Manager users that will need to use the Nomad Download Pause feature. These users will be added to the Nomad Admins role in step 15.
  11. Navigate to Settings > Permissions > Roles and click Add, then enter the Name Nomad Admins on the Add role form and click Add to add the Nomad Admins role to the Roles table
  12. Scroll down the Roles table and click on the Nomad Admins hyperlink then click Add on the Role: Nomad Admins page
  13. On the Add permission form, select Instruction set from the Type drop-down, then select 1E Nomad from the Name drop-down. Select Actioner and click Add
  14. On the Role: Nomad Admins page, select the Management groups tab, click Add, select the All Devices management group and click Add
  15. On the Role: Nomad Admins page, select the Members tab and add any users or groups that will need to use the Nomad Download Pause feature. 

Dynamic packages in Task Sequences sometimes remain in Installing state.When SMSTSNomad is used to download Dynamic Packages, through using the Set Nomad as Download Program action in a Task Sequence, they may remain in Installing state.
Download using Nomad during a Task Sequence occasionally reverts to using the default Configuration Manager download process.When SMSTSNomad is used in a Task Sequence by using the Set Nomad as Download Program action, certain error conditions that would normally be translated to success codes by the list held in the SuccessCodes registry value are instead being returned as failures, thereby causing Configuration Manager to revert to the use of BITS for the transfer when those errors occur.
Task Sequence downloads may failover to using the default Configuration Manager download process if any errors occur during the Nomad download.Due to a problem in Configuration Manager the Always return success option in the Set Nomad as Download Program action is not working. This means that downloads may failover to using the default Configuration Manager download process. You will need to regularly check the Nomad logs to check that this is not occurring in order to address any issues that may have arisen.
The Nomad properties dialog in the Configuration Manager console does not save changed values when focus moves to another tab.Where the Nomad Admin UI extensions are installed, in any of the dialogs in the Configuration Manager console where the Nomad properties appear as a tabbed pane (e.g. in the properties of a package), if a Nomad property is modified but the "Apply" button is not clicked before moving to another tab, the value is not saved and reverts to the original value.Save the values by clicking the "Apply" button before moving to another tab.
Certain issues with Applications in Configuration Manager 1802.Due to the Application model used in Configuration Manager 1802, the following features do not work when using Nomad, Applications and Configuration Manager 1802:
  • Applications are not downloaded using Nomad when they are part of a Task Sequence and the Task Sequence has been deployed with Download all content locally before starting task sequence. To download application using Nomad in a Task Sequence use the Task Sequence action Create Nomad Application Policy
  • Applications referenced in Task Sequences are not available for selection in the Pre stage content using Nomad and Redirect content location to Nomad cache custom Task Sequence actions.
  • Central Multicast is not available for Applications.
  • MaxPackageSizeFastLAN, MaxPackageSizeRAS and MaxPackageSizeSlowLAN parameters are not honored for Applications in Configuration Manager 1802.
  • Remote Differential Compression (RDC) is not available for Applications in Configuration Manager 1802.  This feature is available for Packages, Boot Images and Operating System images.

To download application using Nomad in a Task Sequence use the Task Sequence action Create Nomad Application Policy.

No workarund for other issues.

An exception may be seen when Nomad Admin UI extensions are upgraded and Task sequence editor is immediately launched.A rare exception may occur when Nomad Admin UI extensions are upgraded and Task sequence editor is immediately launched.Launch the Task sequence editor after 30 minutes once the upgrade has completed.
Resume and Pause GUI menu items in CM Console is not available to all users who are Full Admin in CM and assigned to Nomad Admins role in Tachyon.It happens with users who belong to a security group which is Full Admin in CM. The same users should be able pause and resume from Tachyon Explorer app.
Offer ID status message attribute is missing in some of the Nomad Status Messages.The status messages sent by Nomad in case of content download for application and software update deployments, have missing Offer ID attribute.

Multicast

IssuesDescriptionWorkaround
Nomad may not check available disk space in a timely fashion during a Multicast transmission.If a PC joins the multicast session mid-way through, it immediately starts to cache data locally and is not aware of the Package size. This is by design.In environments where disk space is critical this issue is mitigated by:
  • Ensuring that machines have enough disk space prior to sending the deployment
  • Deferring the deployment start time to ensure that a Policy refresh has occurred on all the machines. This enables all the machines to start at same time, and they will therefore check for sufficient disk space.
“Slow sockets” log message.This error message occurs during distributions using multicast if some datagram packets are lost.  Some packet loss is to be expected, especially if a network traffic peak occurs, Nomad is designed to fill in the lost data at the end of the distribution.  If excessive logging of this error message occurs and the statistics are returning a low percentage of data multicast, your network infrastructure may not be suited to efficient multicast. This can occur if you have an infrastructure with mixed network speeds for example.
Using MADCAP over very slow links with pre-cached data.In scenarios with very slow WAN links (i.e. <256kbps) and pre-cached package data, peer copying is used instead of local multicast. If this occurs the following warning message will be displayed in the log file.

WARNING: MADCAP_Request for PACKAGE_ID discarded $$<MCastControl><datetime>

This happens due to the time taken to get a MADCAP address over the WAN. Package data is still shared at the branch and only copied once over the WAN successfully, however local network traffic will be higher as peer copying is used instead of local multicast. 
MADCAP performance can be improved by specifying the MADCAP server IP address in the Nomad MULTICASTMADCAPSCOPE registry value.
Multicast continues after deployment has expired.If the deployment expires during a multicast transmission, the transmission will continue.
Multicast is not supported on FAT file systems.Nomad with Multicast is not currently supported on FAT file systems. This may be addressed in a later version, pending customer feedback.None.

SMSNomad.exe as a program command-line

IssuesDescriptionWorkaround
Using “Start in” Configuration Manager Program property.SMSNomad.exe assumes the working folder is the Distribution Point. If a “start in” location is specified as an Configuration Manager Program property then SMSNomad.exe is unable to locate the package source and fails to distribute software.

Single-Site Downloads

IssuesDescriptionWorkaround
Nomad registers with ActiveEfficiency platform using network interface other than primary interface on multihomed machines.On multihomed machines Nomad may register with a network interface other than the primary network interface. This may result in the machine becoming unavailable for single site download to other machines in the same site since it has registered itself with a network interface other than the intended one.

Nomad Pre-caching

IssuesDescriptionWorkaround
Download may fail for Pre-caching jobs that are setup for content that is still being distributed to distribution pointsDownload may fail for Pre-caching jobs that are setup for content that is still being distributed to distribution points. It is always advisable to setup Pre-caching jobs for content that has been successfully distributed to distribution points.

Office 365 updates

IssueDescriptionWorkaround
Office 365 download does not resume and fails when Nomadbranch service is restarted or when machines resume from a restart or shutdown.

A single Office 365 installation leads to multiple Nomad jobs which follows following this sequence:

- Begin Job .. - End Job - Wait For Next Job - Begin Job .. - End Job - Wait For Next Job ....

If the Nomad service is restarted while waiting for the next job, there is no persisted job (if there is , it picks it up from the WMI). If the Nomad service is restarted between Begin and End, it should pick the persisted job on startup.


NightWatchman may be able to shutdown the machine when an Office 365 job is running.Office 365 updates comes as a collection of multiple jobs. When a job completes and another is yet to start, there is small time gap. During this gap, In between the job, ByteRange job manager queue is empty. If at this time, "Nomadbranch -canshutdown" is triggered, it will return "TRUE".
Corrupt Content is downloaded successfully, transferred to Office 365 cache and update installation succeedsAs Nomad doesn't receive hashes to validate downloaded contents so user can get the corrupted contents downloaded.
ClickToRun stuck in Cancelling Job.. and further install request from Software centre does not triggers any Office JobClickToRun is part of Microsoft office 365 and sometimes it stuck while cancelling a job. Also, each new job is provided and handed over to Nomad by ClickToRun. So if ClickToRun is stuck then user won't be able to proceed further.
While Running cachecleaner command, user faces "Error: CreateInstance-IUIResourceMgr <FAILED> - Class not registered".It is caused by UIResource.dll getting unregistered. So workaround is to run the following command(Administrator user context): "regsvr32 UIResource.dll"
NomadBranch switches "Activateall" and "Activate=(Content ID)" fails to verify Office 365 content in Nomad Cache.Office 365 Cache is activated on Nomad service start up. So if, Manually copied some (Valid) data in Nomad Cache, Service needs restart to activate data. - Activate cmd does not impacts office cache.
Nomad Office Job keeps on going even after reserve space got full.This is happening in a particular scenario and is related to the case when a full file is being downloaded by Nomad office 365 job. As for full file download, the information about content size is not with Nomad so it keeps on downloading.
Nomad Cache refused to clear cache on Peer when other client downloading it from P2P.The behavior is that the ByteRanges content might or might not get deleted depending on whether it's content is being accessed at that point in time or not. If it does get deleted, the Peer move next available peer and if not then move to DP for downloading.
Intermittent issue: Non office job is not cancelling with command line properly.This issue is a randomly occurring one and sometimes when user tries to cancel a job using nomad command line(Nomadbranch -cancel) then sometimes(randomly) the job is not cancelled. User can rerun the command or in rare case restart the nomadbranch service and then rerun the Cancellation command.
Office 365 Update might fail if during download of Office 365 update SMSAgent service is restarted.Office 365 Update might fail if during download of Office 365 update SMSAgent service is restarted. When download of failed job is re-initiated from Software Center the job download fails. Again ClickToRun being stuck in cancelling is causing this issue.
Office 365 Update will sometimes fail if during download of Office 365 update requests a file which does not exist or folder reference does not exist.This issue is specific to "Office 365 Client Update - Current channel(1609-4)" update. Here it is observed that wrong path is being generated in manifest file from Office 365 which results in update failure due to resources not found. All updates prior to this update were generating correct content path in the manifest file but this specific(Latest update by the time of writing this information) the content path is wrong in manifest file. Also this issue is not limited to Nomad alone but even the CM software center triggered and CM managed update download is also failing.
Nomad failed to delete cache with Percent Available disk space value.This issue has two parts to it:
  • Only one content is deleted to reserve the space and not all, whereas it should delete all to make sure percentavailabledisk is 10%.
  • dummyAutoDelete gets added to cache and 1 byte is reserved for it. So when you again run, it won't' even delete one content.

Nomad office updates doesn't support failover to BITS.Nomad is not supporting "Failover to BITS" scenario in this release.

The Nomad Dashboard

IssueDescriptionWorkaround
Export intermittently generates an Excel file format even if PDF or Word is chosen.This is random occurrence, but for most of the time the correct export file format is generated.
Filter fails to list data when applied on Nomad Dashboard tiles when user changes the size of the opened application (CM Console/Supported Browsers)Resizing of the console/browser window results in records listed getting empty in UI.
Dashboard caching metrics of latest deployment shows 100% download on deployment only while no activity was performed on client side.Dashboard in this case is actually showing last download detail and not the current one. This is observed for Software Updates and Applications.
No In progress report of deployment-due to NULL subnet value.When there is no subnet value present, Dashboard is not able to show "In Progress" report in chart: "download progress: latest deployment".
Dashboard Chart showing incorrect portions when a machine has cancelled and restarted a job.This issue is caused by another issue where Dashboard caching metrics of latest deployment shows 100% download on deployment.
Dashboard is showing data older than the configured one.Dashboard is showing data older than the configured one. For example if user configured dashboard to show data for 30 days only, which is also a default number but dashboard will be showing data for older than 30 days.
In Nomad dashboard's "Client version distribution" tile, if user clicks on Missing bar, user may get a JavaScript error.In Nomad dashboard's "Client version distribution" tile, if user clicks on Missing bar, user may get a JavaScript error. The error pop-up depends on the underlying data in AE so not all users may face this problem.
Nomad 7.0 (1E Client 4.1) and above clients do not support Client Version Distribution and Client Health Status tiles in Nomad Dashboard.Nomad 7.0 (1E Client 4.1) and above clients do not support Client Version Distribution and Client Health Status tiles in Nomad Dashboard. The tiles still work well with older version of Nomad Clients, for example 6.3.201 and earlier.
In Nomad dashboard's Caching metric tile may not show result as per the deploymentCaching metric tile gives incorrect result if user tries to redeploy the same Task sequence again and again.
In Nomad dashboard's Content by Type Tile - "Where is my content cached" drill down report gives incorrect information of cached content in case of application deployment.On Dashboard for Application only "Where is my content cached" always will give Count cached is as 0
In Nomad dashboard's Content by Type Tile - "Where is my content cached" drill down report does not populate data in Machine filter.On Machine Filters does not have machine names in case user navigates to "Where is my content" located on Content By Type tile.
Latestdeployment download progress chart shows incorrect results for user collections.Reporting is incorrect in the Nomad dashboard for user collections when the same user downloads content from two or more machines. This event is a rare occurrence.
Client health report would get exported in .xlsx format even when PDF/Word format is selected.Client health extended view reports would not get exported in desired file format. When user choose pdf or doc format, the report always gets exported in xlsx format.

Peer-Backup Assistant

IssueDescriptionWorkaround
Client does not participate in PBA Polling when two clients with the same name exist in two different domains.If a client machine with same hostname name exists in two different domains, during PBA Polling the client does not participate.

Nomad elections

IssueDescriptionWorkaround
Peer replying first in election is elected as Master irrespective of start-up time.

When None of the replying peer is current Master for Given Package and all the replying peers have same weight-age, also all the peers have 100% content for the given package.

During download for the given package Elections is triggered and Peer replying first in election is elected as Master irrespective of start-up time of Nomad service


Nomad shows incorrect logging indicating connection limit is over.When there network disconnection during P2P download over http(s), sometimes incorrect logging appears indicating connection limit is over.
Elections don't correctly honour uptime.When election weight is same on all peers and one of the peer has greater uptime than everybody else then Nomad may not elect the machine with better uptime as master.
In some cases high election weight peer loses election despite same content percentage.When all the peers have almost same content percent then sometimes peer with higher election weight does not win elections.

Nomad and Windows Servicing Assistant

Windows Servicing Assistant (WSA) is a feature of the Tachyon Agent and 1E Client.

IssueDescriptionWorkaround
WSA deployment may restore data, which was captured by a different user.When Replace capture WSA deployment is executed on source machine multiple times, different Nomad PBA Hosts can be honored to capture USMT data each time. During replace restore, target machine can restore any captured USMT data. Nomad PBA doesn't have a notion of version.
TS execution fails as Content is not located in Nomad Cache if Nomad Cache was configured on Custom Drive.If Nomad Cache is configured on the Custom drive then TS execution will fail as content will be searched in the default Nomad location.
WSA Wizard might requests USB drive even when there is enough disk space.Even though there is enough disk space on users workstation WSA Wizard might request for USB drive.
PBA POLL / FIND fails during WSA TS execution.If potential PBA host found during WSA prepareness, goes offline during Task Sequence execution, the TS can fail. Enabling HA can reduce the chances of such failures.