Sounds like you've edited your PXE deployment script somewhat ... the default script copies the files from the Core to the client direct, not via a package server.
If you're using a package server for this, you may want to think of re-working your script - to either use something like HTGET or SDCLIENT to copy the files down, as that may be more reliable for you (plus with SDCLIENT you can have the benefit of a log-file as well as pulling files down from HTTP-shares rather than UNC).
LANDesk EMEA Technical Lead
Yes we are using package servers. We have many locations throughout North America and will need to deploy PXE reps to those locations.
We create scripts for those locations to point to their package servers to copy files.
The PXE rep deployment script worked fine before the upgrade and the scripts before and after the upgrade are identical.
We did not want to copy files from the core to remote locations, especially those locations with less bandwidth.
Did something change in 8.8 to affect the REMCOPY command? Is there a way I can test just the REMCOPY command like through a DOS prompt?
1 of 1 people found this helpful
No, you cannot test REMCOPY, since it's essentially a "LANDesk internal" thing between CUSTJOB and the client's LANDesk agent. It's not just a "copy"-command as it were :).
This is why I suggest using what would essentially be a somewhat glorified SDCLIENT-file transfer script instead for this scenario - allows for logging and more reliability for your particular scenario.
REMCOPY per se (and CUSTJOB) hasn't particularly changed in quite a while - it's simply possible that you've got a network hiccup or so. Hence my suggestion (in your case) to go and use SDCLIENT, especially since you can make it more bandwidth friendly and all that :).
LANDesk EMEA Technical Lead.