WinPe boot images

I created WinPe boot images from Windows AIK, Windows AIK was installed on a Windows 7 machine. Once Winpe wims were generated I moved them to sccm and imported the images to sccm, images were successfully distributed to DP. The question is when I am adding
drivers and I want to add drivers to my WinPe, they do not show up on the list. where have I gone wrong?

Perhaps Johan's excellent OSD Matrix will help you understand the requirements a bit more:
http://www.deploymentresearch.com/Research/tabid/62/EntryId/127/What-if-I-told-you-The-OSD-Support-Matrix-for-MDT-and-ConfigMgr-is-here.aspx
If you're using ConfigMgr 2012 R2 to deploy Windows 7 SP1, you should be using a WinPE 5.0 (or 5.1 it doesnt matter) image. WinPE 4.0 is not supported in ConfigMgr 2012 R2, nor are WinPE 3.1. You can still import these boot images, but you'll not be able
to amend them like adding drivers etc.
Regards,
Nickolaj Andersen | www.scconfigmgr.com |
@NickolajA

Similar Messages

How to update WinPE Boot image

Currently using WinPE 3.0 Version A10.
As face some new model laptop fail to run WinPE.
After i update WinPE3.0 Version A12.
How to update the boot image?
Please help.
Whelen

Are you using MDT or just WinPE alone?
If you are using MDT, you can add the driver into the "Out of Box" driver category, and then perform an update of the Deployment Share.
Keith Garner - keithga.wordpress.com

T520 won't detect Network card in WDS/WinPE/Ghost image disk

Hello all,
I figured I would just post this so I could save 2 days of someone elses life.
I'm not sure how many other modes have the EFI and UEFI bios's in them but this has caused a lot of problems when trying to capture an image / image the Lenovo T520. So for anyone else that is having these problems here is how I got around the problem.
The Problem:
While trying to boot up off a Capture image with a CD or PXE boot for our WDS server the laptop would not detect the network card giving no IP address and listing the adapter as a hybrid. When trying to do a ipconfig /renew it would give an error around the lines of the loopback something or other ....... the adapter could not be contacted or initated.
I instantly thought this was due to the vanila WinPE / Capture image not having the drivers for the Lenovoo T520, so I went to the website downloaded the new drivers and injected them into the WinPE disk(You will want ot use the NDIS Drivers which are included in the package for this). Following this process it would still not detect or install the NIC. After many hours of searching it would apear this was due to the EFI/UEFI bios options not going through the proper boot cycle when in a PE enviroment. The solution was to mess around with the EFI/UEFI switches in the WinPE boot image during the creation proccess as listed below:
ocdimg -m -o -u2 -udfver102 -bootdata:2#p0,e,bc:\winpe_x64\etfsboot.com#pEF,e,bc:\winpe_x64\efisys.bin c:\winpe_x64\ISO c:\winpe_x64\winpeuefi.iso
The link with more details is here: http://support.microsoft.com/kb/947024
Eseentially once the new boot image was complied with the proper EFI / UEFI options enabled it went through the proper boot process detected the NIC and installed the drivers which I previously provided on the disk and we where off to the races imaging the new laptop.
Hopefull this will help some others who are struggling with this or any other model that has this type of bios.
Cheers, and thanks
Please feel free to post any additional comments to help others if you found better ways to get around this
One side note the EFI/UEFI to legacy mode only does nothing for the NIC problem, I have seen some posts where they can help with the hard drive issues when imaging, however as for the nic not loading in PE enviroments this setting in the BIOS did not reslove the problem.

Hi Rusty1234
If I did not remember wrongly, you may present or add drivers (network, hardware) under WDS / Ghost software or copy necessary drivers (e.g. your T520 network card drivers) under it's PXE / boot section.
Happy 2012!
Peter
W520 (4284-A99)
Does someone’s post help you? Give them kudos as a reward, as they will do better to improve | Mark it as solved if the solution works for you, so it could be reference for others in the future
=====================================
Sound Enthusiast and Enhancement (Post comments, share mixes, etc.)
http://forums.lenovo.com/t5/General-Discussion/Dolby-Home-Theater-v4-for-most-Lenovo-Laptops/td-p/62...

Task Sequence Failing after Stating Boot Image and Restart in WinPE - Windows XP to Windows 7

