Import MDT Task Sequence Error - The ConfigMgr Provider Reported and Error -error
Hi, I'm working on importing a Microsoft Deployment Task Sequence.. After completing the wizard (after sysprep), it tries to go to summary but then displays an error on the screen: Error while importing Microsoft Deployment Toolkit Task Sequence: Details: The ConfigMgr Provider reported an error. Not sure what this means... anyone know? Or where to look for more information?
August 14th, 2008 9:25pm

Hi there! Can you post your log file? Check the smsprov.log its located in %install path%\logs. If you cant find it, just search for the file. Post the section which contains the error. Thanks
Free Windows Admin Tool Kit Click here and download it now
August 14th, 2008 10:13pm

Thanks for pointing me to the smsprov.log it contained a WMI error. I simply rebooted the server and tried again and it worked. So, I think this error may have been a result of installing many different components during my SCCM MDT deployment to this server (and not rebooting). The problem is now fixed... the key was to look to the smsprov.log to find out more details about the problem. Thank you for you help!
August 15th, 2008 2:40pm

Happy that i could point you in the right direction
Free Windows Admin Tool Kit Click here and download it now
August 15th, 2008 11:26pm

I'm having the same issue. I tried rebooting. Here's my smsprov.log from the site server. Can i post or email someone my .log file?
September 24th, 2009 7:14am

post the errors heremy SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064
Free Windows Admin Tool Kit Click here and download it now
September 24th, 2009 10:56am

ok from the smsprov.log file you sent me I see this ERROR> The boot image is not finalized. We only support to import a finalized boot image [106C][Wed 09/23/2009 15:15:19]: * * e:\nts_sms_fre\sms\siteserver\sdk_provider\smsprov\sspbootimagepackage.cpp(3057) : Failed to insert OSD binaries into the WIM file * * [106C][Wed 09/23/2009 15:15:19]: * * Failed to insert OSD binaries into the WIM file which sounds like you are not using the correct boot.wim file, "The boot image is not finalized. We only support to import a finalized boot image", interestingly enough someone has the exact same problem here, but did not post a solution http://deploymentforum.com/Community/Forums/tabid/124/forumid/16/postid/3899/view/topic/ptarget/3899/Default.aspx so, how are you doing this exactly ? what versions of SCCM are you using, what version of WAIK ?my SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064
September 25th, 2009 8:17am

ERROR> The boot image is not finalized. We only support to import a finalized boot image It's covered in the docs: http://technet.microsoft.com/en-us/library/bb680372.aspx(see "Adding Custom Boot Images").
Free Windows Admin Tool Kit Click here and download it now
September 25th, 2009 9:48am

Wow, this is getting frustrating, must be user error!!! I'm using SCCM 2007 SP1 R2 and I'm trying to create and amd64 and I guess a x86 boot.wim image for deploying WS08 to a x64 platform.I've followed the Quick Start Guide for Configuration Manager 2007.docx, no luck...I've followed this article, which was useful, http://www.windows-noob.com/forums/index.php?/topic/562-how-can-i-deploy-windows-server-2008-using-sccm-2007-sp1/but no luckI've followed this, which all worked but sccm didn't like the image, https://www.sit.auckland.ac.nz/Create_a_custom_boot_image_with_WAIK_for_Windows_7how do i get a boot.wim imported into SCCM??? Below is cut from my smsprov.log....any ideas? :([79C][Wed 09/30/2009 10:47:50]:WIM_MSG hit default [79C][Wed 09/30/2009 10:47:50]:WIM_MSG hit default [79C][Wed 09/30/2009 10:47:50]:WIM_MSG hit default [79C][Wed 09/30/2009 10:47:50]:WIM_MSG hit default [79C][Wed 09/30/2009 10:47:50]:WIM_MSG hit default [79C][Wed 09/30/2009 10:47:50]:**e:\nts_sms_fre\sms\siteserver\sdk_provider\smsprov\sspbootimagepackage.cpp(3057) : Failed to insert OSD binaries into the WIM file**[79C][Wed 09/30/2009 10:47:50]:**Failed to insert OSD binaries into the WIM file **[79C][Wed 09/30/2009 10:47:50]:CExtUserContext::LeaveThread : Releasing IWbemContextPtr=32242864[1214][Wed 09/30/2009 10:47:51]:CExtUserContext::EnterThread : User=DOMAIN1\bxw1a Caching IWbemContextPtr=32242864 in Process 0xe04 (3588)[1214][Wed 09/30/2009 10:47:51]:-------------------------------------------------------------[1214][Wed 09/30/2009 10:47:51]:CExtUserContext: Context Item Name: SMSAppName[1214][Wed 09/30/2009 10:47:51]:CExtUserContext: Context Item String value: SMS Administrator Console[1214][Wed 09/30/2009 10:47:51]:-------------------------------------------------------------[1214][Wed 09/30/2009 10:47:51]:CExtUserContext: Context Item Name: MachineName[1214][Wed 09/30/2009 10:47:51]:CExtUserContext: Context Item String value: SAD2207[1214][Wed 09/30/2009 10:47:51]:-------------------------------------------------------------
September 30th, 2009 9:05pm

