DaRT Tools in SCCM Boot Image

I'm looking for a way to integrate DaRT into my SCCM/PXE environment. I'm not using MDT integration, but want to give technicians the option to start an OS deployment or go to DaRT, all from a network boot. Originally, I had my DaRT boot images,
one for each OS that we support, but I found that the systems were booting into the DaRT images instead of the SCCM boot images. Does anyone have any input on what they do or how to inject the DaRT tools into an existing boot image? (I assume that
if the tools were present, I could just add a variable to my HTA to skip all steps except for a winrec step)
Best, Jacob I'm a PC.

Take a look at this post of Johan:
http://www.deploymentresearch.com/Research/tabid/62/EntryId/131/Adding-DaRT-8-1-from-MDOP-2013-R2-to-ConfigMgr-2012-R2.aspx
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Similar Messages

Mdt integration boot image and SCCM boot image

I created a MDT task sequence in SCCM and went through all the steps for setting up the toolkit and settings and boot image. After all that, I distributed everything to my DP. When i try to boot to pxe and run that new MDT task sequence it finds the pxe
server, but just sits at "Contacting server" for some time until it times out. If I select the SCCM boot image in the task sequence properties then it works. the one created when i create the task sequence doesn't.
Any Idea?

Sounds like you didn't enable the boot image for PXE. This is a checkbox at the bottom of the Data Source page in the properties of the boot image.
Have you reviewed smspxe.log?
Jason | http://blog.configmgrftw.com | @jasonsandys

Boot image does not exist and cannot read disk label errors.

