So, I need to make a new master image for the PC's where i work. The thing is, we have about 4-5 different model PC's IBM, HP's, some old some new. What i would like to do is, instead of having an image for each model computer, have a single image work for all the model types. From what i understand, as long as i load all the drivers, while booted from the corresponding model PC, things should work fine. But, my co-worker says otherwise and that its a bad idea. Just that something is going to go wrong with no real logic behind it. So does anyone with experience know if it is recommended or not to do this? These clients all log on under a windows 2003 server and use group policy. I just need a second more experienced option on this before its carried out. Thanks! p.s. if you need more information just ask

We use master images but you have to prepare the system to be imaged as a master first. We also use one of for some models. Not sure which is better. For the 4-5 you could make an image of all of them fast than you could sysprep one I'd guess and not fool with settings. "Best Practices", Event viewer, host file, perfmon, are in my top 10

Thanks for your reply! In the past, we would use the 4-5 different images. This works fine and all, but to have 4-5 images on 4-5 different hard drives can be a pain in the butt. (having to install SP2/and all other misc software they need) Having just one master image HD is a lot cleaner and easier to manage, so, i guess what im mainly asking is are there any drawbacks to doing it this way, or problems that can occur if i do this. But as you said you've done a couple models with one image yourself and it works ok? p.s. We are going to try out ghost server/client. Previous years we would have to p2p ghost all the labs, yeck.

One master image won't really work. Even if you're using the same manufacturer, HALS vary from model to model. Worst case scenario would be you restore an image to a machine, and it blue-screens. Then, you'd have to do an XP Repair. You'll also need different images for 64 bit machines. An image created on a 32-bit machine won't work on those. (In my experience.) Life's more painless for the brainless.

Try looking into vLite or even delve into Microsoft Windows Aik to create the images. Maybe 4-5 may not be worth it right now, but possibly down the road it will be.

Opps, didn't see the different models. That make's it way too hard for a single image. I should really read this stuff. "Best Practices", Event viewer, host file, perfmon, are in my top 10

Thanks for all the replies, i'll just make the images separately then. (Dont think they would like me using vLite or such similar tool if they were against my idea of 1 image w/o a logical argument) Thanks again!