Hmmmmm, I even get the same error when I tried to add the default sccm .wim's back. Guess i change those too.[B88][Wed 09/30/2009 11:13:19]:WIM_MSG hit default [B88][Wed 09/30/2009 11:13:19]:WIM_MSG hit default [B88][Wed 09/30/2009 11:13:19]:WIM_MSG hit default [B88][Wed 09/30/2009 11:13:19]:WIM_MSG hit default [B88][Wed 09/30/2009 11:13:19]:**e:\nts_sms_fre\sms\siteserver\sdk_provider\smsprov\sspbootimagepackage.cpp(3057) : Failed to insert OSD binaries into the WIM file**[B88][Wed 09/30/2009 11:13:19]:**Failed to insert OSD binaries into the WIM file **[B88][Wed 09/30/2009 11:13:19]:CExtUserContext::LeaveThread : Releasing IWbemContextPtr=32242864[79C][Wed 09/30/2009 11:13:20]:CExtUserContext::EnterThread : User=DOMAIN1\bxw1a Caching IWbemContextPtr=32242864 in Process 0xe04 (3588)[79C][Wed 09/30/2009 11:13:20]:-------------------------------------------------------------[79C][Wed 09/30/2009 11:13:20]:CExtUserContext: Context Item Name: SMSAppName[79C][Wed 09/30/2009 11:13:20]:CExtUserContext: Context Item String value: SMS Administrator Console[79C][Wed 09/30/2009 11:13:20]:-------------------------------------------------------------[79C][Wed 09/30/2009 11:13:20]:CExtUserContext: Context Item Name: MachineName[79C][Wed 09/30/2009 11:13:20]:CExtUserContext: Context Item String value: SAD2207[79C][Wed 09/30/2009 11:13:20]:-------------------------------------------------------------
Free Windows Admin Tool Kit Click here and download it now
September 30th, 2009 9:16pm

Has anyone found an answer to this question? I am attempting to run this using the "Create Microsoft Deployment Task Sequence" by following the instructions provided in the Quick Start Guide for Configurat Manager 2007, but the task creation fails when trying to import the new boot image. Here are the errors from my smsprov.log file:[11D4][Mon 10/05/2009 11:22:07]:Failed to get the PEIMG tool installation location due to error -1[11D4][Mon 10/05/2009 11:22:07]:ERROR> Failed to get PEImage command line[11D4][Mon 10/05/2009 11:22:07]:ERROR> The boot image is not finalized. We only support to import a finalized boot image[11D4][Mon 10/05/2009 11:22:18]:**e:\nts_sms_fre\sms\siteserver\sdk_provider\smsprov\sspbootimagepackage.cpp(3057) : Failed to insert OSD binaries into the WIM file**[11D4][Mon 10/05/2009 11:22:18]:**Failed to insert OSD binaries into the WIM file
October 5th, 2009 8:34pm

what version of mdt have you got installed ? what version of sccm is installed ? what os are you running ? and what version of SQL server are you running I'm just trying to understand your setup before figuring out why it\s failing. cheers niallmy SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064
Free Windows Admin Tool Kit Click here and download it now
October 5th, 2009 9:15pm

