Thinkpad 10 SCCM 2012 R2 x64 WINPE OSD boot wim

Trying to inject drivers in to my CM12 x64 boot wim (ADK and MDT 2013 integration with CM12) for the new Thinkpad 10 Tablet.  The x86 worked flawlessly and touch screen works on the x86 builds even my S1 Yoga.  Errors galore with the x64 versions of the drivers from the SCCM pack.  Being UEFI boot only both versions are needed and not all my locations will have the dock for using a keyboard so touch just needs to work.
Here is what successfully got added,the 2 display drivers and thats it.  I started with all the drivers and worked in reverse by removing each driver after every error. 
from SCCM:
Success: Drivers that will be included:
Realtek USB GBE Family Controller
Lenovo USB2.0 Ethernet Adapter
Intel(R) 5 Series 4 Port SATA AHCI Controller
Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller
Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller
Intel(R) C600 Series Chipset SATA AHCI Controller
Realtek USB GBE Family Controller
VMware Pointing Device
VMware USB Pointing Device
VMware PVSCSI Controller
VMware SVGA 3D
VMware VMCI Bus Device
vmxnet3 Ethernet Adapter
Intel(R) HD Graphics
ThinkPad Display 640x480
Realtek USB GBE Family Controller
Any help is appreciated and parkerj, as usual I am willing to be your huckleberry if needed.  On a unrelated item any tips for removing the lenovo scup data from my wsus/scup environment?  We had an issue and now i cannot publish the data.  Whick makes me sad as I think the Lenovo SCUP catalog shows good progress.  Primary issue is knowing what applies to what without publishing everything.

Hi,
UEFI BIOS Version: GWET23WW (1.23)
I have managed to implement drivers in a different way. I have created a package containing all drivers and placed it in a part of task sequence running inside installed operating system instead of running in WinPE. There is a script inside a package looking like this:
Start /w .\win\Chipset\setup.exe -s
Start /w pnputil -i -a .\WIN\TXEI\INF\TXEI.inf
Start /w setup.exe -SILENT
Start /w .\WIN\Audio\setup.exe /s
Start /w .\WIN\Bluetooth\setup.exe /s
Start /w .\WIN\Fingerprint\WBF_SPI_DDK_Extended_Setup.exe /s
Start /w .\WIN\GPS\setup.msi /qn
Start /w .\HOTKEY\setup.exe /S /B /H
pnputil -i -a .\WIN\MONITOR\TPLCD.INF
Start /w .\WIN\NFC\setup.exe /s
Start /w .\WIN\PMDriver\setup.exe -S -SMS
Start /w .\WIN\WLAN\setup.exe -s
reg import .\OSFIXES\ALSOR\ALSOR_Apply.reg
For anyone interested just make sure you follow correct paths to executables as presented in this script.
After running it I am left with Security Device unrecognized in Device Manager so I have to add another task sequence for Restart and than another one with a line with a package for Security Device and runing this as a command: pnputil -i -a TXEI.inf
Using regular pre-driver deploy task sequence commands in WinPE enviorenment unfortunately didn't helped so I have ended with workarounds presented here.
If anyone can add something to this I will be more than glad to hear.

