Image Package Replication and Image Deployment moves very slowly, though manual copy is very quick.
Last Updated January 23, 2015
When attempting to deploy an image to a client machine, or when image packages attempt to replicate from the Notification Server to the Site Server, data transfer is extremely slow (<1 MB/sec). However, when the file is copied manually via Windows Explorer or accessing the file via a UNC path, the transfer moves much more quickly.
No error message is shown. Given enough time the process completes, though very slowly.
Find the HTTP (or HTTPS) path to the image package in question. This can be found in the console under the entry for that package, or in the download sources in the Package Server's agent. Put the URL into a browser and attempt to download the package (or parts of the package) through the browser. The download speed will likely mirror the speeds seen during imaging/package replication.
This indicates that there is something active on the Notification Server which is slowing transfer speeds via HTTP (or HTTPS) traffic, while not affect SMB communication (used by Windows Explorer, etc). This can range from a firewall to antivirus.
The source program/process needs to be identified and an exception made for HTTP or HTTPS traffic. While it will not be blocked it is being throttled or actively scanned, which is slowing the transfers. Alternatively, the program/process can be disabled on the Notification Server to allow communication to be accelerated.
Imported Document ID: TECH218354
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe