The key things here are that they are deploying just one family of operating systems and that the hardware is from the same vendor. This is for a small company, they are only deploying one operating system, say Windows 8.1 圆4, and they have a few hardware models from the same vendor. This scenario has the following assumptions. The three scenarios are based on the size of the company, the number of operating systems being deployed, the level of control desired, and the number of hardware models. To simplify things I recommend starting with one of three core scenarios when configuring drivers for MDT 2013 Lite Touch. Also in the deployment share properties, in the Windows PE x86 Settings tab, in the Lite Touch Boot Image Settings area, set the Scratch space size to 128, do the same in the Windows PE 圆4 Settings tab.ĭeployment Share configured to use the WinPE 5.0 圆4 selection profile.Do the same for Windows PE 圆4 Components tab, but select the WinPE 圆4 selection profile. ![]() In the Windows PE x86 Components tab, in the Driver Injection area, select the WinPE x86 selection profile. Then configure the deployment share properties to use the correct selection profile.Create two selection profiles, one named WinPE 5.0 x86 (where you select the WinPE 5.0 x86 folder in Out-Of-Box drivers), and one named WinPE 5.0 圆4 (where you select the WinPE 5.0 圆4 folder in Out-Of-Box drivers.Note: You should only use Windows 8.1 drivers for the boot images, even if you plan to deploy Windows 7 SP1 with MDT 2013 Lite Touch. Import any needed x86 drivers into the WinPE 5.0 x86 folder, and any needed 圆4 drivers into the WinPE 5.0 圆4 folder.Create two folders in Out-Of-Box drivers, name the folders WinPE 5.0 x86 and WinPE 5.0 圆4.To be successful with boot image drivers in MDT Lite Touch I recommend that you do the following You also need to set the scratchspace in Windows PE to increase the temporary storage that is used when the Windows setup engine is injecting drivers. But in this article you find guidance if you need to add any driver. The good thing about Windows PE is that it supports the same hardware as Windows 10, so if you are lucky you don't need to add any drivers at all to it. For the boot image you need at Nic and Storage drivers at minimum, but sometimes you need to add other drivers as well (such as mouse drivers for remote cards like ILO etc.) The boot image you use for deployment is based on Windows PE (a subset of the Windows 10 operating system). ![]() But first, let's start with the boot image drivers. To simplify I have broken down drivers for the Windows Operating system in to three core scenarios (see later in this post). There are drivers for Windows PE (the boot image) and there are drivers for the Windows Operating System that you deploy.ĭriver management for the boot image is pretty straight, but driver management for the Operating Systems that you deploy is more complex. In MDT Lite Touch, there are two types of drivers to worry about when deploying Windows.
0 Comments
Leave a Reply. |