Boot image question

Question

I have a boot image that calls a wim file called   Mh100002.wim.   I injected some NIC drivers into this .wim file.  When I updated the wim with NIC drives it created a new file called mh1000002.mg100002.wim.  I right click
on my boot image, pick Data Source and I choose this new .wim file mh1000002.mg100002.wim.  I point my task sequence to use this boot image.  I update content to all DPs with this new Boot image.   When I F12 a machine it connects to the correct
DP but it uses mh1000002.wim.  Why?  How come it does not use the updated .wim called mh1000002.mg100002.wim ?
mqh7

Answer 1

Your data source is the original bits. Say you have default boot image
[Boot Image (x64)] with PackageID of PS100005 where the source is here:
\\MY-SCCM-SITE.my.domain.com\SMS_ABC\osd\boot\x64\boot.wim.
When you inject drivers into it, SCCM recompiles it and saves new wim file as boot.{SiteName}{PackageID}.wim. In your task sequence you attach the “boot image package” of say [Boot Image (x64)], but SCCM will actually use the newly created wim file.
Now, I am assuming you are PXE booting correct? There is a twist when you PXE boot. SCCM uses the boot image to PXE boot that is tied the most recently deployed task sequence on the target collection.
For example if you create a TS and the appropriate media tied to it and deploy it to the “unknown” computers collection, and then a colleague comes in behind you and creates and new task sequence with different media attached to it and deploys it the “unknown”
computers collection that boot image will get used instead.
Hope this helps!
Cheers!
--Tony