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.

Similar Messages

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.

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)

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

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.

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

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

Having issues with Surface Pro 3 downloading boot image over PXE

Hi,
We've recently started to buy the new Surface Pro 3 with the new USB 3.0 Gigabit Ethernet adapter and we have some issues deploying them through SCCM. Basically, with the Pro 2 and Fast Ethernet adapter we have no issue at all, of course the deployment is
a bit longer than on any other computer, but it is still quite faster than the latest Surface.
We have the new 8.13.414.2014 driver injected in the Win 8.1 boot image for the USB 3.0 Gigabit adapter and all the drivers assigned to the new Surface in SCCM.
The problem occurs when we try to load the boot image after choosing PXE, it takes more than an hour to load it when it shouldn't take more than 5 minutes.
I tried rolling back to the old driver (8.6.128.2013) and use the Fast Ethernet adapter, use the Fast Ethernet adapter with the new driver and use the new adapter with the old driver, but it's still slow in any case, so
I'm pretty sure it has something to do with the new Surface and not the Ethernet adapter.
Anyone have an idea what could be the problem here? Anyone having issues with Surface Pro 3 and SCCM 2012?

I would imagine you have upgraded to R2, have you also applied KB2905002.
This hasn't got anything to do with the TFTP loading phase of the boot image.
Similar thread to this can be found here:
http://social.technet.microsoft.com/Forums/en-US/a6d80714-dc26-43db-a071-93eaee267122/surface-pro-2-surface-ethernet-adapter-super-slow-pxe?forum=configmanagergeneral
I already asked in that thread the same question, but how about normal PCs that are connected to the same network segment as the Surface devices, do they boot slow also?

Cannot backup Windows 7 (dual-boot) image to external HD (formated as Mac OS Extended)

I cannot backup my Windows 7 (dual-boot) image to my external HD (formated as Mac OS Extended). I installed MacDrive 8.0 hoping to solve the problem but Windows 7 gives me an error when I try to create a backup: "...drive is not formatted as NTFS, cannot use as backup...".
I also tried making an Image of the Windows 7 partition through Disk Utility but was not allowed to do so.
I am not sure where else to go from here. I need to keep my external hard drive formatted as Mac OS Extended but I also need to backup my Windows 7 partition. I only have the single external at the moment. Is there a way to backup my Windows 7 partition?
Thanks

Winclone will backup your Windows partition to a Mac formatted drive.
Just search for Winclone on this forum and on Goggle.

Unable to import Windows 7 boot images

When we installed our SCCM 2012 server, no boot images appear to have been created. I have since upgraded to R2, and added CU3, and there are still no boot images available. I would like to add boot images for Windows 7 x64 but so far have been
completely unsuccessful. I have tried creating images with MDT on the server, and they will not import. I have also created them with WAIK 3.0 with the WAIK 3.1 Supplement from a Windows 7 machine, and those will also not import. In every situation I
receive the following error: The specified UNS path does not contain a valid WIM file or you do not have permission to access it. Specify a valid path. This occurs if I try to import from a share on the sccm server, or from a share on
another computer. The permissions on the share are set at Everyone--full control share permission, and NTFS permissions are set to give the system account, the computer account and domain admins full control. The SMSProv.log file shows the
following error on each failed attempt: Failed to get the image property from the source WIM file due to error 80070002. I have read everything I can find and tried everything that people are mentioning that has fixed the problem for them, and so far
no success. I feel like I must be missing something, but I'm not sure where else to look. Any suggestions will be most appreciated!

