has anybody else encountered a file size limitation on deploying software? I now have two tasks, both stuck-on-active because the peerdownload system freezes at 59,0 MB (61.888.610 bytes). I don't know how to force it to 'download from core only'.
A little background: I am running two versions of landesk on the same subnet, some old systems are completely 8.7sp3 and talking to the old server, while a dozen or so are 9.0sp2 and talking to a new server (which should become the only one eventually, but it has still not made it out of testing). Usually the mixed environment works fine, but today I am hitting a snag.
The 8.7sp3 systems had no problem whatsoever with a batchfiletask (1.4Gb in about 70 files, standard push without policy) running off of the old environment, installing just fine.
About two hours later, the exact same task is being deployed to the 9.0sp2 systems, from the corresponding core-server with its own storage (identical path and filenames as the 8.7sp3 deployment package, just on a different server). From the logfiles I see the 9.0sp2 clients downloading files from the 8.7sp3 clients, which should be fine - except for the full freeze at 59.0Mb. No errors, task remains active, can't cancel it, can't restart it, can't start other tasks, unless I logon to the client, kill sdclient.exe manually, and restart the machine. Not nice.
Question1 - can I force the clients to download from core only, bypassing the entire peer-download system?
Question2 - shouldn't clients be restricted to only download from peers at the same coreserver? Or, differently put, can I somehow convince peer87 that a file downloaded from landeskserver87 should not be offered to a peer 90 that looks for files on landeskserver90?