I haven't really read through your site or looked at your Unattended
tool yet, but I noticed something that you are making out to be a 'bad'
thing that can actually be fairly simple. On the main page, you say to
stay away from imaging due to the number of images that need to be
created for a complex computer infrastructure. I've worked with the Tech
Support team here at Bucknell University for a couple years now and have
seen a very wide variety of systems that the school purchases for lab,
classroom, faculty, staff, and other various uses, but yet it still uses
imaging for every system, from 5-6 year old systems with hardware that
doesn't really like XP, to brand new systems that are vastly different
from the old hardware and are ready to run Windows Vista. Now, if what
you say was true, they would need an image for all the laptops and
desktops from every year for every model, yet they only use one, yes one
single image, that will work on every system that they have purchased
for the past 5, 6, maybe more years. It also works on laptops and
desktops, so one image is catering to probably 20 different types of
systems and hardware configurations. The only time a different image is
used is if a different set of software needs installed (engineering
applications mostly). So, I don't think that the statement that a lot of
different system images need made to cater to each different hardware
setup is necessarily true. I think that the current image that is being
created will also work for dual or single core computers, and I'm sure
that most other companies that do imaging have the same type of setup.
Mark
|