0xc0000135 while adding driver packages to boot image

Hi, I am currently having issues adding driver packages to the boot image.
Currently running Server 2008 R2 and have MDT 2013 installed.
Tried searching for the error but no luck. No matter if I choose the specific driver I want to add or if I just start from the beginning it just constantly fails. Does anybody have any clue as to what could be causing it to not accept either from the boot image
created from MDT Deployment Share or even using a generic boot image?

Hi,
First make sure you are using the correct version of DISM
Secondly look at this http://social.technet.microsoft.com/Forums/en-US/ff8509ec-0ddd-4ad8-9e53-ecf527a80919/dismexe-is-failing-to-add-drivers-to-a-mounted-image-file?forum=w7itproinstall

Similar Messages

  • Driver Signing for Boot Images - 2008r2 Site Server

    I was trying to update a driver in our boot image due to instability in the previous version.  This new driver officially supports Server 2012 R2 (as well as 2012, in a single driver) and is digitally signed.
    However, the certificate is not recognized by our Site Server which runs on 2008r2  (because it is a 2012 driver), and DISM.log is flagging the driver as Unsigned, and I cannot update the boot image - it fails every time.
    I'm able to work around this by injecting it myself with /forceunsigned, but it doesn't seem to be the "correct" way of handling this.  I can also do the mount and driver add on my 8.1 workstation, and not need /forceunsigned (thus proving
    it IS signed.)
    While it's flagging almost every other driver as unsigned (which is incorrect) - those other drivers aren't deemed "boot-critical", so it allows them.
    This one is a SCSI driver, hence it blocking it.
     Signature status of driver \\SCCMServer\ConfigMgrDrivers\Server 2012\SCSIAdapter\hpsa2_62.8.0.64\hpsa2.inf is: UNSIGNED - CDriverPackage::InitSignatureStatus                                                                                          
     Cannot install non-signed boot-critical drivers on amd64 images. Use /forceunsigned switch to override. \\SCCMServer\ConfigMgrDrivers\Server 2012\SCSIAdapter\hpsa2_62.8.0.64\hpsa2.inf - CDriverManager::CheckClientAddDriverScenarios(hr:0x80070032) 
    For those of us who have our site servers on 2008r2, I'd call this a bug.  Anyone else getting this?  Is my workaround the supported solution for people not running site servers on Server 2012 / 2012 R2?

    I had similar problem with one driver in the past. The way I 'fixed' my situation was that I manually injected the driver to .wim -image with DISM and then re-added the Boot Image to ConfigMgr 2012. The driver won't show up in the properties of the boot
    image but I didn't really care, because I just wanted to get this thing working.

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

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

  • 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

  • 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

  • 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)

  • Build & Capture TS (MDT) - Capture fails at PrepareOS (sysprep) with "Boot Image package not found"

    Hi all,
    I'm searching for a while on this one now... I'm unable to perform a "ZeroTouch" Build & Capture of my reference machine to get a master image, with Capture Media it seems to be working, but this is a manual step...
    While running a W7SP1 Build & Capture task sequence, the "Capture the reference machine" group fails at "PrepareOS". The step before "PrepareOS",  "Prepare ConfigMgr Client" runs without any issues.
    The only error I can find, shows up in the report "OSD - history of a TS":
    ... 0005 that is either already released or we have not connected to it.
    BootImage::ResolveImageSource( pszPackageId, sImagePackageSourcePath, sImageSourcePath), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\bootimage.cpp,732)
    TS::Boot::BootImage::StageBootImage(sPkgID), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\prepareos\prepareos.cpp,917)
    PreStageWINPE(m_bDebug), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\prepareos\prepareos.cpp,1363)
    pCmd->Sysprep(bActivate, bMsd), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\prepareos\main.cpp,270)
    De-Initialization successful
    Exiting with error code 2
    sending with winhttp failed; 80072ee2
    SendResourceRequest() failed. 80072ee2
    Download() failed. 80072ee2.
    Boot Image package not found.
    he system cannot find the file specified. (Error: 80070002; Source: Windows)
    Failed to pre-stage WINPE image, hr=0x80070002
    Unable to sysprep the machine, hr=80070002
    Sysprep'ing the machine failed, hr=80070002
    I've searched the smsts.log file hundreds of times for errors, nothing there... 
    Can anyone give me a clue or just something...? I really don't know what my next step, to make this work, could be...
    Thanks!

    The error Torsten pointed out gave me some clue... After much digging around on the web, I've stumbled upon this
    article which led me into adding the following TS-variables:
    SMSTSDownloadRetryCount: 5
    SMSTSDownloadRetryDelay: 15
    It seems to be working now on all types of hardware...
    Case closed, thank you for the assistance! 
    Let's hope this article can save someone a couple of days... :)
    Wesley

  • Error while adding Image: ORA-00001: unique constraint

    Dear all,
    I have an error while adding images to MDM I can´t explain. I want to add 7231 images. About 6983 run fine. The rest throws this error.
    Error: Service 'SRM_MDM_CATALOG', Schema 'SRMMDMCATALOG2_m000', ERROR CODE=1 ||| ORA-00001: unique constraint (SRMMDMCATALOG2_M000.IDATA_6_DATAID) violated
    Last CMD: INSERT INTO A2i_Data_6 (PermanentId, DataId, DataGroupId, Description_L3, CodeName, Name_L3) VALUES (:1, :2, :3, :4, :5, :6)
    Name=PermanentId; Type=9; Value=1641157; ArraySize=0; NullInd=0;
    Name=DataId; Type=5; Value=426458; ArraySize=0; NullInd=0;
    Name=DataGroupId; Type=4; Value=9; ArraySize=0; NullInd=0;
    Name=Description_L3; Type=2; Value=; ArraySize=0; NullInd=0;
    Name=CodeName; Type=2; Value=207603_Img8078_gif; ArraySize=0; NullInd=0;
    Name=Name_L3; Type=2; Value=207603_Img8078.gif; ArraySize=0; NullInd=0;
    Error: Service 'SRM_MDM_CATALOG', Schema 'SRMMDMCATALOG2_m000', ERROR CODE=1 ||| ORA-00001: unique constraint (SRMMDMCATALOG2_M000.IDATA_6_DATAID) violated
    Last CMD: INSERT INTO A2i_Data_6 (PermanentId, DataId, DataGroupId, Description_L3, CodeName, Name_L3) VALUES (:1, :2, :3, :4, :5, :6)
    Name=PermanentId; Type=9; Value=1641157; ArraySize=0; NullInd=0;
    Name=DataId; Type=5; Value=426458; ArraySize=0; NullInd=0;
    Name=DataGroupId; Type=4; Value=9; ArraySize=0; NullInd=0;
    Name=Description_L3; Type=2; Value=; ArraySize=0; NullInd=0;
    Name=CodeName; Type=2; Value=207603_Img8085_gif; ArraySize=0; NullInd=0;
    Name=Name_L3; Type=2; Value=207603_Img8085.gif; ArraySize=0; NullInd=0;
    I checked all data. There is no such dataset in the database. Can anybody give me a hint how to avoid this error.
    One thing I wonder: The PermanentId is allways the same but I can´t do anything here.
    BR
    Roman
    Edited by: Roman Becker on Jan 13, 2009 12:59 AM

    Hi Ritam,
    For such issues, can you please create a new thread or directly email the author rather than dragging back up a very old thread, it is unlikely that the resolution would be the same as the database/application/etc releases would most probably be very different.
    For now I will close this thread as unanswered.
    SAP SRM Moderators.

  • Where to see the boot image package path installed on my DP server

    I have distribute the boot image content to one of my DP server. Where can I see the package is installed at which location at that particular DP in SCCM 2012 console?

    Hi,
    The blog below could answer your question.
    Configuration Manager 2012: Content Monitoring and Validation
    Best Regards,
    Joyce Li
    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.

  • Boot Image - Driver Path

    I have another question on drivers and the boot image.  I changed the UNC path of a driver and updated the driver itself with the new path.  I thought all was good however that driver is in one of my boot images and now I am unable to update the
    DP with the boot image as it fail for a that driver with the old path...  I verified that the driver in the drivers list has the new path however the boot image still see the 'old' path.  this does not make since as I would assume it would just reference
    the 'driver' and thus see the new path but I guess it holds its own driver information?.. weird
    Is there anyway to see/change the path of a driver listed in the boot image?

    Hi,
    Based on my test, you could resolve this issue by delete the driver from the list and re-add it.
    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.

  • Captured & imported image, and driver package not going to DP

    I have an image I've imported and even though I've selected "Distribute Content" manually it does not go to DP.   I checked everything I could think of (making sure DP was set to service the boundary group, etc.), but it still won't go.  
    In status, it says "in process".  
    Question - do I need image/properties/package share settings "copy the content in this package to a package share on distribution points" selected to enable this image to be sent to the DP?
    Under Distribution Settings - do I need to select "Distribute the content for this package to a preferred DP..." and any recommendations on if this should be sent to Automatically, Download only changes, or Manual?
    Similarly, I also noticed my Driver Package had also not been sent to the DP, so my question applies to that as well.  After creation, do these settings need to be selected?
    Thank you
    Nathan

    Hi,
    The reason why this happens is a combination of the following two reasons:
    - You enabled for prestaged content in the distribution point.
    - Go to the properties of the image, on the "Distribution Settings" tab the radio button is set to "Manually copy this content to the distribution point".
    Enabling the prestaging option on a DP will tell the DP to not receive content automatically. It is waiting until an administrator copied *.pkgx files manually to it and registers them using extractcontent.exe. That might be useful for DPs at the end of very
    small WAN links. 
    For more infomation, please review the link below:
    Operations and Maintenance for Content Management in Configuration Manager
    http://technet.microsoft.com/en-us/library/gg712694.aspx
    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.

  • Struggling with a Dell Precision T3600, Boot Image does not see Hard drive.

    Hi
    I recently got a lab of 25 of these stations in and shortly I will be imaging them. I am using the Boot Image (x86) the ones that come with sccm 2012  and I downloaded the sccm driver cab from dell and imported the storage and raid drivers into the
    boot image, yet every time I boot winpe to try to image the machine no hard drive is found.
    I followed this thread at Dell
    http://en.community.dell.com/support-forums/disk-drives/f/3534/t/19460505.aspx
    and seeming all these drivers are in the boot image (x86)
    Intel(R) C600/X79 series chipset 6-Port SATA AHCI Controller - 1D02
    Intel(R) C600 Series Chipset SAS RAID Controller
    PERC H310 for Dell Precision
    and still now hard drive seen when I boot winpe via sccm pxe.
    Does anyone have any of these machines, or any advice for me I REALLY need to solve this, I been struggling for a day so far and getting nowhere fast.
    Thanks

    Are you using the correct driver for the version of WINPE you are using?
    3.1
    Built from Windows
    7 SP1 code base. 
    4.0
    Built from Windows
    8 code base. 
    5.0
    Built from Windows
    8.1 code base. 
    So if you had a boot image based on WINPE 4.0, you would need to use a Windows 8 driver, etc.

  • Task Sequence fails on "Apply Driver Package" when PXE-booting but not with bootable media

    I have an issue where my Task Sequence fails during 'Apply Driver Package' when PXE-booting but works ok when booting from CD or USB-stick. It fails withe error code 0x80070002 and when pressing F8 and checking the ipconfig there's a 169.254.x.x address.
    Somehow it looses it's real ip during the process.
    I'm grateful for any advice!

    Please enable verbose logging for Task sequence, then upload the smsts.log to Skydrive.
    0x80070002 error is too generic, which cannot be used to determine the cause.
    Juke Chou
    TechNet Community Support

  • OSD - Creating 1 Image with choice of Software & Driver Packages

    I am kindda new to SCCM 2012. I was wondering if it is possible to have like 1 Windows 8.1 Image and when it is being deployed we get a prompt for choice of Driver and Application Packages. The reason is that we have different kind of laptops and different
    requirements for software. It would be good to have a prompt where you can choose which Driver Package to deploy based on the hardware and choice of software package that depends of the user's department.

    Retrograde_PAK, a good majority of our software deployments occur based on our computer naming convention so having a decent naming convention would
    be very helpful. I also create collections for all(most) of my software packages and am able to pull device records into their deployment collections based on membership queries again typically I leverage our naming convention but you could use any number
    of things... AD location... Installed OS... basically anything that sccm has stored in its db for those records. then those collection are populated automatically based on those queries and the package is installed.

Maybe you are looking for