WDS - No boot image

Good afternoon,
Hoping that one of you gurus will be able to help save my sanity here. :)
Background: We used RIS for quite a while, but after the SP2 update it failed so we decommisioned it. Now, WDS is on a Server 2008 R2 box and joined to the in the domain. While not an actual DHCP server, it is authorized in AD as a DHCP server. The DHCP
server is on a different server (running Solaris) on the same subnet. I have created images and have been able to do captures and remote installations.
Issue: The WDS server and the PXE clients work perfectly if they are both connected to a workgroup/soho type switch (5 port Linksys/DLink/etc). However if they are both plugged into the wall (the 'real' network) they do not work at all...the PXE client just
spins waiting for an address before returning that it couldn't locate a boot image. This is true even if I put both the WDS server and the PXE client on the same subnet.
I have ran packet captures on both working and non-working scenarios. In the non-working scenario with both machines on the same subnet the server's NIC can see the network traffic, but does not respond to it. When they are both on the workgroup switch it
does respond to it. I have checked the routers for this subnet and there is an ip address helper configured to match the IP of the WDS server. However, if they are both on the same subnet then they are in the same broadcast domain and really that shouldn't
matter...but it is there and configured because eventually the WDS server will move to a different subnet than the PXE clients.
So I am curious, does anyone have any ideas as to why WDS would work flawlessly on a little workgroup switch, but not on the corporate network even when on the same subnet, in the same room, on the same wallplate, running to the same switch?
I appreciate any and all advice, tips, tricks, insights that anyone could provide. :)
-Joe

Hi Joe,
Can I ask if you've configured the DHCP options required on your Solaris DHCP Server?
A snippet from the WDS deployment guide
http://technet.microsoft.com/en-us/library/cc766320(WS.10).aspx
"Add DHCP options 66 and 67. Option 66 should be set to the Windows Deployment Services server, and option 67 should be set to boot\x86\wdsnbp.com."

Similar Messages

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.

Automating OS install in WDS with multiple boot image

Hi, can someone explain to me if it is possible to completely automate a windows install in WDS with 3 different install and boot image. I am new to this and trying to learn everything i can.
I have 3 unattended files attributed to each install.wim already (and they work fine) and 1 unattended file for Windows Deployment Services.
my problem is as soon as the client PC PXE boot, I'm presented with 3 options in boot manager, maybe because i have 3 boot.wim files (from what i understand). after i pick which boot option
i want to use, i don't have to do anything anymore and windows is installed, the disk is partitioned and a user account is created.
https://drive.google.com/file/d/0ByIjtLJtT3oHaTFLcF9mWldnZmM/edit?usp=sharing
Is it possible to have an unattend file that will help me bypass the 3 options to make the process completely automated.
Can i create a script for a type of PC or brand of PC, so that the deployment server can see what type of PC or what brand of PC it is and automatically pick the boot file for that pc and automate the rest of the install. (maybe another software that can help
me do that, or i need to put something on the client computers so that they themselves pick the appropriate boot options)
Any help would be greatly appreciated.
Thanks
Georges

If you are new to deployment you should really learn the recommended way to deploy os:es.
You should use MDT (Microsoft Deployment Toolkit)
http://technet.microsoft.com/en-us/windows/dn475741.aspx
Here is a good virtual lab to get started:
http://go.microsoft.com/?linkid=9845755

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...

Branch office WDS still pullinh image from main site

Hi,
I'm trying to configure a WDS on our branch site.
what i did was open a new folder named DeployFilesFromMaster on the branch office server and replicate the DeploymentShare from main to branch office using DFS.
then i installed WDS services on the branch office and add a Boot Image (taken from DeployFilesFromMaster)
next i configured, under Scope Option on the DHCP server, options 66 (giving the ip address of the branch WDS), and option 67 (giving the path \Boot\x64\wdsnbp.com).
now when I'm booting a computer into PXE it start working, but when pressing F8 and use the netstat command i see it has a session to my main office deploy server instead to the branch office.
what do i need to change?
when looking in the branch office server, there is ofcourse the DeployFilesFromMaster folder and there is another folder named DeploymentShare that was made while installiing the WDS server, and there is a wdsnbp.com file as well. how do I know, when DHCP
direct me to the boot file name, that it direct me to the right file, or it doesnt matter.
thanks for your help

