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

Similar Messages

  • 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

  • SCCM 2012 SP1 Boot Image

    Hi Guys,
    We upgraded to SCCM 2012 SP1 from the RTM yesterday and now our OS Deployment has stopped working. I have tried to update the DP's with the boot images and it keep failing to add drivers. I have also tried to add a Boot Image but this failing.
    Any suggestion on what might be going wrong? Our upgrade processed completed successfully.
    Kind Regards
    TPark IT Technician

    Hi,
    I have removed all the drivers and I am now getting the following error.
    Error: Boot image to update:
    Microsoft Windows PE (x86)
    　Error: Actions to perform:
    Add ConfigMgr binaries
    Add custom background
    Enable Windows PE command line support
    Optional components:
    Scripting (WinPE-Scripting)
    Startup (WinPE-SecureStartup)
    Network (WinPE-WDS-Tools)
    Scripting (WinPE-WMI)
    　Error: The wizard detected the following problems when updating the boot image.
    The SMS Provider reported an error.: ConfigMgr Error Object:
    instance of SMS_ExtendedStatus
    Description = "Failed to insert OSD binaries into the WIM file";
    ErrorCode = 2152205056;
    File = "e:\\qfe\\nts\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
    Line = 4630;
    ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
    Operation = "ExecMethod";
    ParameterInfo = "SMS_BootImagePackage.PackageID=\"ASH00001\"";
    ProviderName = "WinMgmt";
    StatusCode = 2147749889;
    I am only trying to Deploy Windows 7 images currently but we are looking to upgrade to Windows 8 at Christmas. Can I import a boot image from a Windows 7 or Windows 8 cd?

  • 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

  • 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 when I try to import a boot image

    Hi guys,
    I have SCCM 2012 SP 1 updated.
    I delete all boot image from library and I try to import anther boot.wim from original dvd.
    Error: Data Source Information
    • Source location: \\xxx\sccm image\X17-24269\sources\boot.wim
    • Boot Image: 1 - Microsoft Windows PE (x64)
    Error: Package Information
    • Name: boot
    Error: Errors
    • You can not import this boot image. Only finalized boot images are supported. For more information press F1.
    Any idea's ?
    Thanks.

    Long thread here. It might help you.
    http://social.technet.microsoft.com/Forums/en-US/064981ba-47ea-4b05-9986-9ed0ccd06853/sccm-2012-sp1-cant-add-boot-image-only-finalized-boot-images-are-supported?forum=configmanagerosd
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson

  • Boot image does not exist and cannot read disk label errors.

    Hi - I'm having a problem with installing Solaris 9 4/04 on a Netra T1. The Netra already has Solaris 7. I need to get this set up as a jumpstart server but it can't find the boot image. I'm using a brand new bonafide installation disk - not a copy. The system won't let me install/upgrade to Solaris 9 either. I get an error stating that disk label can't be read. I've tried swapping out the CDROM but I still get the same errors. Does anyone know what or why this may be happening? (Oh - and another strange thing - like I said the CDs are the original but there doesn't appear to be a cdrom/cdrom0/s0 directory. The directory I see is cdrom/cdrom0/sol_9_404_sparc/Solaris_9/Tools)
    ERROR: Install boot image /cdrom/sol_9_404_sparc/Solaris_9/Tools/Boot does not exist
    Check that boot image exists, or use [-t] to
    specify a valid boot image elsewhere.
    and
    Excuting last command: boot cdrom [- nowin]
    Boot device: /pci@1f,0/pc1@1/ide/cdrom@2:f file and args: [- nowin]
    Can't read disk label.
    Can't open disk label package
    Evaulating: boot cdrom [- nowin]@1/ide@e/cdrom@2:f File and args: [- nowin]
    Can't open boot device
    I appreciate any help at all - is there anyone out there who can tell me what I may be doing wrong?
    Thanks

    Hi check that you are booting of the right cd. Make sure it is soalris 9 software 1/2 if that fails then it may well be that your cd is buggered. most likely it is buggered it it cant find the boot image.

  • HT1899 Is Boot Camp Assistant supported in Mac OS X 10.8.1? I am getting an error "Boot Camp Assistant cannot be used. You must update your computer's Boot ROM firmware before using this setup assistant."

    Please advice I am getting an error "Boot Camp Assistant cannot be used. You must update your computer's Boot ROM firmware before using this setup assistant."

    No I have only one physical HDD. Here is a diskutil list result
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *500.3 GB   disk0
       1:                        EFI                         209.7 MB   disk0s1
       2:                  Apple_HFS Macintosh HD            499.4 GB   disk0s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
    Also here is a system info
    Hardware Overview:
      Model Name:          MacBook Pro
      Model Identifier:          MacBookPro8,2
      Processor Name:          Intel Core i7
      Processor Speed:          2.5 GHz
      Number of Processors:          1
      Total Number of Cores:          4
      L2 Cache (per Core):          256 KB
      L3 Cache:          8 MB
      Memory:          8 GB
      Boot ROM Version:          MBP81.0047.B27
      SMC Version (system):          1.69f3
    15-inch, Late 2011
    current situation
    - I've recovered from external drive (mountain lion 10.8.1 ) which i prepared by Lion Diskmaker before.
    Current issues:
    1) I have Recovery HD but when I boot from it - Reinstall Mac OS X option is not working
    2) I have EFI password and won't be able to clear it as well as reset PRAM
    3) Boot Camp Assistant is not working as well with the error in the subject
    Any ideas how to fix all of these?

  • Boot Camp driver update error

    I keep getting Error code 1603 whenever I try to install the boot camp driver update under Windows Vista, it says something about a restart pending in the event log but I've restarted twice and it hasn't changed a thing, is there any way to fix this?

    right click on my computer, go to manage, then to device manager.
    Under display adapters, remove everything, may ask to reboot, try rebooting or just run installer again.
    This fixed it for me, i tried so many things before i found this fix.

  • 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

  • MDT Boot Image Creation Error: The server did provide a meaningful reply

    I'm creating an mdt boot image in SCCM 2012 SP1. When I first configured MDT integration everything worked fine (version 6.1.2373). Then after creating 2 boot images, I went to create a 3rd, that's when I started having problems. The wizard starts, copies
    the wim file, adds the standard components, then goes to add the winpe-dismcmdlets. After a few minutes this error comes up.
    However, I went to check the pemanager.log file in the appdata\local\microsoft\temp\1\pemanager.3392 folder and it was adding the .net 4 components (after the error had already come up). I also opened up the dism.log file. The .net install completed without
    error and then the winpe-dismcmdlets install started and finished without error. All this was after the error occured, so the process kept running after the error. This continues to happen after a reboot of the site server.
    Log from pemanager.log:
    Deployment Image Servicing and Management tool
    Version: 6.2.9200.16384
    Image Version: 6.2.9200.16384
    Processing 1 of 1 - Adding package WinPE-DismCmdlets-Package~31bf3856ad364e35~amd64~en-US~6.2.9200.16384
    The operation completed successfully.
    Exit code = 0
    Log snippet from dism.log
    2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3996 DismApi.dll: Version 6.2.9200.16384 - DismInitializeInternal
    2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3996 DismApi.dll: Parent process command line: C:\Windows\system32\wbem\wmiprvse.exe - DismInitializeInternal
    2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3996 Enter DismInitializeInternal - DismInitializeInternal
    2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3996 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
    2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3996 Initialized GlobalConfig - DismInitializeInternal
    2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3996 Initialized SessionTable - DismInitializeInternal
    2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3996 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
    2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3996 Waiting for m_pInternalThread to start - CCommandThread::Start
    2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3288 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3996 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
    2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3996 m_pInternalThread started - CCommandThread::Start
    2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3996 Created g_internalDismSession - DismInitializeInternal
    2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3996 Leave DismInitializeInternal - DismInitializeInternal
    2013-04-29 20:19:33, Info                  DISM   API: PID=1296 TID=3288 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2013-04-29 20:20:10, Info                  DISM   API: PID=1296 TID=5096 Enter DismShutdownInternal - DismShutdownInternal
    2013-04-29 20:20:10, Info                  DISM   API: PID=1296 TID=5096 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
    2013-04-29 20:20:10, Info                  DISM   API: PID=1296 TID=5096 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
    2013-04-29 20:20:10, Info                  DISM   API: PID=1296 TID=5096 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
    2013-04-29 20:20:10, Info                  DISM   API: PID=1296 TID=3288 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
    2013-04-29 20:20:10, Info                  DISM   API: PID=1296 TID=3288 Successfully dequeued command object - CCommandThread::DequeueCommandObject
    2013-04-29 20:20:10, Info                  DISM   API: PID=1296 TID=3288 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
    2013-04-29 20:20:10, Info                  DISM   API: PID=1296 TID=3288 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2013-04-29 20:20:10, Info                  DISM   PID=1296 TID=3288 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
    2013-04-29 20:20:10, Info                  DISM   PID=1296 TID=3288 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
    2013-04-29 20:20:10, Info                  DISM   PID=1296 TID=3288 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
    2013-04-29 20:20:12, Info                  DISM   API: PID=1296 TID=3288 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-04-29 20:20:12, Info                  DISM   API: PID=1296 TID=5096 Deleted g_internalDismSession - DismShutdownInternal
    2013-04-29 20:20:12, Info                  DISM   API: PID=1296 TID=5096 Shutdown SessionTable - DismShutdownInternal
    2013-04-29 20:20:12, Info                  DISM   API: PID=1296 TID=5096 Leave DismShutdownInternal - DismShutdownInternal
    2013-04-29 20:20:12, Info                  DISM   API: PID=1296 TID=5096 DismApi.dll:                                         
    - DismShutdownInternal
    2013-04-29 20:20:12, Info                  DISM   API: PID=1296 TID=5096 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
    2013-04-29 20:20:12, Info                  DISM   API: PID=1296 TID=5096 DismApi.dll:                                         
    - DismShutdownInternal
    I tried removing the mdt integration, uninstalling mdt, reboot, install mdt, configure mdt integration. Error occurs whenever an additional component tries to install .net4 or if it installs directly. This is on an almost brand new install
    of the sccm site server on sever 2012. Any ideas?

    For me disabling the anti virus software (TrendMicro OfficeScan) solved the problem.

  • 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

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

Maybe you are looking for

  • Up and down brightness

    Thanks to anyone who can help. I have an iMac slot loading 2001. 600mhz, 40GB harddrive, 128 mbs ram, system 9.2.2 US After being on for a half hour the monitor brightness goes up and down like once or twice a second. On top of that it goes slowly di

  • Does the iPhone 4S work with the tom-tom car kit?

    The tomtom car kit still works fine with my old iPhone 4. I can not get it to work with my iPhone 4S at all it does not recognize the car kit.

  • Wireless file/media transfer to/from Xperia Z3 to/from PC/Mac

    What is the easiest way you would recommend for file/media transfer to/from Xperia Z3 to/from PC/Mac wirelessly?

  • Invoice Per stage

    Hi All, I am havind a problem. <b>I want to make invoice based on per shipment stage.</b> I am creating invoice through VF01, by entring all the deliveries in a particular shipment stage. Can ny one plz help me out... The actual requiremen tis as bel

  • 2wsx keys not working

    I got a PowerBook G4 1.5 17' with 1GB RAM. After a trip I placed the PowerBook on my office and did some work. I left it open all night and the morning the keys 2wsx won't work anymore. i try the hardware test the resets but still nothing . anyone go