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

Similar Messages

  • PXE not working - getting no boot file recived (done lots but still not working) boot image issue I think

    Hello
    Thank you for you time and help
    I am trying to set up a test OSD deployment on a virtual system. I have followed my book and it looks like its been set up correctly. I read lots of posts in this forum and others and I am still having issues. 
    The Issue
    When booting a client system getting "PXE-E53 - No boot filename received"
    That I have done
    1. Made sure that both my X64 and X86 Boot files have been distributed with "Deploy this boot image to from PXE-enabled DP" on both of them (looked under content statues on my DP and both are at 100)
    2.Removed my DP and WSDS role and restarted and reinstalled
    3. Created a new Boot image using a windows 2012 R2 DVD and used this in my task sequence, I removed both  of the boot images  (this got a bit further but I got an error telling me that It needs both X64 and X86). SO I readded them to my DP from
    the boot folder of my  E:\Program Files\Microsoft Configuration Manager\OSD\boot folder)
    Here is my SMSPXE file
    Client is set to use HTTPS when available. The current state is 224. SMSPXE 19/04/2015 16:15:43 6616 (0x19D8)
    Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
     SMSPXE 19/04/2015 16:15:43 6616 (0x19D8)
    PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 19/04/2015 16:15:43 6616 (0x19D8)
    PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 19/04/2015 16:15:43 6616 (0x19D8)
    Adding TRD00015.3 SMSPXE 19/04/2015 16:15:43 6616 (0x19D8)
    Adding TRD00016.2 SMSPXE 19/04/2015 16:15:47 6616 (0x19D8)
    Found new image TRD00015 SMSPXE 19/04/2015 16:15:52 6616 (0x19D8)
    Loaded C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll SMSPXE 19/04/2015 16:15:52 6616 (0x19D8)
    Opening image file E:\RemoteInstall\SMSImages\TRD00015\boot.TRD00015.wim SMSPXE 19/04/2015 16:15:52 6616 (0x19D8)
    Found Image file: E:\RemoteInstall\SMSImages\TRD00015\boot.TRD00015.wim
     PackageID: TRD00015
     ProductName: Microsoft® Windows® Operating System
     Architecture: 9
     Description: Microsoft Windows PE (x64)
     Version: 
     Creator:
     SystemDir: WINDOWS
     SMSPXE 19/04/2015 16:15:52 6616 (0x19D8)
    Closing image file E:\RemoteInstall\SMSImages\TRD00015\boot.TRD00015.wim SMSPXE 19/04/2015 16:15:52 6616 (0x19D8)
    Found new image TRD00016 SMSPXE 19/04/2015 16:15:52 6616 (0x19D8)
    Loaded C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll SMSPXE 19/04/2015 16:15:52 6616 (0x19D8)
    ================= PXE Provider loaded. ===================== SMSPXE 19/04/2015 16:17:54 4496 (0x1190)
    Machine is running Windows Longhorn. (NTVersion=0X603, ServicePack=0) SMSPXE 19/04/2015 16:17:54 4496 (0x1190)
    Cannot read the registry value of MACIgnoreListFile (00000000) SMSPXE 19/04/2015 16:17:54 4496 (0x1190)
    MAC Ignore List Filename in registry is empty SMSPXE 19/04/2015 16:17:54 4496 (0x1190)
    Begin validation of Certificate [Thumbprint C4D34F3B6322A19274BBC9EF1F9D71ECC8B9EC71] issued to 'c8b0427c-2014-419b-b251-ef0a6fbd96a0' SMSPXE 19/04/2015 16:17:54 4496 (0x1190)
    Completed validation of Certificate [Thumbprint C4D34F3B6322A19274BBC9EF1F9D71ECC8B9EC71] issued to 'c8b0427c-2014-419b-b251-ef0a6fbd96a0' SMSPXE 19/04/2015 16:17:54 4496 (0x1190)
    Initializing PXEPerfObject. SMSPXE 19/04/2015 16:17:54 4496 (0x1190)

    I agree with Narcoticoo, most of the time this comes down to either firewall, IPhelper, or DHCP options getting in the way.
    MS best practice is to use _no_ DHCP options at all unless the DP/PXE is also a DHCP server.  So remove any OPtion 67,68 from DHCP. 
    Then check the pxe.log on your DP.  You should see the MAC address broadcast then the PXE/DP take action (or ignore it if things arn't correct).
    1.  If you don't see the appropriate MAC address broadcast, check IPHelper/firewall
    2.  If you see the MAC address broadcast but the DP ignores it, check your collections/deployments
    3.  If you see the PD respond in the pxe.log ... but the client does nothing, time to look at DHCP and make sure those silly options are cleared.

  • Illustrator CC October Update - Moving Images Issue

    Just updated my CC to Oct 14 version and now when I open any file with a linked image and try to move that image, I just get a spinning wheel…
    I can remove these links from my layers palette but the same thing happens when I place a new image.
    The only way out is to force quit. Never had this problem before and if I open any of these files up in CC 17.1.0 it works perfectly.
    My work colleague sat next to me has exactly the same problem.
    Both of us work on a mac OSX 10.9.5.
    Any one else with the same issue?
    Thanks

    Hi Ana,
    Kindly try the below mentioned link.
    Installation failed. Error U44M1P7 | Updates
    Thanks
    Atul Saini

  • Slow boot image

    hello all
    we have new HP 800G1 hardware and now the boot image is very very slow 10Mb/sec?
    I have add all driver to out-of-box and create a new boot image. same problem 10mb
    After GUI and Tasksequence Deploy Question, it work's fine with 1Gb.
    Chris

    Hi Steph,
    Have you installed this patch on your site server ?
    http://support.microsoft.com/kb/2905002/en-us
    Issue 2
    When you download operating system image files to Configuration Manager 2012 R2 clients, the process takes longer than it did
    in previous versions of Configuration Manager 2012 clients. You may see this behavior if the target client is running Windows PE or a full Windows operating system.
    It has been superseded by KB2910552 meaning that the Issue described will still be fixed.
    Even if your server are DP, the patch is applicable at your primary site and will be applied to you boot image when you'll distribute your content.
    fter the update is installed on site servers, any operating system boot images should be updated. To update boot images after the hotfix
    is applied, follow these steps:
    In the Configuration Manager console, click Software Library.
    In the Software Library workspace, expand Operating Systems, and then click Boot Images.
    Select the boot image that you want to update.
    Right-click and then select the Update Distribution Points action.
    Note This action updates all distribution points and may have an adverse effect on an environment that contains many distribution points.
    Repeat steps 3 and 4 for all boot images that were previously distributed.

  • Boot Image French

    Hi
    I need to boot image in "French".
    I view this:
    http://www.petervanderwoude.nl/post/how-to-change-the-language-in-windows-pe-via-configmgr-2012/
    I change 1031 for 1036, i check in <ConfigMgrInstallFolder>\OSD\bin\x64\0000040c\tsres.dll is present (OK).
    I go to "Boot Images (x64), "properties", "Customization" tab.
    Check "Enable prestart command", in comand line "cscript.exe SetSMSTSLanguageFolder.vbs /LocaleID:1036" and check "Includes files for the prestart command", Source Directory
    \\ServerName\share (Full control, Everyone)
    Update Distribution Point
    But when i start deployment all in Eglish
    Thanks

    It's really nothing more than the steps outlined in that specific post. The only thing I can say is to double check everything. Make sure to save the script and test it and make sure to use the folder in which you saved the script is used with the
    Includes files for the prestart command. After applying those changes simply update the distribution point(s) and it should create the updated boot image.
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • Issues with Boot Images & PXE Booting Since SP1 Install

    Good Afternoon All - 
    I recently updated to SP1, had some issues, but they got resolved.  Now, though, I'm having an issue booting to PXE as well as updating any boot images created
    before SP1 was installed.  Booting to USB Bootable media using a newly created boot image seems to work fine. 
    Boot Images
    When I update my DPs for any of my boot images in SCCM, they fail and i get the below error:
      Error: The wizard detected the following problems when updating the boot image.
    • Failed to install required components into 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:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
    • Line = 4566;
    • ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
    • Operation = "ExecMethod";
    • ParameterInfo = "SMS_BootImagePackage.PackageID=\"BBS0012F\"";
    • ProviderName = "WinMgmt";
    • StatusCode = 2147749889;
    I've even gone as far as removing all drivers from the boot image, but still get the same message.  I was able to create a couple of
    new MDT boot images which seem to work fine, though.  I am not sure which log file is for boot images, but nothing appeared in distmgr.log.
    PXE Booting Issue
    After trying many things, I removed PXE config from my site and uninstalled WDS then started all over again.  Here's what I did and my results.  Please tell me what I'm missing...
    After uninstall & server reboot, I enabled PXE + every option in DP tab in SCCM
    It automatically installed WDS (same server) and added the two boot images I had checked for PXE use.  one x64 and one x86.
    I checked my DHCP Scope whose values hadn't changed sine it worked (that I know of).  They are:
    Option #66: 192.168.20.37 (SCCM Server/DP/PXE) 
    Option #67 \boot\x86\wdsnbp.com.  I've tried \boot\x86\pxeboot.com as well as each of these with x64.
    When I PXE boot from a workstation, I receive an IP, a bit of info, then it goes to Contacting Server....  When trying one of the boot files above, I was prompted for F12, but receved a blue screen with error.  When trying all other boot files,
    they just hang at Contacting Server until they timeout.
    I looked at SMSPXE.log and found something interesting...
    The IDs for the two boot images I have assigned to PXE are ABC003B3 & ABC00B36.  In the smspxe.log, though, it keeps repeating "could not find boot image ABC0012F!  12F does exist and is a boot image,
    but not the one I want to use by any means and does not have PXE checked.
    I went ahead and checked 12F, updated DPs (which failed - see above); unchecked it; then updated the DPs again.  PXEBoot.log showed that it was trying to remove the 12F files from RemoteInstall which was a good sign.  I then restarted the WDS service
    and tried PXE booting again.  Yet again, it failed and was still looking for 12F.
    Any suggestions / Ideas???  Thanks!
    UPDATE 1
    I just changed option #67 to \smsboot\x86\pxeboot.com then restarted the WDS service.  I booted to PXE and this time was asked to hit F12.  I did so and it looked as if it would work.
    Instead, I got a blue screen with the following error:
    Recovery
    Your PC needs to be repaired
    The boot configuration disk contains errors or is missing 
    file: boot\BCD
    Error Code: 0x000000f
    I think that it's the same error as before, but is blue instead of black due to new Win8ADK perhaps.  Thanks
    Ben K.

    Update 4
    Sorry to make this the longest post ever :)
    I just read that others with this error checked DISM.log.  I did so when running a DP update for the boot image and got the below errors:
    2013-01-11 16:27:04, Info                  DISM   DISM Provider Store: PID=1636 TID=5104 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
    2013-01-11 16:27:07, Info                  CBS    Failed to find a matching version for servicing stack: C:\Windows\TEMP\BootImages\{DADCFE01-3557-4058-99CC-2A15EDF905AF}\mount\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_655452efe0fb810b\
    [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
    2013-01-11 16:27:07, Info                  CBS    Failed to find servicing stack directory in online store. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
    2013-01-11 16:27:07, Warning               DISM   DISM Provider Store: PID=4104 Failed to Load the provider: C:\Windows\TEMP\0555ABC5-006D-4C3F-B79F-EA0E723FA971\MsiProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2013-01-11 16:27:07, Warning               DISM   DISM Provider Store: PID=4104 Failed to Load the provider: C:\Windows\TEMP\0555ABC5-006D-4C3F-B79F-EA0E723FA971\TransmogProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2013-01-11 16:27:07, Error                 DISM   DISM Package Manager: PID=4104 The package WinPE-Scripting-Package is not applicable to the image. - CPackageManagerCLIHandler::Private_ProcessPackageChange
    2013-01-11 16:27:08, Info                  DISM   DISM Package Manager: PID=4104  Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error
    2013-01-11 16:27:08, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/TEMP/BootImages/{DADCFE01-3557-4058-99CC-2A15EDF905AF}/mount/Windows/System32/config/SOFTWARE,
    the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
    (The above one appears 8 times - almost in a row)
    2013-01-11 16:27:08, Error                 DISM   DISM Package Manager: PID=4104 Failed while processing command add-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081e)
    Help!  Thanks :)
    Ben K.

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

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

  • 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 distribution point errors updating the boot image....SCCM 2012 r2

    Fairly new to SCCM (started on it about a month and a half ago and only been troubleshooting different things).  As of this moment I'm attempting to get imaging back up, which it looks as if the drivers did not get injected into the boot image properly
    before.  This seems to be resolved but when I attempt to update the distro point i end up with this error below.  Any help is appreciated.
    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:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
    • Line = 4716;
    • ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
    • Operation = "ExecMethod";
    • ParameterInfo = "SMS_BootImagePackage.PackageID=\"SMS00005\"";
    • ProviderName = "WinMgmt";
    • StatusCode = 2147749889;

    What version of Configuration Manager are you running, and are you using MDT?
    Blog: www.danielclasson.com/blog |
    LinkedIn:
    Daniel Classon | Twitter: @danielclasson

  • Boot Image Update Logs

    Where are the logs for when I am updating the distribution point for a boot image?
    I added some drivers to a boot image on SCCM 2012 and then I performed an "update distribution sites" and it took several hours.
    I would like to review the logs to see if there is any reason it is taking so long.
    To clear up any confusion here is what I am doing:
    Open SCCM 2012
    Go to Software Library -> Operating Systems -> Boot Images
    Right click any Boot Image and select "Update Distrobution Points"
    J Gruber

    Distmgr, pkgxfermgr (if DP is remote) and smspxe.log
    Torsten Meringer | http://www.mssccmfaq.de

  • Can´t update SRW2024 to firmware 1.2.2, without boot image "runtop_boot-101.rfb"

    Hello
    I need a bit help upgrading a SRW2024 to latest firmware.
    I started by upgrading to v.1.2.2, but the switch just started rebooting all the time, I flashed back to 1.0.0.86 via console xmodem.
    On Cisco FAQ theres a guide how to upgrade the SRW2024. The guide says I have to update the boot image before the flash image, but the boot image is not available on cisco´s download section anymore.
    Can you please help me with the boot image. (runtop_boot-101.rfb)
    Thanks.

    Hi
    I hope you have called the SBSC, since they haven't as yet responded to this request.
    http://www.cisco.com/en/US/support/tsd_cisco_small_business_support_center_contacts.html
    regards Dave

  • How to update WinPE Boot image

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

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

  • Hi,  Had boot issue and got the following from DU repair function on Macintosh hd: updating boot support.....Error: Disk utility can't repair this disk.....reformat and restore backed up files. How is that done or do I go to Genius?

    In reference to question the computer gave no warning but lost internet connectivity.  I shut down for a while and when returned it would only boot to gray logo screen with spinning gear.  Ran disk utility and on Mac HD drive it stopped after "Updating boot support partitions as required". Then in red: Error: Disk utility can' repair this disk ....disk, and restore backed up files.   I'm running OS X 10.8 and had just updated the iOS about three days ago.  Not familiar with reformat process on MacBook Pro and would like some ideas whether I should go to the Genius Bar here in Sydney or try it on my own.   I have been using time machine to back up to a 1TB La Cie drive right up to the crash.   Thanks for any advice.

    Well it turned out the drive was shot.  Took it to the genius bar yesterday and they ran a test on the drive before trying the restore routine again.  Drive failed. 
    Replaced the drive and got the MBP back today.  Pretty quick and decent service once you get an appointment. 
    Now having trouble figuring how to do the Time Machine  saved files.  Have several applications which I'd like to keep but not sure how to trans the apps from my backup to the new.  Hunting for answers on that on the web.
    Thanks for you help, Eustace.

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

Maybe you are looking for