Cannot Add drivers to boot image

does any one know why ?
cuz i can in 7 but not in vista
cause of this , cannot successfly wds windows vista

Hi David Smale,
Added Windows 7 boot image to WDS then try to deploy vista again.
More information:
Windows Deployment Services Overview
http://technet.microsoft.com/en-us/library/hh831764.aspx
Managing and Deploying Driver Packages
http://technet.microsoft.com/en-us/library/dd348456(WS.10).aspx
WDS - Using WAIK - Inject Driver into boot.wim image
https://social.technet.microsoft.com/Forums/windowsserver/en-US/195d1451-35c4-4117-b673-9d2acebb76b9/wds-using-waik-inject-driver-into-bootwim-image?forum=winservergen
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

Can't add drivers to boot images

I am just getting into OSD with SCCM 2012 R2 and have run into issues with the OS Image deployment. I think it is because the boot image doesn't have the correct NIC drivers injected, but I can't seem to do it. When I right-click the driver(s)
in SCCM, click Edit->Boot Images the section where I can select the boot images that I want to inject the drivers into is dark grey and there are no images listed. Is there something I have to do to the drivers/packages/categories before I am able
to add the drivers? Again, this is my first attempt at doing this so be kind. :)

No, my user account is a domain admin member.
I know this is a totally side topic, but that's a terrible practice security wise. That's my point whether or not it's the domain admin.
As for the drivers in the boot image, you need to be using boot images that line up with your version of ConfigMgr to manage them in the console.
2012 RTM -> WinPE 3.1
2012 SP1 -> WinPE 4.0
2012 R2 -> WinPE 5.0
2012 SP1 with CU3 or CU4 supports WinPE 31 and WinPE 5.0 boot images but you can't manage certain aspect of them in the console like drivers.
2012 R2 supports WinPE 3.1 boot images (but not WinPE 4.0) with the same caveats.
You can use the method outlined by Jordan to manually inject drivers if necessary. If there a reason you aren't using the standard boot images created during ConfigMgr installation though?
Also, you mentioned using the boot images you used in WDS. If these are based on the boot images directly from the Windows media, those won't work at all. As mentioned, you should be using the ones created at install time.
Jason | http://blog.configmgrftw.com

Can't inject drivers into boot images as they don't appear

Hello,
I have a problem trying to inject some drivers into the boot image using SCCM 2012.
I right click on the specific driver, I choose Edit > Boot image and there no boot images show up! The list is empty.
We do have 2 boot images (x32 and x64) and they are working just fine!
Does anybody have a clue what is going wrong here?
Thanks.

What version of ConfigMgr (RTM, SP1, or R2) are you using and what version are the boot images?
Each version of ConfigMgr can only directly manage (including driver injection) specific boot image versions.
RTM -> WinPE 3.1
SP1 -> WinPE 4.0
R2 -> WinPE 5.0
Thus, you are most likely trying to edit downlevel (or maybe uplevel) boot images.
Jason | http://blog.configmgrftw.com

Extract drivers from boot image

I have a boot image and my team members added lot of drivers on top of boot images.... Now I want to get a report to get the list of drivers that are integrated
and their source path as I must have to keep them in a separate folder so that in my up coming migration project I can use them again to integrate in new boot images when migrated from sccm 2012 RTM to SP1 and R2
Kindly through some light on this
HunBoy Started learning from this page

You should not use the drivers from your old boot images in your new boot images.
Windows PE drivers are not the same for every verison of ConfigMgr.
Win PE 5.0 = SCCM 2012 R2
Win PE 4.0 = SCCM 2012 SP1
Win PE 3.0 = SCCM 2012 RTM
And the drivers you need are:
Win PE 5.0 = Windows 8.1
Win PE 4.0 = Windows 8
Win PE 3.0 = Windows 7
Windows PE 5.0 also includes many new drivers so drivers that you needed in older versions of PE might not be required any more...
Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs:
www.ronnipedersen.com/ and www.SCUG.dk/ | Twitter
@ronnipedersen

Help.. cannot add user on restored image to xserve

Hello;
After a hardware failure of a 10.5.8 ical server I restored the ccc image to a brand new xserve (purchased early 2009).
All looks good until I log into wgm... authenticate to ldap... and see that the new user button is greyed out, all editing capabilities are gone...
I am panicked and don't know what I did wrong?
Thanks.

Wow, that was obscure, thanks for posting an update with the solution. Maybe you save someone from the same issue or answer the question for someone in future and save them the trouble you went through.
=Tod

Default or custom boot image

Hi to everyone. Currently I am in a process of learning SCCM 2012 R2, having experience in working with MDT & WDS. I want to perform capturing of reference virtual Windows 7 machine image and to deploy it later to bare-metal virtual machine. In order
to do this I have to create task sequence media and while creating it I have to choose boot image. Since I have to "inject" vmxnet3 network drivers into boot image before using it for creation of task sequence media, what is recommended practice
- doing so with default boot image (for example x64 flavour of it) or adding Windows 7 boot image into SCCM and injecting these drivers into it? In MDT I did not have any default boot images so I had to add them from Windows 7 installation media and inject
these network drivers into them.

No consequence. As Darrick says IT Admins often add their own custom images. However that is not essential. If you're just learning keep it simple.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Upgrade to SCCM R2 have to recreate boot image and TS

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

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

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

Using MDT boot image in SCCM 2012

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

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

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.

Use DISM to add drivers returns an error on an image which has profiles and programdata on a seperate volume