The variable WDSSERVER is a variable that is figured out by MDT when booting a machine using the boot image created by Microsoft Deployment Toolkit. Therefore it is not available in Windows.
If you want different WSUS servers depending on location of the client you can use for instance this technique in CustomSettings.ini. This will point clients on a specific subnet to a specific WSUS server.
[Settings]
Priority=DefaultGateway,Default
[DefaultGateway]
10.0.0.1=HQ
10.0.1.1=BranchOffice
[HQ]
WSUSServer=http://wsus-hq:8530
[BranchOffice]
WSUSServer=http://wsus-branch:8530
Blogging about Windows for IT pros at
www.theexperienceblog.com

WDS Multiple x64 Images for Windows 7 & 8.1

Hi all,
I wanted to know, what would be the best way to setup my WDS so that I can incorporate both windows 7 & 8.1 x64 boot and capture images.
The reason I ask this, is because I added the Windows 8.1 boot image, created a capture image and then after sysprep'ing a machine with windows 8.1 64 bit, I tried to capture it but ended up with the 0xc000000f error which has knocked out all of my
capture images.
I've only just attempted the dism mount & dismount method to see if it has fixed it, but I would appreciate if anyone knows an error free method so that I can have both windows 7 & 8.1 capture images to work together.
Thanks,
Hasan

Hi Hasan,
You can use the following similar thread solution to fix this issue.
Image Capture Boot Image Fails with 0xc000000f
https://social.technet.microsoft.com/Forums/windowsserver/en-US/a164b948-1778-42bd-8d77-9cef1ca70866/image-capture-boot-image-fails-with-0xc000000f?forum=winserversetup
If your WDS server are integrate with DFS please confirm the DFS has sync complete then to start deploy.
More information:
0xc000000f after reboot
http://answers.microsoft.com/en-us/windows/forum/windows_7-system/0xc000000f-after-reboot/5da88257-837d-4475-ad6e-9ea8968826f4
MDT 2012: File: \boot\BCD Status: 0xc000000f error
https://social.technet.microsoft.com/Forums/en-US/e8d30795-bda8-4162-80bb-2af6b90f1365/mdt-2012-file-bootbcd-status-0xc000000f-error?forum=mdt
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

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?

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

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

Unable to find a volume that is suitable for staging the boot image.

I have an SCCM 2012 OSD task sequence that is failing when it tries to stage the boot image to the drive before rebooting. The log file shows:
Staging boot image CET00028 TSManager 6/5/2014 3:57:58 PM 1492 (0x05D4)
Mounting \Device\HarddiskVolume6 at Z: TSManager 6/5/2014 3:57:58 PM 1492 (0x05D4)
Unmounting volume Z:\ TSManager 6/5/2014 3:57:58 PM 1492 (0x05D4)
Checking to see if the data path is on a bootable volume TSManager 6/5/2014 3:57:59 PM 1492 (0x05D4)
Volume C:\ because it is not suitable as the system partition TSManager 6/5/2014 3:57:59 PM 1492 (0x05D4)
Searching for a volume to stage the boot image TSManager 6/5/2014 3:57:59 PM 1492 (0x05D4)
Volume S:\ is not NTFS TSManager 6/5/2014 3:57:59 PM 1492 (0x05D4)
Volume C:\ because it is not suitable as the system partition TSManager 6/5/2014 3:57:59 PM 1492 (0x05D4)
Volume R:\ is not on a fixed disk TSManager 6/5/2014 3:57:59 PM 1492 (0x05D4)
Volume X:\ is not on a fixed disk TSManager 6/5/2014 3:57:59 PM 1492 (0x05D4)
BootImage::FindBootableVolume( NULL, sPath), HRESULT=80070490 (e:\qfe\nts\sms\framework\tscore\bootimage.cpp,1045) TSManager 6/5/2014 3:57:59 PM 1492 (0x05D4)
Unable to find a volume that is suitable for staging the boot image.
Element not found. (Error: 80070490; Source: Windows) TSManager 6/5/2014 3:57:59 PM 1492 (0x05D4)
I've seen others get this error code and fix it by injecting the correct storage drivers. In my case I believe I have the correct storage drivers. In a separate MDT 2013/WDS environment I can deploy
8.1 to the same machine using the same drivers with no problems so my drivers appear to allow proper access to the drive. When I check the volumes with DiskPart they all appear to be fine. The C:\ volume has the _SMSTaskSequence folder on it with
files so it is certainly writable. The system is set for UEFI mode. Of course if I change it to Legacy mode this problem doesn't happen. I have also integrated MDT 2013 into SCCM console and both an SCCM task sequend and an MDT task sequence
do the same thing. Any ideas?
Thanks,