Uninstalled and reinstalled ADK--no improvement.
Every time I try to import a boot image, the SMSProv log shows this:
~ $$<SMS Provider><01-21-2015 15:30:43.623+300><thread=7084 (0x1BAC)>
CExtUserContext::EnterThread : User=COP\reistg Sid=0x01050000000000051500000010DFF9978E4D14F2AFDA7FC15A0C0000 Caching IWbemContextPtr=000000385D804E50 in Process 0xd80 (3456)~ $$<SMS Provider><01-21-2015 15:30:43.623+300><thread=7084
(0x1BAC)>
Context: SMSAppName=Configuration Manager Administrator console~ $$<SMS Provider><01-21-2015 15:30:43.623+300><thread=7084 (0x1BAC)>
Context: MachineName=xxx.xxxx.xxx~ $$<SMS Provider><01-21-2015 15:30:43.624+300><thread=7084 (0x1BAC)>
Context: UserName=COP\reistg~ $$<SMS Provider><01-21-2015 15:30:43.624+300><thread=7084 (0x1BAC)>
Context: ObjectLockContext=1316ccc7-f4be-40c3-9b9e-c34dd1028080~ $$<SMS Provider><01-21-2015 15:30:43.624+300><thread=7084 (0x1BAC)>
Context: ApplicationName=Microsoft.ConfigurationManagement.exe~ $$<SMS Provider><01-21-2015 15:30:43.624+300><thread=7084 (0x1BAC)>
Context: ApplicationVersion=5.0.7804.1400~ $$<SMS Provider><01-21-2015 15:30:43.625+300><thread=7084 (0x1BAC)>
Context: LocaleID=MS\0x409~ $$<SMS Provider><01-21-2015 15:30:43.625+300><thread=7084 (0x1BAC)>
Context: __ProviderArchitecture=32 ~ $$<SMS Provider><01-21-2015 15:30:43.625+300><thread=7084 (0x1BAC)>
Context: __RequiredArchitecture=0 (Bool)~ $$<SMS Provider><01-21-2015 15:30:43.625+300><thread=7084 (0x1BAC)>
Context: __ClientPreferredLanguages=en-US,en~ $$<SMS Provider><01-21-2015 15:30:43.626+300><thread=7084 (0x1BAC)>
Context: __CorrelationId={2F91BBB1-35A9-0008-97BC-912FA935D001}~ $$<SMS Provider><01-21-2015 15:30:43.626+300><thread=7084 (0x1BAC)>
Context: __GroupOperationId=13101 ~ $$<SMS Provider><01-21-2015 15:30:43.626+300><thread=7084 (0x1BAC)>
CExtUserContext : Set ThreadLocaleID OK to: 1033~ $$<SMS Provider><01-21-2015 15:30:43.626+300><thread=7084 (0x1BAC)>
CSspClassManager::PreCallAction, dbname=CM_COP~ $$<SMS Provider><01-21-2015 15:30:43.626+300><thread=7084 (0x1BAC)>
PutInstanceAsync SMS_BootImagePackage~ $$<SMS Provider><01-21-2015 15:30:43.627+300><thread=7084 (0x1BAC)>
CExtProviderClassObject::DoPutInstanceInstance~ $$<SMS Provider><01-21-2015 15:30:43.627+300><thread=7084 (0x1BAC)>
GetStorage : doing Loggin due to aged out context~ $$<SMS Provider><01-21-2015 15:30:43.627+300><thread=7084 (0x1BAC)>
************ WBEM Missing property TransformAnalysisDate~ $$<SMS Provider><01-21-2015 15:30:43.645+300><thread=7084 (0x1BAC)>
************ WBEM Missing property TransformReadiness~ $$<SMS Provider><01-21-2015 15:30:43.645+300><thread=7084 (0x1BAC)>
~*~*~e:\qfe\nts\sms\siteserver\sdk_provider\smsprov\sspbootimagepackage.cpp(3634) : Failed to read image property from the source WIM file due to error 80070002~*~*~ $$<SMS Provider><01-21-2015 15:30:43.669+300><thread=7084 (0x1BAC)>
~*~*~Failed to read image property from the source WIM file due to error 80070002 ~*~*~ $$<SMS Provider><01-21-2015 15:30:43.669+300><thread=7084 (0x1BAC)>
Auditing: User COP\reistg called an audited method of an instance of class SMS_BootImagePackage.~ $$<SMS Provider><01-21-2015 15:30:43.669+300><thread=7084 (0x1BAC)>
CExtUserContext::LeaveThread : Releasing IWbemContextPtr=1568689744~ $$<SMS Provider><01-21-2015 15:30:43.678+300><thread=7084 (0x1BAC)>

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.

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.

MDT 2012 Update 1 Boot Image Creation Fails in SP1

