We've been using the pull method with DFS w/ replication of installers to be able to use one pdq deploy and inventory setup across multiple buildings.
It has been working great except for "large" deployments where the installer file size (or all included files for the installer) are large (anywhere over a couple hundred MB's). Deployments such as this which work flawlessly with the push method seem to hang for pull method. They sit at "copying" forever until timing out (no % is ever displayed and the machines that are supposed to be pulling have no to little activity on them when it is sitting there). It seems that if the deployment file size is "large" that the clients or for some reason pdq deploy stops the pull copy and hangs.
Is there some limitation of file size hidden somewhere in the pull method?
Please sign in to leave a comment.