{"id":326,"date":"2009-02-08T19:32:26","date_gmt":"2009-02-08T19:32:26","guid":{"rendered":"http:\/\/andrius.kozeniauskas.com\/blog\/?p=326"},"modified":"2010-10-19T15:03:03","modified_gmt":"2010-10-19T14:03:03","slug":"sccm-adding-deleted-boot-image","status":"publish","type":"post","link":"http:\/\/www.kozeniauskas.com\/itblog\/2009\/02\/08\/sccm-adding-deleted-boot-image\/","title":{"rendered":"SCCM: Adding deleted Boot image"},"content":{"rendered":"

So lets say you’ve accidentally delete one or both Boot images from OSD in Configuration manager console and want to add them back.
\nWhen you delete the image in the console the default image file is still located on the SCCM server.<\/p>\n

So here are the steps to add Boot image back:<\/p>\n

1. Open Configuration manager console. Navigate to Site Database>Computer Management>Operating System Deployment>Boot images<\/strong>. Click on Add Boot Image<\/strong>
\nAdd Boot Image Package Wizard <\/strong>will start
\n\"\"<\/a><\/a><\/p>\n

2. In the path field you need to enter the path where WIM boot image file is located. The location of the file should be:
\n\\\\SCCMserverName\\sms_SiteCode\\OSC\\boot\\platform\\boot.wim
\n<\/strong>So if you server name is dubsccm, site code is MET and you want to add image for x86(32bit) platform your file location should look like this:
\n\\\\dubsccm\\sms_met\\OSD\\boot\\i386\\boot.wim
\nOnce you enter the path the Boot Image<\/strong> field should come up automatically.
\n\"\"<\/a><\/a><\/p>\n

3. Enter the name, version and comment if you need them.
\n\"\"<\/a><\/a><\/p>\n

4. In the sumary page click next and after the progress is finished click Close.
\n\"\"<\/a><\/a><\/p>\n

5. Now you have your Boot image but you need to assign the drivers to it as without them most likely you will not be able to OSD many machines.
\nRight click on the image that you’ve created and select properties.
\n\"\"<\/a><\/a><\/p>\n

6. Select Windows PE tab. Click on Yellow flower button. This will open a list of drivers available. Select the one you need and click OK. Unfortunately you cannot select multiple drivers so you’ll have to do them one by one. Other option would be to create a drivers package with multiple drivers and apply it to the Boot image.
\n\"\"<\/a><\/a><\/p>\n

7. Now you have to assign PXE Distribution point to you newly created Boot image. You could have assigned it straigh away, but after adding drivers it would need to be refreshed so better to add drivers first and then add distribution point. The steps are shown bellow.
\n\"\"<\/a><\/a><\/p>\n

\"\"<\/a><\/a><\/p>\n

\"\"<\/a><\/a><\/p>\n

\"\"<\/a><\/a><\/p>\n

\"\"<\/a><\/a><\/p>\n

\"\"<\/a><\/a><\/p>\n

So your newly added Boot image is ready for use.<\/p>\n

If the boot image that was deleted was already used for Task sequences then you will need to modify your task sequence to point to new Boot image. This is because after the boot image is deleted all the associated Task Sequences are modified and ‘Use a boot image<\/strong>‘ option is disabled.<\/p>\n

To point the task sequence to boot image just Right click on the task sequence and choose properties. Select Advanced tab. In there tick on ‘Use a boot image<\/strong>‘ and click on browse. Select the boot image and click OK. Click OK again in the task sequence properties window.
\n\"\"<\/a><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

So lets say you’ve accidentally delete one or both Boot images from OSD in Configuration manager console and want to add them back. When you delete the image in the console the default image file is still located on the SCCM server. So here are the steps to add Boot image back: 1. Open Configuration […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[5,6],"tags":[33,311,219,297],"_links":{"self":[{"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/posts\/326"}],"collection":[{"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/comments?post=326"}],"version-history":[{"count":2,"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/posts\/326\/revisions"}],"predecessor-version":[{"id":424,"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/posts\/326\/revisions\/424"}],"wp:attachment":[{"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/media?parent=326"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/categories?post=326"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.kozeniauskas.com\/itblog\/wp-json\/wp\/v2\/tags?post=326"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}