Hi,
We capture and modify W7 Ent and Pro OS images on a regular base by using DISM to add drivers for example. Until now we never had a problem because we always had images which only had 1 OS volume captured. DISM works fine to mount the image to a mount
folder, add drivers, and save the changes in the image.
However now we encounter an issue when doing the same actions on an image where the \Windows folder was located on the C:\ volume and \programdata and \users folders where redirected to a D:\ volume.
When mounting the C:\ volume image (including everything except \programdata and \users folders) the error we receive when trying to add or get drivers is:
Error 3 - the \Windows folder is not a valid Windows directory.
The DISM.Log file show right before this error that the remote registry could not be contacted.
This is caused I think because the registry files are located on the \Users folder, but since this folder is not captured in the image (located on another volume during capture) it cannot find the registry.
My question is: how can we resolve this?
What we have now is 1 WIM file where index1 is the OS (C:\ volume) and index2 is the \ProgramData and \Users folders (D:\ volume). Probably the way of capturing the image and redirecting programdata/users is not done in a correct way...
Note: the image index1 and index2 restore works fine - the unattended.xml contains also redirection to the folders paths for \programdata and \users...
Any help or advice would greatly be appreciated!
Thx.
Steve
Wkr, Steve

Hi Steve,
You can be right that DISM don’t support the scenario that User profile and System are in the separated volumes.
As a workaround, we should use the defaults to put the profile on C: during capture image, and then set the profile path to be on the D: drive after the image deploying.
Please refer to below KB for how to using Sysprep to redirect profiles’ locations.
Customize the default local user profile when preparing an image of Windows
http://support.microsoft.com/kb/973289/en-hk
Hope these could be helpful.
Kate Li
TechNet Community Support

Solaris 10 won't boot up "Cannot load drivers for /pci@400.....

This is the error message that I am getting on a Solaris 10 sparc server
scsi: no major number
cannot load drivers for /pci@400.....
Can't load the root filesystem
Type 'go' to resume
{0} ok
Is there a way for me to correct this issue. It looks like I am missing a scsi driver to boot up the server? Is there a way to boot into single user mode, mount the filesystem and rediscover the hardware, etc.....

First i guess you have to verify that you can find the disks with a probe-scsi-all
next you can boot it of a CD-rom/dvd into single-user:
boot cdrom -s
.. or similar into single-user from a jumpstart image:
boot net -s
Then you can mount the root disk under something such as:
/mnt
and rebuild the config with:
devfsadm -R /mnt
be careful if you have a mirrored filesystem though, you don't want to update just one of the mirrors without first breaking the mirror..
.7/M.

Handling boot-critical Win 7 drivers in ZCM imaging

Does anyone know how to handle boot-critical drivers with ZCM imaging?
These are typically disk controller and/or NIC drivers.
MS WIM seems to require that you mount the image and "reflect" the
driver into the image. (Gotta love MS's way with words.)
I was wondering if this could be done in one of the Sysprep phases?
Use and add-on image to deliver the boot-critical driver to, say,
C:\Drivers then install it during the phase.
I tried the Windows-PnpCustomizationsNonWinPE entry in the
offlineServicing phase. Doesn't work.
Maybe the Windows-PnpCustomizationsNonWinPE or
Windows-PnpCustomizationsWinPE entry in the windowsPE phase?
I'm trying to avoid having to open the image and add critical drivers
that way.
BTW, I've gotten other drivers to install easily in a Powershell
script with DPINST. Works like a champ and allows me to deliver just
the drivers I need as an add-on image.
All suggestions/discussion welcome.
Regards,
Don

Don,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

64-bit Boot Image Drivers Are Not Working

I've been deploying Windows 7 x86 and x64 for years. I've been using the same 32-bit boot image for both and it's been working great.
We've decided to take the plunge and go all x64 moving forward. I want to switch to a 64-bit boot image so I don't have to curate the drivers for two architectures.
I've created a 64-bit boot image, and included all of the 64-bit versions of the drivers in my 32-bit boot image, but they don't seem to be working. I've tried booting 3 different models, but I receive "Failed to find a valid network adapter."
I've looked within the boot image, because I wanted to see the driver files. Either I just don't know where I'm looking, or they're in the "Files" folder where each file is renamed to a number.
What might I have done wrong?

I've solved my problem by downloading and importing the Dell WinPE driver pack. Now I've just got to add the USB 3.0 drivers (I support laptops that don't have optical drives), and I'll be set.

Boot Image Drivers (More Detail)

I have a boot image with multiple drivers with the same name added (6 in total). They are different OS versions of the same Ethernet driver. I need to remove a specific one of these drivers however the 'drivers' tab of the boot image does not
provide any more detail then the 'Driver name' field.
Is there any way that I can see which is which? i do not want to remove all 6 of them and re-add the remaining 5 drivers since I do not know which 5 those are I do not know when 5 to add back.... catch 22.

I submit to you that that is completely invalid and you have drawn a false conclusion based on some other activity or coincidence. Each WinPE version corresponds to a exactly one Windows version and thus only needs and uses a single driver
for that corresponding OS. There is no way that it can or will use other drivers for other OSes for the same reason a full versions will not and does not.
Jason | http://blog.configmgrftw.com | @jasonsandys
Ok... not sure how to take that? If I deploy a 'x' Task Sequence to a Dell Latitude 6430u and PXE boot it will fail were that same task sequence has succeeds for all previous models. When I add the necessary network driver to my boot image, which
happens to have the same name as other network drivers in my boot image, the OSD succeeds for the 6430u. Based on this behavior my conclusion is that the driver is necessary for PXE/OSD to a 6430u.

Cannot Add drivers to boot image

Similar Messages

Maybe you are looking for