Hello,
We are moving to Kaseya from Altiris. We are used to deploying one hardware independent image using Altiris for over 30 different models of computer. With Altiris, we inject the drivers into the image after the image has been laid down, but prior to the machine booting. We are able to accomplish this same task using FOG, an open source imaging solution. For many reasons, we want to use Kaseya, as we hope to use many modules of Kaseya that FOG or Altiris do not offer.
We thought we had this cracked...on the repository server, we were modifying the initrd file structure to include our custom code that would inject these drivers. However, it appears that each time KID is called, the initrd file is created and replaced dynamically by a static version of initrd, presumably from the primary Kaseya server. When looking at the initrd file on the main Kaseya server, it is actually an initrd.exe file, which i can look at with 7-zip, but when I try to extract that file using gzip or cpio in linux, I cannot extract the file. We talked on the phone to support today, but they weren't able to offer much help. we obviously realize that modifying the initrd structure is not a supported solution, but using the current imaging process in Kaseya is just not going to work for us.
Seeing that there isn't much movement in this forum, what is everyone else using for imaging? I'm surprised there aren't more people pushing for Kaseya as an imaging solution, just to try and get more things under one umbrella, but maybe we are the exception. By the way, we are a school district with 7 tech staff members for over 5,000 computers, so efficiency is the name of the game for us, hence our desire to have one product that can do most everything. Obviously the alternative is to continue using Altiris (don't want to pay for more licensing) or FOG (which does seem to work well for imaging), but it just becomes a bit more complex having to use more than one product.
Thanks for any thoughts.
Brad