How drivers are added to Windows PE and Windows Vista during an unattended installation
My MCS colleague and top deployment gent - Mark Aslett has put together a handy process list for how device drivers are added to Windows PE and Windows Vista during deployment. The example below assumes than an unattend.xml file is being used to specify the location of drivers in both the windowsPE pass and the offlineServicing pass of the unattend.xml file.
If peimg is used to inject drivers directly into an offline Windows PE p_w_picpath then this fully installs the drivers, i.e. it performs the registry load, hardware ID and service information reflection, etc, and does not significantly delay the Windows PE boot or Vista deployment times.
BDD 2007 gets around most of the issues around deployment time identified above. When BDD creates the Windows PE boot p_w_picpath it will add any drivers that you specify at p_w_picpath creation time, so there is no need to use the windowsPE pass (or peimg to add drivers directly). BDD 2007 uses the offlineServicing pass for driver injection avoiding the bulk of the delays. It also has the added benefit of only copying across the drivers required instead of the entire driver store.
Big thanks to Mark for sharing his findings...
提问和评论都可以，用心的回复会被更多人看到
评论
发布评论
相关文章
-
如何安装驱动程序
把所有要安装的驱动程序都准备好后，我们就可以开始安装驱动程序了。驱动程序的安装方法也有很多种，下面就从易到难慢慢来看看。
职场 驱动 休闲 驱动界定 WHQL -
什么是Windows驱动程序？
1.Windo
windows os dll api 扩展 -
如何安装驱动程序？
自己手动调用“添加新硬件”程序，并通过告诉该程序inf文件的位置
windows system 子目录 配置信息 即插即用
