I have two questions. One question is about multicasting and how it works. The second question is about deploying an image where the size doesn't match up.
Question 1:
I have researched and I think I have an okay understanding of how the multicasting works...correct me if I am wrong.
If I need deploy an image to 30 machines that's about 80GB, the NS server will find a computer that will be a MASTER. Once ALL 30 machines connect, or when the timeout runs out, the NS server would then push the 80GB image to the MASTER PC and the other PC's would pull its image from the MASTER PC...correct? If this is the case, I would find this to be...slow since the PC might not be able to handle that many machines but a server would be able to handle it better I would assume so. It seems like it takes a LONG time when deploying a lab and it seems some PC's fail when obtaining the image...at least 3-7 machines. I would think that having a "torrent" type of technology that would have the machine grab a file from random machines or the server would be faster. I know the .gho is ONE file, but I would think splitting them up and being able to distribute them in that fashion would be more effective. Am I wrong in this assumption about the MASTER?
Question 2:
Whenever I deploy an image, it seems it tries to push the FULL 300GB file even though the image is actually 80GB. Is there a reason why the size is different, or a way I can ONLY force the actual image and not the entire HD that was captured before? The image eventually pushes and it seems to be okay afterwards, but it seems like a lot of wasted space that is being pushed...if the actual 300GB is being pushed at the time. I tried to push the image to ONE PC and it seemed have takend 2 hours to push the image. The speed behind it seems "okay", but I am not 100% sure if it is. I attached a screenshot.
Image may be NSFW.
Clik here to view.