Good Morning,
I am trying to upgrade an XP Machine to Windows 7 (x86). I was using the boot image inbuilt with SCCM 2012 R2 but read that it wont work correcltly. I am using Windows PE 3.1 boot image to boot.
The TS fails after trying to restart in Windows PE when staging the boot image.
From the Logs in CCM\Logs\SMSTSLog
I am still getting the same issue as when i am using the Boot image from ADK 8.1.
Anybody has an idea on how to solve this issue ? I have read a workaround about replacing the bootsect from the boot image but funily i am using an older boot image.
Kind Regards,
Mathieu

http://support.microsoft.com/kb/2910552
Torsten Meringer | http://www.mssccmfaq.de

How to use two different boot images in the same task sequence

I have a need to use Two boot images in the same task sequence. The reason is I'm deploying ZTI to McAfee encrypted devices which I have already done with McAfee v6 Encryption successfully.
Here's where my problem comes in. We are about to deploy McAfee v7 which means we will have a mix of v6 and v7 in our environment. I must have two special Boot images one with v6 drivers and one with v7 drivers in order for my process to work. I don't see
a way right now to assign more than one boot image to a task sequence. Is there any way to do this?
If I can't do that then I will have to create two task sequences and target collections based on the Endpoint Encryption version to deploy to.
If anyone has suggestions it would be much appreciated. Thank you

Have you tested copying those files to %windir%\system32\drivers during the WinPE session (just enable commandline support to your boot image) to see if they need to be in there before the OS start? Test that and if they don't need to be there during the
boot up of WinPE then:
Create two packages (v6 and v7)
"Run command line", use the package created earlier and just use "copy /Y .\*.* %windir%\system32\drivers" ...again, this should be run according to your needs, variable or some other check like I said

Can't add drivers to Server 2012 R2 boot image in WDS

Hi all.
I want to use my "old" Windows Server 2012 (not R2), WDS to deploy new R2 servers but i can't add driver package to the R2 boot image, it comes out with error code: 0xc0000135 no matter what drivers i use.
Without network drivers i can't boot the image on my physical servers, i've tried on a virtual machine where it works just fine.
I can't use the old boot image to install R2, then it comes with error: "Windows could not apply unattend settings during pass [offlineServicing]." when it tries to install it on both virtual and physical servers.
My initial thought is that the WDS server has to be on a R2 server but i can't find anything that proofs that.
Can someone confirm that non R2 WDS is not supported to R2 or does anyone have an idea to a solution?
Thank you in advance.

Okay maybe not a solution but i installed a new WDS server on R2 and then there was no problem adding driver package to to boot image.
So i was able to confirm my theory that it's not supported to deploy R2 from a non-R2 WDS server. If anyone can make it work please let me know but until then i think this is the only way.
If I understand your description of the issue, the problem is that you are trying to update a WinPE 5.0 WIM with a version of the ADK that services WinPE 4.0 images. Installing the new Windows Server 2012 R2 server caused SCCM to use the version of the
ADK that services WinPE 5.0 images. You should be able to deploy them fine from the other server, but you can only service them from the new one. You will not be able to service the older WinPE 4.0 images from the new server either.

Driver in boot image

Hi all,
I add some drivers for Wi-Fi and video, in boot image. I update distribution point. I see how the new drivers was injected in the image. I recreate the task with involved image. I create a new .iso file for offline deployment. But after installation
computer don't have installed drivers. Manually I update the drivers with some drivers used to add to the image and works.
Were I mistake ?
Thanks.

Parsing step node: Apply Driver Package TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Description: TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
ContinueOnError: TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
SuccessCodeList: 0 TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
(__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582) TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
No condition is associated with the step. TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Disable: TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Run in attribute: WinPE TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Timeout: TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
DefaultVarlist found TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Variable name: OSDAllowUnsignedDriver TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Action command line: osddriverclient.exe /install:NTM0003C /unsigned:%OSDAllowUnsignedDriver% TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Adding instruction at 7 TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Processed all elements TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Adding end group instruction at 8 TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
The next instruction after group will be at 9 TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Processing group TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Parsing group node: Setup Operating System TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Description: Setup Operating System TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
ContinueOnError: TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Disable: TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
(__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582) TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
No condition is associated with the step. TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Adding begin group instruction at 9 TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
There are 1 first level steps or groups TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Parsing step node: Setup Windows and Configuration Manager TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
Description: Actions to setup Windows and Configuration Manager client TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
ContinueOnError: TSManager 3/10/2014 3:20:05 PM 864 (0x0360)
SuccessCodeList: 0 TSManager 3/10/2014 3:20:05 PM 864 (0x0360)

Image Capture Boot Image Fails with 0xc000000f

