Sysprep and additional device drivers
Since all our servers are boot from SAN I was thinking about creating one LUN with a harden OS (2003 or 2008) and then running a sysprep on that and marking that LUN as read only and use that as a clone for new servers. My question is if I do that how can
I package other drivers onto that image? Say I build it with a model of server that has a certain nic installed. Then I use that on a different server with a different NIC. Is there a way I can package those drivers into my image? If sysprep isn't the answer
then is there another tool I can use?
My idea is to really get away from a full building of a server because it takes so long for the actual install along with all the patches. I want some image that I can throw down and turn it on and just answer a few questions like Server name and have it
up and running.
July 5th, 2011 11:54pm
Hello,
sysprep can be used to have a kind of included driver store:
http://technet.microsoft.com/de-de/library/cc736393(WS.10).aspx
http://support.microsoft.com/kb/314828
http://support.microsoft.com/kb/828287
http://technet.microsoft.com/en-us/library/dd744512(WS.10).aspx
Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
July 6th, 2011 12:56am
Other than the previous suggestion of adding a custom driver store, which should work, you could create a real Microsoft image. ImageX from the Windows AIK would allow you to create an image and then DISM could be used to inject drivers and even Windows
updates into your image even while offline. The Microsoft Deployment Toolkit can make this easier, but first things first.
Shane Cribbs
Georgia Technologies
http://www.georgiatechnologies.com C Shane Cribbs http://www.georgiatechnologies.com
July 6th, 2011 2:11am