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
  • Network devices such as Cisco routers may have HTTP/HTTPS packet inspection rules turned on by default which may also interfere with Nomad bandwidth utilization calculations and cause Nomad to back-off unnecessarily.
  • Do you have network optimisation or caching devices?  If so, work with your Network team to determine the configuration.
  • Ensure that all local connected network devices such data switches, network adapters, are using 1Gpbs links. We also recommended that network adapter on clients are using the latest device drivers.
  • Antivirus solutions might be scanning content as it is being transferred through Nomad. It might be necessary to add an exclusion to the SCCMContentLib folders in the Configuration Manager Distribution Points as well as the Nomad and Configuration Manager client cache folders.
  • If the remote Configuration Manager Distribution Points are running Windows 2008 or Windows 2008 R2 Server (Internet Information Services 7 or 7.5) it may need to be configured to session based authentication rather than request based authentication to improve transfer performance. See Microsoft's slow performance blog.
  • By default, Nomad requests 32KB blocks and every request needs to be authenticated which may add to the content transfer time. You can increase the blocksize (4096 to 65536 inclusive) in the registry under HKLM\Software\1E\NomadBranch on all the Nomad clients and Distribution Point.
  • Ensure that the Nomad work rate (the proportion of available bandwidth) is not set too low. The default Nomad work rate is 80 and this should work fine in most environments.
  • Avoiding configuring Nomad P2PEnable registry value to 6 – Connectionless Server and Client expect Nomad enable OSD task sequences.  Connectionless is considerably slower than SMB and HTTP/HTTPS therefore it is not a recommended setting except  when there is a business requirement that all Nomad peer-to-peer communications must use connectionless.
  • Nomad peers performance bottlenecks such as CPU, Memory and Disk I/O.  Outdate hardware might not provide the best transfer performance when large content such as Windows image file is being transferred to local Nomad peers.