i need to know if there is a way to automatically install windows xp on multiple computers (about 50). Something like creating a "bat" file or some sort of script file where I would write the configuration I need and then just power on the computers and windows will install in all the computers. I think this problem may be a very common one and have googleed it but no solution I've found I've liked it. It would be great if I could configure automatically the computer's name and IPs address but I think this may be too much to ask. Thanks in advance
|
feedback
|
|
You've got a couple of options. All of them involve using the Windows XP Deployment Tools, so make sure you download that.
There's some specifics involved in each one of these solutions. Figure out what you want to do, study up on it, then ask some more questions here as you run into problems. | |||
|
feedback
|
|
You're going about it wrong, don't install it 50 times. Install it once then clone it. There are all sorts of cloning utilities. Ghost and Clonezilla are but two. Also, see Microsoft's sysprep utility before cloning. | |||
|
feedback
|
|
It might be helpful to know why you didn't like the answers you found while googling, or indeed what they actually were. There are two ways to deploy client OSes and lots of tools that let you use one or the other of these methods or some combination. There is the scripted deployment: install windows with an OS image and an "answer file" that provides scripted answers to the typical questions you see during deployment, with the possibility of further scripting to install subsequent application packages and OS patches. This can be painful to set up and debug but is very flexible, especially if combined with windows servers running Active Directory (AD), as you can then use Group Policies (GPOs) to handle the app deployment based on various criteria. There's the "clone-the-disk- method. This is fairly self explanatory... set up one machine exactly how you want it, take a copy of the disk image, and deploy that to many machines. Faster than a scripted image but potentially less flexible (if your image includes Adobe CS5 and you need a dozen machines without it...) We use a hybrid method, which is probably one of the more popular ways of doing this among people I speak to these days: Clone Windows image for baseline OS install, major OS patches and major applications that take forever to install via the scripted method, plus deployment into active directory and assign "smaller" applications to install via AD GPOs which allows us to use one baseline image for our whole site (about 1300 machines) while ensuring that only HR get the HR software, only finance + people in departments authorised by finance to place orders get the finance software, etc. We also do something similar for Mac OSX. | |||
|
feedback
|
|
FOG is an open-source cloning solution. Don't let the low version number scare you. | |||
feedback
|
just creating a batch filethough....really, if you have to even ask this question here I don't think you're on the right site. – tombull89 Sep 9 '11 at 21:26I think this problem may be a very common one and have googleed itmeans they haven't quite done enough reasearch. Saying that, if they asked about a specific type of deployment I would be more than willing to help. – tombull89 Sep 9 '11 at 22:21