From the error, the C could not be the staging location because it is system partition. You need to format a fixed drive to NTFS partition and try again.
Juke Chou
TechNet Community Support

SCCM WDS PXE Boot Authentication

Hi All,
The ability to do domain authentication for a PXE boot in RIS could be achieved by modifying the security directly on the image folder on the RIS server - however, I can't seem to implement the same access control in SCCM 2007 SP1 using WDS.
I have set up the capability to build bare metal machines using the OS Deployment feature in SCCM. The image process is advertised to “All Unknown Computers” and starts with the “builder” hitting F12 on the workstation. The boot image is loaded from the DP share and then the process begins.
My question is: How can I protect the PXE boot process by having the system request a domain Username and Password in order to begin the PXE boot process and also limit who can see the advertisements for the avialable images.
Thanks,
phil

Hi,
You can specify a password for computers that boot to PXE.
For more info :
http://technet.microsoft.com/en-us/library/bb680668.aspx
http://blogs.technet.com/configurationmgr/archive/2009/07/27/a-step-by-step-for-using-osd-through-system-center-configuration-manager-2007.aspx
http://technet.microsoft.com/en-us/library/bb632767.aspx
Regards.
Bechir Gharbi. MCSA, MCSE M+S, MCITP Server/Enterprise Administrator, MCT, MCTS Configuration Manager/Forefront

WDS & ISO boot

Hi there,
Can WDS be used to have clients PXE boot from a ISO image rather than WIM (such as a minimalistic Linux boot image)?
It was possible using RIS I think but WDS seems to support WIM images only or is there some other way?
Thanks beforehand,
Steven

Hi,
WDS works with Microsoft Windows Reinstallation Environment (Windows PE) 2.0, which is the new boot image format for Windows Deployment Services and must be .WIM format. Besides, RIS couldn't work with ISO image either. I suggest using WDS to deploy, because it can provide you the following extra benefits, comparing with RIS:
•    Reduces the complexity of deployments and the cost associated with inefficient manual installation processes.
•    Allows network-based installation of Windows operating systems.
•    Deploys Windows images to computers without operating systems.
•    Supports mixed environments that include Windows Vista, Microsoft Windows XP and Microsoft Windows Server 2003
•    Provides an end-to-end solution for the deployment of Windows operating systems to client computers and servers.
•    Built on standard Windows Vista setup technologies including Windows PE, .WIM files, and image-based setup.
What's more, it's not a complex task to create the .WIM boot image. You can simply use the standard boot images that are included on the Windows Vista or Windows Server 2008 media (located at \Sources\boot.wim) without modification. However, the Boot.wim that you use must match (or be newer than) the operating system of the install image. For instance, we couldn't use Windows Vista install media to create a Windows server 2008 boot image.
More information about Windows PE 2.0 boot image, please refer to:
Step-by-Step Guide for Windows Deployment Services in Windows Server 2003
http://technet2.microsoft.com/WindowsVista/en/library/9e197135-6711-4c20-bfad-fc80fc2151301033.mspx?mfr=true
I hope this helps.

WDS Problem when imaging PC

My WDS Server has been working fine for many months now.
Today i wanted to deploy an image to an all in one dell 3011 machine.
I uploaded the drivers for that machine and optimized the boot image so that the drivers are now there.
Now when I try to image a PC, I would, as always select the image i would like to use, rename the PC, and set it going.
It shows that it is injecting drivers and then goes on to installing the OS, now for some reason, normally once this is done it boots the PC to the desktop and then reboots, but at the point where it should do this the command prompt pops up and just hangs
there.
Any reason to why this is happening? is this a driver conflict of some sort?
Please get back to me ASAP as this is causing me huge problems.
Zac :)

Hi,
normally once this is done it boots the PC to the desktop and then reboots, but at the point where it should do this the
command prompt pops up and just hangs there.
What do you mean by this? Can you elaborate what you have done, could be better if you can share a screenshot? What you can do when it hangs?
Reboot it, can you get into the OS?
According to the current information, I guess it is a driver issue. Remove it and try again.
Hope this helps.

WDS - No boot image

Similar Messages

Maybe you are looking for