Hi, I tryed to "Build and Capture" a WinXP. The Setup starts with the Tasks, creating Volume, formatting and installing the os is ok. But joining the domain and capturing the image I havent seen - where can I find the respective Log files? After this I assumed that can be a problem with the lan drivers, so I tryed to update the boot image. This failed. To check If the update process dont have a general failure I removed the drivers and checked the "enable command support" in the boot image. Then I will update that image without any additional drivers - it failed also. So Iwillcheck the files. I found two wim images in the folder given by the image properties. a boot.wim and a boot.ZMH00001.wim. I'm wondering about the file size the... boot.wim is 102 MB and the boot.ZMH00001.wim is 107 MB In the properties of the Image-GUI the size is given with 283.97MB. and if I will reload this properties the command failed. I get the following errors if I will update the distribution point: Error: Boot image to update: Microsoft Windows Vista PE (X86) Error: Actions to perform: Add ConfigMgr binariesEnable Windows PE command line supportAdd drivers Error: Failed to import the following drivers: Error: The wizard detected the following problems when updating the boot image.Failed to insert OSD binaries into the mounted WIM fileThe ConfigMgr Provider reported an error.: ConfigMgr Error Object:instance of SMS_ExtendedStatus{Description = "Failed to insert OSD binaries into the WIM file";ErrorCode = 2152205056;File = "e:\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";Line = 3822;ObjectInfo = "CSspBootImagePackage:reRefreshPkgSrcHook"; How can I fix the boot image, where can I find the original WIM file to import? Thanks for your help Best regards Damian

I found the problem. I hat to reinstall the AIK and the Images will update without errors.

I am getting the following error too when trying to inject drivers for the Dell Optiplex 755: Error: The wizard detected the following problems when updating the boot image. Failed to insert OSD binaries into the mounted WIM file The ConfigMgr Provider reported an error.: ConfigMgr Error Object: instance of SMS_ExtendedStatus { Description = "Failed to insert OSD binaries into the WIM file"; ErrorCode = 2152205056; File = "e:\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp"; Line = 3822; ObjectInfo = "CSspBootImagePackage:reRefreshPkgSrcHook"; Operation = "ExecMethod"; ParameterInfo = "SMS_BootImagePackage.PackageID=\"P0100001\""; ProviderName = "WinMgmt"; StatusCode = 2147749889; I have tried re-installing WAIK but this has not helped. Anyone got any other ideas?

I've had this happen often, especially when new drivers are imported and linked to the boot image. In all cases, it was a problem with the driver. Review the error message that appears after the unsuccessful update. It should reflect which driver is failing to update. You can delete the driver from the store and try the update again.

I was getting this issue when I moved my .bmp I was using for winpe. I re-entered the correct path and the error went. Suspect this might be the symptom for any related file not found?

Perhaps this article comes in handy: How to add WAIK 1.1. boot images to SCCM 2007 OSD http://www.techlog.org/archive/2008/03/21/how_to_add_waik_11_boot_images

Hello, I have the same issue while driving to update distribution points for a newly created boot image. I uninstalled and reintsalled WAIK with still no success. Is there something else I could look at to fix this problem.? Thanks

I figured it out. The problem was with a custom logo I was specifiying for the boot image. I changed the file location to the root of my site folder and the update worked. Probably a rights issue.

In my situation, I was unable to inject any USB drivers of any kind. By the time I fettered them all out I reached 100%

Hi!After many hours, I remove the drivers that I would want to import and I rebooted the Configuration Manager Server...Now I can import drivers into boot images! :)Aitor CampoyMCIT 2008Barcelona, Spain

I've had this issue in the past and I fixed it by deleting the boot image and re-creating it. Also, make sure that you right click and manage distribution points. Lastly right cilck and do an update distribution points.Jeremy Whittaker MCSE MCSA CCNA CCA Senior Consultant N2 Network Solutions http://www.N2NetworkSolutions.com

I too had this error when updating boot images. The problem was related to invalid driver locations. I followed the instructions in this thread, and manually updated the boot images. I also purged the driver library (not too sure which driver(s) were causing the problem), and I reimported the drivers I needed. Problem solved.This was the VB script I used to delete all drivers in SCCM. 'This VB script deletes all drivers in the SCCM driver database. ' Connect to the SMS namespace siteNamespace = GetSiteNamespace() SET objWMIService = GetObject( "winmgmts:{impersonationLevel=impersonate}!"_ &siteNamespace) SET drivers = objWMIService.ExecQuery("SELECT * From SMS_Driver") numDriversDeleted = 0 ' Process the results FOR EACH driver in drivers driver.Delete_ numDriversDeleted = numDriversDeleted + 1 NEXT WScript.Echo "Successfully deleted "&numDriversDeleted&" drivers." ' ' Utility function to search for the site namespace ' FUNCTION GetSiteNamespace() ' Find SMS Provider SET objSMSNamespace = GetObject("winmgmts:{impersonationLevel="&_ "impersonate}!\\.\root\sms") SET results = objSMSNamespace.ExecQuery("SELECT * From "&_ "SMS_ProviderLocation WHERE ProviderForLocalSite = true") ' Process the results FOR EACH r in results namespacePath = r.NamespacePath NEXT ' Fail if we did not find the site IF namespacePath = "" THEN WScript.Echo "Failed to locate SMS provider." WScript.Quit 1 END IF ' Return GetSiteNamespace = namespacePath END FUNCTION

