PDQ Deploy - CS5 Suite "Failed to copy file to target" only to laptops

[DeGrimmy]

Hi all,

 

Since upgrading to Windows 10, we've used PDQ Deploy to push out all of our applications and it's been working well. We're finally getting around to upgrading the laptops we have around school, and we've noticed that our Adobe CS5 suite package keeps failing to deploy. The status in PDQ Deploy says "Failed to copy file to target. The system cannot find the path specified". This has not happened on any of the desktop PCs we've deployed to, we've tested deploying to a desktop PC since the laptops have been failing and the desktops successfully deploy. I've been having to manually copy the files and then run the installer locally.

 

I should mention that everything else deploys successfully to the laptops, it's just the CS5 package!

 

The CS5 suite is set up to include the entire directory in the copy to the PC. We're at a bit of a loss here and we can't figure out why it works to the desktop PCs, but not to the laptops. Has anyone had anything similar? Does anyone have any ideas? Let me know if I can provide more info.

 

Thanks in advance!

Edited December 3, 2019 by DeGrimmy

[MYK-IT]

Can only assume something 'specific' to the laptops is blocking / restricting this from deploying.

 

Could be many things, for example:

 

- Are there any Laptop specific restrictions (GPO / SRP) place? affecting (restricting) deployment?

- VLAN rules - are laptops on a different IP scope / range / different lease period? Perhaps PDQ is attempting to push out to an old IP address? (Could try ipconfig /registerdns on laptops, and/or ipconfig /deploy on PDQ server)

- Is the configured PDQ Deploy / Scan Account valid for both workstations / laptops?

- Check the PDQ Deployment package, specifically 'conditions' - Any applied conditions restricting installation on laptops? (e.g. O/S Version, architecture, PDQ Inventory collection) - Are file paths / variables used (e.g. drive letters, variables) valid for your laptops?

- Check the PDQ logs for further information

[fordea]

We use PDQ Deploy here too. PDQ really relies on your environment having a healthy / up to date DNS. From your description I'm guessing that your laptops may often get different IP addresses and thus multiple entries in DNS until the old records are scavenged. There's an option in PDQ Deploy under Preferences -> Performance called 'Test Multiple Addresses in Name Resolution' that will attempt to ping all addresses for a particular computer name in DNS before deploying. It's worth enabling that and trying to deploy to a laptop again to see if that helps

[DeGrimmy]

Thanks both for your replies! I should mention that every other package in our deployment list deploys successfully, it's just the CS5 package. I've edited my original post.