question

BoopathiSubramaniam-6294 avatar image
0 Votes"
BoopathiSubramaniam-6294 asked BoopathiSubramaniam-6294 commented

Tabs on Boot Image properties are not found

Hello,

All the Tabs on Boot ImageProperties exist in recently created Boot Image. But it does not exist in all other boot images.




![137505-capture1.jpg][2] [2]: /answers/storage/attachments/137505-capture1.jpg

Please let me know how does the boot image created where few tabs are not found in the boot image properties and all the tabs exist in the other boot image properties.

I need to add the drivers to the properties of the boot image where few tabs are not found
137542-capture.jpg


mem-cm-osd
capture1.jpg (64.3 KiB)
capture.jpg (124.5 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Jason-MSFT avatar image
1 Vote"
Jason-MSFT answered

If the ADK version installed on the site server and/or site system hosting the SMS Provider role does not match the version of WinPE in the boot image, then you will not be able to modify certain things about the boot images from the ConfigMgr console. This includes drivers and the options on the Customization tab.

Assuming this is an older boot image, you need to upgrade it which can fairly easily be done in ConfigMgr: https://docs.microsoft.com/en-us/mem/configmgr/osd/get-started/manage-boot-images#update-distribution-points-with-the-boot-image

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AllenLiu-MSFT avatar image
0 Votes"
AllenLiu-MSFT answered BoopathiSubramaniam-6294 commented

Hi, @BoopathiSubramaniam-6294
Thank you for posting in Microsoft Q&A forum.

Like Jason said, this happens because SCCM compares the version of the installed ADK to the version of the boot image, and if these do not match, the tabs to modify the boot image will be hidden.

So we can update distribution points of the boot image with the option to "Reload this boot image with the current Windows PE version from the Windows ADK".

If we upgrade the ADK version before the SCCM upgrade, the boot image version will be upgraded during the SCCM upgrade.
And a little suggestion, when we upgrade the ADK version, it's better to restart the server after remove the old ADK, then install the new version of ADK.


If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hello @Jason-MSFT and @AllenLiu-MSFT,

Thanks for the help.

I did "Reload this boot image with the current Windows PE version from the Windows ADK" and I can see all the tabs.

I have the below clarifications

  1. It created a new WIM winpe.PACAKGEID.wim and winpe.wim which was existing one.
    Let me know which one can be kept and other can be deleted

  2. There are no drivers found in the Drivers Tab. Newly created wim will contain the drivers where drivers which were available before the Update Distribution Point?

Please help



0 Votes 0 ·
Jason-MSFT avatar image Jason-MSFT BoopathiSubramaniam-6294 ·
  1. You need them both. winpe.wim is the original file without anything injected into from ConfigMgr, and winpe.PACKAGEID.wim is a copy with the ConfigMgr items injected into it (like drivers, the ConfigMgr client agent, and other customizations).

  2. Drivers should get carried over and should display if injected properly. If they are not shown, then they were not injected previously.

1 Vote 1 ·

Thank you for the assistance @Jason-MSFT

0 Votes 0 ·