Resolving slow content transfer issues
If you encounter slow content transfers, we recommend you consider the following:
Consideration | Notes |
|---|---|
WAN accelerators | WAN accelerators can sometimes interfere with Nomad bandwidth utilization calculations making Nomad to back-off unnecessarily. |
Cisco routers | 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. |
Network optimization or caching devices | Do you have network optimization or caching devices? If so, work with your Network team to determine the configuration. |
Local connected network devices | Ensure that all local connected network devices such data switches, network adapters, are using 1Gpbs links. |
Network adapter device drivers | We also recommended that network adapter on clients are using the latest device drivers. |
Antivirus solutions | 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. |
Blocksize | The default blocksize for Nomad 7.0 (and later) is 128KB. The default for earlier versions is 32KB. Every block needs to be authenticated, which may add to the content transfer time. Please refer to BlockSize page for more information. |
Nomad work rate | 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. |
P2PEnable | 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. |
Outdated hardware | Nomad peers performance bottlenecks such as CPU, Memory and Disk I/O. Outdated hardware might not provide the best transfer performance when large content such as a Windows image file is being transferred to local Nomad peers. |