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

Similar Messages

  • How to load a boot image to cisco aironet 1140 series after missing boot image

    Hi all,
    I need a solution for this. When i switch my cisco aironet 1140 , it s blinking with red light .and gives a message "no boot image to load".
    When i tried next time, by pressing escape it shows this message that i have mentioned below.
    ap:
    ap:
    using  eeprom values
    WRDTR,CLKTR: 0x83000800 0x40000000
    RQDC ,RFDC : 0x80000035 0x00000208
    using ÿÿÿÿ ddr static values from serial eeprom
    ddr init done
    Running Normal Memtest...
    Passed.
    IOS Bootloader - Starting system.
    FLASH CHIP:  Numonyx P33
    Checking for Over Erased blocks
    Xmodem file system is available.
    DDR values used from system serial eeprom.
    WRDTR,CLKTR: 0x83000800, 0x40000000
    RQDC, RFDC : 0x80000035, 0x00000208
    PCIE0: link is up.
    PCIE0: VC0 is active
    PCIE1: link is NOT up.
    PCIE1 port 1 not initialized
    PCIEx: initialization done
    flashfs[0]: 1 files, 1 directories
    flashfs[0]: 0 orphaned files, 0 orphaned directories
    flashfs[0]: Total bytes: 32385024
    flashfs[0]: Bytes used: 1536
    flashfs[0]: Bytes available: 32383488
    flashfs[0]: flashfs fsck took 16 seconds.
    Reading cookie from system serial eeprom...Done
    Base Ethernet MAC address: 28:94:0f:d6:c8:62
    Ethernet speed is 100 Mb - FULL duplex
    The system is unable to boot automatically because there
    are no bootable files.
    C1140 Boot Loader (C1140-BOOT-M) Version 12.4(23c)JA3, RELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Compiled Tue 18-Oct-11 14:51 by prod_rel_team
    ap:
    So , now my question is how to load the boot image ? From where will we get this ? OR
    I m also having another Cisco aironet 1140 , Can i get bootimage from that . Kindly let me know the solution from genius ?

    Take a look at this link as it should have the info you need
    https://supportforums.cisco.com/docs/DOC-14636
    Sent from Cisco Technical Support iPhone App

  • 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

  • WinPe boot images

    I created WinPe boot images from Windows AIK, Windows AIK was installed on a Windows 7 machine. Once Winpe wims were generated I moved them to sccm and imported the images to sccm, images were successfully distributed to DP. The question is when I am adding
    drivers and I want to add drivers to my WinPe, they do not show up on the list. where have I gone wrong?

    Perhaps Johan's excellent OSD Matrix will help you understand the requirements a bit more:
    http://www.deploymentresearch.com/Research/tabid/62/EntryId/127/What-if-I-told-you-The-OSD-Support-Matrix-for-MDT-and-ConfigMgr-is-here.aspx
    If you're using ConfigMgr 2012 R2 to deploy Windows 7 SP1, you should be using a WinPE 5.0 (or 5.1 it doesnt matter) image. WinPE 4.0 is not supported in ConfigMgr 2012 R2, nor are WinPE 3.1. You can still import these boot images, but you'll not be able
    to amend them like adding drivers etc.
    Regards,
    Nickolaj Andersen | www.scconfigmgr.com |
    @NickolajA

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

  • How To Update Custom ItemRenderer (Image) on DataGrid Edit

    I have an DataGrid with 2 columns, column 1 called "Name" and column 2 called "Actions".
    The "Name" column contains editable text and the "Actions" column uses a (inline) custom ItemRenderer which displays 2 icon images ( for Edit and Delete). All works fine. Clicking Edit or Delete calls the corrosponding outerDocument method.
    The feature I am trying to add is as follows: when someone double-clicks on the text in the Name column to edit it, I would like the edit icon in the Actions column to ( grow/shrink, change color  - or some such indication/reminder to click it ). Not seeing how to do this with the inline ItemRenderer, I created a custom item renderer class and, in that class, use mx:Resize to perform the "grow/shrink". I created a method called "pulse()" and, from within that renderer, all works well. ( for testing, I wired the icons click event to the pulse() method ). However, now I am not sure how to call that ItemRenderers "pulse()" method to perform the effect from the main DataGrid (when the user double-clicks on Name field to edit).
    The tried using the DataGrid's "itemEditBegin", which fires correctly, but from that point I am not sure how to access the selected rows edit icon in the "Action" column. ( to call its pulse() ) method.
    So any suggestions how I can achieve my end result? Being able to manipulate the edit icon in the "Actions" column, when the user double-clicks (edits) that row's "Name" column?
    If I'm going about it all wrong, feel free to offer alternative solutions.
    Any help would be appreciated.
    Thanks,
    ~e

    Hi,
      Check the  BAPI_MATERIAL_SAVEDATA ,in the BAPI  is there a table parameter EXTENSIONIN ?
    which you can use to pass the values for user defined fields to the BAPI..
    Regards
    Kiran Sure

  • How to update previously modified Image and prevent from reverting?

    Below is my code for updating a painComponent:- it basically zooms in on a particular image. The zooming works for the first try. But since the Image ITSELF isnt updated if i try to zoom in on the zoomed image its actually trying to zoom the original image since my g.drawImage() has the original Image (not zoomed). Is there anyway to update the Image so that it is the previously zoomed image and not the original? I searched for "zoom" throughout the boards and no one seemed to brough this "problem" up. Can someone help me out? thanks
    public void paintComponent(Graphics g) {
    g.drawImage(zoomingImage,0,0,(int)zoomFrame.getWidth(),(int)zoomFrame.getHeight(),((Point) zoomStartPoints.lastElement()).x,((Point) zoomStartPoints.lastElement()).y,((Point)zoomEndPoints.lastElement()).x,((Point) zoomEndPoints.lastElement()).y,Color.WHITE,null);}
    setOpaque( false ); // background will not be painted by super.paintComponent()
    if (startPoint != null && endPoint != null) {
    int x = Math.min(startPoint.x, endPoint.x);
    int y = Math.min(startPoint.y, endPoint.y);
    int width = Math.abs(endPoint.x - startPoint.x);
    int height = Math.abs(endPoint.y - startPoint.y);
    g.drawRect(x, y, width, height);
    if (dragged ) {
    g.drawImage(zoomingImage,0,0,(int)zoomFrame.getWidth(),(int)zoomFrame.getHeight(),((Point) zoomStartPoints.lastElement()).x,((Point) zoomStartPoints.lastElement()).y,((Point) zoomEndPoints.lastElement()).x,((Point) zoomEndPoints.lastElement()).y,Color.WHITE,null);
    dragged = false;
    super.paintComponent(g); }

    http://feeds.feedburner.com/
    http://feeds.feedburner.com/scottwimberly/JDaY is my URL to see what I have done.

  • How to identifiy Faulty Driver in Boot Image (Reverse Engineering of Adding a Driver to Boot Image)

    Hello SCCM'lovers
    I'm having a new EliteBook 820 G2 here which Fails PXE boot due to a false corrupted
    Intel Advanced Network Service Virtual Adapter-Driver.
    The PROBLEM now is how to determine under Boot Images - Properties - Drivers ... the correct one.
    (see pic)
    Over the months, I injected different ones. smsts.log indicates me that this driver is the problem but how can I reverse engineer it to find the correct version/timestamp whatever it on my DP

    in theory at least there is a way.
    The driver loading in windows will select the best driver based on the PNP-id, version of driver, if it's signed and so on. 
    you can find the PNP deviceID for that hardware on a installed system by looking in device manager. 
    After that you can follow the same rules that the system uses to determine which driver it would load by reading the inf files for each driver. 
    Would it be faster to just create a new one - most likely. 
    I also would recommend that you create a dedicated driver folder and category  in SCCM for WinPE and only add the drivers you need. I prefer to use Original vendor drivers here (aka nicdrivers straight from Intel instead of DELL or HP or ... repackaged
    versions

  • 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

  • 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

  • T520 won't detect Network card in WDS/WinPE/​Ghost image disk

    Hello all,
    I figured I would just post this so I could save 2 days of someone elses life.
    I'm not sure how many other modes have the EFI and UEFI bios's in them but this has caused a lot of problems when trying to capture an image / image the Lenovo T520.  So for anyone else that is having these problems here is how I got around the problem.
    The Problem:
    While trying to boot up off a Capture image with a CD or PXE boot for our WDS server the laptop would not detect the network card giving no IP address and listing the adapter as a hybrid.  When trying to do a ipconfig /renew it would give an error around the lines of the loopback something or other ....... the adapter could not be contacted or initated.
    I instantly thought this was due to the vanila WinPE / Capture image not having the drivers for the Lenovoo T520, so I went to the website downloaded the new drivers and injected them into the WinPE disk(You will want ot use the NDIS Drivers which are included in the package for this).  Following this process it would still not detect or install the NIC.  After many hours of searching it would apear this was due to the EFI/UEFI bios options not going through the proper boot cycle when in a PE enviroment.  The solution was to mess around with the EFI/UEFI switches in the WinPE boot image during the creation proccess as listed below:
    ocdimg -m -o -u2 -udfver102 -bootdata:2#p0,e,bc:\winpe_x64\etfsboot.com#pEF,e,​bc:\winpe_x64\efisys.bin c:\winpe_x64\ISO c:\winpe_x64\winpeuefi.iso
    The link with more details is here: http://support.microsoft.com/kb/947024
    Eseentially once the new boot image was complied with the proper EFI / UEFI options enabled it went through the proper boot process detected the NIC and installed the drivers which I previously provided on the disk and we where off to the races imaging the new laptop.
    Hopefull this will help some others who are struggling with this or any other model that has this type of bios.
    Cheers, and thanks
    Please feel free to post any additional comments to help others if you found better ways to get around this
    One side note the EFI/UEFI to legacy mode only does nothing for the NIC problem, I have seen some posts where they can help with the hard drive issues when imaging, however as for the nic not loading in PE enviroments this setting in the BIOS did not reslove the problem.

    Hi Rusty1234
    If I did not remember wrongly, you may present or add drivers (network, hardware) under WDS / Ghost software or copy necessary drivers (e.g. your T520 network card drivers) under it's PXE / boot section.
    Happy 2012! 
    Peter
    W520 (4284-A99)
    Does someone’s post help you? Give them kudos as a reward, as they will do better to improve | Mark it as solved if the solution works for you, so it could be reference for others in the future 
    =====================================
    Sound Enthusiast and Enhancement (Post comments, share mixes, etc.)
    http://forums.lenovo.com/t5/General-Discussion/Dol​by-Home-Theater-v4-for-most-Lenovo-Laptops/td-p/62​...

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

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

  • MDT 2010: How to change WinPE drivers?

    We have boot images that currently work for all of our systems and is used for PXE booting with a WDS server, but I think we have lots of extra drivers in the PE image because the boot image size is quite large and it seems to spend a long time injecting
    drivers during the PE portion before the OS is installed.  
    Which drivers other than than NIC drivers are needed in the boot image?
    How can we change the boot image so that it has only the minimum necessary drivers for each computer model?

    Network and storage controller drivers are the essential ones and that is included by default in the boot image. However there are certain types of these drivers you do not want/need in the boot image and that is drivers for wireless network cards and for
    instance all kinds of memory card reader drivers.
    One of way of gaining full control over the drivers in the boot image is to create a WinPE structure in the driver part of Deployment Workbench and then use Selection profiles (see the settings on the deployment share) to make sure that only the drivers
    from the selection profile is added to the WinPE/Boot image.
    Blogging about Windows for IT pros at
    www.theexperienceblog.com

  • Boot image

    I have made a disk image of my harddrive. I now would like to know how I can make a univeral boot image that I can use to them install my disk image.
    Any sugestions on how to make a boot image?

    If you are storing this image on an external drive, then I would suggest a different approach. Make a bootable clone of your hard drive onto the external drive. You can then boot from the external drive and use the clone to restore the system on the hard drive should you have a problem. With the right backup software you can also schedule regular incremental updates to the clone so the clone is always the same as the hard drive. See the following:
    Basic Backup
    Use an external Firewire drive at least equal in size to the internal hard drive and make (and maintain) a bootable clone/backup. You can make a bootable clone using the Restore option of Disk Utility. You can also make and maintain clones with good backup software. My personal recommendations are (order is not significant):
    1. Retrospect Desktop (Commercial - not yet universal binary)
    2. Synchronize! Pro X (Commercial)
    3. Synk (Backup, Standard, or Pro)
    4. Deja Vu (Shareware)
    5. PsynchX 2.1.1 and RsyncX 2.1 (Freeware)
    6. Carbon Copy Cloner (Freeware - 3.0 is a Universal Binary)
    7. SuperDuper! (Commercial)
    8. Intego Personal Backup (Commercial)
    9. Data Backup (Commercial)
    The following utilities can also be used for backup, but cannot create bootable clones:
    1. Backup (requires a .Mac account with Apple both to get the software and to use it.)
    2. Toast
    3. Impression
    4. arRSync
    Apple's Backup is a full backup tool capable of also backing up across multiple media such as CD/DVD. However, it cannot create bootable backups. It is primarily an "archiving" utility as are the other two.
    Impression and Toast are disk image based backups, only. Particularly useful if you need to backup to CD/DVD across multiple media.
    Visit The XLab FAQs and read the FAQs on maintenance, optimization, virus protection, and backup and restore. Also read How to Back Up and Restore Your Files.
    Although you can buy a complete FireWire drive system, you can also put one together if you are so inclined. It's relatively easy and only requires a Phillips head screwdriver (typically.) You can purchase hard drives separately. This gives you an opportunity to shop for the best prices on a hard drive of your choice. Reliable brands include Seagate, Hitachi, Western Digital, Toshiba, and Fujitsu. You can find reviews and benchmarks on many drives at Storage Review.
    Enclosures for FireWire and USB are readily available. You can find only FireWire enclosures, only USB enclosures, and enclosures that feature multiple ports. I would stress getting enclosures that use the Oxford chipsets (911, 921, 922, for example.) You can find enclosures at places such as;
    Cool Drives
    OWC
    WiebeTech
    Firewire Direct
    California Drives
    NewEgg
    All you need do is remove a case cover, mount the hard drive in the enclosure and connect the cables, then re-attach the case cover. Usually the only tool required is a small or medium Phillips screwdriver.

Maybe you are looking for

  • Saving a PDF file without the comments

    In Acrobat Reader, is it possible to save a copy of a PDF file without the comments. I'm doing a PhD, and would like to be able to send some scientific papers to colleagues without the annotation I may have added. Of course, manually removing all the

  • MIME object download by BSP  with 'Save as' box

    hello ,   i am trying to download a Excel file which is in MIME objects in my BSP application. From portal i want to download this with 'Save as' box . Currently excel file is opening and i have to save it manually on local drive.    can u suggest me

  • Issues with opening multiple artboard docs in Illustrator CS6

    Hi. I'm working in CS6 Cloud. I have a document with multiple artboards. However, when I go to open it, a dialogue box comes up and says "Open Pdf - Select a page from PDF to open...". I can then only open single artboards as separate documents. How

  • FCExpress VS FCP (quick answer please!)

    Hello, I'm a student in Digital Media at a design school, just finished a 2 month course involving FCP. I'm not financially able to purchase FCP, but Express is within my budget. What are the major differences between them? I cant find anything that

  • Using html:select with mutiple

    hy, guys!I need some help:I am developing a form were I use a heml:select wich have to use the mutiple selecting function( the user could select more then one option)it looks like this: <html:select property="sectors" multiple="true" size="3" ><html: