We have 3 sites spread across the globe, connected via VPN, with the PDQ server in the main HQ. Connectively to the remote sites is pretty poor as they are so far away, so characterised by high latency, low bandwidth.
The PDQ repo is sync'd across these sites via DFSR and referenced in PDQ using DFS-N. All deployment packages use the repo variable, so are pushed/pulled from the local repo in each site.
Understandably, deployments and inventory scans in the HQ complete much quicker than in the remote sites. All sites have fast local networks, so the slow performance must be in the time taken to send commands to workstations and retrieve results back.
I'm probably being picking, as most deployments/inventory scans occur on a schedule. But on the occasions where I do these manually, I'm a little frustrated by the time it takes to complete.
Is there something I'm missing? Is there a best-practice approach to remote sites? I appreciate there isn't anything PDQ can do about topology and WAN speeds. I just want to make sure I haven't missed a webinar on this topic.
Please sign in to leave a comment.