I am trying to capture a Windows 8.1 Enterprise (with Update) x64 installation using WDS, but the Capture Image fails to load. I used the boot.wim from the Windows Server 2012 R2 (with Update) ISO to create a boot image in WDS and then a capture image from
it. After I press F12 and the progress bar finishes the following message appears:
This only happens when I boot the capture image - the original boot image that I imported in WDS boots normally. I also tried with the Windows 8.1 (with Update) boot.wim, but the issue reoccurs. This is a Hyper-V VM on Windows Server
2012. Is this a problem with the recent update?

Hi,
We’re currently experiencing exactly the same issue. Also a fully-updated Server 2012R2 (with the recent KB2919355 update) machine.
So far, I found two other posts with exactly the same issue:
1) http://wp.secretnest.info/?p=1474
2)
http://community.spiceworks.com/topic/472581-wds-capture-image-winload-exe-corrupt-or-missing
According to these posts it seems like the issue occurs after the first time a capture image based upon a Windows 8.1 or Server2012R2 boot.wim is created.
What I’ve tried so far is removing the server role, deleting the WDS store, rebooting the server and start over with a Windows 7 boot.wim. The normal boot.wim starts ok, but the created capture image doesn’t.
So the process of creating the capture boot image did ‘something’ in a way the new boot.wim differences from the old boot.wim. To find out what, I first mounted the new .wim file to see if winload.exe is actually there – it is both in
system32 as well as systen32\boot. So my second guess was that the Windows Boot Manager cannot find the windows loader, because of an incorrect declaration of disks in the BCD store.
I used BCDEDIT to show the differences between the working and non-working boot images:
Windows Boot Loader
identifier {1d214c07-6892-401c-a762-04647ad38560}
device ramdisk=[boot]\Boot\x64\Images\boot.wim,{b321afc0-8a23-4
961-85dd-a10f3c46473f}
description Windows 7 Boot Image
osdevice ramdisk=[boot]\Boot\x64\Images\boot.wim,{68d9e51c-a129-4
ee1-9725-2ab00a957daf}
systemroot \WINDOWS
detecthal Yes
winpe Yes
Device options
identifier {b321afc0-8a23-4961-85dd-a10f3c46473f}
inherit {68d9e51c-a129-4ee1-9725-2ab00a957daf}
ramdiskmcenabled No
ramdiskmctftpfallback Yes
-- Second - Non Working disk --
Windows Boot Loader
identifier {872352a0-0ad9-46f6-8612-1aed71ea8534}
device ramdisk=[boot]\Boot\x64\Images\boot-win7-capture.wim,{7a
b86a3a-3651-4f50-a748-34f3e784158c}
description Windows 7 Capture
osdevice ramdisk=[boot]\Boot\x64\Images\boot-win7-capture.wim,{68
d9e51c-a129-4ee1-9725-2ab00a957daf}
systemroot \WINDOWS
detecthal Yes
winpe Yes
Device options
identifier {7ab86a3a-3651-4f50-a748-34f3e784158c}
inherit {68d9e51c-a129-4ee1-9725-2ab00a957daf}
ramdiskmcenabled No
ramdiskmctftpfallback Yes
So the ID for the osdevice is the same, and only the device is different, but mentioned correctly under Device options (as far as my knowledge goes in this subject). I hope there will be a solution anytime soon.

Client getting an IP lease on the 64-bit LiteTouch boot image, but not the 32-bit version.

MDT 2012 U1. No problem with PXE booting so WDS is not the issue.
The NIC in question is the Intel I217-LM, which resides on both the new Dell Optiplex 9020 and the Latitude E7440. I downloaded the Dell drivers and then the Intel drivers and imported them into the WindowsPE drivers folder in the workbench. Updated
the boot images to make sure the new drivers were injected. Both yielded the same result. I can do everything I need to do when booting to the 64-bit LiteTouchPE_x64.wim boot image, but not the 32-bit version. When booting to the 32-bit
version, I get no IP configuration info at all.
When looking at the drivers in MDT, I see only one difference: the supported OS versions. The 64-bit driver supports 6.1, 6.1.1, and 6.2. The 32-bit driver supports only 6.1.1 and 6.2. Not sure if that's the issue.
Tried using drvload within 32-bit WinPE to manually inject the NIC driver. Still no luck. Ipconfig yields no configuration at all.
If I can't get these machines to boot to the 32-bit boot images, I can't deploy 32-bit images, unless there's a way of which I'm unaware.
EDIT: A little extra background. My WindowsPE folder has two subfolders called x86 and x64. Obviously, 32-bit drivers go into the x86 folder and 64-bit drivers go into the x64 folder. Then in the properties of the deployment share a
selection profile is selected which points to the architecture-specific folders.

