Deploy Task Sequence to Unknown Computers fails

Hi everyone,
I am experiencing some problems regarding running a task sequence for unknown computers.
When I boot certain computers from PXE, I will receive an abortpxe.com
I have verified the following in my environment:
No duplicate "SMBIOS GUID" in my  environment
No duplicate "MAC-addresses" in my enviroment
x64 & x86 unkown computer is located in collection "Unknown Computers"
Correct TS (with correct boot image) is targetted for this collection
In SMSPXE.log I can find the following:
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
 SMSPXE 7/07/2014 12:37:51 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: no advertisements found SMSPXE 7/07/2014 12:37:51 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: No boot action. Rejected. SMSPXE 7/07/2014 12:37:51 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: Not serviced. SMSPXE 7/07/2014 12:37:51 2052 (0x0804)
Getting boot action for unknown machine: item key: 2046820*** SMSPXE 7/07/2014 12:37:53 2052 (0x0804)
Item key "2046820***" is the corresponding "x64 Uknown Computer". Sometimes this will be "x86 Unkown Computer" for the same device.
When looking at previous entries in the logfile, this computer was once unkown and wa able to receive a PXE:
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: device is not in the database. SMSPXE 4/07/2014 11:26:20 2052 (0x0804)
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 4/07/2014 11:26:20 2052 (0x0804)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName="" ServerRemoteName=""><Machine><ClientID>e5a90706-d840-4261-93ca-************</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="D30201C3" OfferIDTime="11/23/2012 3:14:00 PM" PkgID="D3000091" PackageVersion="" PackagePath="http://*webserver*/SMS_DP_SMSPKG$/D3000019"
BootImageID="D3000019" Mandatory="1"/></ClientIDReply>
 SMSPXE 4/07/2014 11:26:20 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: using advertisement D30201C3 SMSPXE 4/07/2014 11:26:20 2052 (0x0804)
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 4/07/2014 11:26:22 2052 (0x0804)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName="" ServerRemoteName=""><Machine><ClientID>e5a90706-d840-4261-93ca-************</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="D30201C3" OfferIDTime="11/23/2012 3:14:00 PM" PkgID="D3000091" PackageVersion="" PackagePath="http://*webserver*/SMS_DP_SMSPKG$/D3000019"
BootImageID="D3000019" Mandatory="1"/></ClientIDReply>
 SMSPXE 4/07/2014 11:26:22 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: using advertisement D30201C3 SMSPXE 4/07/2014 11:26:22 2052 (0x0804)
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 4/07/2014 11:26:24 2052 (0x0804)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName="" ServerRemoteName=""><Machine><ClientID>e5a90706-d840-4261-93ca-************</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="D30201C3" OfferIDTime="11/23/2012 3:14:00 PM" PkgID="D3000091" PackageVersion="" PackagePath="http://*webserver*/SMS_DP_SMSPKG$/D3000019"
BootImageID="D3000019" Mandatory="1"/></ClientIDReply>
 SMSPXE 4/07/2014 11:26:24 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: using advertisement D30201C3 SMSPXE 4/07/2014 11:26:24 2052 (0x0804)
Getting boot action for unknown machine: item key: 2046820*** SMSPXE 4/07/2014 11:26:28 2052 (0x0804)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820***" ServerName="" ServerRemoteName=""><Machine><ClientID>96de0ff0-0bc2-4f21-ac90-***********</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="D30201C3" OfferIDTime="11/23/2012 3:14:00 PM" PkgID="D3000091" PackageVersion="" PackagePath="http://*webserver*/SMS_DP_SMSPKG$/D3000019"
BootImageID="D3000019" Mandatory="1"/></ClientIDReply>
 SMSPXE 4/07/2014 11:26:28 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: using advertisement D30201C3 SMSPXE 4/07/2014 11:26:28 2052 (0x0804)
Looking for bootImage D3000019 SMSPXE 4/07/2014 11:26:28 2052 (0x0804)
What could be the issue? Is it possible that there is still some record referring to this PC and how can I trace/delete it?
Would restarting the WDS server solve this issue?
Thanks in advance!

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
 SMSPXE 7/07/2014 12:37:35 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: device is not in the database. SMSPXE 7/07/2014 12:37:35 2052 (0x0804)
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 7/07/2014 12:37:35 2052 (0x0804)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID=""
LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
 SMSPXE 7/07/2014 12:37:35 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: no advertisements found SMSPXE 7/07/2014 12:37:35 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: No boot action. Rejected. SMSPXE 7/07/2014 12:37:35 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: Not serviced. SMSPXE 7/07/2014 12:37:35 2052 (0x0804)
Getting boot action for unknown machine: item key: 2046820353 SMSPXE 7/07/2014 12:37:37 2052 (0x0804)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820353" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID=""
LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
 SMSPXE 7/07/2014 12:37:37 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: no advertisements found SMSPXE 7/07/2014 12:37:37 2052 (0x0804)
Getting boot action for unknown machine: item key: 2046820352 SMSPXE 7/07/2014 12:37:51 2052 (0x0804)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID=""
LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
 SMSPXE 7/07/2014 12:37:51 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: no advertisements found SMSPXE 7/07/2014 12:37:51 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: No boot action. Rejected. SMSPXE 7/07/2014 12:37:51 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: Not serviced. SMSPXE 7/07/2014 12:37:51 2052 (0x0804)
Getting boot action for unknown machine: item key: 2046820353 SMSPXE 7/07/2014 12:37:53 2052 (0x0804)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820353" ServerName="" ServerRemoteName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID=""
LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
 SMSPXE 7/07/2014 12:37:53 2052 (0x0804)
3C:97:0E:**:**:**, 5589C501-5273-11CB-8236-************: no advertisements found SMSPXE 7/07/2014 12:37:53 2052 (0x0804)
These are all of the lines of that PXE boot (previous and next values have a timestamp difference of 3 minutes).
Thanks for looking into this, Torsten!

