This article walks through updating an WDS infrastructure such that Hyper-V RTM bits are “slipstreamed” into the operating system installation. Given that Hyper-V has reached RTM (release to manufacturing), it was time to refresh my test deployment environment in my office anyway. I have an entirely private network segment here with its own domain controller and WDS server. I use this environment extensively for quickly deploying test operating system installations to both physical and virtual machines. (It’s also helpful as I can get full dedicated gigabit networking – something which I can’t get from corporate services here at Microsoft – this alone almost halves the overall installation time :) )
There are a few resources you need to refer to start with:
- Mikes posts on servicing from which I’m borrowing many of these instructions
- http://blogs.msdn.com/mikekol/archive/2008/03/25/hyper-v-installation-tricks-part-2-unattended-installation-of-windows-and-hyper-v-rc0.aspx
- http://blogs.msdn.com/mikekol/archive/2008/03/27/hyper-v-installation-tricks-part-3-integrated-installation-and-the-beauty-of-the-win6-servicing-stack.aspx
- The download for KB950049 x64 – This is the Hyper-V RTM bits for Windows Server 2008
- The install.wim from Windows Server 2008 x64 RTM media. The WIM is present in the sources directory of the media.
- The boot.wim from Windows Server 2008 x64 RTM media (for preparing the WDS server – outside the scope of this post)
- The Automated Installation Toolkit (AIK) for Windows Vista SP1 and Windows Server 2008
- KB928636 to provide more information on extracting an MSU
TrackBack URI Leave a comment »