This really depends on the full command that's being sent. The character limit has not changed, even in our latest 9.5 SP2 release.
The failures are always occurring on the download. The biggest problem I am having is with the Adobe applications. They tend to have many nested paths and long file names.
The root of my storage for these install sources is 40 characters long. Some of the paths are 260 characters or more which would still fail if I somehow cut out the root path, so modifying the share name is not an option.
How can I determin what the full command that is being run is?
Is there any other way that I can deal with this situation to get the Adobe installers and other similar ones to replicate?
Thanks for your help.
When do you plan to correct it ?
I can't use Content Replication since we bought LANDesk (9.0 SP2)
Robocopy in a cmd script is more reliable
Vincent, this 260 character limit is a limitation of the Microsoft Windows API so it's not something we can correct. There are a couple enhancements being looked at which would have the command line just call a scripted copy or an XML with the full copy paths. Hopefully that logic becomes part of a future release as I know this limitation is frustrating.
David, you should be able to see the full length of the command looking at the servicehost.log in the Landesk\SharedFiles directory on the client. If it's not feasible to shorten the path then I would suggest scripting the copy using Robocopy similar to what Vincent is doing.