Similar Messages

  • SCCM 2012 R2 Won't import boot.wim

    Over the weekend I have upgraded to SCCM R2 CU4 and today I am having issues with OSD, After the install of the client, the task just ends and does not continue to install the applications.
    I checked: drivers, network access account, redistributed all content to DPs still the same issue. After some googleing I found this thread "Failed to get the environment key - SMSTS.log" Sorry not allowed to link yet.
    My wim versions are 6.2.9200 so I figured I need to import new boot images, not a big deal.
    I have ADK 8.1 Setup up on the server. exported the boot.wim from the adk but whem I attept to import the new boot.wim sccm gives me an error. So back to google. People have stated that MacAfee can cause errors, well we don't run MacAfee, we have
    Symantec. For jokes sake I disabled that anyway, but still sccm fails to import the boot.wim, for any user, including the addmin user that was used to install SCCM. As well as from multiple network locations.
    Any one have any idea. Any logs I can look at?

     I've removed ALL drivers and all packages from SCCM, as well as task sequences pointing to driver packages. Still same issue.
    I cannot add or remove drives from boot images. When attempting to add driver to a boot image. the dialog where I select the boot image is just blank and does not list any boot images that are in sccm console.
    When attempting to update files on distribution points from the boot images that exist i get this error message.
    Error: Boot image to update:
    •    Microsoft Windows PE (x86)
      Error: Actions to perform:
    •    Add ConfigMgr binaries
    •    Disable 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 = 4716;
    •    ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
    •    Operation = "ExecMethod";
    •    ParameterInfo = "SMS_BootImagePackage.PackageID=\"SPS00004\"";
    •    ProviderName = "WinMgmt";
    •    StatusCode = 2147749889;
    What else is there to try? I am running out of ideas.

  • SCCM 2012 with MDT intergration OSD

    Does anyone have some links or suggested study material with regards to SCCM 2012 with MDT integration. I am specifically looking for the OS deployment.
    Most of the stuff I found only cover OSD with SCCM task sequences. Any assistance would be greatly appreciated.

    If you download the MDT 2013 documentation from this link:
    http://www.microsoft.com/en-us/download/details.aspx?id=40796
    You will find two Word documents about integrating MDT 2013 with ConfigMgr 2012. They are called:
    Quick Start Guide for System Center 2012 R2 Configuration Manager
    Quick Start Guide for User Driven Installation
    You could also have a look at this book:
    http://www.amazon.com/Deployment-Fundamentals-Vol-Deploying-Configuration/dp/9197939021/ref=sr_1_4?s=books&ie=UTF8&qid=1400523728&sr=1-4&keywords=arwidmark
    It is written for ConfigMgr 2007 and MDT 2010 but most of the steps in the book would be the same on ConfigMgr 2012 and MDT 2013.

  • SCCM 2012 R2 PxE can't boot - your pc need to be repired.

    Dear All,
    These days, I upgraded SCCM 2012 to R2 , after that PxE can't boot , and shows a blue screen that your pc need to be repired, same issue like this:http://www.gerryhampsoncm.blogspot.ie/2013/02/sccm-2012-task-sequence-fails-with-bcd.html
    And, i have also re-configed the pxe more times follow by this acticle , and still failed.
    And, after I replace the \RemoteInstall\SMSTemp\2014.01.08.12.31.26.01.{xxxxxxxxx}.boot.bcd to \RemoteInstall\Tmp\x86x64{xxxxxxx}.bcd, and the PC can boot to the winpe well. that means the pc using Tmp folder's BCD store
    to boot to WinPE, and not using SMSTemp's.
    I check the PxE process:http://technet.microsoft.com/en-us/library/cc722358(v=ws.10).aspx
    PXEBoot.com downloads Bootmgr.exe and the BCD store, and I think PXEBoot.com should download BCD store from SMSTemp folder, and should not be the Tmp folder.
    So, my question is that why te PXEBoot.com download BCD from Tmp folder ? And how can I change it to download BCD from SMSTemp folder. ? I have been getting to crazy about this fucking problem.
    Nemo

    Reinstalling WDS and the PXE was not the answer, at least not for me, but I dunno about the original poster as he kept quiet.
    For now I am trying to get SCCM2012 R2 running as this is the topic for my final projekt.
    But I am stuck here, the problem is the same as the original poster mentioned.
    Even thougt DHCP options are set to my CM and smsboot\x86\wdsnbp.com, pxe keeps loading boot\... and fails.
    Making a copy from smsboot to boot and renaming the file fixes it in a dirty way.
    The WDS-service has never been configured manually, after rolling back to a fresh Server and installing CU1 first nothing changed about that (PXE worked at all at least) und reinstalling the living dead out of the roles and features fixes nothing.
    The remoteinstall folder gets populated everytime, with the SMS related stuff and the wds related stuff, I guess (boot, SMSboot, ...).
    I tried various variations of the start path, TFTP still loads from boot instead smsboot.
    The Images have been temporarily replaced with the one from our old site.
    I renewed the whole site, this bugs me since 2012 R1 and R2 is the second site too.
    I would really appreciate it if someone could help with an working solution.
    Let me know if you need some more informations, site is described below.
    In case this should get another Thread, let me know.
    Thank you guys :)
    Hyper-V Environment, Windows Server 2012 R2 Standard on all three Hosts (Gen 2),
    Followed mainly the MS TLG for SCCM2012 for this, supported by windows-noob.
    Have a nice day.
    Little Edit right here: renaming the file only helps with the 89 error thing, but it doesn't help booting the sccm image.

  • SCCM 2012 R2 Won't PXE Boot

    I'm trying to get PXE booting to work on our SCCM 2012 R2 server and am getting the dreaded "PXE-E53: No Boot file Name Received."  DHCP server is in same subnet on a different machine, so supposedly no DHCP options or ip helpers are necessary.  I'm
    testing using a client VM with the legacy adapter for the NIC, and that machine PXE boots fine from our SCCM 2007 server.
    When I test, I've been shutting down the SCCM 2007 server so that the 2012 machine is the only PXE server on our network. 
    In a nutshell, I'm trying to deploy Windows 8.1 using
    this as a guide. The x86 and x64 boot images are enabled for PXE distribution and I've deployed the task sequence for the 8.1 OS image to all unknown computers.  The DP  shows content for the OS image and the boot images.  PXE on the DP is enabled
    and checkmarked to listen for PXE requests on all interfaces and for unknown computer support. 
    For troubleshooting I've tried unchecking all the PXE settinging in the DP, which removes WDS and then putting it back, as well as removing the MP role and putting it back (see attached snippet of SMSPXE.LOG).
    I feel like I'm missing something basic here.  Can anyone help?
    Thanks!

    Thanks, Jason.  Yes, the MAC addrss is the client I'm trying to PXE boot.
    I've reviewed the health in the monitoring section.  No issues in System Status, and in Content Status there is only one error regarding the DP trying to contact an old SCCM 2007 distribution point at a branch office.  This
    appears to be a leftover from the migration process from SCCM 2007.  This old distribution point is no longer in use and I can't seem to find any references to it on my SCCM 2012 R2 installation.  Not sure if this is significant or not. 
    I've attached a snippet of the error: 

  • SCCM 2012 sp1 - can't add boot image - Only finalized boot images are supported.

    so when i updated to sp1 i had to install the new assessment and deployment kit which i have done.
    when i try to add a boot image to sccm now i get the error:
    You can not import this boot image. Only finalized boot images are supported. For more information press F1.
    i have searched technet and on old versions of sccm you could re-install waik to fix this issue, i have tried re-installing ADK and its still doing the same.
    has anyone had this problem on 2012 sp1?

    Hi,
    It works to import x86 image of windows 8 and now I have some problems when I try to import x64 boot image of 8.1.
    Where I can see errors in logs. Are sow many log files and I'm little confuse and I cant find error to see what is the reason of this error.
    And the error is:
    Error: Data Source
    Information
    • Source location:
    \\xxx\yyy\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.

  • SCCM 2012 R2 & MDT 2013 OSD Refresh - BDEDrive Assigned letter

    Hello,
    I'm having an issue with my MDT OSD refresh for Win 7 machines. I've capture a Win 7 reference image from a VM using MDT capture TS and I can successfully deploy that image to a bare metal VM
    using an MDT integrated SCCM TS. The disk partitions are expected, C:\ is the primary OS and BDEDrive is assigned 500MB and is hidden, no drive letter assigned.
    DISKPART> list volume
      Volume ###  Ltr  Label        Fs     Type        Size     Status    
    Info
      Volume 0     E                       DVD-ROM         0 B  No Media
      Volume 1         BDEDrive (P  NTFS   Partition    500 MB  Healthy
      Volume 2     C   OSDisk       NTFS   Partition     19 GB  Healthy    System
    DISKPART>
    However, when I run a refresh TS to re-deploy the same imaged used in my bare metal TS, the BDEDrive is assigned D:\ and is visible in windows explorer.
    DISKPART> list volume
      Volume ###  Ltr 
    Label        Fs    
    Type        Size    
    Status     Info
      Volume 0    
    E                      
    DVD-ROM         0 B 
    No Media
      Volume 1    
    D   BDEDrive (P  NTFS  
    Partition    500 MB  Healthy
      Volume 2    
    C   OSDisk      
    NTFS   Partition    
    19 GB  Healthy
    DISKPART>
    In the ‘Formart and Partition Disk 6.1’ step, I have checked the option ‘Do 
    not assign a drive letter this partition’ but it’s obviously not working as expected. Any suggestions?
    Thanks!

    Not sure if this is the same as what you are seeing, but check out this post: https://social.technet.microsoft.com/Forums/systemcenter/en-US/b3e2fc1f-e9df-4c6e-99a5-5d0e0dff648a/refresh-scenario-with-bitlocker-partition?forum=configmgrosd
    Jeff

  • SCCM 2012: Failed to insert OSD binaries into the WIM file' error when you create a MDT Task Sequence

    Hi,
    When I try to import the MDT boot image X86, I get the following error:
    Started processing.
    Creating boot image.
    Copying WIM file.
    Mounting WIM file.
    WIM file mounted.
    Setting Windows PE system root.
    Set Windows PE system root.
    Set Windows PE scratch space.
    Adding standard components.
    Adding component: winpe-mdac
    Adding extra content from: C:\Users\ADMINI~1.afO\AppData\Local\Temp\3\sfup2yp2.0rt
    Unmounting WIM.
    Copying WIM to the package source directory.
    Creating boot image package.
    Error while importing Microsoft Deployment Toolkit Task Sequence.
    Failed to insert OSD binaries into the WIM file
    Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException: The SMS Provider reported an error. ---> System.Management.ManagementException: Generic failure
       at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
       at System.Management.ManagementObject.Put(PutOptions options)
       at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
       --- End of inner exception stack trace ---
       at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
       at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put()
       at Microsoft.BDD.Wizards.SCCM_ImportTaskSequenceTask.DoWork(SmsPageData smspageData, Dictionary`2 data)
    Note: previous x86 image was deleted some time ago.
    Please advise.
    J.
    Jan Hoedt

    This is the error in smsprov.log
    *********** WBEM Missing property TransformAnalysisDate    SMS Provider    16/04/2014 15:11:00    7856 (0x1EB0)
    ************ WBEM Missing property TransformReadiness    SMS Provider    16/04/2014 15:11:00    7856 (0x1EB0)
    Image language ID 1033 and en-US    SMS Provider    16/04/2014 15:11:00    7856 (0x1EB0)
    Image language ID 1033 and en-US    SMS Provider    16/04/2014 15:11:10    7856 (0x1EB0)
    Image language ID 1033 and en-US    SMS Provider    16/04/2014 15:11:19    7856 (0x1EB0)
    ERROR> Error -1073741502 returned to execute the command line: "C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /Image:"C:\windows\TEMP\BootImages\{8AEF81AB-4B11-4AEF-96D3-E90D84D3DA94}\mount" /Add-Package
    /PackagePath:"C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\WinPE-Scripting.cab"    SMS Provider    16/04/2014 15:11:19    7856 (0x1EB0)
    Failed to install required components into the boot image C:\windows\TEMP\BootImages\{8AEF81AB-4B11-4AEF-96D3-E90D84D3DA94}\mount    SMS Provider    16/04/2014 15:11:19    7856 (0x1EB0)
    *~*~e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\sspbootimagepackage.cpp(3766) : Failed to insert OSD binaries into the WIM file~*~*    SMS Provider    16/04/2014 15:11:36    7856 (0x1EB0)
    *~*~Failed to insert OSD binaries into the WIM file ~*~*    SMS Provider    16/04/2014 15:11:36    7856 (0x1EB0)
    Auditing: User FAC\administrator called an audited method of an instance of class SMS_BootImagePackage.    SMS Provider    16/04/2014 15:11:36    7856 (0x1EB0)
    CExtUserContext::LeaveThread : Releasing IWbemContextPtr=9281008    SMS Provider    16/04/2014 15:11:36    7856 (0x1EB0)
    Jan Hoedt

  • 16-Bit App Support for SCCM 2012 Task Sequence / WinPE 4.0

    I'm not sure if what we're trying to do is even possible, but I am hoping it is.  I wrote a little script to check the BIOS asset tag info and if it isn't a valid numeric number it prompts in the task sequence to enter the correct asset tag number. 
    We're trying to do this so we have it on a custom SCCM report for inventory tracking.  The problem is the Acer utility is 16-bit and it kicks back an error in WinPE saying that
    you don't have access to run 16-bit applications and to check your permissions with your system admin.  Where does WinPE store these permissions?  I know where they are in GPO's but not for SCCM's WinPE.
    ' Beta Test Version' Define Variables
    Dim AssetTag, BiosVer, Serial, Model, Vendor, strAssetTag, FSO, objShell, objName, objBios, objAsset
    ' Define WMI Objects / queries
    Set wmi = GetObject("winmgmts:")
    Set objAsset = wmi.InstancesOf("Win32_SystemEnclosure")
    Set objBios = wmi.InstancesOf("Win32_Bios")
    Set objName = wmi.InstancesOf("Win32_ComputerSystemProduct")
    Set FSO = CreateObject("Scripting.FileSystemObject")
    Set objShell = WScript.CreateObject ("WScript.shell")
    ' Set values of variables based on the WMI Object query
    For Each obj in objAsset
    AssetTag = obj.SMBIOSAssetTag
    Exit For
    Next
    For Each obj in objBios
    BiosVer = obj.SMBIOSBIOSVersion
    Serial = obj.SerialNumber
    Exit For
    Next
    For Each obj in objName
    Model = obj.Name
    Vendor = obj.Vendor
    Exit For
    Next
    ' Test for Valid Asset Tag number
    Set re = New RegExp
    re.Pattern = "\D+"
    re.IgnoreCase = True
    re.Global = True
    hasMatches = re.Test(AssetTag)
    If hasMatches = True Then
    FSO.CreateFolder "C:\BIOS"
    strAssetTag = InputBox("Asset Tag info is INVALID." & vbCrLf & "Please enter a valid ACSD Asset Tag: ","ACSD Asset Tag",AssetTag,20,20)
    Else
    Wscript.Quit
    End If
    ' Process Asset Tag Update in BIOS
    If Model = "5100C2U" Then
    FSO.CopyFile "\\server\share\BIOS\Lenovo-5100C2U\*.*", "C:\BIOS\"
    objShell.Run "CMD /K CD C:\BIOS & C:\BIOS\wflash2.exe /tag:" & strAssetTag
    ElseIf Model = "2117EKU" Then
    FSO.CopyFile "\\server\share\BIOS\Lenovo-2117EKU\*.*", "C:\BIOS\"
    objShell.Run "CMD /K CD C:\BIOS & C:\BIOS\wflash2.exe /tag:" & strAssetTag
    ElseIf Model = "Aspire V5-121" Then
    FSO.CopyFile "\\server\share\BIOS\Acer-V5-121\*.*", "C:\BIOS\"
    objShell.Run "CMD /K CD C:\BIOS & C:\BIOS\DQDMI.EXE /Wasset " & strAssetTag
    Else
    Wscript.Quit
    End If

    I guess that it has nothing to do with permissions. WinPE is missing the 16bit subsystem in total as far as I know.
    Torsten Meringer | http://www.mssccmfaq.de

  • MDT 2012 Win7 x64 capture fails - boot loop

    Hi everyone,
    I'm pretty new to MDT and having a problem capturing a Win7 x64 reference image.
    It seems to start out fine doing the Sysprep and so on, but then it has to restart the computer and after that it goes into a boot loop. After this, I have been forced to format and reinstall Win7 on the computer. This picture shows what it loops through
    in about 20 seconds - and it shows nothing else than what's on these pictures :)
    www.jaded.dk/boot_loop.png
    I have been Google'ing alot, but can't find any post with the same issue, since most other get an error msg which I dont.
    Here is some info about the setup.
    I'm deploying the task sequence locally using these commands:
    net use * \\mdtserver\DeploymentShare$ /user:domain\username
    cscript \\mdtserver\DeploymentShare$\Scripts\LiteTouch.wsf
    Server running MDT 2012 U1 - Win server 2008 R2, 64 bit
    The laptop on which i'm trying to capture the ref img is a HP Elitebook 8470p. It is fully patched with windows updates and I have installed a few apps like Office 2010, flash player, reader etc.
    The "Rules" on my MDT Workbench is like this:
    [Settings]
    Priority=Default
    Properties=MyCustomProperty
    [Default]
    OSInstall=Y
    SkipCapture=NO
    SkipAdminPassword=YES
    SkipProductKey=YES
    SkipComputerBackup=YES
    SkipBitLocker=YES
    SkipTimeZone=YES
    SkipLocaleSelection=YES
    InputLocale=0406:00000406
    KeyboardLocale=0406:00000406
    KeyboardLocalePE=0406:00000406
    SystemLocale=0406:00000406
    UILanguage=0406
    UserLocale=0406:00000406
    My task sequence looks like this:
    www.jaded.dk/task_seq.png
    I don't know where to find a log of the capture, to get a hint of what has gone wrong.
    Hope you can help me out here :) And please let me know if you need more info.
    Thanks
    Morten

    Thank you both for answering.
    ccatlett_sogeti:
    I didn't seem to have Windows Deployment Services installed on my server. I just installed it and added WinPE boot files as bootimage according to this guide: http://blogs.technet.com/b/manojnair/archive/2011/11/23/exploring-mdt-2012-beta-2-part-6-of-10-integrating-mdt-2012-beta-2-with-windows-deployment-services-wds.aspx
    Is that correct?
    Keep in mind that I don't use PXE at the moment, if that makes any difference :)
    David:
    I will try to add SLShareDynamicLogging. I set it like this - hope it's correct:
    SLShareDynamicLogging =\\MDTSERVER\DeploymentShare$\Logs\%ComputerName%

  • SCCM 2012 OS deployment fails post loading.WIM

    I am trying to install an image on a laptop - I get the PXE boot and it downloads the NBP file and starts loading the files for the .wim - it does this (I suspect) and after about 30 minutes of doing that (loading files.....) it goes to a login screen but
    it is not the new image, it is what came with it.
    How do I troubleshoot this.
    In the smspxe.log it shows that it is looking for the bootimage HQ200005 (which corresponds to my x64 boot image) then I get some Begin validation of certificate and completed validation of certificate and then that's all.

    Also, it's always a good rule of thumb to make sure you've got all your content properly distributed, boundaries and boundary groups setup and good to, and a network access account created.

  • SCCM 2012 - OSD - HAL.dll error (windows XP) using USB

    Hi
    SCCM 2012
    I'm creating OSD for Windows XP  and create .iso files
    1. I create ISO files
    2. make the USB bootable
    3. Copy the ISO files in content in USB
    4. Boot from USB,  when it finish I;m getting the HAL.dll error
    Please advise
    Robert

    The hal.dll is missing?
    http://support.microsoft.com/kb/314477/en-gb
    Juke Chou
    TechNet Community Support

  • SCCM 2012 SP1 MDT task sequence fails on reboot does not retain ip

    we are having a sccm 2012 sp1 server that used for installation of win 8.1 Enterprise , the task sequence works perfectly fine but when we  run the same task on HP Elite 8300 system having Intel 82579LM Adapter from Windows XP , after the reboot the
    task fails as no ip address is assigned the NIC , We did download the WInPE Adapter drivers from HP site and injecting to the x86 Boot Image (6.2.9200) however the task still fails ,
    Our environment uses all static ip address , the same task as mentioned earlier has worked fine with Different brands of HP elite 8200/8100 , infact the elite 8200 also uses the same NIC card
    Find below the smsts.log file
    Main error in the log file is
    No physical network adapters found    OSDNetSettings    2/12/2014 1:02:38 AM    2064 (0x0810)
    Found network adapter "Intel(R) 82579LM Gigabit Network Connection" with IP Address 169.254.181.151.    TSMBootstrap    2/12/2014 1:05:41 PM    1984 (0x07C0)
    Xtract from LOG
    SMSTSRebootDelay=60    Reboot    2/12/2014 1:01:56 AM    3496 (0x0DA8)
    SMSTSRebootMessage=A new Microsoft Windows operating system is being installed. The computer must restart to continue.    Reboot    2/12/2014 1:01:56 AM    3496 (0x0DA8)
    SMSTSRebootRequested=WinPE    Reboot    2/12/2014 1:01:56 AM    3496 (0x0DA8)
    Process completed with exit code 0    TSManager    2/12/2014 1:01:56 AM    1876 (0x0754)
    !--------------------------------------------------------------------------------------------!    TSManager    2/12/2014 1:01:56 AM    1876 (0x0754)
    Successfully completed the action (Restart to Windows PE) with the exit win32 code 0    TSManager    2/12/2014 1:01:56 AM    1876 (0x0754)
    Set authenticator in transport    TSManager    2/12/2014 1:01:56 AM    1876 (0x0754)
    Set a global environment variable _SMSTSLastActionRetCode=0    TSManager    2/12/2014 1:01:57 AM    1876 (0x0754)
    Set a global environment variable _SMSTSLastActionSucceeded=true    TSManager    2/12/2014 1:01:57 AM    1876 (0x0754)
    Clear local default environment    TSManager    2/12/2014 1:01:57 AM    1876 (0x0754)
    Updated security on object E:\_SMSTaskSequence.    TSManager    2/12/2014 1:01:57 AM    1876 (0x0754)
    Set a global environment variable _SMSTSNextInstructionPointer=59    TSManager    2/12/2014 1:01:57 AM    1876 (0x0754)
    Set a TS execution environment variable _SMSTSNextInstructionPointer=59    TSManager    2/12/2014 1:01:57 AM    1876 (0x0754)
    Set a global environment variable _SMSTSInstructionStackString=0 41 57    TSManager    2/12/2014 1:01:57 AM    1876 (0x0754)
    Set a TS execution environment variable _SMSTSInstructionStackString=0 41 57    TSManager    2/12/2014 1:01:57 AM    1876 (0x0754)
    Save the current environment block    TSManager    2/12/2014 1:01:57 AM    1876 (0x0754)
    Executing command line: "bcdedit.exe"    TSManager    2/12/2014 1:01:57 AM    1876 (0x0754)
    CreateProcess failed. Code(0x80070002)    TSManager    2/12/2014 1:01:57 AM    1876 (0x0754)
    Command line execution failed (80070002)    TSManager    2/12/2014 1:01:57 AM    1876 (0x0754)
    Staging boot image UNB0003A    TSManager    2/12/2014 1:01:57 AM    1876 (0x0754)
    ResolveSource flags: 0x00000000    TSManager    2/12/2014 1:01:59 AM    1876 (0x0754)
    SMSTSPersistContent: . The content for package UNB0003A will be persisted    TSManager    2/12/2014 1:01:59 AM    1876 (0x0754)
    Set authenticator in transport    TSManager    2/12/2014 1:01:59 AM    1876 (0x0754)
    WinHttp credentials set    TSManager    2/12/2014 1:01:59 AM    1876 (0x0754)
    List of files to be downloaded    TSManager    2/12/2014 1:01:59 AM    1876 (0x0754)
    Downloaded file from http://unb-ho-sccmdb.exch1.mas.unb.com:80/SMS_DP_SMSPKG$/UNB0003A/sccm?/WinPE.UNB0003A.wim to E:\_SMSTaskSequence\Packages\UNB0003A\WinPE.UNB0003A.wim     TSManager    2/12/2014 1:02:22 AM    1876
    (0x0754)
    VerifyContentHash: Hash algorithm is 32780    TSManager    2/12/2014 1:02:22 AM    1876 (0x0754)
    Found boot image E:\_SMSTaskSequence\Packages\UNB0003A\WinPE.UNB0003A.wim    TSManager    2/12/2014 1:02:25 AM    1876 (0x0754)
    Copying boot image locally...    TSManager    2/12/2014 1:02:25 AM    1876 (0x0754)
    Failed to find ADK installation root registry key    TSManager    2/12/2014 1:02:32 AM    1876 (0x0754)
    Opening image file E:\_SMSTaskSequence\WinPE\sources\boot.wim    TSManager    2/12/2014 1:02:32 AM    1876 (0x0754)
    Applying image 1 to volume E:\_SMSTaskSequence\WinPE    TSManager    2/12/2014 1:02:32 AM    1876 (0x0754)
    Closing image file E:\_SMSTaskSequence\WinPE\sources\boot.wim    TSManager    2/12/2014 1:02:35 AM    1876 (0x0754)
    Capturing WinPE bootstrap settings    TSManager    2/12/2014 1:02:35 AM    1876 (0x0754)
    Environment scope successfully created: Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78}    TSManager    2/12/2014 1:02:35 AM    1876 (0x0754)
    Executing command line: "osdnetsettings.exe" capture adapters:true scope:Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78}    TSManager    2/12/2014 1:02:35 AM    1876 (0x0754)
    ==============================[ OSDNetSettings.exe ]===========================    OSDNetSettings    2/12/2014 1:02:36 AM    2064 (0x0810)
    Command line: "osdnetsettings.exe" capture adapters:true scope:Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78}    OSDNetSettings    2/12/2014 1:02:36 AM    2064 (0x0810)
    No adapters found with non-empty DNSDomainSuffixSearchOrder    OSDNetSettings    2/12/2014 1:02:36 AM    2064 (0x0810)
    Adapter "ROOT\SYMC_TEEFER2MP\0000" not found    OSDNetSettings    2/12/2014 1:02:38 AM    2064 (0x0810)
    No physical network adapters found    OSDNetSettings    2/12/2014 1:02:38 AM    2064 (0x0810)
    OSDNetSettings finished: 0x00000000    OSDNetSettings    2/12/2014 1:02:38 AM    2064 (0x0810)
    Process completed with exit code 0    TSManager    2/12/2014 1:02:38 AM    1876 (0x0754)
    Installing boot image to hard drive    TSManager    2/12/2014 1:02:38 AM    1876 (0x0754)
    Backing up existing boot system before trying to set up new boot system    TSManager    2/12/2014 1:02:38 AM    1876 (0x0754)
    BootLoader::backup: C:\, E:\_SMSTaskSequence\backup    TSManager    2/12/2014 1:02:39 AM    1876 (0x0754)
    BootLoader::restore: E:\_SMSTaskSequence\WinPE, C:\    TSManager    2/12/2014 1:02:43 AM    1876 (0x0754)
    Saving bcd store to E:\_SMSTaskSequence\WinPE\boot\BCD    TSManager    2/12/2014 1:02:43 AM    1876 (0x0754)
    Executing command line: "E:\_SMSTaskSequence\WinPE\SMS\bin\i386\bootsect.exe" /NT60 SYS /MBR    TSManager    2/12/2014 1:02:45 AM    1876 (0x0754)
    Process completed with exit code 0    TSManager    2/12/2014 1:02:46 AM    1876 (0x0754)
    Updated security on object E:\_SMSTaskSequence.    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Set a global environment variable _SMSTSNextInstructionPointer=59    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Set a TS execution environment variable _SMSTSNextInstructionPointer=59    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Set a global environment variable _SMSTSInstructionStackString=0 41 57    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Set a TS execution environment variable _SMSTSInstructionStackString=0 41 57    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Save the current environment block    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Updated security on object C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca.    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Updated security on object D:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca.    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Updated security on object E:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca.    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Updated security on object E:\_SMSTaskSequence.    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Set a global environment variable _SMSTSNextInstructionPointer=59    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Set a TS execution environment variable _SMSTSNextInstructionPointer=59    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Set a global environment variable _SMSTSInstructionStackString=0 41 57    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Set a TS execution environment variable _SMSTSInstructionStackString=0 41 57    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Save the current environment block    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    Expand a string: %_SMSTSMDataPath%\Logs    TSManager    2/12/2014 1:02:47 AM    1876 (0x0754)
    <![LOG[LOGGING: Finalize process ID set to 780]LOG]!><time="01:04:01.537+480" date="02-12-2014" component="TSBootShell" context="" type="1" thread="784" file="tslogging.cpp:1495">  
          1/1/1601 12:00:00 AM    1995266923 (0x76ED5B6B)
    ==============================[ TSBootShell.exe ]==============================    TSBootShell    2/12/2014 1:04:01 AM    784 (0x0310)
    Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL'    TSBootShell    2/12/2014 1:04:01 AM    784 (0x0310)
    Debug shell is enabled    TSBootShell    2/12/2014 1:04:01 AM    784 (0x0310)
    Waiting for PNP initialization...    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    RAM Disk Boot Path: MULTI(0)DISK(0)RDISK(0)PARTITION(3)\_SMSTASKSEQUENCE\WINPE\SOURCES\BOOT.WIM    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    WinPE boot path: E:\_SMSTASKSEQUENCE\WINPE\SOURCES\BOOT.WIM    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    Booted from fixed disk    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    Found config path E:\_SMSTaskSequence    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515)    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337)    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,549)    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515)    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337)    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,549)    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515)    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337)    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,430)    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    Can not find DeploymentType in file TsmBootstrap.ini or the file doesn't exist. This is not running on Windows To Go.    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515)    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337)    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,430)    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    Restoring boot system from E:\_SMSTaskSequence\backup    TSBootShell    2/12/2014 1:04:01 AM    796 (0x031C)
    Successfully loaded the BCD boot system    TSBootShell    2/12/2014 1:04:05 AM    796 (0x031C)
    Successfully loaded an exported NTLDR boot system    TSBootShell    2/12/2014 1:04:05 AM    796 (0x031C)
    BootLoader::restore: E:\_SMSTaskSequence\backup, C:\    TSBootShell    2/12/2014 1:04:05 AM    796 (0x031C)
    Successfully merged logs from cache.    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515)    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337)    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,430)    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    Loading bootstrap settings from E:\_SMSTaskSequence\WinPE    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    Loading saved WinPE settings    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00450037004500350042004200360039002D0036003100390038002D0034003500350035002D0042003500430041002D003600430034003600410032004200350045004200370038007D00'    TSBootShell  
     2/12/2014 1:04:06 AM    796 (0x031C)
    Environment scope successfully created: Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78}    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    Configuring WinPE bootstrap settings    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    Creating WinPE answer file    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    Setting hive location to "X:\windows\system32"    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    Getting namespace "Microsoft-Windows-Setup" for architecture "x86"    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    Configuring global network settings    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    Join type:     TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    DNS domain: exch1.mas.unb.com    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    DNS domain search order:     TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    IP filter sec enabled: false    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    No adapters found in environment.  Performing global configuration only.    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    Writing configuration information to E:\_SMSTaskSequence\WinPE\WinPeUnattend.xml    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    Successfully saved configuration information to E:\_SMSTaskSequence\WinPE\WinPeUnattend.xml    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    Executing command line: wpeinit.exe -winpe    TSBootShell    2/12/2014 1:04:06 AM    796 (0x031C)
    The command completed successfully.    TSBootShell    2/12/2014 1:05:40 AM    796 (0x031C)
    Starting DNS client service.    TSBootShell    2/12/2014 1:05:40 AM    796 (0x031C)
    Finalizing network settings    TSBootShell    2/12/2014 1:05:40 AM    796 (0x031C)
    No adapters found in environment.  Performing global finalization only.    TSBootShell    2/12/2014 1:05:40 AM    796 (0x031C)
    Finalizing global network settings    TSBootShell    2/12/2014 1:05:40 AM    796 (0x031C)
    DNS domain: exch1.mas.unb.com    TSBootShell    2/12/2014 1:05:40 AM    796 (0x031C)
    DNS domain search order:     TSBootShell    2/12/2014 1:05:40 AM    796 (0x031C)
    DNS for WINS enabled: false    TSBootShell    2/12/2014 1:05:40 AM    796 (0x031C)
    LMHosts file enabled: true    TSBootShell    2/12/2014 1:05:40 AM    796 (0x031C)
    Host lookup file:     TSBootShell    2/12/2014 1:05:40 AM    796 (0x031C)
    WINS scope ID:     TSBootShell    2/12/2014 1:05:40 AM    796 (0x031C)
    Executing command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:E:\_SMSTaskSequence    TSBootShell    2/12/2014 1:05:40 AM    796 (0x031C)
    The command completed successfully.    TSBootShell    2/12/2014 1:05:40 AM    796 (0x031C)
    ==============================[ TSMBootStrap.exe ]==============================    TSMBootstrap    2/12/2014 1:05:40 AM    1984 (0x07C0)
    Command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:E:\_SMSTaskSequence    TSMBootstrap    2/12/2014 1:05:40 AM    1984 (0x07C0)
    Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL'    TSMBootstrap    2/12/2014 1:05:40 AM    1984 (0x07C0)
    Succeeded loading resource DLL 'X:\sms\bin\i386\TSRESNLC.DLL'    TSMBootstrap    2/12/2014 1:05:40 AM    1984 (0x07C0)
    Adding SMS bin folder "X:\sms\bin\i386" to the system environment PATH    TSMBootstrap    2/12/2014 1:05:40 AM    1984 (0x07C0)
    Failed to open PXE registry key. Not a PXE boot.    TSMBootstrap    2/12/2014 1:05:40 AM    1984 (0x07C0)
    Resuming Task Sequence in WinPE    TSMBootstrap    2/12/2014 1:05:40 AM    1984 (0x07C0)
    Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00350031004100300031003600420036002D0046003000440045002D0034003700350032002D0042003900370043002D003500340045003600460033003800360041003900310032007D00'    TSMBootstrap  
     2/12/2014 1:05:40 AM    1984 (0x07C0)
    Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}    TSMBootstrap    2/12/2014 1:05:40 AM    1984 (0x07C0)
    Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00420041003300410033003900300030002D0043004100360044002D0034006100630031002D0038004300320038002D003500300037003300410046004300320032004200300033007D00'    TSMBootstrap  
     2/12/2014 1:05:40 AM    1984 (0x07C0)
    Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}    TSMBootstrap    2/12/2014 1:05:40 AM    1984 (0x07C0)
    Loading the Task Sequencing Environment from "E:\_SMSTaskSequence\TSEnv.dat".    TSMBootstrap    2/12/2014 1:05:41 AM    1984 (0x07C0)
    Updating the local data path in the Task Sequencing Environment.    TSMBootstrap    2/12/2014 1:05:41 AM    1984 (0x07C0)
    Setting LogMaxSize to 1000000    TSMBootstrap    2/12/2014 1:05:41 AM    1984 (0x07C0)
    Setting LogMaxHistory to 1    TSMBootstrap    2/12/2014 1:05:41 AM    1984 (0x07C0)
    Setting LogLevel to 0    TSMBootstrap    2/12/2014 1:05:41 AM    1984 (0x07C0)
    Setting LogEnabled to 1    TSMBootstrap    2/12/2014 1:05:41 AM    1984 (0x07C0)
    Setting LogDebug to 1    TSMBootstrap    2/12/2014 1:05:41 AM    1984 (0x07C0)
    Command line for extension .exe is "%1" %*    TSMBootstrap    2/12/2014 1:05:41 AM    1984 (0x07C0)
    Set command line: "X:\sms\bin\i386\TsProgressUI.exe" /Register:WinPE    TSMBootstrap    2/12/2014 1:05:41 AM    1984 (0x07C0)
    Executing command line: "X:\sms\bin\i386\TsProgressUI.exe" /Register:WinPE    TSMBootstrap    2/12/2014 1:05:41 AM    1984 (0x07C0)
    ==========[ TsProgressUI started in process 2004 ]==========    TsProgressUI    2/12/2014 1:05:41 AM    2008 (0x07D8)
    Command line: "X:\sms\bin\i386\TsProgressUI.exe" /Register:W
    In dire need of help,
    I have already gone through the below articles on the NET
    http://social.technet.microsoft.com/Forums/systemcenter/en-US/0fe5cded-51cf-487a-97e3-837fb3426a3e/install-software-updates-in-osd-reboots-leaves-clients-in-provisioning-mode?forum=configmgrosd
    http://social.technet.microsoft.com/Forums/systemcenter/en-US/c590e486-d3ca-423f-8953-e596160f3567/updates-hang-during-osd-kb2509007-not-working-for-me?forum=configmgrosd
    Awating response,
    Hasan Reza

    Well Finally I sorted my issue ,
    Just want to share the solution, may be it would be helpful to some one else and save some times
    The problem was that the Xp images has lot of hidden NIC installed , this would not allow the system to work with the correct NIC card and Ip address (System -> View Hidden Devices) , what I did 2 things
    1) Copied the OSD Script folder from the SCCM Server to the Client pc and ran that ztigather.wsf and captured the output , it was evident that it showed capturing multiple adapters , (There are some blogs that pointed out that OSD can capture only one nic
    due to the only one Adapter0 section being defined in the ZTIgather.xml file,)
    2) I open the registry at the xp pc navigated to HKLM-> System ->Current Control Set-> Services-> TCPIP -> Parameters-> Interfaces ->
    Expect for the NIC card that had the Ip address assigned I deleted all other nic card's guid,
    As then post running deleting the old scanstate (USMTUTIL /rd c:\statestore) , reran the task and VOILA..
    All worked fine , below are the two post I followed , though notvery relevant but they were helpful and help me reached the conclusion.
    Thanks,
    Hasan Reza.
    http://systemscenter.ru/mdt2012.en/ztigatherwsf.htm
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/8acb7cd1-7028-4ffe-86c9-eb43041cf8b3/how-do-i-get-rid-of-second-169254xx-ipv4-address-on-windows-server-2008-sp2-x86?forum=winservergen

  • New SCCM 2012 client machines still getting SCCM 2012 SP1 client not the new SCCM 2012 SP1 CU3 client

    Hi,
    I've successfully (as far as I can tell) deployed SCCM 2012 SP1 CU3 and all my existing clients are showing a client version of 5.00.7804.1400.  But when I setup a new client system recently I noticed that the client version was showing 5.00.7804.1000,
    and not 5.00.7804.1400. 
    For new client systems, do I need to redeploy the packages that were created for SCCM 2012 SP1 CU3 so that the new systems get the new SCCM 2012 SP1 CU3 client? 
    Thanks,
    Nick

    Hi,
    Here's some good information to look over:
    http://sccmfaq.wordpress.com/2013/09/24/sccm-2012-include-cu-in-osd/
    I haven't followed these instructions myself, since I haven't really had any good reason to include CUs during the initial installation process. I use this method instead and I've never run into any problems:
    http://www.ronnipedersen.com/2013/06/installing-sccm-2012-sp1-cu2-quick-start-guide/
    Don't retire TechNet! -
    (Don't give up yet - 12,575+ strong and growing)

  • SCCM Client R2 CU3 in OSD

    Our base image was created using SCCM build and capture. I created the base image using sccm client 2012 SP1 ( 5.00.7804.1300). Now, we recently upgraded to SCCM 2012 R2 CU3 and we would like to update our deployment production task sequence with
    the config manager client package so that the machine will pick up the new client version after the build. Upon testing, I always encounter an incomplete build. After the installation of the sccm client, the ts stops and will show the login window. The ccmsetup.log
    indicates a successful installation of the client as it  exits with a return code of 0. I have a gut feeling that the sccm client was upgraded and was not able to save the task sequence which caused the task sequence to stop. Any idea on why the build
    stops after the installation of the client and how to resolve the issue?

    You can follow this post to configure CU3 in OSD.
    http://sccmfaq.wordpress.com/2013/09/24/sccm-2012-include-cu-in-osd/
    Nick Pilon | Blog : System Center Dudes

Maybe you are looking for

  • Adobe Muse APTEE Licensing NOT WORKING!!

    Hi, I am an IT Professional working for a major University in Missouri. We have an Apple computer lab of 26 20" iMacs, all running Adobe Creative Cloud with an Enterprise license. This license includes Adobe Muse (with its own serial number). We use

  • Wrt160nv2 wireless security help

    Hello I'm new to this forum and had some questions regarding the wireless security settings on this router (WRT160Nv2) I have the security mode set to: WPA2 and what I need to know is which Encryption is better AES or the other setting which is TKIS

  • Can't import from SD Card

    My i-Mac, running OSX 10.5.6 is no longer able to import photo files from my SD cards, into Aperture 2.1.2. I have tried to import both using a USB connection between camera and computer, and by using a USM card reader. Interestingly, there is no pro

  • IPad programming - listing class/object variables

    Hey there, Im stuck with a little thing, I think i'm confused with value or object coding, anyways heres the deal: I've made and declared an object which consists of some information (ID, name, etc) and I want to parse XML results into this object. T

  • How do I fix DVD recorder error 69889 on mac

    What does error 69889 mean on DVD Recorder on a Mac