Specifically what do you see when you are in WinPE, press the F8 button, and run ipconfig.
1. ipconfig shows no network adapters (see:
http://myitforum.com/cs2/blogs/rpedersen/clip_image002_53DA17D4.jpg ). This means you still have not loaded the correct device drivers, check the c:\windows\system32\wpeinit.log file.
2. ipconfig shows an "autoconfiguration IPv4 Address" with a netmastk of 255.255.0.0. This means that the client did not get an IP address from the DHCP server. Double check the connection between the client and the DHCP server.
3. ipconfig shows a correct address. There is no problem. :^)
Keith Garner - keithga.wordpress.com
I get the first result. Absolutely no network adapters, which I assumed indicated no appropriate device driver.
This is the result of the wpeinit.log from the machine booting to the 32-bit boot image:
Info WPEINIT is processing the unattend file [X:\unattend.xml]
Info Spent 1747ms initializing removable media before unattend search
Info ==== Initializing Display Settings ====
Info Setting display resolution 1024x768x32@60: 0x00000000
Info STATUS: SUCCESS (0x00000000)
Info ==== Initializing Computer Name ====
Info Generating a random computer name
Info No computer name specified, generating a random name.
Info Renaming computer to MININT-TFRU2BT.
Info Acquired profiling mutex
Info Service winmgmt disable: 0x00000000
Info Service winmgmt stop: 0x00000000
Info Service winmgmt enable: 0x00000000
Info Released profiling mutex
Info STATUS: SUCCESS (0x00000000)
Info ==== Initializing Virtual Memory Paging File ====
Info No WinPE page file setting specified
Info STATUS: SUCCESS (0x00000001)
Info ==== Initializing Optional Components ====
Info WinPE optional component 'Microsoft-WinPE-HTA' is present
Info WinPE optional component 'Microsoft-WinPE-MDAC' is present
Info WinPE optional component 'Microsoft-WinPE-WMI' is present
Info WinPE optional component 'Microsoft-WinPE-WSH' is present
Info STATUS: SUCCESS (0x00000000)
Info ==== Initializing Network Access and Applying Configuration ====
Info No EnableNetwork unattend setting was specified; the default action for this context is to enable networking support.
Info Acquired profiling mutex
Info Install MS_MSCLIENT: 0x0004a020
Info Install MS_NETBIOS: 0x0004a020
Info Install MS_SMB: 0x0004a020
Info Install MS_TCPIP6: 0x0004a020
Info Install MS_TCPIP: 0x0004a020
Info Service dhcp start: 0x00000000
Info Service lmhosts start: 0x00000000
Info Service ikeext start: 0x00000000
Info Service mpssvc start: 0x00000000
Info Released profiling mutex
Info Spent 749ms installing network components
Info Spent 1669ms installing network drivers
Error QueryAdapterStatus: no adapters found.
Info Spent 0ms confirming network initialization; status 0x80004005
Info WaitForNetworkToInitialize failed; ignoring error
Info STATUS: SUCCESS (0x003d0001)
Info ==== Applying Firewall Settings ====
Info STATUS: SUCCESS (0x00000001)
Info ==== Executing Synchronous User-Provided Commands ====
Info Parsing RunSynchronousCommand: 1 entries
Info Command 0: 0x00000000
Info Successfully executed command 'wscript.exe X:\Deploy\Scripts\LiteTouch.wsf' (exit code 0x00000000)
Info STATUS: SUCCESS (0x00000000)
Info ==== Executing Asynchronous User-Provided Commands ====
Info STATUS: SUCCESS (0x00000001)
Info ==== Applying Shutdown Settings ====
Info No shutdown setting was specified
Info STATUS: SUCCESS (0x00000001)
At first I thought the first bolded section might be relevant, but when I booted to the x64 boot image, which works fine, I get the same message in its wpeinit.log file. The only difference between the two log files is that the x64 boot image actually
shows successful installation of a driver where the second bolded section is.

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?

MDT Boot Image Creation

