white43210

So I figured this out. It was nothing with my configuration, but rather when I imported the drivers from the Intel package I neglected to import some of the required files that were named differently than my primary NIC .inf. This link helped me resolve the issue.

Thanks for your response Lucid. I originally was running an earlier version of AIK. It didn't work at that point and after reading posts regarding WAIK I installed the latest and greatest version ... so essentially I have reinstalled - copied new files over old and used WBEM to update WinPE versions. I have tried this on 4-5 custom boot images with 4 different intel drivers ... 32 bit and 64 bit. A version from Panasonic and a version directly from Intel. I'm really only trying to install one driver at a time instead of a whole list of drivers. I have tried giving extended permissions to the target image folder ... I'm suspicious of the image staging folder however. Isn't that going to be the Windows/Temp folder where it actually mounts the image to add the drivers? I'm guessing SYSTEM should have full control on this folder? Thanks!

I would like to add that I have tried drivers from both the laptop manufacturer and directly from Intel's website.

SCCM 2007 SP2 R3, SQL Server 2008 x64, Windows Server 2008 R2 x64 I am having difficulty with a bare metal install and capture of Win7 on a laptop. I have followed all guides closely and verified correct version of MDT, AIK, WINPE, but I simply cannot inject drivers into my boot image. I keep getting the following message from the wizard. Error: Boot image to update: MDT Custom PE Error: Actions to perform: Add ConfigMgr binaries Enable Windows PE command line support Add drivers Error: Failed to import the following drivers: Intel® 82567LM-3 Gigabit Network Connection - Failed to inject a ConfigMgr driver into the mounted WIM file Error: The wizard detected the following problems when updating the boot image. Failed to inject a ConfigMgr driver into the mounted WIM file Failed to inject a ConfigMgr driver into the mounted WIM file Failed to inject a ConfigMgr driver into the mounted WIM file Failed to inject a ConfigMgr driver 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 = "c:\\qfe\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp"; Line = 4262; ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook"; Operation = "ExecMethod"; ParameterInfo = "SMS_BootImagePackage.PackageID=\"BWW00015\""; ProviderName = "WinMgmt"; StatusCode = 2147749889; }; I've noted several other posts where user advise using DSIM. Is this a requirement? I like the ability to utilize the driver repository / see the injected drivers in the SCCM console. Thanks!

Having same issue. I find that when I run IPCONFIG the computer reports no NIC information. I'm guessing that I need to provide additional drivers for the boot image? On a side note - this website has been a wealth of knowledge in the process of getting SCCM up and running. I would dare say that no other site (including M'soft) has the detail or spectrum of information included here. Thanks a bunch!!

I noted that in a previous post that R2 cannot be installed on Volume Licensing Product Version. Is that still true?

I'm guessing that perhaps I don't have R2 installed because I don't have the check box in the General tab of my PXE Service Point Site System Properties. Is this a requirement?

Thanks Anyweb for your quick response. Yes I followed your instructions from your step by step on deploying XP. 1)Right clicking on Computer Association - Import Computer Information - 2)Choose Single Computer - 3)Typed in a Computer Name - And typed in the MAC address - 4)Pointed the computer at my Build & Capture collection - 5)When I refresh the collection the computer shows up in the collection - I'm not getting far enough thru the process to see anything in the SMSTS.log on the client PC. Is there other LOG files that you would recommend? I ran a test deploy on the PC once before, and it installed XP. I then changed my task sequence to employ a more advanced task sequence including drivers and software, but it only ran to the point of quick formatting the drive. I have since deleted everything and gone back to just a basic advertisement just to start from the top and troubleshoot which task was bombing out - but now I'm stuck at this annoying error. I even removed my network driver from the boot.wim thinking it was corrupting the boot image. Could there be residual information in SCCM that I need to flush from a previous "Import Computer Information"? I simply deleted the computer from the original Build & Capture collection.

I'm fairly new to SCCM and thus was very happy to find this site. The step by step HOW TO guidance has been wonderful. I'm getting this error message when i try to boot to PXE boot to a Build & Capture task sequence. Every other reference I see to this error is about deploying Windows 7. However I am trying to build and capture a Windows XP sp3 machine. Windows failed to start. A recent hardware or software change might be the cause. To fix the problem: 1. Insert your Windows installation disc and restart your computer 2. Choose your language settings and then click "Next." 3. Click "Repair your computer." If you do not have this disc, contact your system administrator or computer manufacturer for assistance. File: \windows\system32\boot\winload.exe Status: 0xc0000001 Info: The selected entry could not be loaded because the application is missing or corrupt. I get the option to hit Enter=Continue or ESC=Exit at the bottom of the screen. When I hit Enter it shows me the OS Chooser screen with Microsoft Windows PE (x86) displayed as an option. However, if I choose this option it takes me back to the original error message. My environment is Windows 2008 Server w/ SCCM 2007 sp2 installed. WDS resides on a seperate 2008r2 server. My LAN is broken up into many VLANs so I manually inserted options 66 =<FQDN of WDS server> and 67 = <\SMSBoot\X86\wdsnbp.com> on a separate 2003 DHCP server.