Hi - I'm having a problem with installing Solaris 9 4/04 on a Netra T1. The Netra already has Solaris 7. I need to get this set up as a jumpstart server but it can't find the boot image. I'm using a brand new bonafide installation disk - not a copy. The system won't let me install/upgrade to Solaris 9 either. I get an error stating that disk label can't be read. I've tried swapping out the CDROM but I still get the same errors. Does anyone know what or why this may be happening? (Oh - and another strange thing - like I said the CDs are the original but there doesn't appear to be a cdrom/cdrom0/s0 directory. The directory I see is cdrom/cdrom0/sol_9_404_sparc/Solaris_9/Tools)
ERROR: Install boot image /cdrom/sol_9_404_sparc/Solaris_9/Tools/Boot does not exist
Check that boot image exists, or use [-t] to
specify a valid boot image elsewhere.
and
Excuting last command: boot cdrom [- nowin]
Boot device: /pci@1f,0/pc1@1/ide/cdrom@2:f file and args: [- nowin]
Can't read disk label.
Can't open disk label package
Evaulating: boot cdrom [- nowin]@1/ide@e/cdrom@2:f File and args: [- nowin]
Can't open boot device
I appreciate any help at all - is there anyone out there who can tell me what I may be doing wrong?
Thanks

Hi check that you are booting of the right cd. Make sure it is soalris 9 software 1/2 if that fails then it may well be that your cd is buggered. most likely it is buggered it it cant find the boot image.

SCCM 2012 SP1 Boot Image

Hi Guys,
We upgraded to SCCM 2012 SP1 from the RTM yesterday and now our OS Deployment has stopped working. I have tried to update the DP's with the boot images and it keep failing to add drivers. I have also tried to add a Boot Image but this failing.
Any suggestion on what might be going wrong? Our upgrade processed completed successfully.
Kind Regards
TPark IT Technician

Hi,
I have removed all the drivers and I am now getting the following error.
Error: Boot image to update:
Microsoft Windows PE (x86)
　Error: Actions to perform:
Add ConfigMgr binaries
Add custom background
Enable Windows PE command line support
Optional components:
Scripting (WinPE-Scripting)
Startup (WinPE-SecureStartup)
Network (WinPE-WDS-Tools)
Scripting (WinPE-WMI)
　Error: The wizard detected the following problems when updating the boot image.
The SMS 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:\\qfe\\nts\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
Line = 4630;
ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
Operation = "ExecMethod";
ParameterInfo = "SMS_BootImagePackage.PackageID=\"ASH00001\"";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
I am only trying to Deploy Windows 7 images currently but we are looking to upgrade to Windows 8 at Christmas. Can I import a boot image from a Windows 7 or Windows 8 cd?

Failed to Create MDT Boot Image in SCCM 2007

Hello Everyone,
I am trying to create MDT Integrated Boot Image in SCCM to Enable DART Integration on it. But when i try to Create Boot Image it Fails with below Error Message.
Started processing.
Creating boot image.
Copying WIM file.
Mounting WIM file.
WIM file mounted.
Setting Windows PE system root.
Set Windows PE system root.
Set Windows PE scratch space.
Adding standard components.
Adding extra content from: C:\Users\ADMINI~1\AppData\Local\Temp\1\i5wqsynb.efm
Unmounting WIM.
Copying WIM to the package source directory.
Creating boot image package.
Error while importing Microsoft Deployment Toolkit Task Sequence.
Failed to insert OSD binaries into the WIM file
Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException: The ConfigMgr Provider reported an error.
---> System.Management.ManagementException: Generic failure
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObject.Put(PutOptions options)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
--- End of inner exception stack trace ---
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
I have searched over Internet for the same Error and I guess it was a Permission Issue. But my Environment is as below.
AD & SCCM Server on Same Machine
Folder have Full Permissions to SYSTEM, SCCMComputerAccount, DomainAdministrators, and Even I gave to Everyone Full
Control.
This is a LAB Environment with No Antivirus, No UAC
ANY HELP ON THIS Folks..... (:-()
Ram

Hi Ychinnari,
As your question is related to SCCM report. it is not supported here.
you could post it in SCCM forum for better supports, Thanks for your understanding.
SCCM forum link:
https://social.technet.microsoft.com/Forums/systemcenter/en-US/home?category=configurationmanager
Best regards,
Youjun Tang
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Automatically start DaRT in Boot Image

I have ConfigMgr 2012 SP1 R2 deployed with MDT 2013. I created an MDT boot image and chose DaRT from the checklist and created the new boot image. Once PXE booting into WinPE I can press F8 and execute Windows\System32\RemoteRecovery.exe.
I would like to have RemoteRecovery.exe execute automatically when WinPE starts. I have found some older blogs but nothing for ConfigMgr 2012 R2/MDT 2013/DaRT 8.1. Can someone please recommend the best approach?
Thanks

I have ConfigMgr 2012 SP1 R2 deployed with MDT 2013. I created an MDT boot image and chose DaRT from the checklist and created the new boot image. Once PXE booting into WinPE I can press F8 and execute Windows\System32\RemoteRecovery.exe.
I would like to have RemoteRecovery.exe execute automatically when WinPE starts. I have found some older blogs but nothing for ConfigMgr 2012 R2/MDT 2013/DaRT 8.1. Can someone please recommend the best approach?
Thanks
I roughly followed the older instructions from the following URL and it's working as expected:
http://www.deploymentresearch.com/Research/tabid/62/EntryId/36/Software-Assurance-Pays-Off-Remote-Connection-to-WinPE-during-MDT-SCCM-deployments.aspx

Using MDT boot image in SCCM 2012

Hi,
I want to import MDT boot image in SCCM 2012. Please let me know if this is possible.
I have integrated all the driver in it and want to use from SCCM.
Any suggestion on this?
Regards, Shishir Kushawaha "If this thread answered your question, please click on "Mark as Answer"

These two blogs explain this process very very well.
http://myitforum.com/myitforumwp/2013/08/01/how-to-create-configmgr-2012-boot-images-from-scratch/
http://www.niallbrady.com/2013/10/09/how-can-i-manually-add-winpe-5-boot-images-to-system-center-2012-configuration-manager-sp1-cu3/
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Update distribution point errors updating the boot image....SCCM 2012 r2

Fairly new to SCCM (started on it about a month and a half ago and only been troubleshooting different things). As of this moment I'm attempting to get imaging back up, which it looks as if the drivers did not get injected into the boot image properly
before. This seems to be resolved but when I attempt to update the distro point i end up with this error below. Any help is appreciated.
Error: The wizard detected the following problems when updating the boot image.
• Failed to inject a ConfigMgr driver into the mounted WIM file
The SMS 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_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
• Line = 4716;
• ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
• Operation = "ExecMethod";
• ParameterInfo = "SMS_BootImagePackage.PackageID=\"SMS00005\"";
• ProviderName = "WinMgmt";
• StatusCode = 2147749889;

What version of Configuration Manager are you running, and are you using MDT?
Blog: www.danielclasson.com/blog |
LinkedIn:
Daniel Classon | Twitter: @danielclasson

SCCM 2012 R2 Boot Image won't load in Windows XP

I'm using ADK 8.1, MDT 2013, x86 Boot image w/ PE 5. Deployed a TS to Windows XP SP3 computer with a single task: Reboot Computer to PE
Getting this: Executing command line: "C:_SMSTaskSequence\WinPE\SMS\bin\i386\bootsect.exe" /NT60 SYS /MBR TSManager 10/31/2013 9:49:27 AM 3000 (0x0BB8)
Failed to install boot image. is not a valid Win32 application. (Error: 800700C1; Source: Windows)
More detailed smsts.log below:
<![LOG[Captured settings for adapter 1]LOG]!><time="09:33:52.197+420" date="10-31-2013" component="OSDNetSettings" context="" type="1" thread="5368" file="netsettings.cpp:99">
<![LOG[OSDNetSettings finished: 0x00000000]LOG]!><time="09:33:52.197+420" date="10-31-2013" component="OSDNetSettings" context="" type="1" thread="5368" file="main.cpp:192">
<![LOG[Process completed with exit code 0]LOG]!><time="09:33:52.307+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="commandline.cpp:1123">
<![LOG[Installing boot image to hard drive]LOG]!><time="09:33:52.353+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="bootimage.cpp:621">
<![LOG[Backing up existing boot system before trying to set up new boot system]LOG]!><time="09:33:52.353+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856"
file="bootimage.cpp:644">
<![LOG[BootLoader::backup: C:\, C:\_SMSTaskSequence\backup]LOG]!><time="09:33:53.213+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="bootloader.cpp:85">
<![LOG[BootLoader::restore: C:\_SMSTaskSequence\WinPE, C:\]LOG]!><time="09:33:54.479+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="bootloader.cpp:382">
<![LOG[Saving bcd store to C:\_SMSTaskSequence\WinPE\boot\BCD]LOG]!><time="09:33:57.057+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="bootconfigimplbcd.cpp:703">
<![LOG[Executing command line: "C:\_SMSTaskSequence\WinPE\SMS\bin\i386\bootsect.exe" /NT60 SYS /MBR]LOG]!><time="09:33:57.166+420" date="10-31-2013" component="TSManager" context="" type="1"
thread="4856" file="commandline.cpp:827">
<![LOG[CreateProcess failed. Code(0x800700C1)]LOG]!><time="09:33:57.182+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="commandline.cpp:1018">
<![LOG[Command line execution failed (800700C1)]LOG]!><time="09:33:57.182+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="commandline.cpp:1245">
<![LOG[Failed to install boot image.
is not a valid Win32 application. (Error: 800700C1; Source: Windows)]LOG]!><time="09:33:57.182+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="bootimage.cpp:681">
<![LOG[Failed to install boot image UCI00073.
is not a valid Win32 application. (Error: 800700C1; Source: Windows)]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="engine.cxx:840">
<![LOG[Failed to reboot the system. Error 0x(800700c1)]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="engine.cxx:953">
<![LOG[Failed to initialize a system reboot.
is not a valid Win32 application. (Error: 800700C1; Source: Windows)]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="engine.cxx:577">
<![LOG[Fatal error is returned in check for reboot request of the action (Restart in Windows PE).
is not a valid Win32 application. (Error: 800700C1; Source: Windows)]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="engine.cxx:273">
<![LOG[An error (0x800700c1) is encountered in execution of the task sequence]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="engine.cxx:348">
<![LOG[Set authenticator in transport]LOG]!><time="09:33:57.198+420" date="10-31-2013" component="TSManager" context="" type="0" thread="4856" file="libsmsmessaging.cpp:7734">
<![LOG[Task Sequence Engine failed! Code: 800700C1]LOG]!><time="09:34:45.920+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="tsmanager.cpp:919">
<![LOG[****************************************************************************]LOG]!><time="09:34:45.920+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856"
file="tsmanager.cpp:953">
<![LOG[Task sequence execution failed with error code 800700C1]LOG]!><time="09:34:45.920+420" date="10-31-2013" component="TSManager" context="" type="3" thread="4856" file="tsmanager.cpp:954">
<![LOG[Cleaning Up.]LOG]!><time="09:34:45.920+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="tsmanager.cpp:675">
<![LOG[Removing Authenticator]LOG]!><time="09:34:45.920+420" date="10-31-2013" component="TSManager" context="" type="1" thread="4856" file="tsmanager.cpp:686">

See the "Workaround" section of this post for an example of downgrading bootsect.exe:
http://social.technet.microsoft.com/Forums/en-US/6e934990-999a-4367-860a-3ce4e5eda956/sccm-2012-r2-error-0x800700c1?forum=configmanagerosd
It is not the version of WinPE that is the problem here, but the version of bootsect.exe that gets injected into the boot media.
Nash Pherson, Senior Systems Consultant
Now Micro -
My Blog Posts
<-- If this post was helpful, please click "Vote as Helpful".
This workaround worked in my environment. Fixed my in-place upgrades from XP to Windows 7, and as a bonus, fixed imaging XP as well. yeah, I have to keep XP for awhile. :-(

SCCM 2012 RTM to SP1 to R2 Boot Images Migration What steps to be consider

We are Migrating SCCm 2012 to SP1 then to R2…
My question would be specific to Boot images.
We are in RTM edition, we have different boot images got created by our Imaging guys, These boot Images also have network/mass storage drivers are added along with some WINPE Back Group screen wallpaper, when cross checked the boot image properties. And
finally these the Boot Images are distributed to all the required distribution points.
Help me to understand what are the action steps to be taken now? In the process of RTM to SP1 and R2
HunBoy Started learning from this page

From RTM to SP1, the upgrade process will upgrade your WinPE 3.x boot images to WinPE 4.0 (if it can). From SP1 to R2, the upgrade process will not upgrade your boot images but will instead create new ones. Only WinPE 5.0 and WinPE 3.1 boot images are supported
by R2 -- the 3.1 boot images are meant for supporting XP since WInPE 5.0 doesn't support XP (God help you if you're still on XP though).
Thus, you need to get your "imaging" guys to create new WinPE 5.0 boot images.
Jason | http://blog.configmgrftw.com

SCCM 2012 sp1 - can't add boot image - Only finalized boot images are supported.

so when i updated to sp1 i had to install the new assessment and deployment kit which i have done.
when i try to add a boot image to sccm now i get the error:
You can not import this boot image. Only finalized boot images are supported. For more information press F1.
i have searched technet and on old versions of sccm you could re-install waik to fix this issue, i have tried re-installing ADK and its still doing the same.
has anyone had this problem on 2012 sp1?

Hi,
It works to import x86 image of windows 8 and now I have some problems when I try to import x64 boot image of 8.1.
Where I can see errors in logs. Are sow many log files and I'm little confuse and I cant find error to see what is the reason of this error.
And the error is:
Error: Data Source
Information
• Source location:
\\xxx\yyy\X17-24269\sources\boot.wim
• Boot Image:
1 - Microsoft
Windows PE (x64)
Error: Package
Information
• Name: boot
Error: Errors
• You can not
import this boot image.
Only finalized boot images are supported.
For more information press F1.

Upgrade to SCCM R2 have to recreate boot image and TS

Wanna ask, I have upgraded from my SCCM from SP1 CU3 to R2. But i noticed that in boot image, the WinPE tab is missing thus i cannot include the network driver. Anyway that i can make the tab reappear again? Net says have to recreate the boot image and TS...
http://www.deploymentresearch.com/Research/tabid/62/EntryId/117/A-Geeks-Guide-for-upgrading-to-ConfigMgr-2012-R2-and-MDT-2013.aspx

This often happens after R2 upgrade. If your boot image does not have 6.3.9600 version then you will not be able to manipulate it using the R2 console. You don't need MDT to create a new one though (this new version).
You can use dism. See here. It's very easy. I had to do it yesterday.
http://www.niallbrady.com/2013/10/09/how-can-i-manually-add-winpe-5-boot-images-to-system-center-2012-configuration-manager-sp1-cu3/
http://myitforum.com/myitforumwp/2013/08/01/how-to-create-configmgr-2012-boot-images-from-scratch/
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

SCCM 2012: PXE deploy: import boot images?

Hi,
We fully configured sccm 2012 and did osd via bootable media. Now we want to configure PXE.
We enabled it (http://prajwaldesai.com/deploying-sccm-2012-part-14-build-and-capture-windows-7-64-bit/).
My questions:
*Is that all that needs to be done?
*It seems to me we need to import boot images in WDS?
*If we do, which to import then (both x86 and x64 probably) + there is a winpe and a winpe.....wim made by sccm, which one to import then?
*on DHCP we change the boot server hostname but what about the bootfile name, what is the path of that? \boot\x64\wdsnbp.com?
Please advise.
J.
Jan Hoedt

I keep on getting TFTP open timeout
I find in smspxe.log that it reaches to the SCCM-server but then something goes wrong. Not sure what.
How can I troubleshoot find more info, please advise?
00:51:55:2A:5C:C5, 0A190A42-FFDe6-5e69-9e41-70e481B852E3: device is not in the database.   SMSPXE   21/03/2014 16:10:08   2720 (0x0AA0)
Getting boot action for unknown machine: item key: 2046820352   SMSPXE   21/03/2014 16:10:08   2720 (0x0AA0)
CLibSMSMessageWinHttpTransport::Send: URL: oursccmserver.prod.ourcompany.be:80 GET /SMS_MP/.sms_aut?MPKEYINFORMATIONEX   SMSPXE   21/03/2014 16:10:08   2720 (0x0AA0)
CLibSMSMessageWinHttpTransport::Send: URL: oursccmserver.prod.ourcompany.be:80 CCM_POST /ccm_system/request   SMSPXE   21/03/2014 16:10:08   2720 (0x0AA0)
Jan Hoedt
Note: what I also can see:
Client IP Address: 000.000.000.000
Your IP Address: 000.000.000.000
Server IP Address: 000.000.000.000
Relay Agent IP Address: 000.000.000.000

SCCM 2012 Matching Processor Architecture Boot Image (0) not found

SCCM2012 SP1 ,One Site, 3DP.
one DP can not install os with PXE boot. when start PXE F12, system crush with code 0x00000f. and Log like this
"00:0C:29:90:D1:C0, 291241B9-AB25-4400-B746-99E018F70F1A: device is in the database. SMSPXE 2014/10/1 2:28:11 4504 (0x1198)
Warning: Matching Processor Architecture Boot Image (0) not found SMSPXE 2014/10/1 2:28:11 4504 (0x1198)"
The BOOT.wim file works well in ither DP.
I have try to redeploment the PXE and reload the Boot.Wim file in this DP, but can not reslove this problem.
I'm afried reset the Boot.wim will take other 2 DP can not work too.
Please Help.

Hi Pazza,
As Torsten said, please ensure that you have an x86 and x64 boot image configured and deployed, regardless of the architecture of the OS that
you wish to deploy. Secondly, ensure that the boot images for both architectures have the network drivers for the respective model that you are imaging injected.
Otherwise, please review the link below:
ConfigMgr PXE Boot Warning: Matching Processor Architecture Boot Image (0) not found
http://www.systemcentercentral.com/configmgr-pxe-boot-warning-matching-processor-architecture-boot-image-0-not-found/
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Update Boot Image Issues

Environment: SCCM 2012 SP1 CU3
Issue: errors when trying to update distribution points (Driver Additions)
Error Message:
Error: Boot image to update:
• Microsoft Windows PE (x64)
Error: Actions to perform:
• Add ConfigMgr binaries
• Disable Windows PE command line support
• Add drivers
Error: Failed to import the following drivers:
• Intel(R) Ethernet Connection I217-LM
• Broadcom NetLink (TM) Gigabit Ethernet
• 3Com Dual Port 1000-SX PCI-X Server NIC
• Realtek PCI GBE Family Controller
• LAN7500 USB 2.0 to Ethernet 10/100/1000 Adapter
• Intel(R) 82579LM Gigabit Network Connection
• Intel(R) 82575EB Gigabit Network Connection
• Intel(R) 82580 Gigabit Network Connection
• Intel(R) 82599 Multi-Function Network Device
• DELL PERC RAID Virtual Device
• PERC H310 for Dell Precision
• LSI MegaRAID Virtual Device
• Intel(R) C600 series chipset SATA AHCI Controller
• Intel(R) C600/C220 series chipset SATA RAID Controller
• Intel(R) C600 Series Chipset SAS RAID Controller
• Intel(R) 5 Series 4 Port SATA AHCI Controller
• Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller
• System Management Device
• System Management Device
• LSI SAS x28 Expander
• LSI Adapter, SAS2 2116 Meteor ROC(E)
• Intel(R) ICH9M-E/M SATA AHCI Controller
• Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller
Optional components:
• Scripting (WinPE-Scripting)
• Startup (WinPE-SecureStartup)
• Network (WinPE-WDS-Tools)
• Scripting (WinPE-WMI)
Error: The wizard detected the following problems when updating the boot image.
• Failed to inject a ConfigMgr driver into the mounted WIM file
The SMS 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:\\qfe\\nts\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
• Line = 4630;
• ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
• Operation = "ExecMethod";
• ParameterInfo = "SMS_BootImagePackage.PackageID=\"PS100081\"";
• ProviderName = "WinMgmt";
• StatusCode = 2147749889;
Anyone have any idea's why the WIM file will not update? I have been trying to get a Dell 7440 to boot properly so I can image it but the problem is: PXE loads fine but when the system starts to load the SCCM deployment piece it just restarts.
I have not found any errors during this portion and did not see anything in the SCCM logs. Assumed it had to do with the drivers but now I am unsure.
Thanks,
JAK
EDIT: on a side note, I have re-created the boot images and removed and re-added drivers still same issues.

SMSPROV.log
CExtUserContext::EnterThread : User=**** Sid=0x0105000000000005150000002EA925CE2D54C0A5946DF1F931320000 Caching IWbemContextPtr=00000000050CF1A0 in Process 0xe60 (3680) SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
Context: SMSAppName=Configuration Manager Administrator console SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
Context: MachineName=****.**** SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
Context: UserName=**** SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
Context: ObjectLockContext=501335b7-4817-4296-9032-30a05bb53be6 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
Context: ApplicationName=Microsoft.ConfigurationManagement.exe SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
Context: ApplicationVersion=5.0.7804.1400 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
Context: LocaleID=MS\0x409 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
Context: ReturnAll=1 (Bool) SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
Context: FolderTypeName=SMS_BootImagePackage SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
Context: QueryQualifiers=1 (Bool) SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
Context: InstanceCount=1001 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
Context: __ProviderArchitecture=32 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
Context: __RequiredArchitecture=0 (Bool) SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
Context: __ClientPreferredLanguages=en-US,en SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
Context: __GroupOperationId=10280 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
CExtUserContext : Set ThreadLocaleID OK to: 1033 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
CSspClassManager::PreCallAction, dbname=CM_PS1 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
ExecQueryAsync: START SELECT * FROM SMS_BootImagePackage WHERE ActionInProgress!=3 ORDER BY Name SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
Adding Handle 45277256 to async call map SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
CExtProviderClassObject::DoCreateInstanceEnumAsync (SMS_Query) SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
CSspQueryForObject :: Execute... SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
Execute WQL =SELECT * FROM SMS_BootImagePackage WHERE ActionInProgress!=3 ORDER BY Name SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
Execute SQL =select all SMS_BootImagePackage.PkgID,SMS_BootImagePackage.Action,SMS_BootImagePackage.Architecture,SMS_BootImagePackage.DefaultImage,SMS_BootImagePackage.Description,SMS_BootImagePackage.DisconnectDelay,SMS_BootImagePackage.UseForcedDisconnect,SMS_BootImagePackage.ForcedRetryDelay,SMS_BootImagePackage.Icon,SMS_BootImagePackage.IgnoreSchedule,SMS_BootImagePackage.ImagePath,SMS_BootImagePackage.IsVersionCompatible,SMS_BootImagePackage.Language,SMS_BootImagePackage.LastRefresh,SMS_BootImagePackage.Manufacturer,SMS_BootImagePackage.MIFFilename,SMS_BootImagePackage.MIFName,SMS_BootImagePackage.MIFPublisher,SMS_BootImagePackage.MIFVersion,SMS_BootImagePackage.Name,SMS_BootImagePackage.NumOfPrograms,SMS_BootImagePackage.PkgID,SMS_BootImagePackage.PackageType,SMS_BootImagePackage.PkgFlags,SMS_BootImagePackage.StorePkgFlag,SMS_BootImagePackage.Source,SMS_BootImagePackage.PreferredAddress,SMS_BootImagePackage.Priority,SMS_BootImagePackage.SedoObjectVersion,SMS_BootImagePackage.ShareName,SMS_BootImagePackage.ShareType,SMS_BootImagePackage.SourceDate,SMS_BootImagePackage.SourceSite,SMS_BootImagePackage.SourceVersion,SMS_BootImagePackage.StoredPkgPath,SMS_BootImagePackage.StoredPkgVersion,SMS_BootImagePackage.TransformAnalysisDate,SMS_BootImagePackage.TransformReadiness,SMS_BootImagePackage.Version
from vSMS_BootImagePackage_List AS SMS_BootImagePackage where (SMS_BootImagePackage.PkgID not in (select all Folder##Alias##810314.InstanceKey from vFolderMembers AS Folder##Alias##810314 where Folder##Alias##810314.ObjectTypeName =
N'SMS_BootImagePackage') AND SMS_BootImagePackage.Action <> 3) order by SMS_BootImagePackage.Name SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
Results returned : 0 of 0 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
Removing Handle 45277256 from async call map SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
ExecQueryAsync: COMPLETE SELECT * FROM SMS_BootImagePackage WHERE ActionInProgress!=3 ORDER BY Name SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
CExtUserContext::LeaveThread : Releasing IWbemContextPtr=84734368 SMS Provider 04/12/2013 11:53:21 AM 6588 (0x19BC)
SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
CExtUserContext::EnterThread : User=**** Sid=0x0105000000000005150000002EA925CE2D54C0A5946DF1F931320000 Caching IWbemContextPtr=00000000050CF0C0 in Process 0xe60 (3680) SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Context: SMSAppName=Configuration Manager Administrator console SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Context: MachineName=****.**** SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Context: UserName=**** SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Context: ObjectLockContext=501335b7-4817-4296-9032-30a05bb53be6 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Context: ApplicationName=Microsoft.ConfigurationManagement.exe SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Context: ApplicationVersion=5.0.7804.1400 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Context: LocaleID=MS\0x409 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Context: __ProviderArchitecture=32 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Context: __RequiredArchitecture=0 (Bool) SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Context: __ClientPreferredLanguages=en-US,en SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Context: __GroupOperationId=10290 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Context: __WBEM_CLIENT_AUTHENTICATION_LEVEL=6 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
CExtUserContext : Set ThreadLocaleID OK to: 1033 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
CSspClassManager::PreCallAction, dbname=CM_PS1 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
ExecMethodAsync : SMS_BootImagePackage::GetImageProperties SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Requested class =SMS_BootImagePackage SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Requested num keys =0 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
CExtProviderClassObject::DoExecuteMethod GetImageProperties SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
*~*~e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\sspimagepackage.cpp(586) : Failed to get the image property from the source WIM file due to error 80070002~*~* SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
*~*~Failed to get the image property from the source WIM file due to error 80070002 ~*~* SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
CExtUserContext::LeaveThread : Releasing IWbemContextPtr=84734144 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
CExtUserContext::EnterThread : User=**** Sid=0x0105000000000005150000002EA925CE2D54C0A5946DF1F931320000 Caching IWbemContextPtr=00000000050CF0C0 in Process 0xe60 (3680) SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Context: SMSAppName=Configuration Manager Administrator console SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Context: MachineName=****.**** SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Context: UserName=**** SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Context: ObjectLockContext=501335b7-4817-4296-9032-30a05bb53be6 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Context: ApplicationName=Microsoft.ConfigurationManagement.exe SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Context: ApplicationVersion=5.0.7804.1400 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Context: LocaleID=MS\0x409 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Context: __ProviderArchitecture=32 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Context: __RequiredArchitecture=0 (Bool) SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Context: __ClientPreferredLanguages=en-US,en SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Context: __GroupOperationId=10295 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Context: __WBEM_CLIENT_AUTHENTICATION_LEVEL=6 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
CExtUserContext : Set ThreadLocaleID OK to: 1033 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
CSspClassManager::PreCallAction, dbname=CM_PS1 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
ExecMethodAsync : SMS_BootImagePackage::GetImageProperties SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Requested class =SMS_BootImagePackage SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
Requested num keys =0 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
CExtProviderClassObject::DoExecuteMethod GetImageProperties SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
*~*~e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\sspimagepackage.cpp(586) : Failed to get the image property from the source WIM file due to error 80070002~*~* SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
*~*~Failed to get the image property from the source WIM file due to error 80070002 ~*~* SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
CExtUserContext::LeaveThread : Releasing IWbemContextPtr=84734144 SMS Provider 04/12/2013 11:53:48 AM 6588 (0x19BC)
JAK

DaRT Tools in SCCM Boot Image

Similar Messages

Maybe you are looking for