I just upgraded my SCCM 2012 RTM to SP1 and then to R2
I uninstalled the WAIK and installed 8.1 ADK
MDT 2012 Update 1
Now I am trying to add new MDT Boot images and I get this error
Started processing.
Creating boot image.
Copying WIM file.
Error while importing Microsoft Deployment Toolkit Task Sequence.
System.Exception: Unhandled exception occurred:
System.IO.FileNotFoundException: Could not find file '\winpe.wim'.
File name: '\winpe.wim'
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileInfo.get_Length()
at Microsoft.BDD.Core.DEInfo..ctor(FileInfo theFile)
at Microsoft.BDD.Core.DirectoryUtility.BeginCopyFile(String theSourceFile, String theDestFile)
at Microsoft.BDD.ElevatedProxy.NewBootImage.Create(String platform, String scratchSpace, String[] components, String[] extraContent, String wimFile)
Jacob

You need to remove the old MDT integration components and then reintegrate MDT with the new R2 installation of Configuration Manager by running the Configure ConfigMgr Integration utility from the start menu (inside the Microsoft Deployment Toolkit folder)
, if your on Server 2012 make sure you run the utility as an administrator (elevated) otherwise it will fail.
If you haven't already done so you will also need to update MDT to 2013 as 2012 Update 1 isn't supported in R2.
Its also a good idea to create new MDT Integrated Task Sequences and copy over any custom actions from your old ones to the new ones.
Cheers
Damon

How to identifiy Faulty Driver in Boot Image (Reverse Engineering of Adding a Driver to Boot Image)

Hello SCCM'lovers
I'm having a new EliteBook 820 G2 here which Fails PXE boot due to a false corrupted
Intel Advanced Network Service Virtual Adapter-Driver.
The PROBLEM now is how to determine under Boot Images - Properties - Drivers ... the correct one.
(see pic)
Over the months, I injected different ones. smsts.log indicates me that this driver is the problem but how can I reverse engineer it to find the correct version/timestamp whatever it on my DP

