molman

Hi Nois3, Can you please point me to the thread where you argue why not to use Ghost. I was unable to find it. I'm curious why you would so strongly discourage the use of Ghost when even Microsoft itself seems to advocate its use. What pitfalls am I getting into that I might not be aware of? The ones I am so far are; HAL issues Drivers issues (Esp. for Mass Storage) Hardware SID Cheers.

I should clarify, that the 5weeks does not refer to the available man hours for the project, but rather the time in days. Full manual install is not an option due to the time constraints, including the fact that these machines are all in use, so would need to task this work out of hours, or have it done in short order if in hours. Windows 2003 Server, AD will be available, but possibly not till day 1 of deployment. So RIS option can not be effectively tested. Network install option is possible. WSUS is in the works, but again will likely not be available on day 1. Ghost software will likely be available. Windows XP should be a volume license, all Pro verson. As an side, what is the best way to check a machines HAL type? Thanks for the advice/comments so far.

Ok, lets say your in a senario where you need to have a deployable corporate SOE (Standard Operating Environment), and you only have 5weeks. The SOE has to be deployable on 11-14lines of different hardware. You have no available application deployment infrustructure (RE: SMS etc..). The SOE needs the usual: WinXP+Patches, MS Office+Patches, PDF Reader, AV Software, Java, Citrix Client, Flash, Quicktime.. etc.. The SOE will then need to be deployed on 55 (in use) machines in a proceeding 4week period... more later. Please rule out external help, design, etc.. at this stage. How would you approach this senario? (Helpful comments only please)