One of the things about new platforms is you get to learn new technology. One of the bad things about new technology is that a lot of your old methods might not apply anymore, need to be revamped, or redesigned completely. Over the last few months I’ve been working on a Cisco UCS platform deployment for work.

This has been quite exciting as it’s all new gear, and it’s implementing stuff that we should have been able to implement with our HP BladeSystem C7000 gear. One of the biggest gotchas so far is that the build image we have for our machines no longer works. The Cisco UCS B200 servers have hardware that isn’t detected out of the box with Windows 2012R2. This means we have to inject drivers into the boot image, and the install image, to make the install work when using Boot From SAN (BFS). This post is a reflective for myself, and others that might find it handy, because I’m constantly forgetting how to update the drivers in boot images.

One thing I’m very thankful for, the new ImageX format that Microsoft started using with Windows Vista. This makes image management so very much easier. Preparing your build environment First step is to install (Assessment and Deployment Kit). When you run the install, you only need to install the 2 deployment and build packages. The next step is to prepare the build environment. I have a secondary drive in my desktop, so I built the following structure.

1 2 3 4 5 6 7 8 F: -Build -ISO -Windows -Drivers -Network -Storage -Chipset You’ll need a valid copy of Windows 2012R2. If you have it on DVD, simply copy the contents of the DVD into your Windows folder as I have documented above. You’ll also need a copy of the driver CD from the vendor. As this is for the Cisco UCS B200, you need a login, and you can find them tucked. Find the drivers you need on the DVD, in my case the Network and Storage drivers were easy as there were only one in the named folders. Free Download Achi Ir Pro Sc Manual Programs For Single. The chipset was a little difficult because a clean install of Windows didn’t detect the chipset, but pointing the Windows at the driver DVD found all the drivers, and then the device said no special drivers were needed so refused to list any.

After some fudging around, I managed to identify these as Intel’s Ivytown drivers, so dropped those in the Chipset folder. Identifying Install Image and Injecting Drivers This is where all the magic happens. We’re going to inject the drivers into the image, or slipstream them as it’s called in some places. Safelink Wireless Agent Program on this page. This is done with just a handful of commands. The first thing we need to do is identify which install image we want to work with.