Similar Messages

  • Failed to Run Task Sequence on unknown computers

    Hey everyone i need some major help here.  I am 99.9% sure that we dont have something configured properly but here goes.  I have a the following:
    A task sequence that is enabled to deploy a image to all platforms (Console, Boot media, PXE)
    I have Boot Media created that has "Enable unknown computer support"
    I have a workstation that has NEVER been on our network (Bare Metal
    Now here is the problem on that workstation, I use the boot media, and get a "Failed to run Task Sequence" There are no Task Sequences available for this computer"
    BUT, if it has/had the SCCM agent on it.. It works fine..
    Ideas? Starting points?

    A task sequence that is enabled to deploy a image to all platforms (Console, Boot media, PXE)
    I have Boot Media created that has "Enable unknown computer support"
    Step #2 alone is not sufficient. There has to be a deployment for the task sequence to the 'All Unknown Computers' collection too. You did not mention this ...
    Torsten Meringer | http://www.mssccmfaq.de

  • Move SCCM client to another OU at the end of the deployment task sequence

    Hi
    I'm looking to modify my SCCM task sequence so that it can put a computer in the correct OU at the end of provisioning. I've come across a couple of scripts to do this, but neither are working at the moment
    1. A few lines of PowerShell here (http://stackoverflow.com/questions/22966037/move-computer-to-new-ou-in-sccm-2012-task-sequence-with-powershell)
    C:\windows\system32\WindowsPowerShell\v1.0\powershell.exe -command iex \" `$TargetOU=\"\"OU=TargetOUName,DC=ConglomiCo,DC=com\"\"; `$SysInfo=New-Object -ComObject \"\"ADSystemInfo\"\";`$ComputerDN=`$SysInfo.GetType().InvokeMember(\"\"ComputerName\"\",\"\"GetProperty\"\",`$Null,`$SysInfo,`$Null);`$Computer=[ADSI]\"\"LDAP://`$ComputerDN\"\";`$OU=[ADSI]\"\"LDAP://`$TargetOU\"\";`$Computer.psbase.MoveTo(`$OU);"
    With the above command, I keep on receiving a syntax error and/or invalid OU error. My specified OU is valid and I'm using an account with sufficient permissions to move computers in AD. I also find the syntax with the "\" difficult to follow.
    2. The second script I've tried here, doesn't seem to work either:
    http://blog.coretech.dk/jgs/vbscript-move-computer-object-to-another-ou-via-command-line-parameter/
    On Error Resume Next
    'Get MachineObjectOU Value
    Set wshNetwork = CreateObject("WScript.Network")
    Set oFso = CreateObject("Scripting.FileSystemObject")
    Set objSysInfo = CreateObject( "ADSystemInfo" )
    Set ArgObj = WScript.Arguments
    'Use first argument as target OU
    strMachineObjectOU = strLDAPofOU
    strComputerDN = objSysInfo.ComputerName
    'msgbox(strMachineObjectOU)
    nComma = InStr(strComputerDN,",")
    strCurrentOU = Mid(strComputerDN,nComma+1)
    strComputerName = Left(strComputerDN,nComma - 1)
    'msgbox(strCurrentOU)
    'If current ou is different than target OU. Move object
    If UCase(strCurrentOU) <> UCase(strMachineObjectOU) Then
        Set objNewOU = GetObject("LDAP://" & strMachineObjectOU)
        Set objMoveComputer = objNewOU.MoveHere("LDAP://" & strComputerDN, strComputerName)
        'msgbox("LDAP://" & strComputerDN & strComputerName)
    End If
    If I put this script into a task sequence, how does SCCM know which computer to move in AD? I'm assuming by using variable strComputerDN = objSysInfo.ComputerName
    Thanks in advance
    IT Support/Everything

    If I put this script into a task sequence, how does SCCM know which computer to move in AD? I'm assuming by using variable strComputerDN = objSysInfo.ComputerName
    Correct. Jörgen did a post about the usage of that script a long time ago that should help you, see:
    http://ccmexec.com/2010/12/move-computer-to-the-correct-ou-during-deployment/
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • Task Sequence Auto Apply Drivers fails - CMPDBConnection::ExecuteSQL(): ICommandText::Execute() failed with 0x80040E14

    SCCM 2007 SP2 R2--
    I have copied my working task sequences for Operation System Deployment (Windows 2008 R2) because I am introducing new hardware into our environment.  After adding new drivers to the Boot image and to the Drivers catalog, I am now experiencing an issues
    when running the TS.
    In my SMSTS.log, I see these errors:
    ***************    SMSTS.LOG   ********************************
    Processing driver match result.    OSDDriverClient    7/25/2012 9:48:01 AM    1296 (0x0510)
    XML parsing error at line 1 char 1: Invalid at the top level of the document.
    Request failed (Code 0x80040e14)    OSDDriverClient    7/25/2012 9:48:01 AM    1296 (0x0510)
    bSuccess == ((VARIANT_BOOL)-1), HRESULT=80004005 (e:\nts_sms_fre\SMS\common\inc\ccmxml.h,1116)    OSDDriverClient    7/25/2012 9:48:01 AM    1296 (0x0510)
    spXMLDoc.loadFromXML(pszResponse), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\onlinedrivercatalog.cpp,536)    OSDDriverClient    7/25/2012 9:48:01 AM    1296 (0x0510)
    Server response: Request failed (Code 0x80040e14)    OSDDriverClient    7/25/2012 9:48:01 AM    1296 (0x0510)
    processDriverResponse( sResponseBody, fpCallbackProc, pvCallbackData, matchResultMap ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\onlinedrivercatalog.cpp,457)    OSDDriverClient    7/25/2012 9:48:01
    AM    1296 (0x0510)
    Failed to process driver catalog response. Code 0x80004005    OSDDriverClient    7/25/2012 9:48:01 AM    1296 (0x0510)
    pDriverCatalog->match( deviceList, m_fpCallbackProc, m_pvCallbackData, matchResultMap ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\driverinstaller.cpp,854)    OSDDriverClient    7/25/2012 9:48:01
    AM    1296 (0x0510)
    pDriverInstaller->AutoInstallDrivers( pDriverCatalog, bBestMatch ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,286)    OSDDriverClient    7/25/2012 9:48:01 AM    1296
    (0x0510)
    Failed to auto provision driver. Code 0x80004005    OSDDriverClient    7/25/2012 9:48:01 AM    1296 (0x0510)
    ProcessAutoProvision( pDriverInstaller, bBestMatch ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,415)    OSDDriverClient    7/25/2012 9:48:01 AM    1296 (0x0510)
    Failed to auto provision drivers.  Code 0x80004005    OSDDriverClient    7/25/2012 9:48:01 AM    1296 (0x0510)
    Exiting with return code 0x80004005    OSDDriverClient    7/25/2012 9:48:01 AM    1296 (0x0510)
    Process completed with exit code 2147500037    TSManager    7/25/2012 9:48:01 AM    1632 (0x0660)
    !--------------------------------------------------------------------------------------------!    TSManager    7/25/2012 9:48:01 AM    1632 (0x0660)
    Failed to run the action: Post Install - Auto Apply Drivers.
    Unspecified error (Error: 80004005; Source: Windows)    TSManager    7/25/2012 9:48:01 AM    1632 (0x0660)
    I have also checked my NLB MP's and have found this error in the MP_DriverMgr.log
    ********************* MP_DriverMgr.log  *******************************************
    CMPDBConnection::ExecuteSQL(): ICommandText::Execute() failed with 0x80040E14    MP_DriverManager    7/24/2012 12:47:50 PM    7436 (0x1D0C)
    =======================================    MP_DriverManager    7/24/2012 12:47:50 PM    7436 (0x1D0C)
    MPDB ERROR - CONNECTION PARAMETERS
    SQL Server Name     : SERVERNAME
    SQL Database Name   : SMS_AM0_RPL
    Integrated Auth     : True
    MPDB ERROR - EXTENDED INFORMATION
    MPDB Method         : ExecuteSP()
    MPDB Method HRESULT : 0x80040E14
    Error Description   : Syntax error or access violation
    OLEDB IID           : {0C733A63-2A1C-11CE-ADE5-00AA0044773D}
    ProgID              : Microsoft OLE DB Provider for SQL Server
    MPDB ERROR - INFORMATION FROM DRIVER
    null    MP_DriverManager    7/24/2012 12:47:50 PM    7436 (0x1D0C)
    =======================================
        MP_DriverManager    7/24/2012 12:47:50 PM    7436 (0x1D0C)
    Failed to execute strored procedure: MP_MatchDrivers, hr=0x80040e14    MP_DriverManager    7/24/2012 12:47:50 PM    7436 (0x1D0C)
    Failed to execute MatchDrivers task, hr=0x80040e14    MP_DriverManager    7/24/2012 12:47:50 PM    7436 (0x1D0C)
    Response message sent to the client    MP_DriverManager    7/24/2012 12:47:50 PM    7436 (0x1D0C)
    Failed to execute task, hr=0x80040e14    MP_DriverManager    7/24/2012 12:47:50 PM    7436 (0x1D0C)
    Executing Driver Request - Match    MP_DriverManager    7/25/2012 9:48:01 AM    3740 (0x0E9C)
    XML Schema support is not installed, XML validation will be skipped.    MP_DriverManager    7/25/2012 9:48:01 AM    3740 (0x0E9C)
    CMPDBConnection::ExecuteSQL(): ICommandText::Execute() failed with 0x80040E14    MP_DriverManager    7/25/2012 9:48:01 AM    3740 (0x0E9C)
    =======================================    MP_DriverManager    7/25/2012 9:48:01 AM    3740 (0x0E9C)
    MPDB ERROR - CONNECTION PARAMETERS
    SQL Server Name     : SERVERNAME
    SQL Database Name   : SMS_AM0_RPL
    Integrated Auth     : True
    MPDB ERROR - EXTENDED INFORMATION
    MPDB Method         : ExecuteSP()
    MPDB Method HRESULT : 0x80040E14
    Error Description   : Syntax error or access violation
    OLEDB IID           : {0C733A63-2A1C-11CE-ADE5-00AA0044773D}
    ProgID              : Microsoft OLE DB Provider for SQL Server
    MPDB ERROR - INFORMATION FROM DRIVER
    null    MP_DriverManager    7/25/2012 9:48:01 AM    3740 (0x0E9C)
    =======================================
        MP_DriverManager    7/25/2012 9:48:01 AM    3740 (0x0E9C)
    Failed to execute strored procedure: MP_MatchDrivers, hr=0x80040e14    MP_DriverManager    7/25/2012 9:48:01 AM    3740 (0x0E9C)
    Failed to execute MatchDrivers task, hr=0x80040e14    MP_DriverManager    7/25/2012 9:48:01 AM    3740 (0x0E9C)
    Response message sent to the client    MP_DriverManager    7/25/2012 9:48:01 AM    3740 (0x0E9C)
    Failed to execute task, hr=0x80040e14    MP_DriverManager    7/25/2012 9:48:01 AM    3740 (0x0E9C)
    Any pointer where to look to troubleshoot this issue more? 

    Hi All Did  you guyz find a resolution for this ? I am having same error while Installing Power edge R620 
    Below shows SMSTS.log
    Failed to process driver catalog response. Code 0x80004005
    OSDDriverClient 10/11/2012 12:31:21 PM
    1084 (0x043C)
    pDriverCatalog->match( deviceList, m_fpCallbackProc, m_pvCallbackData, matchResultMap ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\driverinstaller.cpp,854)
    OSDDriverClient 10/11/2012 12:31:21 PM
    1084 (0x043C)
    pDriverInstaller->AutoInstallDrivers( pDriverCatalog, bBestMatch ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,286)
    OSDDriverClient 10/11/2012 12:31:21 PM
    1084 (0x043C)
    Failed to auto provision driver. Code 0x80004005
    OSDDriverClient 10/11/2012 12:31:21 PM
    1084 (0x043C)
    ProcessAutoProvision( pDriverInstaller, bBestMatch ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,415)
    OSDDriverClient 10/11/2012 12:31:21 PM
    1084 (0x043C)
    Failed to auto provision drivers.  Code 0x80004005
    OSDDriverClient 10/11/2012 12:31:21 PM
    1084 (0x043C)
    Below is the MP Driver log
    CMPDBConnection::ExecuteSQL(): ICommandText::Execute() failed with 0x80040E14
    MP_DriverManager 10/11/2012 11:12:59 AM
    11228 (0x2BDC)
    ======================================= MP_DriverManager
    10/11/2012 11:12:59 AM 11228 (0x2BDC)
    MPDB ERROR - CONNECTION PARAMETERS
    SQL Server Name     : sqlserver
    SQL Database Name   : SMS
    Integrated Auth     : True
    MPDB ERROR - EXTENDED INFORMATION
    MPDB Method         : ExecuteSP()
    MPDB Method HRESULT : 0x80040E14
    Error Description   : Syntax error or access violation
    OLEDB IID           : {0C733A63-2A1C-11CE-ADE5-00AA0044773D}
    ProgID              : Microsoft OLE DB Provider for SQL Server
    MPDB ERROR - INFORMATION FROM DRIVER
    null MP_DriverManager
    10/11/2012 11:12:59 AM 11228 (0x2BDC)
    =======================================
    MP_DriverManager
    10/11/2012 11:12:59 AM 11228 (0x2BDC)
    Failed to execute strored procedure: MP_MatchDrivers, hr=0x80040e14
    MP_DriverManager 10/11/2012 11:12:59 AM
    11228 (0x2BDC)
    Failed to execute MatchDrivers task, hr=0x80040e14
    MP_DriverManager 10/11/2012 11:12:59 AM
    11228 (0x2BDC)
    Anyone found a resolution for this ?Storage drivver is H710 mini and because of this error,storage driver is not getting installed, and hence OS installation is failing

  • Applications in a PXE deployed task sequence

    Hello forum,
    Can someone confirm, if SCCM2012 is working as intended when considering the following:
    I created MS Lync 2013 as an application (A), superseding an existing application of MS Lync 2010 (B). This in itself works fine when application A is being deployed
    to a collection of computers. (Lync 2010 is being uninstalled, and 2013 installed)
    What baffles me is if I put application A into a task sequence which is only available to PXE (e.g. my OSD task sequence), I will see computers evaluating the application
    and start uninstall/install Lync inside the OS. (AppEnforce.log, AppIntentEval.log)
    Is this really as intended? The TS itself is only available to PXE, but yet will applications in the TS still be evaluated by the OS, and cause Lync (and other application
    if not present on the client) to be uninstalled/installed (when software inventory is run).
    Thanks in advance
    Martin
    Martin Bengtsson | Blog: www.imab.dk

    Hello,
    I am having a similar problem where an application that is not deployed to any collections is being installed or attempted to be installed.
    The application is one I use during an OSD TS to upgrade computer BIOS if there is a newer version available. There is a query that runs to find what version is installed and if there is a newer version, it gets installed. I do not have Supersedence configured,
    but I do use dependencies for situations (maybe 3 models) where you can't just go immediately to the current version but must install a previous BIOS to get to the latest. (So to get to current you have to go from v3 > v7 > v19 > current). I don't
    think this though has anything to do with the issue. All the deployment types for all the models are contained within this one application.
    The only place this application is used like I said is in the OSD TS. Much like in your link, I do have my TS deployed to an "All Workstations" collection (sort of like your All Systems but limited to only workstation class OS's). And like in your link,
    I do understand the danger of doing this and have taken similar precautions to prevent "really bad things" from happening.
    We are moving from CM07 to CM12 and during the first pilot I had one user report after the new client was installed that they were prompted to reboot and during that time their BIOS was upgraded. Checked the logs, sure enough, it was SCCM that did it.
    This week while troubleshooting another issue I was looking through the AppEnforce.log on another workstation. I noticed on this one that also the BIOS is attempting to be updated, as well as on my own workstation. Luckily for the person who did get their
    BIOS upgraded there was not a problem.
    I have checked on the servers to see if there is any reference to any of the OSD applications being attempted to be installed on them but it does not appear so. They don't have an AppEnforce.log (most likely since we don't deploy apps via CM (yet) to servers).
    So it appears  that this most likely has something to do with my TS being deployed to a collection where all the workstations are at. Somehow they are randomly "picking" things to try to install that are in the TS which does not make sense. If the workstations
    suddenly rebooted, formatted, installed OS, drivers, apps, etc and so forth (basically ran through the TS) that would make sense. (I'd be horrified, but I would at least understand why it is happening.
    I guess I'm not making the connection in how an application which only exists in a TS, with no outside dependencies/or superceedence can run.
    I'm wondering if this is a bug or something? It seems that the TS should be treated as a box. TS is presented to the computer and it can only get to things inside that TS once it opens that box and goes through that
    sequence of steps. Instead, it seems like the TS is presented as a "glass window" where the computers can see everything that is inside and somehow those things inside are now available for computers to install.
    to me at least it isnt making sense.

  • Running Task Sequence from Software Center failed after rebooting to WinPE (0x8022001B)

    Hi all
    I have created a task sequence to refresh client OS to windows 8.1 x64. I ran this task sequence in software center on a windows 7 client, everything went well without any fails.
    But when I ran the same ts again after it refreshed to Windows 8.1, it failed immediately after rebooted to WinPE. It shows a warning with error code 0x8022001B.
    My test environment: SCCM 2012 R2 (Windows Server 2012 R2). Client Device: Lenovo L430
    Any suggestions? Thanks in advance!
    SMSTS.log file shows below:
    <![LOG[Configuring 1 of 3 network adapters]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="1" thread="808" file="netsettings.cpp:186">
    <![LOG[Configuring DHCP]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:417">
    <![LOG[DNS suffix: ]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:428">
    <![LOG[DNS server search order: ]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:437">
    <![LOG[DNS registration enabled: false]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:444">
    <![LOG[Full DNS registration enabled: false]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:452">
    <![LOG[Permitted IP protocols: ]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:457">
    <![LOG[Permitted TCP ports: ]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:461">
    <![LOG[Permitted UDP ports: ]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:465">
    <![LOG[Tcpip Netbios options: 0]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:474">
    <![LOG[Enable WINS: false]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:480">
    <![LOG[WINS server(s): ]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:489">
    <![LOG[MAC address: a4:17:31:f3:e4:28]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:503">
    <![LOG[Adapter index: 0]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:512">
    <![LOG[Adapter name: WLAN]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:516">
    <![LOG[Getting namespace "Microsoft-Windows-TCPIP" for architecture "amd64"]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="1" thread="808" file="smiinterface.cpp:222">
    <![LOG[Added list item with key value 'a4-17-31-f3-e4-28']LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="smiinterface.cpp:441">
    <![LOG[Configuring 2 of 3 network adapters]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="1" thread="808" file="netsettings.cpp:186">
    <![LOG[Configuring DHCP]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:417">
    <![LOG[DNS suffix: ]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:428">
    <![LOG[DNS server search order: ]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:437">
    <![LOG[DNS registration enabled: false]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:444">
    <![LOG[Full DNS registration enabled: false]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:452">
    <![LOG[Permitted IP protocols: ]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:457">
    <![LOG[Permitted TCP ports: ]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:461">
    <![LOG[Permitted UDP ports: ]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:465">
    <![LOG[Tcpip Netbios options: 0]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:474">
    <![LOG[Enable WINS: false]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:480">
    <![LOG[WINS server(s): ]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:489">
    <![LOG[MAC address: a4:17:31:f3:e4:28]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:503">
    <![LOG[Adapter index: 1]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:512">
    <![LOG[Adapter name: WLAN]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:516">
    <![LOG[spItem->CreateListElement( var, &spChildItem ), HRESULT=8022001b (e:\nts_sccm_release\sms\framework\osdcore\smiinterface.cpp,439)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="smiinterface.cpp:439">
    <![LOG[Failed to create list element with key value 'a4-17-31-f3-e4-28' (0x8022001B)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="3" thread="808" file="smiinterface.cpp:439">
    <![LOG[pSetupPass->addListItem( m_spSettingsEngine, pszNamespace, pszPath, pszKeyValue ), HRESULT=8022001b (e:\nts_sccm_release\sms\framework\osdcore\smiinterface.cpp,1187)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="smiinterface.cpp:1187">
    <![LOG[m_pSMIInterface->addListItem( SetupPassValue[eSetupPass], pszComponentName, pszPath, pszKeyValue ), HRESULT=8022001b (e:\nts_sccm_release\sms\framework\osdcore\xmlanswerfile.cpp,738)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="xmlanswerfile.cpp:738">
    <![LOG[AddListItem( eSetupPass, XML::TcpIp::ComponentName, XML::TcpIp::Interfaces::InterfaceElement, sIdentifier ), HRESULT=8022001b (e:\nts_sccm_release\sms\framework\osdcore\xmlanswerfile.cpp,1063)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="xmlanswerfile.cpp:1063">
    <![LOG[m_pImpl->AddAdapterTcpIpSettings( XMLAnswerFileImpl::WindowsPE, adapterInfo ), HRESULT=8022001b (e:\nts_sccm_release\sms\framework\osdcore\winpeanswerfile.cpp,176)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="winpeanswerfile.cpp:176">
    <![LOG[pAnswerFile->AddNetworkAdapter(adapterInfo), HRESULT=8022001b (e:\nts_sccm_release\sms\framework\osdcore\netadaptersettings.cpp,575)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:575">
    <![LOG[Failed to configure adapter 1 (0x8022001B)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="3" thread="808" file="netadaptersettings.cpp:575">
    <![LOG[adapterSettings.Configure( pAnswerFile ), HRESULT=8022001b (e:\nts_sccm_release\sms\framework\osdcore\netsettings.cpp,188)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netsettings.cpp:188">
    <![LOG[Failed to configure network settings for adapter 2 (0x8022001B)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="3" thread="808" file="netsettings.cpp:188">
    <![LOG[m_pNetSettings->Configure(pAnswerFile), HRESULT=8022001b (e:\nts_sccm_release\sms\client\tasksequence\bootshell\bootstrapsettings.cpp,191)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="bootstrapsettings.cpp:191">
    <![LOG[this->createAnswerFile(sAnswerFilePath), HRESULT=8022001b (e:\nts_sccm_release\sms\client\tasksequence\bootshell\bootstrapsettings.cpp,140)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="bootstrapsettings.cpp:140">
    <![LOG[pSettings->configureAnswerFile(), HRESULT=8022001b (e:\nts_sccm_release\sms\client\tasksequence\bootshell\bootshell.cpp,595)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="bootshell.cpp:595">
    <![LOG[Execution failed with error 8022001B.]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="3" thread="808" file="bootshell.cpp:703">
    <![LOG[hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,493)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="environmentscope.cpp:493">
    <![LOG[m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,335)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="environmentlib.cpp:335">
    <![LOG[this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,553)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="environmentlib.cpp:553">
    <![LOG[::RegOpenKeyExW (HKEY_LOCAL_MACHINE, sKey.c_str(), 0, KEY_READ, &hSubKey), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,809)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="utils.cpp:809">
    <![LOG[RegOpenKeyExW is unsuccessful for Software\Microsoft\SMS\Task Sequence]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="2" thread="808" file="utils.cpp:809">
    <![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="2" thread="808" file="utils.cpp:842">
    <![LOG[End program: ]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="1" thread="808" file="bootshell.cpp:725">
    <![LOG[Finalizing logging from process 800]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="1" thread="808" file="tslogging.cpp:1741">
    <![LOG[Finalizing logs to root of first available drive]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="1" thread="808" file="tslogging.cpp:1583">
    <![LOG[LOGGING: Setting log directory to "E:\SMSTSLog".]LOG]!><time="14:10:49.130+480" date="01-09-2015" component="TSBootShell" context="" type="1" thread="808" file="tslogging.cpp:1808">

    Then it's using a different boot image that doesn't have the NIC driver. The OS that the TS starts out in has no impact on the WinPE environment. Either the driver is there and properly loads or it doesn't -- there is not and cannot be any connection to
    the OS the system was booted into prior to PE booting.
    Thus, the only possibility here is that the boot image does *not* have the NIC driver in it. You need to verify which boot image I being used in both cases.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • Deploy Task Sequence to VPN based clients

    Can task sequences be deployed to VPN based clients? Its not an OSD task sequence, the task sequence in question has a couple of program installs and relatively small in size.
    The client machine(s) do receive the deployment although the status deployment remains on "Downloading", so I assume the device cannot locate the content on the DP within the VPN (configured Slow) boundary.
    The packages in the custom TS are located on the DP, so its either the boundary or a task sequence configuration.
    Just to note - Software updates are deploy successfully to VPN based clients within the same boundary, so I'm inclined to say it might be the task sequence?
    Any suggestions?
    Thanks
    Craig
    MCTS | MCITP | MCSA

    Thanks - although where is this configuration in the program/package(s):
    "Check the packages/programs called in the TS to ensure they are correctly set for slow-link behaviour."
    Oops, sorry, it's on the deployment;
    Step 10. here:
    http://technet.microsoft.com/en-us/library/gg682178.aspx
    On the Distribution Points page of the Wizard, specify the following information:
    Deployment options – Specify the actions that a client should take to run program content. You can specify behavior when the client is in a fast network boundary, or a slow or unreliable network boundary.
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • SCCM 2012 R2 Task Sequence to Restart Computers

    This is a simple question but I cannot seem to get it right.
    I am working on Monthly Maintenance plan for my servers and I cannot seem to get it right, any help would greatly appreciate it.
    I have Server collections for all OS's (2003, 2008...2012 R2) with maintenance windows for all deployments daily 8PM to 5am.
    I have ADRs setup to run and evaluate the last Thursday of the month to install updates on my machines.
    I have 4 collections created for Server Reboot 1st, 2nd, 3rd, and 4th with Maintenance Window Monthly for the last Friday/Saturday 8PM - 5AM for Task Sequences Only
    I created a Task Sequence called Server Reboot by doing the following:
    Create Task Sequence>Custom Task Sequence>Add x86 Boot Image file
    In the TS I click Add>General>Restart Computer, Add message "Computer will restart............"
    When the Task Sequence runs it does not display the message nor does it reboot the computer, what am I doing wrong?
    Basically I want to install updates on the Last Thursday of the month to my servers, Last Friday of the Month through Saturday morning I want to restart the servers to finish applying the updates, etc.
    What is the best way to accomplish this? Thanks for any suggestions or help!

    I concur with Torsten and narcoticoo -- using a simple package is better.
    One thing you noted however is the use of multiple maintenance windows. Maintenance Windows are not in any way specific to just the deployments on the collection where the MW is applied. MWs are applied to the clients in the collection and the client enforces
    them on *all* deployments it is assigned. Collections are strictly used by the site to build policies -- which include deployments and MWs among other things but not any collection information. Those policies are then delivered to the clients who enforce them
    without regard to collections at all.
    Jason | http://blog.configmgrftw.com

  • Adding Unknown computers resources by direct membership rule issue

    Hi, everybody!
    Finally, i've got issue discrabed here
    http://blog.coretech.dk/kea/collections-not-being-refreshed-in-configmgr-2012-r2/
    In situation with large count of primary sites and unknown computers accounts (two for each site certainly),  it's placed to be a big problem deploying task sequences to unknown computers...The comfort and rigth decision in
    my thought is deploying tasks to site's unknown collection that contains two of all unknows (only each site x86 and x64 account) directly. But after creating those/that collections/collection per sites becomes alive previously noticed trouble....How
    can we add/devide unknown computers for deploying tasks on them....Situations with availiable lists of all task sequences (as you know right that occurs while deploying tasks to  unkonow built-in collection) of all hierarchy in installing process misleads
    primary sites sccm admins....there are situations with starting wrong tasks (belongs not to their site unknowns).....
    I repeat, adding each sites unkonws to separate collection directly occurs upper link problem...
    Is any idea, guys?         

    Jason, it is above 20 sites...
    I've noticed one thing: when i use collection adding direct membership rule wizard using "unknown computer" and it's "site code" like criteria, collecton working fine. As soon as, i use console's "adding to existing collection"
    capability clicking by right mouse click on one of the unknowns...it's gonna to be fail to update in previously described way..... 

  • Deploy OS task sequence fails when deploying to multiple computers

    Hi gang,
    I'm running into an issue when imaging multiple computers with MDT 2012. Let me give some background info.
    I have installed Windows 7 64 bit on a laptop in audit mode, made my configurations, sysprepped the machine, and captured a .wim using WDS (captured to an external hard drive). I then imported this .wim into MDT, created a Standard Client Task Sequence to deploy
    the image, and successfully deployed it to a machine.
    My problem comes up when I initiate this task sequence on multiple computers simultaneously. If I put 6 computers side-by-side and run the task sequence at the same time, only a couple machines will actually succeed. The rest fail with the following:
    FAILURE ( 5624 ): 2: Run ImageX: /apply "\\CAAPPWN40\DeploymentShare$\Operating Systems\T731 (Final) Windows 7 64 bit May 2013\T731 (Final) Windows 7 64 bit May 2013.wim"
    1 C:
    Litetouch deployment failed. Return Code = -2147467259 0x80004005
    Failed to run the action: Install Operating System
    Unknown error (Error: 000015F8; Source: Unknown)
    The execution of the group (Install) has failed and the execution has been aborted. An action failed.
    Operating aborted (Error: 80004004; Source: Windows)
    Failed to run the last action: Install Operating System. Execution of task sequence failed.
    Unknown error (Error: 000015F8; Source: Unknown)
    Task Sequence Engine failed! Code: enExecutionFail
    Task sequence execution failed with error code 80004005
    Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
    BDD.log is saying that "The file or directory is corrupted and unreadable."
    If I restart the computer, boot back into PXE, and run the task sequence again, this time on it's own (as opposed to 6 computers at once) it works fine.
    Can anyone help?

    I just rebooted the server and tried again, same result.
    I keep getting a "Body text cannot contain links or images until we are able to verify your account" error when posting a hyperlink. I've had my technet account since October... weird.
    Here's the snippet that's important:
    <![LOG[ Console > [ 18% ] Applying progress: 14:47 mins remaining ]LOG]!><time="11:27:10.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > [ 19% ] Applying progress: 14:27 mins remaining ]LOG]!><time="11:27:18.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > [ 20% ] Applying progress: 14:15 mins remaining ]LOG]!><time="11:27:32.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > [ RETRY ] Restoring C:\Program Files (x86)\Common Files\microsoft shared\OFFICE15\MSORES.DLL again (Error = 1392)]LOG]!><time="11:27:40.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > [ 21% ] Applying progress: 14:06 mins remaining ]LOG]!><time="11:27:42.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > [ 22% ] Applying progress: 13:49 mins remaining ]LOG]!><time="11:27:48.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > [ 23% ] Applying progress: 13:29 mins remaining ]LOG]!><time="11:27:55.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ZTI Heartbeat: command has been running for 5 minutes (process ID 516)]LOG]!><time="11:28:01.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > [ RETRY ] Restoring C:\Program Files (x86)\Intel Corporation\Intel Wireless Display\it\WiDiApp.resources.dll again (Error = 1392)]LOG]!><time="11:28:01.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > [ RETRY ] Restoring C:\Program Files (x86)\Intel Corporation\Intel Wireless Display\it\WiDiApp.resources.dll again (Error = 1392)]LOG]!><time="11:28:01.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > [ RETRY ] Restoring C:\Program Files (x86)\Intel Corporation\Intel Wireless Display\it\WiDiApp.resources.dll again (Error = 1392)]LOG]!><time="11:28:02.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > [ RETRY ] Restoring C:\Program Files (x86)\Intel Corporation\Intel Wireless Display\it\WiDiApp.resources.dll again (Error = 1392)]LOG]!><time="11:28:02.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > [ 24% ] Applying progress: 13:13 mins remaining ]LOG]!><time="11:28:07.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > [ RETRY ] Restoring C:\Program Files (x86)\Microsoft Analysis Services\AS OLEDB\110\msmdlocal.dll again (Error = 1392)]LOG]!><time="11:28:13.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > [ RETRY ] Restoring C:\Program Files (x86)\Microsoft Analysis Services\AS OLEDB\110\msmdlocal.dll again (Error = 1392)]LOG]!><time="11:28:14.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > [ RETRY ] Restoring C:\Program Files (x86)\Microsoft Analysis Services\AS OLEDB\110\msmdlocal.dll again (Error = 1392)]LOG]!><time="11:28:15.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > [ RETRY ] Restoring C:\Program Files (x86)\Microsoft Analysis Services\AS OLEDB\110\msmdlocal.dll again (Error = 1392)]LOG]!><time="11:28:16.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > [ ERROR ] C:\Program Files (x86)\Microsoft Analysis Services\AS OLEDB\110\msmdlocal.dll (Error = 1392)]LOG]!><time="11:28:17.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > Error restoring image.]LOG]!><time="11:28:17.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[ Console > The file or directory is corrupted and unreadable. ]LOG]!><time="11:28:17.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Return code from command = 2]LOG]!><time="11:28:17.000+000" date="06-11-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[FAILURE ( 5624 ): 2: Run ImageX: /apply "\\MyServer\DeploymentShare$\Operating Systems\T731 (Final) Windows 7 64 bit May 2013\T731 (Final) Windows 7 64 bit May 2013.wim" 1 C:]LOG]!><time="11:28:17.000+000" date="06-11-2013" component="LTIApply" context="" type="3" thread="" file="LTIApply">
    <![LOG[Command completed, return code = -2147467259]LOG]!><time="11:28:18.000+000" date="06-11-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Litetouch deployment failed, Return Code = -2147467259 0x80004005]LOG]!><time="11:28:18.000+000" date="06-11-2013" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">

  • Deploying 100% of available software updates during a task sequence

    Hi,
    Can somebody tell me if it actually possible to fully patch a computer via an SCCM 2012 task sequence using the install software updates task? If you have managed this can you shed some light on where I'm going wrong? For me, this behaviour is exactly
    the same as ConfigMgr07... It simply doesn't work as it should.
    I've integrated IE9 into my image and then added in all available updates via offline servicing. My task sequence installs windows, installs Adobe Reader, Office 2010 and Visio Viewer 2010. I then reboot the machine and perform all my patching via the Install
    Software Updates task (with it set to 'all'), then reboot again. I do this four times in total.
    It downloads and installs some 24 updates in the first instance. The second, third and fourth time it doesn't download or install anything.
    When the task sequence completes and the OS first starts up there are 10 updates waiting to be installed (including updates for Adobe Reader and Flash that I have published to the WSUS server via SCUP). After installing those and rebooting there is a single
    hotfix available (KB2533552). After installing that and rebooting, .NET4 Client Profile is waiting for me. After that there another nine more updates are available (mainly .NET4). Reboot, .NET4 Framework, reboot 5x .NET4 framework updates.
    Why does the software update task not install 'all' updates when that is what I've selected? I have an automatic deployment rule targeted to my OSD and Unknown Computers collections. The rule is set to include Windows 7, Office 2010 and Adobe products with
    all update classification types.

    I don't have a pause in my script and have not encountered any issues with the scan not finishing before the Software Update installation step. This is true for my B&C TSs which install in the region of 200 updates, including custom trusted publisher
    updates from SCUP 2011. So I can't really comment on that side of things.
    With regards to the patching side of things: I tried removing the multiple reboot patches from my Task Sequences by excluding them from the Auto Deployment Rules that target the same containers as the task sequences by adding -KBxxxxxx in the ADR. Unfortunately,
    due to me having the multiple reboot updates targeted up 'update' collections that are populated by hardware/software DB queries, any PC that is performing a 'Refresh' TS ends up with the offending patches being targeted for install anyway and the TS fails.
    For a long time I was just removing the client record from the DB and recreating it so that the offending updates would not be targeted to the client. Once the client has been refreshed, a hardware inventory is performed, the collections updated daily, the
    multiple reboot patches are detected and are scheduled for install for the following Friday afternoon. This used to annoy me as I don't like 'incomplete' clients being delivered to users' desktop.
    Recently though I've been toying with offline servicing. At first I attempted to integrate every available update but this just ended up killing things too. A number of the updates that can be installed via offline servicing have a .net 4 pre-requisite
    but because .net 4 cannot be slipstreamed, the prerequisite is not satisfied, Windows setup fails and so does the TS. So using this method there is a chance you'll end up installing a patch that will kill your image... Still not ideal.
    What I have settled on is slipstreaming specific patches into my installation media using dism and then running a B&C TS to update my image.
    This is the batch file I use (you'll need to change to suit):
    Dism /mount-wim /wimfile:D:\SCCMContentSources\Applications\Microsoft\Windows\7\Professional\SP1\64-bit\Sources\install.wim /index:1 /mountdir:D:\HotFixIntegration\Offline
    Dism /Image:D:\HotFixIntegration\Offline /LogPath:SourceAddPackagex64.log /Add-Package /PackagePath:D:\HotFixIntegration\Hotfixes\64-bit\Updates
    Dism /Image:D:\HotFixIntegration\Offline /LogPath:SourceAddPackagex64.log /Add-Package /PackagePath:D:\HotFixIntegration\Hotfixes\64-bit\IE
    Dism /unmount-wim /mountdir:D:\HotFixIntegration\Offline /commit
    The first line mounts the image.
    The second line slipstreams the following .msu updates:
    kmdf-1.11, KB2526870, KB2529073, KB2545698, KB2561285, KB2574819-v2, KB2592687, KB2617858, KB2670838, KB2726535, KB2729094-v2, KB2786081, KB2834140-v2, KB2847311, KB2855844, KB2862330-v2, KB2862335, KB2864202, KB2868038, KB2876284, KB2883150, KB2884256,
    KB2965788, KB2984976, KB917607, KB971033, KB976399, KB977944, KB981750
    These are essentially just the multiple reboot patches and their pre-requisites, IE11 prerequisites, and a few KBs that not published to WSUS.
    The third line slipstreams IE11 from the IE11 .cab file.
    The fourth line commits the changes to the install media.
    After running a B&C TS from this modified installation source there are no updates available to freshly deployed images (until the next patch Tuesday!).
    Unfortunately this a manual process as I need to check the multiple reboot KB article each time updates are released but it's the only way I can put out 100% patched PCs and have a PC Refresh task sequence that doesn't fail.

  • Non-Deployed Applications in OSD Task Sequence Are Deployed To Collection Members where OSD TS is deployed

    Hello,
    I have a situation where an application (which is not deployed) that is part of an OSD Task Sequence is being deployed to computers that are in the same collection my TS for OSD is deployed.
    For OSD I have created an application to check the BIOS version and upgrade the BIOS if there is a newer one available. The application has numerous deployment types (13) due to various hardware models and the requirement to go to several intermediary BIOS
    versions to reach the current newest version. There are dependencies configured to handle these incremental bumps.
    The OSD TS is deployed to a collection that contains all windows desktop class operating systems. What I have seen happen once is that one users workstation somehow discovered and installed the BIOS Upgrade package and their BIOS was upgraded on their workstation.
    I've checked the logs on several other machines and this same application has been run as well.
    The application is configured "Allow this application to be installed from the Install Applications
    task sequence action without being deployed" which allows it to be ran from a TS even though it is not deployed.
    I have verified the application is not deployed. I have verified there are no superceedence rules configured. As I stated, there are dependencies, but all dependencies are within this one application.
    What I do not understand is, how can an application that is not
    deployed and is only referenced in an Operating System Deployment Task Sequence able to be ran outside the task sequence?
    This is/has occurred with computers imaged with cm2012 and with computers imaged with cm2007 who have now been migrated to cm2012.
    I'm fairly sure that it is due to the task sequence and where it is advertised. Computers that are not in this collection do not show the application being applied in the AppEnforce.log. If it is the TS that is causing this, how can something that is designed
    to be a "sequence of tasks", allow something to occur out of that sequence?
    Current environment is CM2012R2.
    Any thoughts to what might be happening?
    Thanks

    Hello,
    After working with Microsoft Support, we were able to resolve the issue.
    Turns out there was something (old policies) "stuck" in the SCCM database that was causing this to be advertised outside the task sequence and not visible on the console. While they didn't call this "a bug" since it has happens with CM2007 as well, it definitely
    was not normal behavior. Still not sure how that could happen as I'm 99.99% sure I never deployed this to any collection, but that's what they said.
    It took several hours of support rooting through the database to figure out what was going on but after some SQL magic it was fixed. Sorry I don't have more specifics regarding the fix. MS basically said "If it happens again you can do this this and this
    in the db and voila its fixed". Since I'm likely to cause more damage (messing with the database) then good if it were to happen again I'd contact them.
    Anyway, this odd behavior has spooked me and I've reverted back to deploying the TS to the unknown computer collection. As much as it disappoints me to take a step back and cause more work for the guys doing the imaging, the extra safety this grants (if
    something like this or worse were to happen) I think is better than an OSD task sequence gone wild.
    Thanks,
    Mark

  • SCCM 2012 Export Task Sequence fails with generic error message

    We have a complex task sequence comprising of more than 50 applications\packages, 1975 drivers, 18 driver packages etc etc. Its long, it's big and it will not export with it's content.
    We have several environments for development test and live. I am attempting to export the primary task sequence with all it's dependencies from live so that I can port it over to a new development environment.
    I can export the zip file without content and it comes to 92Mb in size. The entire task sequence software set is 50Gb+. When I attempt to export with all dependencies and content the process gets about 60% of the way through and fails with the error
    "Error: The filename, directory name, or volume label syntax is incorrect"
    Googling the error roughly defines the problem as 'the export process cannot access the defined source path for one of the dependant items'
    I wrote a PowerShell script that looks as every application, package, driver, driver package, boot image, os image and software update package in the entire SCCM software library and verifies that each and every package has a valid UNC source directory
    that can be reached using test-path.
    I also wrote another tool that parsed the entire source software library on the server looking for permissions errors (permissions on the structure set at a directory level rather than inherited), directories that were too long, inaccessible or otherwise
    blocked, nothing was found.
    It will take a very long time to go through and check each and every dependency by hand - time I do not have at present.
    I looked in the TaskSequenceProvider.log as that is supposed to contain messages from the export process and found the messages in there far too high a level to use
    =======================
    <![LOG[Setting status complete:  status code = 0x0; ]LOG]!><time="13:00:41.161-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="4168" file="exterror.cpp:128">
    <![LOG[[PID: 3500] Invoking method SMS_TaskSequence.ExportXml]LOG]!><time="13:00:42.339-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="4168" file="wmiprovider.cpp:333">
    <![LOG[[PID: 3500] Done with method SMS_TaskSequence.ExportXml]LOG]!><time="13:00:42.341-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="4168" file="wmiprovider.cpp:352">
    <![LOG[Setting status complete:  status code = 0x0; ]LOG]!><time="13:00:42.341-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="4168" file="exterror.cpp:128">
    <![LOG[[1AFF658 PID:3500] Received shutdown request from WMI]LOG]!><time="13:01:36.036-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="5592" file="wmiprovider.cpp:399">
    <![LOG[[1AFF658 PID:3500] Initializing provider for namespace root\sms\site_P01]LOG]!><time="13:02:36.550-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068"
    file="wmiprovider.cpp:90">
    <![LOG[[1AFF658  PID:3500] Initialization of provider for namespace root\sms\site_P01 succeeded]LOG]!><time="13:02:36.551-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1"
    thread="7068" file="wmiprovider.cpp:107">
    <![LOG[[PID: 3500] Invoking method SMS_TaskSequence.LoadFromXml]LOG]!><time="13:02:36.554-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="wmiprovider.cpp:333">
    <![LOG[[PID: 3500] Done with method SMS_TaskSequence.LoadFromXml]LOG]!><time="13:02:36.558-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="wmiprovider.cpp:352">
    <![LOG[Setting status complete:  status code = 0x0; ]LOG]!><time="13:02:36.559-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="exterror.cpp:128">
    <![LOG[[PID: 3500] Invoking method SMS_TaskSequence.ExportXml]LOG]!><time="13:03:05.428-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="wmiprovider.cpp:333">
    <![LOG[[PID: 3500] Done with method SMS_TaskSequence.ExportXml]LOG]!><time="13:03:05.431-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="wmiprovider.cpp:352">
    <![LOG[Setting status complete:  status code = 0x0; ]LOG]!><time="13:03:05.431-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="exterror.cpp:128">
    <![LOG[[1AFF658 PID:3500] Received shutdown request from WMI]LOG]!><time="13:03:36.369-60" date="08-26-2014" component="TaskSequenceProvider" context="" type="1" thread="7068" file="wmiprovider.cpp:399">
    ====================
    Is there any way of increasing the log verbosity? I need to see what item is causing the export to fail.
    Is there another log containing the information about the export & what it is doing?
    All out builds that use the task sequence complete successfully, we can edit the sequence fine, make changes etc. so no internal corruption we can find.
    Any ideas?

    Torsten, smsprov.log did indeed prove useful, I could see every package as it was validated. Unfortunately the log was wrapping about every 4 minutes and it takes 3+ hours for the task sequence to reach the fail point so I still cannot see the offending
    package as it wraps before I can get to the log.
    I will increase the size of the log and see if I can maintain some details to investigate.
    There was nothing of note in the event logs, certainly nothing leading me to suspect that WMI might be reaching its limits.
    I will keep looking for the cause and will post here when I find it <= positive thinking :)

  • MDT 2013 Windows 8.1 Deployment Starts Prompting For Administrator Login In Middle Of Task Sequence

    I have a 8.1 deployment task sequence that automatically logs into the administrator account until about half way through the deployment.
    It actually looks like it logs in for a second and then dumps back out to the login prompt.
    After this reboot, the problem starts.  When I log in manually, I see it is at the installing the Java application step.  What could cause this?

    Yes, it's possible that the scripts to boot to desktop or the script to remove apps are causing this, but other people use these settings in deployments and didn't mention this as a side effect.
    This reg file is supposed to set the Start Menu background to match the desktop wallpaper and set IE to use desktop version, but does not seem to work.
    regedit.exe /s 81settings.reg
    Windows Registry Editor Version 5.00
    [HKEY_USERS\CUSTOM\Software\Microsoft\Windows\CurrentVersion\Explorer\Accent]
    "MotionAccentId_v1.00"=dword:000000db
    [HKEY_USERS\CUSTOM\Software\Policies\Microsoft\Windows\EdgeUI]
    "DisableHelpSticker"=dword:00000001
    [HKEY_USERS\CUSTOM\Software\Microsoft\Internet Explorer\Main]
    "ApplicationTileImmersiveActivation"=dword:00000000
    "AssociationActivationMode"=dword:00000002
    ================================================
    powershell.exe -Command "set-ExecutionPolicy Unrestricted -Force; cpi '%DEPLOYROOT%\Applications\Remove Windows 8.1 Modern Applications\RemoveWindows8Apps.ps1' -destination c:\; c:\RemoveWindows8Apps.ps1; ri c:\*.ps1 -Force; set-ExecutionPolicy Restricted
    -Force"
    <#     
        Purpose:    Remove built in apps specified in list 
        Pre-Reqs:    Windows 8.1 
    #>
    # Main Routine 
    # Get log path. Will log to Task Sequence log folder if the script is running in a Task Sequence 
    # Otherwise log to \windows\temp
    try
    $tsenv = New-Object -COMObject Microsoft.SMS.TSEnvironment
    $logPath = $tsenv.Value("LogPath")
    catch
    Write-Host "This script is not running in a task sequence"
    $logPath = $env:windir + "\temp"
    $logFile = "$logPath\$($myInvocation.MyCommand).log"
    # Start logging
    Start-Transcript $logFile
    Write-Host "Logging to $logFile"
    # List of Applications that will be removed
    $AppsList = "microsoft.windowscommunicationsapps","Microsoft.BingFinance","Microsoft.BingMaps",`
    "Microsoft.BingWeather","Microsoft.ZuneVideo","Microsoft.ZuneMusic","Microsoft.Media.PlayReadyClient.2",`
    "Microsoft.XboxLIVEGames","Microsoft.HelpAndTips","Microsoft.BingSports",`
    "Microsoft.BingNews","Microsoft.BingFoodAndDrink","Microsoft.BingTravel","Microsoft.WindowsReadingList",`
    "Microsoft.BingHealthAndFitness","Microsoft.WindowsAlarms","Microsoft.Reader","Microsoft.WindowsCalculator",`
    "Microsoft.WindowsScan","Microsoft.WindowsSoundRecorder","Microsoft.SkypeApp"
    ForEach ($App in $AppsList)
    $Packages = Get-AppxPackage | Where-Object {$_.Name -eq $App}
    if ($Packages -ne $null)
          Write-Host "Removing Appx Package: $App"
          foreach ($Package in $Packages)
          Remove-AppxPackage -package $Package.PackageFullName
    else
          Write-Host "Unable to find package: $App"
    $ProvisionedPackage = Get-AppxProvisionedPackage -online | Where-Object {$_.displayName -eq $App}
    if ($ProvisionedPackage -ne $null)
          Write-Host "Removing Appx Provisioned Package: $App"
          remove-AppxProvisionedPackage -online -packagename $ProvisionedPackage.PackageName
    else
          Write-Host "Unable to find provisioned package: $App"
    # Stop logging
    ====================================================
    Install java and turn off updates.
    Start /wait jre-8u25-windows-i586.exe INSTALL_SILENT=1 STATIC=0 AUTO_UPDATE=0 WEB_JAVA=1 WEB_JAVA_SECURITY_LEVEL=H WEB_ANALYTICS=0 EULA=0 REBOOT=0
    regedit.exe /s disableupdate.reg
    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Update\Policy]
    "EnableJavaUpdate"=dword:00000000
    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\JavaSoft\Java Update\Policy]
    "EnableJavaUpdate"=dword:00000000

  • Sccm 2012 simulate deployment for task sequence / OS or applications

    Hi
    I have been getting a lot of problems with Os/Application Task Sequences and have been asked a few questions.
    I cannot find anything on the Web about Limitations for a simulated deployment in SCCM 2012.
    I know SCCM allows you to create them but does it work/Are the results accurate?
    I need to know the following: 
    Can you simulate an OS Deployment Task Sequence?
    Can you simulate an Application Deployment Task Sequence?
    Are there limitations to Simulated Deployments?
    Thanks guys Hope this makes sense and you can help.
    Regards
    Anthony

    If you have the MDT integration with SCCM 2012 you can simulate the settings used by the task sequence, but not the actual task sequence deployment. However, seeing the settings is often enough.
    Check this post:
    Save time (and avoid pain) - Create a MDT simulation environment
    http://www.deploymentresearch.com/Research/tabid/62/EntryId/155/Save-time-and-avoid-pain-Create-a-MDT-simulation-environment.aspx
    / Johan
    Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

Maybe you are looking for