I also had this problem an solved it finally! :-) Thanks for your Hint and this Script DreamensioN ! The error was caused by renaming the folder containing all my Drivers... (Bad idea) So I went do delete all Drivers in the Repository and build it from scratch. Now all Works as it should! THX!

Another common issue I have seen is lack of rights on the OSD boot image staging directory (%programfiles%\Microsoft Configuration Manager\OSD) Make sure your SCCM machine account has full control there. :)Kind Regards, Henk Hofs

having the same problem with updating the boot images ... so i deleted the boot images. since deleting the boot images i cannot import any now. it keeps giving me error even though they are the same boot images which i used before and was able to import. "you can not import this boot image. only finalized boot images are supported" I've deleted all driver and driver packages. any ideas? thanks

Hi itprof88. If you create a custom boot image you have to do some work on it before you can import it in SCCM. If you are working on ConfigMgr 2007 SP1/R2, look at this article: http://blog.frankovic.net/2008/10/creating-custom-boot-image-for-bare-metal-os-deployment-in-sccm-2007/ If you are working on ConfigMgr 2007 SP2, look at my article here:http://www.ithastobecool.com/2009/11/02/creating-a-custom-boot-image-for-sccm-sp2-winpe-3-0/ Hope this helps. Kind Regards, Henk Hofs

Hi Henk, Tried the first method, still giving me the same error when importing boot image. I tried importing the default boot image which SCCM under OSD\boot\ with the same error. Thanks.

Another common issue I have seen is lack of rights on the OSD boot image staging directory (%programfiles%\Microsoft Configuration Manager\OSD) Make sure your SCCM machine account has full control there. :) Kind Regards, Henk Hofs

Try to delete all boot images from your SCCM site server (if you have parent\child site setup, try to delete the boot images from the parent site) After that, create a cusom wim.... For SCCM Pre-SP1/SP1/R2 check these: 1.Copy a boot image from the directory where the Windows Automated Installation Kit (WAIK) is installed. (on the site server where WAIIK is installed start the WAIK command promt and type copype.cmd <ARCH> c:\winpe) (where <ARCH is either "x86" or "amd64" depending on what boot image you want to create" 2.Mount this new copied boot image to the auto-created mount folder. (if you used c:\winpe in the previous example use: "imagex /mountrw c:\winpe\winpe.wim 1 c:\winpe\mount") 3.Install the three optional components that are required to perform Configuration Manager 2007 operating system deployments: peimg.exe /install=WinPE-Scripting-Package C:\winpe\mount\windows peimg.exe /install=WinPE-WMI-Package c:\winpe\mount\windows peimg.exe /install=WinPE-XML-Package c:\winpe\mount\windows Finalize the boot image using the following command: peimg.exe /prep c:\winpe\mount\windows /f Dismount the boot image using the following command: imagex.exe /unmount /commit c:\winpe\mount\\windows These are the steps for a SCCM2007 SP1/R2 boot image. For SCCM 2007 SP2 boot image creation, read my blogpost here:http://www.ithastobecool.com/2009/11/02/creating-a-custom-boot-image-for-sccm-sp2-winpe-3-0/ I hope this helps! Kind Regards, Henk Hofs

Great work Henk, Thanks this is now working for meJoeJoe Assad

Can we not just use the prebuilt WIMs that come with SCCM SP2? They are installed to Program Files\Microsoft Configuration Manager\OSD\boot\i386.

Check the C:\Windows\Logs\DISM\dism.log file and view with SMS Trace. In my case the log showed a failure with a VMWare NIC driver. I had to delete it and reimport the driver again.

i too got the same error message. How do we check if WAIK is working fine or not in sccm environment. Can we remove the drivers which are not getting imported and then try to update DP. Suppose if it fails (DP update happens fine, but boot image is giving issues on machines), can we roll it back (if we have taken a previous backup of boot.wim and its sccm copy), can we just replace the older working one with the newer failed onw...will it work Thanks & Regards Uttam

The error was caused by renaming the folder containing all my Drivers... (Bad idea) In my case this was an ID10T error... I had renamed one of the source directories. Once I renamed the folder back to what it was I was able to successfully update the Boot Image. Thanks seboHH for reminding me that renaming source directories is a BAD IDEA! :) Justin