Tabs on Boot Image properties are not found

Boopathi Subramaniam 3,301 Reputation points


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]: /api/attachments/137505-capture1.jpg?platform=QnA

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

Microsoft Configuration Manager Deployment
Microsoft Configuration Manager Deployment
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Deployment: The process of delivering, assembling, and maintaining a particular version of a software system at a site.
941 questions
0 comments No comments
{count} votes

Accepted answer
  1. Jason Sandys 31,191 Reputation points Microsoft Employee

    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:

    1 person found this answer helpful.
    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. AllenLiu-MSFT 43,061 Reputation points Microsoft Vendor

    Hi, @Boopathi Subramaniam
    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.