Deploy Directly From Server Option
Some explain this to me as I don't completely understand.
We are trying to fix some speed issues at one of our deployment locations. The KACE SDA is housed at one campus and we have a RSA at the other 3 campuses. Each image that I uploaded to the SDA has been pushed to each RSA. Each image was captured and marked as "Deploy Direct from Server" during the capture process.
My question is: What does the "Deploy Directly From Server" option actually do? Does it mean that it processes the install from the SDA rather than the RSA? I'm just wondering if the system is slower than it needs to be because it is pulling the image from the SDA at another campus rather than pulling the upload one on the RSA.
That option debuted on version 5.1.
Before that, every WIM Image, had to be copied as a whole to the Target Device HDD and then applied.
For example, the KACE SDA had to transfer a Single WIM File (10GB), into the C:\ and then proceed to apply it. This caused network issues for some environments.
Direct Deploy was added as an option, and now instead of transferring that huge payload, the KACE will apply\deploy the image directly from the server, streaming pieces of the image through the network. This helps to maintain a good speed and not saturating a single pipe.
Direct Deploys are something SDA and it's RSAs are able to do.