Reference image deployment

In previous chapters, we've discussed drivers, CustomSettings.ini configuration, task sequence, and many other items. All these concepts are utilized here as we build our reference image deployment task sequence and virtual machine. In our examples in this chapter, we're going to be utilizing Hyper-V as a virtualization host for simplicity and cost; other solutions can be used, but they add a complication layer in terms of drivers that need to be inserted into both the Windows Preinstallation Environment (Win PE) and actual driver store for the image itself. However, Hyper-V can pose the same concern with driver-versioning needs.

Tip

What this means is the native Hyper-V drivers that are shipped with Windows 7, for instance, will not work in a Hyper-V virtual machine hosted in Windows Server 2012 R2, for example. Back-level drivers will still need to be provided so that the Win PE and installation task sequence can see the network, and thus communicate with the deployment...