Peter - We don't believe any functionality itself will be lost. As I said, we are using robocopy to do the exact same thing to keep all of our pxe reps up to date. The problem is that both of us are using a 'work around'. Any time we take our employees through the training (LANDesk boot camp) or reference the LANDesk documentation, they are instructed to re-deploy the agent as the process LANDesk intends us to use. This fails to deploy.
We are not looking for a work around, we have that and I appreciate your offering up the script. What we are looking for is to have LANDesk fix the proper process they have documented and are instructing their customers to use, especially now seeing other customers that use the same process are also having the same problems we are. The forum post was to query anyone else having the same problem and validating it's not unique to our environment. Our environment should not break when following LANDesk documented procedures like this.
Are you guys using the script simply to save bandwidth? Or were you guys also having problems with re-deploying the agent?