Niall,I'm running into the exact same issue as Gary when I try creating a boot image via SCCM 2007 R2 using. Below is my configuration:MDT 2010 w/ AIK x86 (6.1.7600.16385)SCCM 2007 SP1 R2Windows Server 2003 Standard SP2 R2 running SQL Server 2005 (9.0.4035)Any help in getting this resolved would be appreciated.Thanks,Steve
October 14th, 2009 8:51pm

well then, I think you should upgrade SCCM 2007 sp1 to sp2 which is still in Release Candidate phase or wait until it's supported, see Johans post here for more details of what verions of WAIK/MDT and SCCM go together.. cheers niallmy SCCM step by step Guides > http://www.windows-noob.com/forums/index.php?showtopic=1064
Free Windows Admin Tool Kit Click here and download it now
October 14th, 2009 9:45pm

Has anyone figured this out?I have a Windows 2008 R2 box running SCCM 2007 R2 with WAIK 7 and Deployment Toolkit 2010.Error from log:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~[1470][Tue 11/24/2009 14:12:12]:WIM_MSG hit default [1470][Tue 11/24/2009 14:12:12]:WIM_MSG hit default [1470][Tue 11/24/2009 14:12:12]:**e:\nts_sms_fre\sms\siteserver\sdk_provider\smsprov\sspbootimagepackage.cpp(3057) : Failed to insert OSD binaries into the WIM file**[1470][Tue 11/24/2009 14:12:12]:**Failed to insert OSD binaries into the WIM file **[1470][Tue 11/24/2009 14:12:12]:CExtUserContext::LeaveThread : Releasing IWbemContextPtr=64308088
November 24th, 2009 10:19pm

In my case it was I needed to install SCCM 2007 SP2 that included Windows 7 support tools. I found that my current verison of SCCM (SP1) was trying to use PEIMG.exe which was a tool included in the previous version of WAIK. It has now been replaced by DISM.exe but SCCM 2007 SP1 with R2 was still trying to use PEIMG even though I had the latest WAIK installed. I have upgraded to SCCM 2007 SP2 R2 and it is now finally working. I have wasted days trying to figure this out. Make sure that you ugrade your SCCM 2007 to SP2.
Free Windows Admin Tool Kit Click here and download it now
January 13th, 2010 9:19pm

I am already at SP2 - I am having similar issues Here is the output of the error that i captured. Started processing. Creating boot image. Generating boot image. Copying additional directory. Capturing new boot image WIM file. Copying WIM image to package source directory. Error while importing Microsoft Deployment Toolkit Task Sequence. 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) at Microsoft.BDD.Wizards.Controls.SCCM_ImportTaskSequenceTask.DoWork(SmsPageData smspageData, Dictionary`2 data) Any help would be great.
October 22nd, 2010 4:32pm

Dear SCCM experts, One of my customers experiences exactly the same issue: SCCM 2007 R2 SP2, SQL 2008, MDT 2010 Update 1. We went through the MDT quick start guide for SCCM 2007 and, upon the Task Sequence creation (step 3.1 in the quick start guide), it miserably fails, exiting with the exact same error as dynas001 above. I interpret it as a task sequence failure to create the MDT package with this wim file. I triple-checked the MDT package source share and the WIM file accessibility. Any help would be greatly appreciated.MVL
Free Windows Admin Tool Kit Click here and download it now
December 2nd, 2010 8:21am

I almost go crazy with the same problem but ... : ) this error is due to you are using a version of WAIK different from what is already included in SCCM 2007 SP2 . Uninstall your current version of WAIK and install the version included in SCCM 2007 SP2 . Then run SCCM 2007 SP2 Setup again and choose " Update ". Boot images should be created without problems under the path " <SCCM_installpath> \ OSD \ boot " Tested and running actually in " Windows 2008 R2 " to " SCCM 2007 SP2 . "
January 22nd, 2011 9:54am

In my case the only thing that solved my problem was add the "System" account to the share with Full Control. You can try to use Process Monitor to see what is the problem as I did. Hope that helps Regards, Bruno Bruno Bertelli - IT Consultant for Victrix
Free Windows Admin Tool Kit Click here and download it now
June 29th, 2011 7:43pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics