Build & capture task sequence fails during software update installation

I'm sure this has been discussed a thousand times already, so I hope no one minds talking about it at least one more time.  About 6 months ago I created a reference image using a build and capture task sequence within SCCM.  After discovering
there were certain updates that would kill a task sequence (because they required multiple restarts), I was able to exclude these updates from deployment so that my task sequence completed successfully.  Fast forward to today.  I'm working on updating
our reference image to include the last 6 months of updates.  Again, I'm having trouble with the task sequence failing to complete.  I have excluded all of the updates mentioned in
Microsoft KB article 2894518.  I'm able to build the image with all software updates up until 6/30/2014.  When I deploy my software group that contains updates from 7/1/2014 to 12/31/2014,
however, the task sequence fails.  I'm pulling my hair out trying to figure out which update may be causing the issue, and trust me, I don't have much hair as it is.  So, here's my question to all of the experts out there.  What is the best
method of debugging this issue and finding which update may be the culprit?  The log files really are confusing, so I'm hoping there are some common codes or phrases I can search for within those files.  Any and all help is much appreciated.  Thanks...

>   I'm working on updating our reference image to include the last 6 months of updates. 
Since this is a Build & Capture task sequence and not joined to the domain, you'll need to treat it
like a workgroup computer.  Here are the big three things that usually trip things up:
1.  Initial Management Point:  The Setup Windows and ConfigMgr step should have the SMSMP=<fqdn>
property specified, as the device won't be able to see the list of MP's in Active Directory
2.  Content Location:  Make sure the reference machine's IP address falls within an IP Range
or Subnet ID boundary, since it can't use a AD Site boundary as a workgroup machine.
3.  Win 7 - NTLM Fallback:  Windows 7 devices may need
hotfix KB2522623 installed (as a package/program or with offline servicing) to ensure they fall back to NTLM properly when they fail to authenticate with Kerberos.
If you have those 3 things taken care of, then you should copy all the logs off of the machine while the
error message is still being displayed, zip them, and then share them out through OneDrive or Dropbox.
I hope that helps,
Nashs
Nash Pherson, Senior Systems Consultant
Now Micro -
My Blog Posts
If you found a bug or want the product to work differently,
share your feedback.
<-- If this post was helpful, please click the up arrow or propose as answer.

Similar Messages

  • Task Sequence Fails after Software Updates Install Step - Lenovo X240

    Hi All.
    I'm having a strange issue trying to run an OSD on Lenovo X240 machines. 
    After the Software Update step, it reboots as expected, then exits the task sequence and sends you to the windows logon screen.
    Review the SMSTS.log, it appears the reason is:
    Found network adapter "Intel(R) Dual Band Wireless-AC 7260" with IP Address 0.0.0.0.
    TSMBootstrap 24/07/2014 15:07:10
    1824 (0x0720)
    Found network adapter "Intel(R) Ethernet Connection I218-LM" with IP Address 0.0.0.0.
    TSMBootstrap 24/07/2014 15:07:10
    1824 (0x0720)
    Full log file:
    SMSTS.log
    If I remove the Software Updates step, the task sequence completes without any problems.
    Don't think it is a driver error, as above, every other step completes without issue. Other models use the same task sequence (including software updates step) without any problems.
    Any ideas? I'm completely stuck.
    Thanks!

    Looks like I am deploying KB2965788 which requires two restarts.
    Thanks all for your help.
    P.S. - I periodically update the base image with a build & capture to include the latest updates, so in the times between this I deploy the software updates as part of the task sequence.
    I've found the offline servicing to be very flaky, have attempted to use it many times and found it either a) doesn't apply the updates to the image b) corrupts the image.

  • Build and Capture task sequence fails at 'Prepare ConfigMgr Client for Capture' step

    The scenario is as follows:
    Task Sequence is a Build and Capture of Windows 7 SP1 x64 Enterprise
    There are 17 Applications installed split into 2 'Install Application' steps due to the 9 item limit
    129 Software Updates are installed
    SCCM 2012 RTM
    I have built and captured on this system previously however there were no 'applications', just traditional SCCM 'packages'
    All task sequence steps run successfully until it gets to the 'Prepare ConfigMgr Client for Capture' step and it fails here. Here are the relevant parts of the SMSTS.log file:
    <![LOG[No certificates to delete]LOG]!><time="15:30:12.531-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:1013">
    <![LOG[Deleting Client properties from file C:\Windows\SMSCFG.INI succeeded.]LOG]!><time="15:30:12.531-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:922">
    <![LOG[Reseting the Trusted Root Key successful]LOG]!><time="15:30:12.531-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:1088">
    <![LOG[Deleting instance of 'CCM_Client' successful]LOG]!><time="15:30:12.531-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:170">
    <![LOG[Successfully reset Registration status flag to "not registered"]LOG]!><time="15:30:12.531-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:309">
    <![LOG[Successfully disabled provisioning mode.]LOG]!><time="15:30:12.546-660" date="11-13-2012" component="PrepareSMSClient" context="" type="1" thread="2880" file="preparesmsclient.cpp:1273">
    <![LOG[Start to cleanup TS policy]LOG]!><time="15:30:12.546-660" date="11-13-2012" component="PrepareSMSClient" context="" type="0" thread="2880" file="utils.cpp:2773">
    <![LOG[getPointer()->ExecQuery( BString(L"WQL"), BString(pszQuery), lFlags, pContext, ppEnum ), HRESULT=ffffffff (e:\nts_sccm_release\sms\framework\core\ccmcore\wminamespace.cpp,389)]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient"
    context="" type="0" thread="2880" file="wminamespace.cpp:389">
    <![LOG[ns.Query(sQuery, &spEnum), HRESULT=ffffffff (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,2800)]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="0" thread="2880" file="utils.cpp:2800">
    <![LOG[Wmi query 'select * from CCM_Policy where PolicySource = 'CcmTaskSequence'' failed, hr=0xffffffff]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="3" thread="2880" file="utils.cpp:2800">
    <![LOG[End TS policy cleanup]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="0" thread="2880" file="utils.cpp:2821">
    <![LOG[TS::Utility::CleanupPolicyEx(false), HRESULT=ffffffff (e:\nts_sccm_release\sms\client\osdeployment\preparesmsclient\preparesmsclient.cpp,457)]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="0" thread="2880"
    file="preparesmsclient.cpp:457">
    <![LOG[Failed to delete policies compiled by TaskSequence (0xffffffff)]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="3" thread="2880" file="preparesmsclient.cpp:457">
    <![LOG[Failed to prepare SMS Client for capture, hr=ffffffff]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="3" thread="2880" file="preparesmsclient.cpp:472">
    <![LOG[pCmd->Execute(), HRESULT=ffffffff (e:\nts_sccm_release\sms\client\osdeployment\preparesmsclient\main.cpp,136)]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="0" thread="2880" file="main.cpp:136">
    <![LOG[Failed to prepare SMS Client for capture, hr=ffffffff]LOG]!><time="15:35:21.000-660" date="11-13-2012" component="PrepareSMSClient" context="" type="3" thread="2880" file="main.cpp:136">
    <![LOG[Process completed with exit code 4294967295]LOG]!><time="15:35:21.015-660" date="11-13-2012" component="TSManager" context="" type="1" thread="2152" file="commandline.cpp:1098">
    <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="15:35:21.015-660" date="11-13-2012" component="TSManager" context="" type="1" thread="2152" file="instruction.cxx:3011">
    <![LOG[Failed to run the action: Prepare ConfigMgr Client for Capture. 
    Unknown error (Error: FFFFFFFF; Source: Unknown)]LOG]!><time="15:35:21.046-660" date="11-13-2012" component="TSManager" context="" type="3" thread="2152" file="instruction.cxx:3102">
    It looks like there is a similar issue over here (http://www.windows-noob.com/forums/index.php?/topic/5906-task-sequence-error-0xffffffff/) that was resolved by removing the Application Installations one by one until a problematic one was found
    and removed - however I would rather avoid this very time consuming process if possible.
    I have also testing this using 'capture media' in the full OS and that also fails at the same step with the same errors in the smsts.log
    The only workaround I have for now is to let the task sequence fail at the 'Prepare ConfigMgr Client for Capture' step, then I uninstall the SCCM client using 'ccmsetup.exe /uninstall' and use the 'capture media' method - obviously with no SCCM client installed,
    it skips the 'Prepare ConfigMgr Client for Capture' step and goes straight to the 'Prepare OS' step and then to the actual capture to the WIM step.
    Anybody else seeing this or have any suggestions?
    My Microsoft Core Infrastructure & Systems Management blog -
    blog.danovich.com.au

    It looks like there is a similar issue over here (http://www.windows-noob.com/forums/index.php?/topic/5906-task-sequence-error-0xffffffff/) that was resolved by removing the Application Installations one by one until a problematic one was found
    and removed - however I would rather avoid this very time consuming process if possible.
    You dont have to test it 18 times....
    Just test with 50% of the applications first, if it fails, test with 25% and then on of the time...
    You should be able to find the application, within 4-5 tests...
    Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs:
    http://www.ronnipedersen.com/ and SCUG.dk/ | Twitter
    @ronnipedersen

  • Sysprep and Capture Task Sequence Fails "Can not find script file C:\LTIBootstrap.vbs"

    I've just installed Windows 8 on a Lenovo ThinkPad T440s using Lenovo's recovery discs. I did not join it to a domain. I logged in as Administrator, navigated to our deployment share, and ran Scripts\LiteTouch.wsf. I selected the new Sysprep and Capture
    Task Sequence that I just made, told it to upload to DeploymentShare$\Captures, then started the Task Sequence.
    It seemed to run fine until after the first reboot. Windows 8 configured the PC for a while, then displayed an error that it had been shut down unexpectedly. I wasn't sure if this was normal, so I just clicked OK. Then I got an error that said "Can
    not find script file C:\LTIBootstrap.vbs". After clicking OK on that, I am brought to the desktop.
    The image cannot be found in DeploymentShare$\Captures. Under the Monitoring section of the DeploymentWorkbench, I can see that MDT thinks the Task Sequence is still running on the machine (though it is not), with progress stuck on step 16 of 23: Execute
    Sysprep. There are 0 errors and 0 warnings listed.
    BDD.log is too long to post all of it, but here's the last few lines in case that's helpful.
    <![LOG[BCD> The operation completed successfully.]LOG]!><time="11:20:35.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[BCDEdit returned ErrorLevel = 0]LOG]!><time="11:20:35.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Run Command: C:\windows\SYSTEM32\bcdedit.exe /default {d22e7e91-9ee7-46eb-89d7-c5859e4302f0}]LOG]!><time="11:20:35.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[BCD> The operation completed successfully.]LOG]!><time="11:20:35.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[BCDEdit returned ErrorLevel = 0]LOG]!><time="11:20:36.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Property BootPE is now = True]LOG]!><time="11:20:36.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[LTI Windows PE applied successfully]LOG]!><time="11:20:36.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Event 41019 sent: LTI Windows PE applied successfully]LOG]!><time="11:20:36.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[LTIApply processing completed successfully.]LOG]!><time="11:20:36.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Event 41001 sent: LTIApply processing completed successfully.]LOG]!><time="11:20:36.000+000" date="12-26-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    I would greatly appreciate any assistance determining what went wrong and how to correct it. Thank you.

    You might get teh c:\LTIBootStrap.vbs error if you are running SysPrep with a unattend.xml template that contains the c:\bootstrap.vbs template, yet you are *NOT* deploying the image with MDT Litetouch, instead just applying the image to the final machine.
    Crack open your install.wim file and search for the unattend.xml file in the normal places to see what it is.
    I am concerned about the "shut down unexpectedly" error. There should be no shutdown state information left  from a captured *.wim file.
    If you still need assistance, please feel free to copy the bdd.log file to a public site like OneDrive, and share the link.
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  • WinPE fails every time after "preparing network connections" message during Build & Capture task sequence

    Sorry, I'm using SCCM 2012 but can't find a forum for that ANYWHERE, so I'm posting this here:
    We're making our first attempt at OSD (build & capture) on an out-of-the box Dell Optiplex 9010 all-in-one. I've injected the NIC drivers found
    here on Dell's Enterprise support blog into the boot image.
    Using PXE boot, the machine starts up in WinPE when we deploy the task sequence, but every time it reaches the "preparing network connections" message in the splash screen, WinPE quits and the machine reboots.
    I've hit F8 to get the command line while WinPE is booting, and from running ipconfig there, it looks like the machine takes a long time to pick up its IP address from DHCP, but it DOES pick up an IP address eventually which implies to me that the NIC driver
    is at least somewhat working.
    See below for the wpeinit.log file from this machine. What am I doing wrong? What's that message about "no operational adapters found", expecially when I've verified that it does get an IP address (albeit after a short while)?
    BEGIN WPEINIT LOG:
    Info      No unattend file was found; WPEINIT is using default settings to initialize WinPE
    Info      ==== Initializing Display Settings ====
    Info      No display settings specified
    Info      STATUS: SUCCESS (0x00000001)
    Info      ==== Initializing Computer Name ====
    Info      Generating a random computer name
    Info      No computer name specified, generating a random name.
    Info      Renaming computer to MININT-S90VG8D.
    Info      Acquired profiling mutex
    Info      Service winmgmt disable: 0x00000000
    Info      Service winmgmt stop: 0x00000000
    Info      Service winmgmt enable: 0x00000000
    Info      Released profiling mutex
    Info      STATUS: SUCCESS (0x00000000)
    Info      ==== Initializing Virtual Memory Paging File ====
    Info      No WinPE page file setting specified
    Info      STATUS: SUCCESS (0x00000001)
    Info      ==== Initializing Optional Components ====
    Info      WinPE optional component 'Microsoft-WinPE-WMI' is present
    Info      WinPE optional component 'Microsoft-WinPE-WSH' is present
    Info      STATUS: SUCCESS (0x00000000)
    Info      ==== Initializing Network Access and Applying Configuration ====
    Info      No EnableNetwork unattend setting was specified; the default action for this context is to enable networking support.
    Info      Acquired profiling mutex
    Info      Install MS_MSCLIENT: 0x0004a020
    Info      Install MS_NETBIOS: 0x0004a020
    Info      Install MS_SMB: 0x0004a020
    Info      Install MS_TCPIP6: 0x0004a020
    Info      Install MS_TCPIP: 0x0004a020
    Info      Service dhcp start: 0x00000000
    Info      Service lmhosts start: 0x00000000
    Info      Service ikeext start: 0x00000000
    Info      Service mpssvc start: 0x00000000
    Info      Released profiling mutex
    Info      Spent 1310ms installing network components
    Info      Installing device pci\ven_8086&dev_1502&subsys_05431028 X:\WINDOWS\INF\oem1.inf succeeded
    Info      Spent 10437ms installing network drivers
    Info      QueryAdapterStatus: no operational adapters found.
    Info      Spent 10140ms confirming network initialization; status 0x80004005
    Info      WaitForNetworkToInitialize failed; ignoring error
    Info      STATUS: SUCCESS (0x003d0001)
    Info      ==== Applying Firewall Settings ====
    Info      STATUS: SUCCESS (0x00000001)
    Info      ==== Executing Synchronous User-Provided Commands ====
    Info      STATUS: SUCCESS (0x00000001)
    Info      ==== Executing Asynchronous User-Provided Commands ====
    Info      STATUS: SUCCESS (0x00000001)
    Info      ==== Applying Shutdown Settings ====
    Info      No shutdown setting was specified
    Info      STATUS: SUCCESS (0x00000001)

    This turned out to work for me, too! It was nothing to do with network switch configuration, per se-- or at least I didn't have to change anything on my switch to fix it. Instead I tried fusiongroup's method of getting into the command-line before the WinPE
    boot hit the "Preparing network connections" step, and I repeatedly ipconfig /renewed until suddenly the TS reached the next step of the sequence instead of failing out.
    I also made this an "Available" sequence instead of a "Required" sequence, which I think buys you a little time in terms of offering a GUI in WinPE for the sequence, instead of just trying to run it.
    One last thing: I was running this on a Workgroup machine that is not joined to our domain; I had followed another tutorial to get the client installed on it even though it's outside the domain. Prior to trying the command-line fix fusiongroup gave, I also
    went into Assets and Compliance in Configuration Manager and right-clicked the machine in the list of devices, and found that I had to "Approve" it for management by SCCM. Don't know if that helped as well.
    Sylvie Andrews

  • Task Sequence fails on "Apply Driver Package" when PXE-booting but not with bootable media

    I have an issue where my Task Sequence fails during 'Apply Driver Package' when PXE-booting but works ok when booting from CD or USB-stick. It fails withe error code 0x80070002 and when pressing F8 and checking the ipconfig there's a 169.254.x.x address.
    Somehow it looses it's real ip during the process.
    I'm grateful for any advice!

    Please enable verbose logging for Task sequence, then upload the smsts.log to Skydrive.
    0x80070002 error is too generic, which cannot be used to determine the cause.
    Juke Chou
    TechNet Community Support

  • Throttle CPU utilization during software updates

    Are there any settings to throttle CPU Utilization during software update installation on client computers?  I am deploying updates to test systems currently and noticed that the CPU utilization was being pegged at 100% during the install.  After
    the updates installed, the system returned to normal.

    Also note that ultimately, it is the Windows Update Agent that is installing the update(s) so it's not really within ConfigMgr's scope of control and would happen no matter what method you chose to use to update these systems with Windows Updates which
    leads me to believe these systems have perf issues to begin with. Are they VMs?
    Jason | http://blog.configmgrftw.com

  • Build and capture task sequence stops after apply windows updates

    Hi
    SCCM 2012 SP1 CU4. Deploying Windows 7 SP1.
    Pulling my hair out over this one. I successfully performed a build and capture installing some applications. When I choose to install Windows updates, the updates install, the system reboots then doesn't continue. Applications don't install, image isn't captured.
    I've tired using the default B&C TS and receive the same results. I've amended the TS to as follows, as suggested in a technet forum post: https://social.technet.microsoft.com/Forums/en-US/a535e509-fc6a-483c-bf24-7e2aa064e5b7/deploying-100-of-available-software-updates-during-a-task-sequence?forum=configmanagerosd
    Looking at smsts.log there's errors relating to not accepting the license agreement, but I didn't think this would stop the TS. 
    Can someone point out why the deployment stops?
    https://dl.dropboxusercontent.com/u/23479177/smsts-20141113-182413.log 
    Cheers

    This is very common scenario you´re having! :)
    For OSD and for Capture I always create myown Software Update Group, which lets me totally control, what updates goes to the image and which doesn´t. I then edit membership of update and tag or un-tag update to the group.
    I suggest you do the following:
    1. Create manual Computer record and add it to OSD Capture collection.
    2. Create SUG for OSD Capture and un-tag updates which are listed in KB2894518. But that might not be enough.
    3. Deploy TS to the OSD Capture collection.
    4. Create/modify virtual machine with MAC matching the computer record.
    5. Run PXE and hook Capture TS.

  • Windows 7 64bit Build and Capture Task Sequence keeps failing. Need to Offline Patch

    Hi All,
    I have been having problems running my SCCM 2007 R3 Build and Capture Task Sequence for Windows 7 64bit since MS released the October 2014 patches. (Having problems described in KB2894518, but can't get workaround to work)
    So my next step is to try to apply the patches directly to the install.wim file using dism and "Offline Servicing". I'm hoping this will allow my TS to finish, and also adds the benifit of making my TS much faster to run every month. So I followed
    the steps in
    this post, and injected 165 updates into the install.wim file (extracted from Win7 ISO). Now, I've copied the updated WIM into my Operating System install package and updated the distribution point. But the Install Software Updates step still installs 160
    updates (same as before the Offline patch injection). The only thing that seems faster is that the download of the updates is instantaneous. So it seems like the Offline patch injection just copied the patch installer files to the WIM, but did not actually
    install them.
    I remember reading a post by Niall C. Brady or Jason Sandys about exactly how they inject patches into a WIM, but have been unable to re-locate the post. Does anybody out there have a tried and true method for offline injection of patches into install.wim
    for use with SCCM Build and Capture task sequence? thanks!

    My recommendation would be to use MDT to build your images instead:
    http://technet.microsoft.com/en-us/library/dn744290.aspx
    This will make your life much easier with the patching of the image :)
    You can use Nickolaj's great MDT Factory tool to set up an MDT Build machine from scratch:
    https://gallery.technet.microsoft.com/MDT-Factory-Tool-100-8e68123b
    Blog: www.danielclasson.com/blog |
    LinkedIn:
    Daniel Classon | Twitter: @danielclasson

  • Task Sequence failed to restore captured data from USB drive onto a new machine using UDI task requence

    Hi,
    Environment ConfigMgr 2012 R2
    Replace Scenario: Capture data to a USB external drive and Restore it from USB external drive.
    Steps taken:
    1) Created Computer Association with New computer and Source computer
    2) Deployed UDI replace Task Sequence to Source computer and captured data to a USB external drive
    3) Run UDI Task Sequence from Boot Media to Restore data from USB External drive which had the captured data.
    Issue:
    My task sequence failed to restore data from USB external drive.
    Is there a fix
    Any help is greatly appreciated it. 

    I created a query to see the deployment logs in real time. I see the TS fails when running "Request State Store" task. Here are the logs.
    Severity Type Site code Date / Time System Component Message ID Description
    Error Milestone POK 7/22/2014 4:13:15 PM MININT-P6E4T6G Task Sequence Engine 11141 The task sequence execution engine failed execution of a task sequence. The operating system reported error 1: Incorrect function.
    Error Milestone POK 7/22/2014 4:13:15 PM MININT-P6E4T6G Task Sequence Engine 11135 The task sequence execution engine failed executing the action (Error in the task sequence) in the group (Gather Logs and StateStore on Failure)
    with the error code 1  Action output: [ smsswd.exe ] PackageID = '' BaseVar = '', ContinueOnError='' ProgramName = 'cscript "C:\_SMSTaskSequence\WDPackage\scripts\ztierrormsg.wsf"' SwdAction = '0001' Set command line: Run command line Working dir 'not
    set' Executing command line: Run command line Process completed with exit code 1 Microsoft (R) Windows Script Host Version 5.8 Copyright (C) Microsoft Corporation. All rights reserved.  Microsoft Deployment Toolkit version: 6.2.5019.0 The task sequencer
    log is located at C:\WINDOWS\CCM\Logs\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log. ZTI deployment failed, Return Code = 1 Command line returned 1. The operating system reported error 1: Incorrect function.
    Information Milestone POK 7/22/2014 4:13:14 PM MININT-P6E4T6G Task Sequence Engine 11134 The task sequence execution engine successfully completed the action (Copy Logs) in the group (Gather Logs and StateStore on Failure)
    with exit code 0  Action output: ... 扴捡杫潲湵⹤潬⁧潴尠停䭏偃䍓䵃卐㄰䍜彍潓牵散尤协屄潌獧䍜剏ⵐ䠳䑗塐就瑺獩瑥慢正牧畯摮氮杯潃祰湩⁧㩃坜义佄南䍜䵃䱜杯屳䵓呓䱓杯穜楴慴潴⹯潬⁧潴尠停䭏偃䍓䵃卐㄰䍜彍潓牵散�潌獧䍜剏ⵐ䠳䑗塐就潃祰湩⁧㩃坜义佄南䍜䵃䱜杯屳䵓呓䱓杯作䑓敓畴坰穩牡⹤潬⁧潴尠停䭏偃䍓䵃卐㄰䍜彍潓牵散尤协屄潌獧䍜剏ⵐ䠳䑗塐就协卄瑥灵楗慺摲氮杯潃祰湩⁧㩃坜义佄南停湡桴�潬⁧潴尠停䭏偃䍓䵃卐㄰䍜彍潓牵散尤协屄潌獧䍜剏ⵐ䠳䑗塐就慐瑮敨屲湕瑡整摮䍇潃祰湩⁧潬⁧㩃坜义佄南䍜䵃䱜杯屳䵓呓䱓杯䉜䑄氮杯挠湯整瑮⁳潴尠停䭏偃䍓䵃卐㄰䍜彍潓牵散尤协屄潌�Console
    > Successfully resized the shadow copy storage association Return code from command = 0 Cleaning up default wallpaper registry keys Process completed with exit code 0 zticopylogs processing completed successfully. Command line returned 0.
    Information Milestone POK 7/22/2014 4:13:07 PM MININT-P6E4T6G Task Sequence Engine 11134 The task sequence execution engine successfully completed the action (Move State Store) in the group (Gather Logs and StateStore on Failure)
    with exit code 0  Action output: [ smsswd.exe ] PackageID = '' BaseVar = '', ContinueOnError='' ProgramName = 'cscript.exe "C:\_SMSTaskSequence\WDPackage\scripts\ztimovestatestore.wsf"' SwdAction = '0001' Command line for extension .exe is "%1" %* Set
    command line: Run command lineWorking dir 'not set' Executing command line: Run command line Process completed with exit code 0 Microsoft (R) Windows Script Host Version 5.8 Copyright (C) Microsoft Corporation. All rights reserved.  Microsoft Deployment
    Toolkit version: 6.2.5019.0 The task sequencer log is located at C:\WINDOWS\CCM\Logs\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log. ztimovestatestore processing completed successfully. Command line returned 0.
    Information Milestone POK 7/22/2014 4:13:07 PM MININT-P6E4T6G Task Sequence Engine 11134 The task sequence execution engine successfully completed the action (Gather) in the group (Gather Logs and StateStore on Failure) with
    exit code 0  Action output: ... (BIOS is 'DELL   - 1072009'). Property IsVM is now = False Finished getting virtualization info Connection succeeded to MicrosoftVolumeEncryption There are no encrypted drives Property IsBDE is now = False Processing
    the  phase. Determining theINI file to use. Using COMMAND LINE ARG: Ini file = CustomSettings.ini Finished determining the INI file to use. Added new custom property MYCUSTOMPROPERTY Using from [Settings]: Rule Priority = DEFAULT ------ Processing the
    [DEFAULT] section ------Process completed with exit code 0 ------ Done processing CustomSettings.ini ------ Remapping variables. Property TaskSequenceID is now =  Property DeploymentType is now = NEWCOMPUTER Finished remapping variables. ZTIGather processing
    completed successfully. Command line returned 0 ReleaseSource() for C:\_SMSTaskSequence\Packages\POK0000F. reference count 1 for the source C:\_SMSTaskSequence\Packages\POK0000F before releasing Released the resolved source C:\_SMSTaskSequence\Packages\POK0000F.
    Information Milestone POK 7/22/2014 4:13:03 PM MININT-P6E4T6G Task Sequence Engine 11130 The task sequence execution engine skipped the action (Use Toolkit Package) in the group (Gather Logs and StateStore on Failure) because
    the condition was evaluated to be false.
    Information Milestone POK 7/22/2014 4:13:02 PM MININT-P6E4T6G Task Sequence Engine 11134 The task sequence execution engine successfully completed the action (Set Error Code) in the group (Gather Logs and StateStore on Failure)
    with exit code 0  Action output: Finished with error code 0.
    Information Milestone POK 7/22/2014 4:13:02 PM MININT-P6E4T6G Task Sequence Engine 11124 The task sequence execution engine started the group (Gather Logs and StateStore on Failure).
    Information Milestone POK 7/22/2014 4:13:02 PM MININT-P6E4T6G Task Sequence Engine 11122 The task sequence execution engine skipped the group (Cancelled Wizard Group) because the condition was evaluated to be false.
    Error Milestone POK 7/22/2014 4:13:02 PM MININT-P6E4T6G Task Sequence Engine 11135 The task sequence execution engine failed executing the action (Connect to State Store) in the group (State Restore) with the error code 1 
    Action output: ... ( 0x80070035 ) , trying to connect without username.  The network path was not found.  Unable to connect to
    \\3807000000100000000000:\2fa390ff58558b49c45bf204dfa5717f.  Sleeping for 15 seconds. Unable to connect to share: The network path was notfound. ( 0x80070035 ) , trying to
    connect without username.  The network path was not found.  Unable to connect to
    \\3807000000100000000000:\2fa390ff58558b49c45bf204dfa5717f.  Sleeping for 20 seconds. Unable to connect to share: The network path wasnot found. ( 0x80070035 ) , trying to
    connect without username.  The network path was not found.  Unable to connect to
    \\3807000000100000000000:\2fa390ff58558b49c45bf204dfa5717f.  Sleeping for 25 seconds. Process completed with exit code 1 ERROR - Unable to map a network drive to
    \\3807000000100000000000:\2fa390ff58558b49c45bf204dfa5717f. Unable to connect to 563807000000100000000000:\2fa390ff58558b49c45bf204dfa5717f ZTI ERROR - Non-zero return code by ZTIConnect,
    rc = 1 Command line returned 1. The operating system reported error 1: Incorrect function.
    Warning Milestone POK 7/22/2014 4:11:46 PM MININT-P6E4T6G Task Sequence Engine 11138 The task sequence execution engine ignored execution failure of the action (Request State Store) in the group (State Restore).
    Error Milestone POK 7/22/2014 4:11:46 PM MININT-P6E4T6G Task Sequence Engine 11135 The task sequence execution engine failed executing the action (Request State Store) in the group (State Restore) with the error code 16389 
    Action output: ... etting Media Certificate. Sending request to MP
    http://abcdefg.xyx.xyz.local. Setting message signatures. Setting the authenticator. CLibSMSMessageWinHttpTransport::Send: URL: abcdefg.xyx.xyz.local:80  CCM_POST /ccm_system/requestRequest was successful. migInfoRequestMessage.DoRequest (m_sResponse,true),
    HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdsmpclient\smpclient.cpp,1098) pClientRequestToMP->DoRequest(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2778) ExecuteRestoreRequestToMP(migInfoFromMP),
    HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2903) ExecuteRestoreRequest(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdsmpclient\main.cpp,84) OSDSMPClient finished: 0x00004005 reply from server
    is 'NoReply' ClientRequestToMP::DoRequest failed (0x80004005). ExecuteRestoreRequestToMP failed (0x80004005). ExecuteRestoreRequest failed (0x80004005).. The operating system reported error 1: Incorrect function.

  • Task Sequence Fails while trying to access a folder in PXE

    Hello Guys,
    I am facing issues while PXE.  It fails with below error.
    Logs from server :
    Severity               Type      Site code             Date / Time       
    System Component        Message ID        Description
    Error      Milestone                    2/4/2014 9:49:11 AM               
    Task Sequence Engine   11135    The task sequence execution engine failed executing the action (DiskPart DataDisk) in the group (Install Operating System) with the error code 2147942402  Action output: T=80070047 (e:\nts_sms_fre\sms\framework\tscore\tsconnection.cpp,148)
    Failed to access the share \\server.org\SMSPKGE$\PCK000AA\ with network access account !sAccessibleSource.empty(), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,2392) GetAccessibleLocation(pszSource,
    saResolvedPath, sSourceDirectory, dwFlags, hUserToken), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3168) TS::Utility::ResolveSource(pszPkgID, sPath, 0, hUserToken, sUserName.empty() ? NULL : sUserName.c_str(), sUserName.empty()
    ? NULL : sUserPassword.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\runcommandline.cpp,395) cmd.Execute(pszPkgID, sProgramName, dwCmdLineExitCode), HRESULT=80070002 (e:\nts_sms_fre\sms\client\osdeployment\installsoftware\main.cpp,385)
    Failed to find an available source location Failed to resolve the source for SMS PKGID=PCK000AA, hr=0x80070002 Install Software failed to run command line, hr=0x80070002. The operating system reported error 2147942402: The system cannot find the file specified.
    SMSTG log from PC where it fails :
    Failed to connect to "\\server.ORG\SMSPKGE$\PCK000AA" (71)
    Task Sequence fails only when acccessing one folder and below steps have been tried.
    - Network access account is configured and its working fine for all other secondary site
    - NAA is having access to folder.
    - NAA is added to Server Local Admin Access Group.
    - Deleted folder and Replicated from central
    - Granted everyone access to folder.
    It works only when other Admin Account is updated in place of existing NAA details on primary server. However the same NAA is working fine on all Primary and Secondary servers. Issue is only with one secondary server.
    Its very strange issue!!!
    Waiting for a solution.
    Mukhyaprana

    0x80070047 = "No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept."
    You must have some non-standard policy or restriction applied to the system hosting the share.
    Jason | http://blog.configmgrftw.com

  • Setup windows and ConfigMgr task sequence failing.

    Hi,
    Am trying to create a reference Windows 7 task sequence and the task sequence is failing at the 'Setup Windows and ConfigMgr' task.
    There are a lot of threads regarding this step and in particular that as the machine is in a workgroup it cannot install the SCCM client successfully. As recommended on other posts have added SMSLP= and SMSMP= into the Installation properties.
    The task sequence is still failing and am unable to make much of the logs. 
    Will post the errors if anyone can assist?.

    <![LOG[Microsoft Deployment Toolkit version: 6.1.2373.0]LOG]!><time="09:48:18.771+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="1104" file="runcommandline.cpp:34">
    <![LOG[The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.]LOG]!><time="09:48:18.771+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="1104"
    file="runcommandline.cpp:34">
    <![LOG[Unable to copy log to the network as no SLShare value was specified.]LOG]!><time="09:48:18.771+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="1104" file="runcommandline.cpp:34">
    <![LOG[No system restore needed, WMI object not present.]LOG]!><time="09:48:18.771+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="1104" file="runcommandline.cpp:34">
    <![LOG[Cleaning up default wallpaper registry keys]LOG]!><time="09:48:18.771+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="1104" file="runcommandline.cpp:34">
    <![LOG[zticopylogs processing completed successfully.]LOG]!><time="09:48:18.771+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="1104" file="runcommandline.cpp:34">
    <![LOG[Unable to create WebService class]LOG]!><time="09:48:18.771+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="1104" file="runcommandline.cpp:34">
    <![LOG[Command line returned 0]LOG]!><time="09:48:18.771+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="1104" file="runcommandline.cpp:565">
    <![LOG[Process completed with exit code 0]LOG]!><time="09:48:18.771+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="commandline.cpp:1123">
    <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="09:48:18.771+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="instruction.cxx:3012">
    <![LOG[Successfully completed the action (Copy Logs) with the exit win32 code 0]LOG]!><time="09:48:18.771+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="instruction.cxx:3038">
    <![LOG[MP server http://UK5SYSDBPR01.s3ms.com. Ports 80,443. CRL=false.]LOG]!><time="09:48:18.771+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:5300">
    <![LOG[Setting authenticator]LOG]!><time="09:48:18.787+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:5322">
    <![LOG[Set authenticator in transport]LOG]!><time="09:48:18.787+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:7751">
    <![LOG[Sending StatusMessage]LOG]!><time="09:48:18.787+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="libsmsmessaging.cpp:4025">
    <![LOG[Setting message signatures.]LOG]!><time="09:48:18.803+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:1297">
    <![LOG[Setting the authenticator.]LOG]!><time="09:48:18.803+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:1327">
    <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: UK5SYSDBPR01.s3ms.com:80  CCM_POST /ccm_system/request]LOG]!><time="09:48:18.803+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="libsmsmessaging.cpp:8621">
    <![LOG[Request was succesful.]LOG]!><time="09:48:18.818+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:8956">
    <![LOG[Set a global environment variable _SMSTSLastActionRetCode=0]LOG]!><time="09:48:18.818+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:668">
    <![LOG[Set a global environment variable _SMSTSLastActionSucceeded=true]LOG]!><time="09:48:18.818+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:668">
    <![LOG[Expand a string: %_SMSTSMDataPath%\Logs]LOG]!><time="09:48:18.818+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:782">
    <![LOG[Clear local default environment]LOG]!><time="09:48:18.834+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:807">
    <![LOG[Updated security on object C:\_SMSTaskSequence.]LOG]!><time="09:48:18.896+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:1121">
    <![LOG[Set a global environment variable _SMSTSNextInstructionPointer=140]LOG]!><time="09:48:18.896+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:668">
    <![LOG[Set a TS execution environment variable _SMSTSNextInstructionPointer=140]LOG]!><time="09:48:18.896+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:386">
    <![LOG[Set a global environment variable _SMSTSInstructionStackString=134]LOG]!><time="09:48:18.896+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:668">
    <![LOG[Set a TS execution environment variable _SMSTSInstructionStackString=134]LOG]!><time="09:48:18.896+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:414">
    <![LOG[Save the current environment block]LOG]!><time="09:48:18.896+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:833">
    <![LOG[Successfully save execution state and environment to local hard disk]LOG]!><time="09:48:18.943+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="engine.cxx:255">
    <![LOG[Start executing an instruction. Instruction name: Error in the task sequence. Instruction pointer: 140]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="engine.cxx:117">
    <![LOG[Set a global environment variable _SMSTSCurrentActionName=Error in the task sequence]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:668">
    <![LOG[Set a global environment variable _SMSTSNextInstructionPointer=140]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:668">
    <![LOG[Set a local default variable SMSTSDisableWow64Redirection]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:700">
    <![LOG[Set a local default variable _SMSTSRunCommandLineAsUser]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:700">
    <![LOG[Set a global environment variable _SMSTSLogPath=X:\windows\TEMP\SMSTSLog]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:668">
    <![LOG[Expand a string: smsswd.exe /run: cscript "%deployroot%\scripts\ztierrormsg.wsf"]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:782">
    <![LOG[Expand a string: ]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:782">
    <![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="commandline.cpp:228">
    <![LOG[Set command line: smsswd.exe /run: cscript "%deployroot%\scripts\ztierrormsg.wsf"]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="commandline.cpp:731">
    <![LOG[Start executing the command line: smsswd.exe /run: cscript "%deployroot%\scripts\ztierrormsg.wsf"]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="instruction.cxx:2930">
    <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="instruction.cxx:2959">
    <![LOG[Expand a string: WinPEandFullOS]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:782">
    <![LOG[Executing command line: smsswd.exe /run: cscript "%deployroot%\scripts\ztierrormsg.wsf"]LOG]!><time="09:48:18.959+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="commandline.cpp:827">
    <![LOG[[ smsswd.exe ]]LOG]!><time="09:48:18.974+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="main.cpp:289">
    <![LOG[PackageID = '']LOG]!><time="09:48:18.974+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="main.cpp:318">
    <![LOG[BaseVar = '', ContinueOnError='']LOG]!><time="09:48:18.974+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="main.cpp:319">
    <![LOG[ProgramName = 'cscript "C:\_SMSTaskSequence\WDPackage\scripts\ztierrormsg.wsf"']LOG]!><time="09:48:18.974+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="main.cpp:320">
    <![LOG[SwdAction = '0001']LOG]!><time="09:48:18.974+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="main.cpp:321">
    <![LOG[Set command line: Run command line]LOG]!><time="09:48:18.974+00" date="12-02-2013" component="InstallSoftware" context="" type="0" thread="2000" file="commandline.cpp:731">
    <![LOG[Working dir 'not set']LOG]!><time="09:48:18.974+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="runcommandline.cpp:542">
    <![LOG[Executing command line: Run command line]LOG]!><time="09:48:18.974+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="commandline.cpp:827">
    <![LOG[Process completed with exit code 2147500037]LOG]!><time="09:48:19.037+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="commandline.cpp:1123">
    <![LOG[Microsoft (R) Windows Script Host Version 5.8]LOG]!><time="09:48:19.037+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="runcommandline.cpp:34">
    <![LOG[Copyright (C) Microsoft Corporation. All rights reserved.]LOG]!><time="09:48:19.037+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="runcommandline.cpp:34">
    <![LOG[]LOG]!><time="09:48:19.037+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="runcommandline.cpp:34">
    <![LOG[Microsoft Deployment Toolkit version: 6.1.2373.0]LOG]!><time="09:48:19.037+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="runcommandline.cpp:34">
    <![LOG[The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.]LOG]!><time="09:48:19.037+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000"
    file="runcommandline.cpp:34">
    <![LOG[ZTI deployment failed, Return Code = -2147467259  0x80004005]LOG]!><time="09:48:19.037+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="runcommandline.cpp:34">
    <![LOG[Unable to create WebService class]LOG]!><time="09:48:19.037+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="runcommandline.cpp:34">
    <![LOG[Command line returned 2147500037]LOG]!><time="09:48:19.037+00" date="12-02-2013" component="InstallSoftware" context="" type="1" thread="2000" file="runcommandline.cpp:565">
    <![LOG[Process completed with exit code 2147500037]LOG]!><time="09:48:19.037+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="commandline.cpp:1123">
    <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="09:48:19.037+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="instruction.cxx:3012">
    <![LOG[Failed to run the action: Error in the task sequence. 
    Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="09:48:19.037+00" date="12-02-2013" component="TSManager" context="" type="3" thread="1048" file="instruction.cxx:3103">
    <![LOG[MP server http://UK5SYSDBPR01.s3ms.com. Ports 80,443. CRL=false.]LOG]!><time="09:48:19.037+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:5300">
    <![LOG[Setting authenticator]LOG]!><time="09:48:19.052+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:5322">
    <![LOG[Set authenticator in transport]LOG]!><time="09:48:19.052+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:7751">
    <![LOG[Sending StatusMessage]LOG]!><time="09:48:19.068+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="libsmsmessaging.cpp:4025">
    <![LOG[Setting message signatures.]LOG]!><time="09:48:19.068+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:1297">
    <![LOG[Setting the authenticator.]LOG]!><time="09:48:19.068+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:1327">
    <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: UK5SYSDBPR01.s3ms.com:80  CCM_POST /ccm_system/request]LOG]!><time="09:48:19.068+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="libsmsmessaging.cpp:8621">
    <![LOG[Request was succesful.]LOG]!><time="09:48:19.083+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:8956">
    <![LOG[Set a global environment variable _SMSTSLastActionRetCode=-2147467259]LOG]!><time="09:48:19.083+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:668">
    <![LOG[Set a global environment variable _SMSTSLastActionSucceeded=false]LOG]!><time="09:48:19.083+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:668">
    <![LOG[Clear local default environment]LOG]!><time="09:48:19.083+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:807">
    <![LOG[Let the parent group (Gather Logs and StateStore on Failure) decides whether to continue execution]LOG]!><time="09:48:19.083+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="instruction.cxx:3212">
    <![LOG[The execution of the group (Gather Logs and StateStore on Failure) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)]LOG]!><time="09:48:19.083+00" date="12-02-2013" component="TSManager" context="" type="3" thread="1048" file="instruction.cxx:2425">
    <![LOG[Failed to run the last action: Error in the task sequence. Execution of task sequence failed.
    Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="09:48:19.083+00" date="12-02-2013" component="TSManager" context="" type="3" thread="1048" file="engine.cxx:214">
    <![LOG[MP server http://UK5SYSDBPR01.s3ms.com. Ports 80,443. CRL=false.]LOG]!><time="09:48:19.099+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:5300">
    <![LOG[Setting authenticator]LOG]!><time="09:48:19.099+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:5322">
    <![LOG[Set authenticator in transport]LOG]!><time="09:48:19.099+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:7751">
    <![LOG[Sending StatusMessage]LOG]!><time="09:48:19.115+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="libsmsmessaging.cpp:4025">
    <![LOG[Setting message signatures.]LOG]!><time="09:48:19.115+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:1297">
    <![LOG[Setting the authenticator.]LOG]!><time="09:48:19.115+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:1327">
    <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: UK5SYSDBPR01.s3ms.com:80  CCM_POST /ccm_system/request]LOG]!><time="09:48:19.115+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="libsmsmessaging.cpp:8621">
    <![LOG[Request was succesful.]LOG]!><time="09:48:19.146+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:8956">
    <![LOG[Executing command line: X:\windows\system32\cmd.exe /k]LOG]!><time="09:48:26.618+00" date="12-02-2013" component="TSBootShell" context="" type="1" thread="744" file="bootshell.cpp:857">
    <![LOG[The command completed successfully.]LOG]!><time="09:48:26.618+00" date="12-02-2013" component="TSBootShell" context="" type="1" thread="744" file="bootshell.cpp:939">
    <![LOG[Successfully launched command shell.]LOG]!><time="09:48:26.618+00" date="12-02-2013" component="TSBootShell" context="" type="1" thread="744" file="bootshell.cpp:430">
    <![LOG[Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanager.cpp,866)]LOG]!><time="10:03:31.818+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048"
    file="tsmanager.cpp:866">
    <![LOG[Task Sequence Engine failed! Code: enExecutionFail]LOG]!><time="10:03:31.818+00" date="12-02-2013" component="TSManager" context="" type="3" thread="1048" file="tsmanager.cpp:866">
    <![LOG[****************************************************************************]LOG]!><time="10:03:31.818+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="tsmanager.cpp:889">
    <![LOG[Task sequence execution failed with error code 80004005]LOG]!><time="10:03:31.818+00" date="12-02-2013" component="TSManager" context="" type="3" thread="1048" file="tsmanager.cpp:890">
    <![LOG[Cleaning Up.]LOG]!><time="10:03:31.818+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="tsmanager.cpp:637">
    <![LOG[Removing Authenticator]LOG]!><time="10:03:31.818+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="tsmanager.cpp:648">
    <![LOG[shKey.DeleteValue( c_szRegValue_SecurityToken ), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\ccmutillib\ccmutillib.cpp,1652)]LOG]!><time="10:03:31.818+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="ccmutillib.cpp:1652">
    <![LOG[Cleaning up task sequence folder]LOG]!><time="10:03:31.818+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:1746">
    <![LOG[Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing.]LOG]!><time="10:03:32.692+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="ccmfile.cpp:1056">
    <![LOG[hr, HRESULT=80070091 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmfile.cpp,1218)]LOG]!><time="10:03:32.863+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="ccmfile.cpp:1218">
    <![LOG[Failed to delete directory 'C:\_SMSTaskSequence']LOG]!><time="10:03:32.863+00" date="12-02-2013" component="TSManager" context="" type="2" thread="1048" file="ccmfile.cpp:1218">
    <![LOG[(dwRet = ::SetNamedSecurityInfoW ((WCHAR*) pszObjectName, objectType, OWNER_SECURITY_INFORMATION, pOwnerSID, NULL, NULL, NULL)) == ERROR_SUCCESS, HRESULT=80070005 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,6090)]LOG]!><time="10:03:32.863+00"
    date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="utils.cpp:6090">
    <![LOG[SetNamedSecurityInfo() failed.]LOG]!><time="10:03:32.863+00" date="12-02-2013" component="TSManager" context="" type="3" thread="1048" file="utils.cpp:6090">
    <![LOG[SetObjectOwner() failed. 0x80070005.]LOG]!><time="10:03:32.863+00" date="12-02-2013" component="TSManager" context="" type="3" thread="1048" file="utils.cpp:6102">
    <![LOG[SetObjectOwner (szFName, SE_FILE_OBJECT, c_szAdministrators), HRESULT=80070005 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,6187)]LOG]!><time="10:03:32.863+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048"
    file="utils.cpp:6187">
    <![LOG[RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005.]LOG]!><time="10:03:32.879+00" date="12-02-2013" component="TSManager" context="" type="3" thread="1048" file="utils.cpp:6231">
    <![LOG[RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence]LOG]!><time="10:03:32.879+00" date="12-02-2013" component="TSManager" context="" type="2" thread="1048" file="utils.cpp:6315">
    <![LOG[Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...]LOG]!><time="10:03:32.879+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="resolvesource.cpp:519">
    <![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,521)]LOG]!><time="10:03:32.879+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="resolvesource.cpp:521">
    <![LOG[Successfully unregistered Task Sequencing Environment COM Interface.]LOG]!><time="10:03:32.879+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="environmentlib.cpp:886">
    <![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="10:03:32.879+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="commandline.cpp:228">
    <![LOG[Set command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="10:03:32.879+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="commandline.cpp:731">
    <![LOG[Executing command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="10:03:32.879+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="commandline.cpp:827">
    <![LOG[==========[ TsProgressUI started in process 1728 ]==========]LOG]!><time="10:03:32.879+00" date="12-02-2013" component="TsProgressUI" context="" type="1" thread="948" file="winmain.cpp:330">
    <![LOG[Command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="10:03:32.879+00" date="12-02-2013" component="TsProgressUI" context="" type="0" thread="948" file="winmain.cpp:332">
    <![LOG[Unregistering COM classes]LOG]!><time="10:03:32.879+00" date="12-02-2013" component="TsProgressUI" context="" type="1" thread="948" file="winmain.cpp:204">
    <![LOG[Unregistering class objects]LOG]!><time="10:03:32.879+00" date="12-02-2013" component="TsProgressUI" context="" type="1" thread="948" file="winmain.cpp:495">
    <![LOG[Shutdown complete.]LOG]!><time="10:03:32.879+00" date="12-02-2013" component="TsProgressUI" context="" type="1" thread="948" file="winmain.cpp:512">
    <![LOG[Process completed with exit code 0]LOG]!><time="10:03:32.894+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="commandline.cpp:1123">
    <![LOG[Successfully unregistered TS Progress UI.]LOG]!><time="10:03:32.894+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:2320">
    <![LOG[g_TSManager.Run(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanager.cpp,725)]LOG]!><time="10:03:32.894+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="tsmanager.cpp:725">
    <![LOG[::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,261)]LOG]!><time="10:03:32.894+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048"
    file="utils.cpp:261">
    <![LOG[RegQueryValueExW failed for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="10:03:32.894+00" date="12-02-2013" component="TSManager" context="" type="2" thread="1048" file="utils.cpp:261">
    <![LOG[GetTsRegValue() failed. 0x80070002.]LOG]!><time="10:03:32.894+00" date="12-02-2013" component="TSManager" context="" type="2" thread="1048" file="utils.cpp:279">
    <![LOG[End program: ]LOG]!><time="10:03:32.894+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="tsmanager.cpp:764">
    <![LOG[Error Task Sequence Manager failed to execute task sequence. Code 0x80004005]LOG]!><time="10:03:32.894+00" date="12-02-2013" component="TSManager" context="" type="3" thread="1048" file="tsmanager.cpp:768">
    <![LOG[Sending error status message]LOG]!><time="10:03:32.894+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="tsmanager.cpp:769">
    <![LOG[MP server http://UK5SYSDBPR01.s3ms.com. Ports 80,443. CRL=false.]LOG]!><time="10:03:32.894+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:5300">
    <![LOG[Setting authenticator]LOG]!><time="10:03:32.910+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:5322">
    <![LOG[Set authenticator in transport]LOG]!><time="10:03:32.910+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:7751">
    <![LOG[Sending StatusMessage]LOG]!><time="10:03:32.941+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="libsmsmessaging.cpp:4025">
    <![LOG[Setting message signatures.]LOG]!><time="10:03:32.941+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:1297">
    <![LOG[Setting the authenticator.]LOG]!><time="10:03:32.941+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:1327">
    <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: UK5SYSDBPR01.s3ms.com:80  CCM_POST /ccm_system/request]LOG]!><time="10:03:32.941+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="libsmsmessaging.cpp:8621">
    <![LOG[Request was succesful.]LOG]!><time="10:03:32.988+00" date="12-02-2013" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:8956">
    <![LOG[Finalize logging request ignored from process 1044]LOG]!><time="10:03:32.988+00" date="12-02-2013" component="TSManager" context="" type="1" thread="1048" file="tslogging.cpp:1737">
    <![LOG[Process completed with exit code 2147500037]LOG]!><time="10:03:32.988+00" date="12-02-2013" component="TSMBootstrap" context="" type="1" thread="824" file="commandline.cpp:1123">
    <![LOG[Task Sequence Manager returned code 0x80004005]LOG]!><time="10:03:32.988+00" date="12-02-2013" component="TSMBootstrap" context="" type="1" thread="824" file="tsmediawizardcontrol.cpp:2136">
    <![LOG[ThreadToResolveAndExecuteTaskSequence returned code 0x00000000]LOG]!><time="10:03:33.004+00" date="12-02-2013" component="TSMBootstrap" context="" type="1" thread="988" file="tsmediaresolveprogresspage.cpp:221">
    <![LOG[ResolveProgressPage::OnWizardNext()]LOG]!><time="10:03:33.004+00" date="12-02-2013" component="TSMBootstrap" context="" type="0" thread="988" file="tsmediaresolveprogresspage.cpp:113">
    <![LOG[Activating Finish Page.]LOG]!><time="10:03:33.004+00" date="12-02-2013" component="TSMBootstrap" context="" type="0" thread="988" file="tsmediafinishpage.cpp:107">
    <![LOG[Exiting with return code 0x00000000]LOG]!><time="10:03:33.004+00" date="12-02-2013" component="TSMBootstrap" context="" type="1" thread="988" file="tsmbootstrap.cpp:1195">
    <![LOG[Execution complete.]LOG]!><time="10:03:33.019+00" date="12-02-2013" component="TSBootShell" context="" type="1" thread="756" file="bootshell.cpp:690">
    <![LOG[hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515)]LOG]!><time="10:03:33.019+00" date="12-02-2013" component="TSBootShell" context="" type="0" thread="756" file="environmentscope.cpp:515">
    <![LOG[m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337)]LOG]!><time="10:03:33.019+00" date="12-02-2013" component="TSBootShell" context="" type="0" thread="756" file="environmentlib.cpp:337">
    <![LOG[this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,549)]LOG]!><time="10:03:33.019+00" date="12-02-2013" component="TSBootShell" context="" type="0" thread="756" file="environmentlib.cpp:549">
    <![LOG[::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,261)]LOG]!><time="10:03:33.019+00" date="12-02-2013" component="TSBootShell" context="" type="0" thread="756"
    file="utils.cpp:261">
    <![LOG[RegQueryValueExW failed for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="10:03:33.019+00" date="12-02-2013" component="TSBootShell" context="" type="2" thread="756" file="utils.cpp:261">
    <![LOG[GetTsRegValue() failed. 0x80070002.]LOG]!><time="10:03:33.019+00" date="12-02-2013" component="TSBootShell" context="" type="2" thread="756" file="utils.cpp:279">
    <![LOG[End program: ]LOG]!><time="10:03:33.019+00" date="12-02-2013" component="TSBootShell" context="" type="1" thread="756" file="bootshell.cpp:722">
    <![LOG[Finalizing logging from process 740]LOG]!><time="10:03:33.019+00" date="12-02-2013" component="TSBootShell" context="" type="1" thread="756" file="tslogging.cpp:1741">
    <![LOG[Finalizing logs to root of first available drive]LOG]!><time="10:03:33.019+00" date="12-02-2013" component="TSBootShell" context="" type="1" thread="756" file="tslogging.cpp:1583">
    <![LOG[Successfully finalized logs to C:\SMSTSLog]LOG]!><time="10:03:33.035+00" date="12-02-2013" component="TSBootShell" context="" type="1" thread="756" file="tslogging.cpp:1640">
    <![LOG[Cleaning up task sequencing logging configuration.]LOG]!><time="10:03:33.035+00" date="12-02-2013" component="TSBootShell" context="" type="0" thread="756" file="tslogging.cpp:584">

  • MDT Capture Task Sequence not working correctly

    Hello All<o:p></o:p>
    I need some help to tell me what I am doing wrong. I am using Hyper V and trying to capture a image of Windows 7 x64. From within the OS I run the
    Litetouch.wsf from the deployment share. I get the normal MDT Wizard windows. I pick my capture task sequence and everything looks like it is running fine sys prep happens and I but back into windows PE I start to process the rules again and I am taken
    back to the Select task sequence screen in WinPE.  If I pick the capture task sequence again the deployment fails. <o:p></o:p>

    (posting for anyone else that found this page, this was my fix)
    I had the same problem as the initial poster apart from what I wanted to capture was a 'real' pc.  The reason my 'capture' task sequence wasn't booting into WinPE from the local disk and continuing on with the capture was because the local disk was
    being wiped when the boot wim - LiteTouchPE_x64.wim, was being run. 
    A few weeks prior to me wanting to capture a PC I'd been working out how to stop the occasional error when you boot a PC off the WDS server - “The Task Sequence Has Been Suspended”.  I was particularly interested in stopping this error as I want to
    remotely start a Win7 install on a PC, this error would stop the install happening but I wouldn't see this error and end up visiting the PC only to find the install hadn't really started.  After googling around, I found a page that explains how to edit
    the unattend.xml file in the boot image - LiteTouchPE_x64.wim, in the xml file to run the command wscript.exe X:\Deploy\Scripts\LTICleanup.wsf.  Sounded good so I done what the page said (myitforum.com/cs2/blogs/cnackers/archive/2010/10/20/microsoft-deployment-toolkit-lite-touch-lti-the-task-sequence-has-been-suspended.aspx)
    but it didn't stop the message appearing.  In the end I fixed this problem by adding the line 'SkipWizard=YES' in my customsettings.ini file.  I didn't remove the LTICleanup.wsf from unattend.xml, it didn't seem to do any harm, that was until I tried
    to capture a PC.
    When I ran though my 'sysprep and capture' task sequence, the PC would sysprep ok and then reboot, ready to capture it.  Instead of the 'capturing a WIM file' sequence I was expecting to see, I, like the original posted got shown the list of available
    task sequences window.  If you try again to run the capture sequence, it will fail as this has to be started in a running Windows environment, not in WinPE.  After several hours wondering what is going wrong, I dawned on me what was going wrong,
    the LTICleanup.wsf was being run when the boot image was being run and wiping my disk, a disk that was ready to run an existing task sequence, the capture sequence, no wonder it was failing.  Removing the LTICleanup.wsf command from within unattend.xml
    or rebuilding the boot image (by running 'Update Deployment Share' within MDT 2010) fixed the problem, the capture now worked.
    Hopefully this will help someone else like me who was wondering what was going wrong with a capture.

  • Error 16389 running a Task Sequence to install software

    We've run into multiple WinXPProSP3 computers generating error code 16389 when trying to run a TS.  After searching on Google, we found this, 
    http://blogs.technet.com/b/smsandmom/archive/2007/10/29/sccm-2007-task-sequence-fails-drive-letter-not-displayed.aspx
    , which led to another article to modify a RegKey,  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318} , to add a key of UpperFilters, with a value of PartMgr.  The key WAS missing on the machines with
    the error, and, adding that key and value DOES fix the problem.  This key and value seem to be default for the OS.
    However, searching Google for that RegKey has a LOT of suggestions to delete that key and value, due to issues with USB Thumbdrives and iPods not being seen when plugged in--so, it seems that there may be a conflict.
    Does anyone know of a fix for Error 16389 without having to add that key, if it's going to cause other problems?
    Thanks.

    Hi,
    Will you please past the detailed errors in the smsts.log?
    From your description your are using TS to install software right?
    If so you should first make sure this software package meats the following requirement when it was deployed through TS:
    this program can be installed under local system account.
    this program can be installed without any user interaction (such as: press next button).
    this program will not force computer reboot, it allows sccm ts to manage the reboot.
    If your OSD TS return 16389 exit code, you can try to change the volume license keys. Because once i have seem this error and it was solved by changing the volume license key.
    Hope this will help.
    Thanks

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

Maybe you are looking for

  • How long should I have to wait before I get a spee...

    I have had weeks of problems with slow broadband issues due to a line fault which only shows when it is wet. They have appeared to fix the problem on Friday at long last as I did not lose my line when it rained today but my speed has remained between

  • "Preview," how to change font size for when you "fill in the blanks" in a pdf file?

    In the pdf reader, "PREVIEW," I specifically want to find out how to change the font size for "fill in the blanks" information. They're usually huge and i just simply want to make them smaller.  As a complete aside, is there a keyboard shortcut for b

  • Customer Service/Care, Really?

    On February 13,2014, I bought my son an Apple 5c phone and had no problems with it at.   On June 20,2014, my son went to a basketball camp and came back to the dorms to find his phone smashed to pieces.  When he got home, I said don't worry I will ju

  • PI-sheet process in sap

    Dear all, By using help portal i go through-ed Pi sheet process I understood the  concept of pi sheet process But i am little bit confused how to process this PI sheet in sap Could you please guide me how to process pi sheet in sap? or else any parti

  • Ruby and Mysql and Nmap

    I am trying to create a table name in a mysql database using ruby scripts. The name of the table should be the current date. this is how i tried to do it, but didnt work: in the ruby code: TOS = Time.now.localtime.strftime("%Y-%m-%d_#{Time.now.hour}: