none
Can we inject drivers(NIC,Storage) into both window wim file and boot wim file ? RRS feed

  • Question

  • Hi just wanted to know Can we inject drivers(NIC,Storage) into both window wim file and boot wim file , also which is the best? injecting drivers in the window im file or boot wim file  and can i have a good blog link for this 
    Wednesday, September 11, 2019 5:40 PM

Answers

  • If ConfigMgr, you simply import the drivers into the console and then add them to the boot image and ConfigMgr takes care of this for you: https://docs.microsoft.com/en-us/sccm/osd/get-started/manage-boot-images#drivers.

    For a Windows image, you would use the same method as in your other post: DISM. For reference, your other post is at https://social.technet.microsoft.com/Forums/en-US/972d3fff-dbca-4d48-bca6-3c5df91d6dd5/how-to-add-files-in-the-bootwim-file-?forum=configmanagerosd#41508d43-18a0-4721-9c4b-313d363ffef8.

    As to which is better, the answer is neither. They each serve different purposes although generally you never directly add drivers to Windows images at all but instead let ConfigMgr do that for you with one of the built-in tasks during the deployment task sequence or you use DISM as a command-line task in the deployment task sequence to inject the necessary drivers into the deployed image.


    Jason | https://home.configmgrftw.com | @jasonsandys

    Wednesday, September 11, 2019 7:33 PM

All replies

  • If ConfigMgr, you simply import the drivers into the console and then add them to the boot image and ConfigMgr takes care of this for you: https://docs.microsoft.com/en-us/sccm/osd/get-started/manage-boot-images#drivers.

    For a Windows image, you would use the same method as in your other post: DISM. For reference, your other post is at https://social.technet.microsoft.com/Forums/en-US/972d3fff-dbca-4d48-bca6-3c5df91d6dd5/how-to-add-files-in-the-bootwim-file-?forum=configmanagerosd#41508d43-18a0-4721-9c4b-313d363ffef8.

    As to which is better, the answer is neither. They each serve different purposes although generally you never directly add drivers to Windows images at all but instead let ConfigMgr do that for you with one of the built-in tasks during the deployment task sequence or you use DISM as a command-line task in the deployment task sequence to inject the necessary drivers into the deployed image.


    Jason | https://home.configmgrftw.com | @jasonsandys

    Wednesday, September 11, 2019 7:33 PM
  • Hi,

    In SCCM, add only storage and network drivers to boot images. Other types of drivers aren't usually required in Windows PE. During the WinPE phase of OSD, the only two critical things are access to the network and access to the local disk. Drivers that aren't required unnecessarily increase the size of the boot image.

    As noted by Jason in another thread: install specific driver on TS sccm, if you are using an Auto Apply Driver or a Install Driver Package task, then the TS isn't responsible for installing drivers. These two tasks merely make the drivers available to Windows and Windows Setup so that they can install the drivers per their driver installation logic.

    If you need to delve into the details of Windows' drivers selection logic,
    Nice to know: – Why did Windows 7 pick THAT driver ?

    Thanks for your time.

    Best regards,
    Simon Ren

    Thursday, September 12, 2019 6:27 AM