in theory at least there is a way.
The driver loading in windows will select the best driver based on the PNP-id, version of driver, if it's signed and so on.
you can find the PNP deviceID for that hardware on a installed system by looking in device manager.
After that you can follow the same rules that the system uses to determine which driver it would load by reading the inf files for each driver.
Would it be faster to just create a new one - most likely.
I also would recommend that you create a dedicated driver folder and category in SCCM for WinPE and only add the drivers you need. I prefer to use Original vendor drivers here (aka nicdrivers straight from Intel instead of DELL or HP or ... repackaged
versions

Error: Boot image to update:

Error: Boot image to update:
Microsoft Windows PE (x64)
Add ConfigMgr binaries
Add custom background
Enable Windows PE command line support
Add drivers
Intel(R) ESB2 SATA AHCI Controller
Intel(R) ESB2 SATA RAID Controller
Intel(R) ESB2 SATA AHCI Controller
Intel(R) ESB2 SATA RAID Controller
Intel(R) 4 Series Chipset Processor to I/O Controller - 2E00
Intel(R) 5000X Chipset Memory Controller Hub - 25C0
Intel(R) 5400 Chipset Memory Controller Hub - 4000
Intel(R) 82852/82855 GM/GME/PM/GMV to Processor I/O Controller - 3580
Intel(R) 82855PM Processor to I/O Controller - 3340
Intel(R) 82865G/PE/P/GV/82848P Processor to I/O Controller - 2570
Intel(R) 915G/P/GV/GL/PL/910GE/GL Processor to I/O Controller - 2580
Mobile Intel(R) 915GM/PM/GMS/910GML Express Processor to DRAM Controller - 2590
Intel(R) 945G/GZ/GC/P/PL Processor to I/O Controller - 2770
Mobile Intel(R) 945GM/GU/PM/GMS/940GML/943GML and Intel(R) 945GT Express Processor to DRAM Controller - 27A0
Intel(R) 946GZ/PL/GL Processor to I/O Controller - 2970
Mobile Intel(R) PM965/GM965/GL960/GS965 Express Processor to DRAM Controller - 2A00
High Precision Event Timer
Intel(R) 5100 Chipset Memory Controller Hub - 65C0
Intel(R) 6702PXH PCI Express-to-PCI Bridge A - 032C
Intel(R) E7230/3000/3010 Processor to I/O Controller - 2778
Intel(R) 7300 Chipset Memory Controller Hub - 3600
Intel(R) E7520 Memory Controller Hub - 3590
Intel(R) E8500/E8501 Hub Interface - 2600
Intel(R) 631xESB/6321ESB/3100 Chipset Serial ATA Storage Controller - 2680
Intel(R) 631xESB/6321ESB/3100 Chipset Serial ATA Storage Controller - 2680
Intel(R) 631xESB/6321ESB/3100 Chipset USB Universal Host Controller - 2688
Intel(R) Q35 Express Chipset Processor to I/O Controller - 29B0
Intel(R) 82801EB LPC Interface Controller - 24D0
Intel(R) 82801EB Ultra ATA Storage Controllers
Intel(R) 82801EB Ultra ATA Storage Controllers
Intel(R) 82801EB USB Universal Host Controller - 24D2
Intel(R) 82801FB LPC Interface Controller - 2640
Intel(R) 82801FB Ultra ATA Storage Controllers - 2651
Intel(R) 82801FB Ultra ATA Storage Controllers - 2651
Intel(R) 82801FB/FBM USB Universal Host Controller - 2658
Intel(R) 82801G (ICH7 Family) SMBus Controller - 27DA
Intel(R) 82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controller - 27C0
Intel(R) 82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controller - 27C0
Intel(R) 82801G (ICH7 Family) USB Universal Host Controller - 27C8
Intel(R) ICH8 Family Thermal Reporting Device - 284F
Intel(R) ICH8 4 port Serial ATA Storage Controller - 2820
Intel(R) ICH8 4 port Serial ATA Storage Controller - 2820
Intel(R) ICH8 Family SMBus Controller - 283E
Intel(R) ICH8 Family USB Universal Host Controller - 2830
Intel(R) ICH9 Family Thermal Subsystem - 2932
Intel(R) ICH9R/DO/DH 4 port Serial ATA Storage Controller 1 - 2920
Intel(R) ICH9R/DO/DH 4 port Serial ATA Storage Controller 1 - 2920
Intel(R) ICH9 Family SMBus Controller - 2930
Intel(R) ICH9 Family USB Universal Host Controller - 2934
Intel(R) ICH10 LPC Interface Controller - 3A10
Intel(R) ICH10 Family 4 port Serial ATA Storage Controller 1 - 3A00
Intel(R) ICH10 Family 4 port Serial ATA Storage Controller 1 - 3A00
Intel(R) ICH10 Family SMBus Controller - 3A30
Intel(R) ICH10 Family USB Universal Host Controller - 3A64
Intel(R) 31154 133MHz PCI TO PCI Bridge - 537C
Intel(R) QuickPath Architecture I/O Hub to ESI Port - 3400
Mobile Intel(R) 45 Express Chipset Series Processor to DRAM Controller - 2A40
Windows Hardware Error Device
Intel(R) 4 Series Chipset Processor to I/O Controller - 2E00
Intel(R) 5000X Chipset Memory Controller Hub - 25C0
Intel(R) 5400 Chipset Memory Controller Hub - 4000
Intel(R) 945G/GZ/GC/P/PL Processor to I/O Controller - 2770
Optional components:
Scripting (WinPE-Scripting)
Startup (WinPE-SecureStartup)
Network (WinPE-WDS-Tools)
Scripting (WinPE-WMI)
Intel(R) QuickPath Architecture System Address Decoder - 2C01 - Failed to inject a ConfigMgr driver into the mounted WIM file
Failed to inject a ConfigMgr driver into the mounted WIM file
The SMS Provider reported an error.: ConfigMgr Error Object:
instance of SMS_ExtendedStatus

Yes as others have said you hardly ever need to inject drivers now into your boot images. There are exceptions to this i.e. Surface Pro USB Ethernet Adapter drivers and some of the newer 2014/2015 Ethernet adapter drivers from Dell and Lenovo. You certainly
don't need to inject all the drivers from a driver folder source as it appears from your post.
If your having problems with no network after you boot into your image just inject the Ethernet drivers only.
If your using WinPE 5 - Use the Windows 8.1 Ethernet Driver (irrespective of what OS your trying to deploy)
If your using WinPE 4 - Use the Windows 7 Ethernet Driver (irrespective of what OS your trying to deploy).
Cheers
Damon

Modifying default boot image

I need to edit default x86 boot image and add one address to host file.
In default directory: \Program Files\Microsoft Configuration Manager\OSD\boot\i386 I see two wim files. Boot.PS100002.wim and boot.wim. What is the one that is used with PXE?

This was a test. I had a problem with multicast (giving error 0x80091007 = hash error) when trying multicast in different vlan than
where configmgr server resides. Multicast was working fine in same vlan as confimgr server.
In problematic vlan only fqdn resolves to configmgr server, not short name. When I add ConfigMgr server to WinPE host file, then multicast
starts to work.

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

WinPe boot images

Similar Messages

Maybe you are looking for