I have my site server (SCCM 2012 SP1) installed on Server 2012 with the Windows 8 ADK installed (I've also tried installing the Win7 WAIK with no change to the below problem). It is hosting the site server, FSP, AIS, and Endpoint protection roles. I
installed MDT 2012 Update 1 (build 6.1.2373.0) and installed ConfigMgr integration. I have a share
\\siteserver\bootimages that I'm creating the boot image to and the system account has full control on both the NTFS and Share permissions. When I create the boot image I get an error almost immediately and
a popup that the Microsoft.BDD.ElevatedProxy has stopped working. Details from the pop-up:
Description:
Stopped working
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: microsoft.bdd.elevatedproxy.exe
Problem Signature 02: 3.0.0.0
Problem Signature 03: 50400c36
Problem Signature 04: System.ServiceModel
Problem Signature 05: 3.0.0.0
Problem Signature 06: 4fee6b19
Problem Signature 07: fb9
Problem Signature 08: a7
Problem Signature 09: G3DT0URDW53KGT4VJDEEQCRAUIFCNTLL
OS Version: 6.2.9200.2.0.0.272.7
Locale ID: 1033
The error in the boot image creation wizard is:
Started processing.
Creating boot image.
Error while importing Microsoft Deployment Toolkit Task Sequence.
System.ServiceModel.FaultException: The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug>
configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.
Server stack trace:
   at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)
   at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at INewBootImage.Create(String platform, String scratchSpace, String[] components, String[] extraContent, String wimFile)
   at NewBootImageClient.Create(String platform, String scratchSpace, String[] components, String[] extraContent, String wimFile)
   at Microsoft.BDD.Wizards.SCCM_ImportTaskSequenceTask.DoWork(SmsPageData smspageData, Dictionary`2 data)
I haven't found anything online on this particular error, I've seen all the ones about MDT 2012 and ConfigMgr 2012 CU 1. Any ideas? Any logs that may be revealing to the cause of this error? I've tried removing integration components, uninstalling MDT, reboot,
re-installing, etc, but same problem occurs each time.

I just tried to create a new boot image again, the DISM.log file does not show any evidence of the attempt to create the boot wim, in fact nothing since 0800 this morning. The most recent logs are as follows:
2013-03-03 20:22:59, Info                  DISM   PID=2252 TID=4312 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
2013-03-03 20:22:59, Info                  DISM   PID=2252 TID=4312 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=4312 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 Deleted g_internalDismSession - DismShutdownInternal
2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 Shutdown SessionTable - DismShutdownInternal
2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 Leave DismShutdownInternal - DismShutdownInternal
2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 DismApi.dll:
- DismShutdownInternal
2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 DismApi.dll:
- DismShutdownInternal
2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll:
- DismInitializeInternal
2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll:
- DismInitializeInternal
2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll: Version 6.2.9200.16384 - DismInitializeInternal
2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll: Parent process command line: C:\Windows\system32\wbem\wmiprvse.exe - DismInitializeInternal
2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Enter DismInitializeInternal - DismInitializeInternal
2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Initialized GlobalConfig - DismInitializeInternal
2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Initialized SessionTable - DismInitializeInternal
2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
2013-03-03 22:02:51, Info                  DISM   API: PID=3544 TID=3672 Waiting for m_pInternalThread to start - CCommandThread::Start
2013-03-03 22:02:51, Info                  DISM   API: PID=3544 TID=4172 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=4172 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=3672 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=3672 m_pInternalThread started - CCommandThread::Start
2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=3672 Created g_internalDismSession - DismInitializeInternal
2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=3672 Leave DismInitializeInternal - DismInitializeInternal
2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=3672 Enter DismShutdownInternal - DismShutdownInternal
2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=3672 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=3672 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=3672 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=4172 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=4172 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2013-03-03 22:03:59, Info                  DISM   API: PID=3544 TID=4172 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
2013-03-03 22:03:59, Info                  DISM   API: PID=3544 TID=4172 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2013-03-03 22:04:39, Info                  DISM   PID=3544 TID=4172 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
2013-03-03 22:04:39, Info                  DISM   PID=3544 TID=4172 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
2013-03-03 22:04:39, Info                  DISM   PID=3544 TID=4172 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=4172 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 Deleted g_internalDismSession - DismShutdownInternal
2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 Shutdown SessionTable - DismShutdownInternal
2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 Leave DismShutdownInternal - DismShutdownInternal
2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll:
- DismShutdownInternal
2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll:
- DismShutdownInternal
2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll:
- DismInitializeInternal
2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll:
- DismInitializeInternal
2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll: Version 6.2.9200.16384 - DismInitializeInternal
2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll: Parent process command line: C:\Windows\system32\wbem\wmiprvse.exe - DismInitializeInternal
2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Enter DismInitializeInternal - DismInitializeInternal
2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Initialized GlobalConfig - DismInitializeInternal
2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Initialized SessionTable - DismInitializeInternal
2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
2013-03-04 08:41:08, Info                  DISM   API: PID=1016 TID=1620 Waiting for m_pInternalThread to start - CCommandThread::Start
2013-03-04 08:41:08, Info                  DISM   API: PID=1016 TID=4176 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=4176 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=1620 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=1620 m_pInternalThread started - CCommandThread::Start
2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=1620 Created g_internalDismSession - DismInitializeInternal
2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=1620 Leave DismInitializeInternal - DismInitializeInternal
2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=1620 Enter DismShutdownInternal - DismShutdownInternal
2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=1620 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=1620 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=1620 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=4176 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=4176 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=4176 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=4176 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2013-03-04 08:42:44, Info                  DISM   PID=1016 TID=4176 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
2013-03-04 08:42:44, Info                  DISM   PID=1016 TID=4176 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
2013-03-04 08:42:44, Info                  DISM   PID=1016 TID=4176 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=4176 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 Deleted g_internalDismSession - DismShutdownInternal
2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 Shutdown SessionTable - DismShutdownInternal
2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 Leave DismShutdownInternal - DismShutdownInternal
2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll:
- DismShutdownInternal
2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll:
- DismShutdownInternal
2013-03-05 08:44:10, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll:
- DismInitializeInternal
2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll:
- DismInitializeInternal
2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll: Version 6.2.9200.16384 - DismInitializeInternal
2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll: Parent process command line: C:\Windows\system32\wbem\wmiprvse.exe - DismInitializeInternal
2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 Enter DismInitializeInternal - DismInitializeInternal
2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 Initialized GlobalConfig - DismInitializeInternal
2013-03-05 08:44:13, Info                  DISM   API: PID=4140 TID=3140 Initialized SessionTable - DismInitializeInternal
2013-03-05 08:44:13, Info                  DISM   API: PID=4140 TID=3140 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
2013-03-05 08:44:14, Info                  DISM   API: PID=4140 TID=3140 Waiting for m_pInternalThread to start - CCommandThread::Start
2013-03-05 08:44:14, Info                  DISM   API: PID=4140 TID=640 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=3140 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=3140 m_pInternalThread started - CCommandThread::Start
2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=3140 Created g_internalDismSession - DismInitializeInternal
2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=3140 Leave DismInitializeInternal - DismInitializeInternal
2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=640 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=1320 Enter DismShutdownInternal - DismShutdownInternal
2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=1320 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=1320 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=1320 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=640 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=640 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=640 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=640 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2013-03-05 08:46:18, Info                  DISM   PID=4140 TID=640 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
2013-03-05 08:46:18, Info                  DISM   PID=4140 TID=640 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
2013-03-05 08:46:18, Info                  DISM   PID=4140 TID=640 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=640 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 Deleted g_internalDismSession - DismShutdownInternal
2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 Shutdown SessionTable - DismShutdownInternal
2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 Leave DismShutdownInternal - DismShutdownInternal
2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 DismApi.dll:
- DismShutdownInternal
2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 DismApi.dll:

Referenced library on internal SSD boot/applications drive?

I have a referenced library, the masters are on an external drive; right now the library is on another external drive (mini, so most everything is on external drives via firewire 800). I'm swapping in an OCZ SSD to use for my boot/applications drive, together with a few GB's of documents that I frequently use. Taking advantage of the weekend to set up a drive to clone on to the SSD after I install it.
Any advantage to moving my library over to the internal SSD?
As a side question - my library has expanded to about 3 G Bytes. Is there a procedure to "compact" the library, maybe it has accumulated useless data between importing, deleting, making changes and then discarding versions.
Thanks very much.

I have moved my entire homefolder (incl. the Aperture library) to the SSD bootdrive in a raid0 setup. While the overall experience is definitely a lot snappier, I didn't find my workflow much faster than it was before with respect to Aperture. I guess most of the time I'm fiddling around with image-edits that hardly involves HD access.

Boot Image - Driver Path

Similar Messages

Maybe you are looking for