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

Similar Messages

Firewire Drive shows in Startup Disk -- But not with Option

I just added a new firewire backup drive. It's the only ext. drive attached. I ran SuperDuper to make a bootable clone of my startup drive. The drive shows up in Startup Disk, with the proper OS, 10.4.11, same as my int. drive.
But when I restart and hold down the option key, only my int. drive shows up.
What do you think is going on?
Thanks

From Western Digital's support web page [HERE|http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/stdadp.php?pfaqid=1715]:
====
Power PC based Macintosh computers are unable to boot to a My Book external hard drive.
Question
Why am I unable to boot to a WD My Book external hard drive using a Power PC (PPC) Based Macintosh computer?
Answer
Problem:
Power PC based Macintosh computer systems are unable to boot to the following My Book external hard drive:
* My Book Pro II Edition
* My Book Premium II Edition
* My Book Home Edition
* My Book Studio Edition
Intel Macintosh computers are not affected by this issue and are able to be booted from My Book external hard drives if the partition on the drive has been setup as a GUID partition scheme.
Cause:
This issue is a Macintosh bug cause by the Mac ROM code of the computer and how it attempts to boot from the first SCSI LUN it detects (LUN 0). In the case of the aforementioned hard drives, the LUN 0 device is dedicated to the button board and safe removal tools of the hard drive case and not the internal hard drive, thus causing booting to be impossible.
Resolution:
There is currently no resolution to this issue. If a resolution is found by Apple, this answer will be updated with this information.
=====
Unbelievably, they blame Apple for the problem.

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

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

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

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.

Drivers - Can you do both "Apply Driver Package" and "Auto Apply Device Drivers - PNP" in the same Task Seqeunce ?

Hi All,
It has been mentioned to be that it is possible to have both "Apply Driver Package" and "Auto Apply Device Drivers - PNP' " specified in the same task sequence, with some kind of logic specified that if the Apply Driver Package step does
not run due to the hardware wmi query not being valid then the 'Apply Device Drivers -PNP' will run instead. Vice-versa - if the "Apply Driver Package" wmi query is correct and driver package applied then the 'Auto Apply Device Drivers -PNP'
will not run and be skipped.
Is this possible ?
I can't seem to find any documentation or reference indication this can be done. :-(
Many thanks everyone..

To add some info here, note that the end result of both tasks is the same. Neither actually *installs* drivers in any way. Both simply copy the drivers to the target system and inject them into the image being deployed where they are then available to Windows
Setup (which runs during the Setup Windows and ConfigMgr task) to install based upon the Windows Setup standard PNP detection.
Thus, using both task types, depending upon what is in the driver packages and what is detected by the OSD PNP detection (which differs slightly from the OS PNP which is far more complex and has been described as a "black art"), potentially injects
more drivers into the image potentially making more drivers available to Windows Setup. This could of course increase your deployment time.
I've thought about this approach before and it is technically valid, but I've never had to resort to it. I've always just made sure that the drivers packages are complete. If you're trying to address the scenario of hardware without a explicit driver package,
I could see it working but I could also see it causing problems because drivers are weird. In general, I would recommend always testing new hardware and anything not accounted for is considered unsupported.
Jason | http://blog.configmgrftw.com | @jasonsandys

Task sequence failed with error 80070002

Dears,
I'm trying deploy OSD, it was working since yesterday but from today I'm facing a problem it's fails with the above error, i got the log file smsts and here it is
Set command line: "OSDApplyOS.exe" /data:BHN00018,1 /target:0,1
ApplyOperatingSystem 3/27/2013 3:05:22 PM
1828 (0x0724)
Adding logical drive: C: ApplyOperatingSystem
3/27/2013 3:05:22 PM 1828 (0x0724)
Skipping non-local logical drive: E: ApplyOperatingSystem
3/27/2013 3:05:22 PM 1828 (0x0724)
Adding logical drive: S: ApplyOperatingSystem
3/27/2013 3:05:22 PM 1828 (0x0724)
Skipping non-local logical drive: X: ApplyOperatingSystem
3/27/2013 3:05:22 PM 1828 (0x0724)
The volume S:\ exists and is a local hard drive.
ApplyOperatingSystem 3/27/2013 3:05:22 PM
1828 (0x0724)
The volume S:\ is using a valid file system.
ApplyOperatingSystem 3/27/2013 3:05:22 PM
1828 (0x0724)
Windows target partition is 0-1, driver letter is S:\
ApplyOperatingSystem 3/27/2013 3:05:22 PM
1828 (0x0724)
Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL'
ApplyOperatingSystem 3/27/2013 3:05:22 PM
1828 (0x0724)
The machine does not have a local client cache.
ApplyOperatingSystem 3/27/2013 3:05:22 PM
1828 (0x0724)
ResolveSource flags: 0x00000000 ApplyOperatingSystem
3/27/2013 3:05:22 PM 1828 (0x0724)
SMSTSPersistContent: . The content for package BHN00018 will be persisted
ApplyOperatingSystem 3/27/2013 3:05:22 PM
1828 (0x0724)
DownloadOnDemand flag is true. Attempting to download content locally for Package BHN00018..
ApplyOperatingSystem 3/27/2013 3:05:22 PM
1828 (0x0724)
Package Flags: 0x1000000 ApplyOperatingSystem
3/27/2013 3:05:22 PM 1828 (0x0724)
GetDirectoryListing() entered ApplyOperatingSystem
3/27/2013 3:05:22 PM 1828 (0x0724)
Initializing HTTP transport. ApplyOperatingSystem
3/27/2013 3:05:22 PM 1828 (0x0724)
Setting URL = http://PRBAHVSSCCM.ARABBANKING.LOCAL/SMS_DP_SMSPKG$/BHN00018.
ApplyOperatingSystem 3/27/2013 3:05:22 PM
1828 (0x0724)
Address=http://PRBAHVSSCCM.ARABBANKING.LOCAL, Scheme=http, Object=/SMS_DP_SMSPKG$/BHN00018, Port=80.
ApplyOperatingSystem 3/27/2013 3:05:22 PM
1828 (0x0724)
Setting Authenticator. ApplyOperatingSystem
3/27/2013 3:05:22 PM 1828 (0x0724)
Set authenticator in transport ApplyOperatingSystem
3/27/2013 3:05:22 PM 1828 (0x0724)
WinHttp credentials set ApplyOperatingSystem
3/27/2013 3:05:22 PM 1828 (0x0724)
CLibSMSMessageWinHttpTransport::Send: URL: PRBAHVSSCCM.ARABBANKING.LOCAL:80 PROPFIND /SMS_DP_SMSPKG$/BHN00018
ApplyOperatingSystem 3/27/2013 3:05:22 PM
1828 (0x0724)
401 - Authentication failure on request with anonymous access, retrying with context credentials.
ApplyOperatingSystem 3/27/2013 3:05:22 PM
1828 (0x0724)
Using thread token for request ApplyOperatingSystem
3/27/2013 3:05:22 PM 1828 (0x0724)
401 - Authentication failure on request with context credentials, retrying with supplied credentials.
ApplyOperatingSystem 3/27/2013 3:05:22 PM
1828 (0x0724)
Request was succesful. ApplyOperatingSystem
3/27/2013 3:05:22 PM 1828 (0x0724)
DAV response string is:
<?xml version="1.0" encoding="utf-8" ?><D:multistatus xmlns:D="DAV:"><D:response><D:href>http://PRBAHVSSCCM.ARABBANKING.LOCAL/SMS_DP_SMSPKG$/sccm?/BHN00018/</D:href><D:propstat><D:status>HTTP/1.1
200 OK</D:status><D:prop><D:getcontenttype/><D:supportedlock/><D:getetag/><D:creationdate/><D:iscollection>1</D:iscollection><D:resourcetype><D:collection/></D:resourcetype><D:ishidden>0</D:ishidden><D:displayname>http://PRBAHVSSCCM.ARABBANKING.LOCAL/SMS_DP_SMSPKG$/sccm?/BHN00018/</D:displayname><D:getlastmodified></D:getlastmodified><D:getcontentlanguage/><D:getcontentlength>0</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://PRBAHVSSCCM.ARABBANKING.LOCAL/SMS_DP_SMSPKG$/BHN00018/sccm?/Win7-x86-BasicApps.wim</D:href><D:propstat><D:status>HTTP/1.1
200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>http://PRBAHVSSCCM.ARABBANKING.LOCAL/SMS_DP_SMSPKG$/BHN00018/sccm?/Win7-x86-BasicApps.wim</D:displayname><D:getlastmodified>Thu,
21 Mar 2013 09:21:33 GMT</D:getlastmodified><D:getcontentlength>4984262577</D:getcontentlength></D:prop></D:propstat></D:response></D:multistatus>
ApplyOperatingSystem 3/27/2013 3:05:22 PM
1828 (0x0724)
List of files to be downloaded ApplyOperatingSystem
3/27/2013 3:05:22 PM 1828 (0x0724)
File: http://PRBAHVSSCCM.ARABBANKING.LOCAL:80/SMS_DP_SMSPKG$/BHN00018/sccm?/Win7-x86-BasicApps.wim
ApplyOperatingSystem 3/27/2013 3:05:22 PM
1828 (0x0724)
GetDirectoryListing() successfully completed
ApplyOperatingSystem 3/27/2013 3:05:22 PM
1828 (0x0724)
Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL'
ApplyOperatingSystem 3/27/2013 3:05:22 PM
1828 (0x0724)
dwStatusCode >= 200 && dwStatusCode <= 299, HRESULT=801901f4 (e:\nts_sccm_release\sms\framework\tscore\downloadcontent.cpp,1304)
ApplyOperatingSystem 3/27/2013 3:05:23 PM
1828 (0x0724)
WinHttpQueryHeaders() returns status code 500 (Internal Server Error)
ApplyOperatingSystem 3/27/2013 3:05:23 PM
1828 (0x0724)
SendWinHttpRequest failed. 801901f4. ApplyOperatingSystem
3/27/2013 3:05:23 PM 1828 (0x0724)
SendWinHttpRequest (hSession, hConnect, hRequest, sRequest.c_str(), 0, bUseSSL, ullFileSize, LastGoodCredentialsType), HRESULT=801901f4 (e:\nts_sccm_release\sms\framework\tscore\downloadcontent.cpp,1542)
ApplyOperatingSystem 3/27/2013 3:05:23 PM
1828 (0x0724)
DownloadFile failed. 801901f4. ApplyOperatingSystem
3/27/2013 3:05:23 PM 1828 (0x0724)
DownloadFile (hSession, hConnect, sSourceFile.c_str(), sDestinationFile.c_str(), ulTotalSizeRequired, ulDownLoaded, LastGoodCredentialsType, bUseSSL), HRESULT=801901f4 (e:\nts_sccm_release\sms\framework\tscore\downloadcontent.cpp,1648)
ApplyOperatingSystem 3/27/2013 3:05:23 PM
1828 (0x0724)
Error downloading file from http://PRBAHVSSCCM.ARABBANKING.LOCAL:80/SMS_DP_SMSPKG$/BHN00018/sccm?/Win7-x86-BasicApps.wim to C:\_SMSTaskSequence\Packages\BHN00018\Win7-x86-BasicApps.wim
ApplyOperatingSystem
3/27/2013 3:05:23 PM 1828 (0x0724)
DownloadFiles failed. 801901f4. ApplyOperatingSystem
3/27/2013 3:05:23 PM 1828 (0x0724)
DownloadFiles (setDirs, setFiles, sDestination.c_str(), bUseSSL), HRESULT=801901f4 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,2523)
ApplyOperatingSystem 3/27/2013 3:05:23 PM
1828 (0x0724)
Retrying download... ApplyOperatingSystem
3/27/2013 3:05:23 PM 1828 (0x0724)
GetDirectoryListing() entered ApplyOperatingSystem
3/27/2013 3:05:26 PM 1828 (0x0724)
Initializing HTTP transport. ApplyOperatingSystem
3/27/2013 3:05:26 PM 1828 (0x0724)
Setting URL = http://PRBAHVSSCCM.ARABBANKING.LOCAL/SMS_DP_SMSPKG$/BHN00018.
ApplyOperatingSystem 3/27/2013 3:05:26 PM
1828 (0x0724)
Address=http://PRBAHVSSCCM.ARABBANKING.LOCAL, Scheme=http, Object=/SMS_DP_SMSPKG$/BHN00018, Port=80.
ApplyOperatingSystem 3/27/2013 3:05:26 PM
1828 (0x0724)
Setting Authenticator. ApplyOperatingSystem
3/27/2013 3:05:26 PM 1828 (0x0724)
Set authenticator in transport ApplyOperatingSystem
3/27/2013 3:05:26 PM 1828 (0x0724)
WinHttp credentials set ApplyOperatingSystem
3/27/2013 3:05:26 PM 1828 (0x0724)
CLibSMSMessageWinHttpTransport::Send: URL: PRBAHVSSCCM.ARABBANKING.LOCAL:80 PROPFIND /SMS_DP_SMSPKG$/BHN00018
ApplyOperatingSystem 3/27/2013 3:05:26 PM
1828 (0x0724)
401 - Authentication failure on request with anonymous access, retrying with context credentials.
ApplyOperatingSystem 3/27/2013 3:05:26 PM
1828 (0x0724)
Using thread token for request ApplyOperatingSystem
3/27/2013 3:05:26 PM 1828 (0x0724)
401 - Authentication failure on request with context credentials, retrying with supplied credentials.
ApplyOperatingSystem 3/27/2013 3:05:26 PM
1828 (0x0724)
Request was succesful. ApplyOperatingSystem
3/27/2013 3:05:26 PM 1828 (0x0724)
DAV response string is:
<?xml version="1.0" encoding="utf-8" ?><D:multistatus xmlns:D="DAV:"><D:response><D:href>http://PRBAHVSSCCM.ARABBANKING.LOCAL/SMS_DP_SMSPKG$/sccm?/BHN00018/</D:href><D:propstat><D:status>HTTP/1.1
200 OK</D:status><D:prop><D:getcontenttype/><D:supportedlock/><D:getetag/><D:creationdate/><D:iscollection>1</D:iscollection><D:resourcetype><D:collection/></D:resourcetype><D:ishidden>0</D:ishidden><D:displayname>http://PRBAHVSSCCM.ARABBANKING.LOCAL/SMS_DP_SMSPKG$/sccm?/BHN00018/</D:displayname><D:getlastmodified></D:getlastmodified><D:getcontentlanguage/><D:getcontentlength>0</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://PRBAHVSSCCM.ARABBANKING.LOCAL/SMS_DP_SMSPKG$/BHN00018/sccm?/Win7-x86-BasicApps.wim</D:href><D:propstat><D:status>HTTP/1.1
200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>http://PRBAHVSSCCM.ARABBANKING.LOCAL/SMS_DP_SMSPKG$/BHN00018/sccm?/Win7-x86-BasicApps.wim</D:displayname><D:getlastmodified>Thu,
21 Mar 2013 09:21:33 GMT</D:getlastmodified><D:getcontentlength>4984262577</D:getcontentlength></D:prop></D:propstat></D:response></D:multistatus>
ApplyOperatingSystem 3/27/2013 3:05:26 PM
1828 (0x0724)
List of files to be downloaded ApplyOperatingSystem
3/27/2013 3:05:26 PM 1828 (0x0724)
File: http://PRBAHVSSCCM.ARABBANKING.LOCAL:80/SMS_DP_SMSPKG$/BHN00018/sccm?/Win7-x86-BasicApps.wim
ApplyOperatingSystem 3/27/2013 3:05:26 PM
1828 (0x0724)
GetDirectoryListing() successfully completed
ApplyOperatingSystem 3/27/2013 3:05:26 PM
1828 (0x0724)
dwStatusCode >= 200 && dwStatusCode <= 299, HRESULT=801901f4 (e:\nts_sccm_release\sms\framework\tscore\downloadcontent.cpp,1304)
ApplyOperatingSystem 3/27/2013 3:05:26 PM
1828 (0x0724)
WinHttpQueryHeaders() returns status code 500 (Internal Server Error)
ApplyOperatingSystem 3/27/2013 3:05:26 PM
1828 (0x0724)
SendWinHttpRequest failed. 801901f4. ApplyOperatingSystem
3/27/2013 3:05:26 PM 1828 (0x0724)
SendWinHttpRequest (hSession, hConnect, hRequest, sRequest.c_str(), 0, bUseSSL, ullFileSize, LastGoodCredentialsType), HRESULT=801901f4 (e:\nts_sccm_release\sms\framework\tscore\downloadcontent.cpp,1542)
ApplyOperatingSystem 3/27/2013 3:05:26 PM
1828 (0x0724)
DownloadFile failed. 801901f4. ApplyOperatingSystem
3/27/2013 3:05:26 PM 1828 (0x0724)
DownloadFile (hSession, hConnect, sSourceFile.c_str(), sDestinationFile.c_str(), ulTotalSizeRequired, ulDownLoaded, LastGoodCredentialsType, bUseSSL), HRESULT=801901f4 (e:\nts_sccm_release\sms\framework\tscore\downloadcontent.cpp,1648)
ApplyOperatingSystem 3/27/2013 3:05:26 PM
1828 (0x0724)
Error downloading file from http://PRBAHVSSCCM.ARABBANKING.LOCAL:80/SMS_DP_SMSPKG$/BHN00018/sccm?/Win7-x86-BasicApps.wim to C:\_SMSTaskSequence\Packages\BHN00018\Win7-x86-BasicApps.wim
ApplyOperatingSystem
3/27/2013 3:05:26 PM 1828 (0x0724)
DownloadFiles failed. 801901f4. ApplyOperatingSystem
3/27/2013 3:05:26 PM 1828 (0x0724)
DownloadFiles (setDirs, setFiles, sDestination.c_str(), bUseSSL), HRESULT=801901f4 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,2523)
ApplyOperatingSystem 3/27/2013 3:05:26 PM
1828 (0x0724)
Retrying download... ApplyOperatingSystem
3/27/2013 3:05:26 PM 1828 (0x0724)
Tried all the available http based locations. SMB based locations will be attempted now.
ApplyOperatingSystem 3/27/2013 3:05:29 PM
1828 (0x0724)
!saSMBContentSources.empty(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,2948)
ApplyOperatingSystem 3/27/2013 3:05:29 PM
1828 (0x0724)
DownloadContentAndVerifyHash(pszPackageID, L"SMSPackage", saHttpContentSources, saSMBContentSources, saMulticastContentSources, sDestination, dwFlags, L"", 0, dwPackageFlags, pszUserName, pszUserPassword ), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3106)
ApplyOperatingSystem 3/27/2013 3:05:29 PM
1828 (0x0724)
DownloadContentLocally(pszSource, sSourceDirectory, dwFlags, hUserToken, pszUserName, pszUserPassword), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3331)
ApplyOperatingSystem 3/27/2013 3:05:29 PM
1828 (0x0724)
ResolveSource(pszSource, sSourceDirectory, dwFlags, 0, 0, 0), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3221)
ApplyOperatingSystem 3/27/2013 3:05:29 PM
1828 (0x0724)
TS::Utility::ResolveSource( this->packageID, this->packagePath ), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installimage.cpp,1483)
ApplyOperatingSystem 3/27/2013 3:05:29 PM
1828 (0x0724)
resolvePkgSource(), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installimage.cpp,1503)
ApplyOperatingSystem 3/27/2013 3:05:29 PM
1828 (0x0724)
Apply(), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installimage.cpp,1712)
ApplyOperatingSystem 3/27/2013 3:05:29 PM
1828 (0x0724)
Installation of image 1 in package BHN00018 failed to complete..
The system cannot find the file specified. (Error: 80070002; Source: Windows)
ApplyOperatingSystem 3/27/2013 3:05:29 PM
1828 (0x0724)
installer.install(), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installimage.cpp,1787)
ApplyOperatingSystem 3/27/2013 3:05:29 PM
1828 (0x0724)
Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\BHN00018
ApplyOperatingSystem 3/27/2013 3:05:29 PM
1828 (0x0724)
The user tries to release a source directory C:\_SMSTaskSequence\Packages\BHN00018 that is either already released or we have not connected to it
ApplyOperatingSystem 3/27/2013 3:05:29 PM
1828 (0x0724)
InstallImage( g_InstallPackageID, g_ImageIndex, targetVolume, ImageType_Data, g_ConfigPackageID, g_ConfigFileName, false, g_RunFromNet ), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\applyos\applyos.cpp,522)
ApplyOperatingSystem 3/27/2013 3:05:29 PM
1828 (0x0724)
Process completed with exit code 2147942402
TSManager 3/27/2013 3:05:29 PM
1456 (0x05B0)
TSManager 3/27/2013 3:05:29 PM
1456 (0x05B0)
Failed to run the action: Apply Data Image 1.
The system cannot find the file specified. (Error: 80070002; Source: Windows)
TSManager 3/27/2013 3:05:29 PM
1456 (0x05B0)
MP server http://PRBAHVSSCCM.ARABBANKING.LOCAL. Ports 80,443. CRL=false.
TSManager 3/27/2013 3:05:29 PM
1456 (0x05B0)
Setting authenticator TSManager
3/27/2013 3:05:29 PM 1456 (0x05B0)
Set authenticator in transport TSManager
3/27/2013 3:05:29 PM 1456 (0x05B0)
Sending StatusMessage TSManager
3/27/2013 3:05:29 PM 1456 (0x05B0)
Setting message signatures. TSManager
3/27/2013 3:05:29 PM 1456 (0x05B0)
Setting the authenticator. TSManager
3/27/2013 3:05:29 PM 1456 (0x05B0)
CLibSMSMessageWinHttpTransport::Send: URL: PRBAHVSSCCM.ARABBANKING.LOCAL:80 CCM_POST /ccm_system/request
TSManager 3/27/2013 3:05:29 PM
1456 (0x05B0)
Request was succesful. TSManager
3/27/2013 3:05:29 PM 1456 (0x05B0)
Set a global environment variable _SMSTSLastActionRetCode=-2147024894
TSManager 3/27/2013 3:05:29 PM
1456 (0x05B0)
Set a global environment variable _SMSTSLastActionSucceeded=false
TSManager 3/27/2013 3:05:29 PM
1456 (0x05B0)
Clear local default environment TSManager
3/27/2013 3:05:29 PM 1456 (0x05B0)
Let the parent group (Install Operating System) decides whether to continue execution
TSManager 3/27/2013 3:05:29 PM
1456 (0x05B0)
The execution of the group (Install Operating System) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
TSManager 3/27/2013 3:05:29 PM
1456 (0x05B0)
Failed to run the last action: Apply Data Image 1. Execution of task sequence failed.
The system cannot find the file specified. (Error: 80070002; Source: Windows)
TSManager 3/27/2013 3:05:29 PM
1456 (0x05B0)
MP server http://PRBAHVSSCCM.ARABBANKING.LOCAL. Ports 80,443. CRL=false.
TSManager 3/27/2013 3:05:29 PM
1456 (0x05B0)
and when trying to open location from IIS of the http://localhost:80/SMS_DP_SMSPKG$
i got the following error
I don't know it is related or not, do you have any idea about that

This post may be of some help..
http://social.technet.microsoft.com/Forums/en-US/configmanagerdeployment/thread/baa2d7e0-599d-4bd0-a375-8905a7d0b2ff/
Delphin

Task sequence failed with error code 0x80070002

I am facing issue in OS deployment my machine PXE boot successfully but on the step of apply operating I got an error "task sequence failed with error code 0x80070002"
I see lot of thread describes to add Network Access Account I already added but still I receive same error please help
Usama Arif

i had this happen on two of my dp's the other day. It drove me nuts, I ended up removing the DP Role, removing the server from SCCM
I then deleted all files on the 'D :' drive
after everything was deleted, I re-added the Server to SCCM and gave it the DP Role back.
I then added the DP Back to the DP Group to receive all packages that was on it before. then finally once everything was re-uploaded my users were able to pxe boot again

OSD Task Sequence Fails with Error 0x80091007

Hello Everyone,
I have a bit of a weird hash mismatch problem. The issue is only occuring on one laptop. The laptop was imaged successfully, new out of the box. Computer started "acting craptacular" according to the tech, so he tried to reimage it,
assuming one of the applications he put on the computer while setting it up for the user may have messed it up.
From that point forward, the computer couldn't image anymore. I can image the same model, TS, and even other models without issue. The error logs are pointing to a hash value mismatch on the OS WIM.
Here are the log files - I wish there was a way to make them cleaner. I ran some hardware tests with IBM's PCDoctor, and it came back clean. I'm starting to run out of ideas.
Thanks in advance!
Log: (SMSTS.LOG)
Download done setting progress bar to 100 ApplyOperatingSystem 5/14/2010 4:09:31 PM 840 (0x0348)
Hash could not be matched for the downloded content. Original ContentHash = A6170DC8CFC5A443636828F093C45377B5FE2A62, Downloaded ContentHash = 7DEBC67B90C2326031EF8727238176C92A02006C ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)
0L == TS::Utility::VerifyPackageHash(pszContentID, sDestination), HRESULT=80091007 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,2901) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)
DownloadContentAndVerifyHash(pszPackageID, L"SMSPackage", saHttpContentSources, saSMBContentSources, saMulticastContentSources, sDestination, dwFlags, L"", 0, dwPackageFlags, pszUserName, pszUserPassword ), HRESULT=80091007 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3000) ApplyOperatingSystem 5/14/2010
4:09:53 PM 840 (0x0348)
DownloadContentLocally(pszSource, sSourceDirectory, dwFlags, hUserToken, pszUserName, pszUserPassword), HRESULT=80091007 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3128) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)
ResolveSource(pszSource, sSourceDirectory, dwFlags, 0, 0, 0), HRESULT=80091007 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,3029) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)
TS::Utility::ResolveSource( this->packageID, this->packagePath, TS::Utility::ResolveSourceFlags::PersistContents ), HRESULT=80091007 (e:\nts_sms_fre\sms\client\osdeployment\applyos\installimage.cpp,1255) ApplyOperatingSystem 5/14/2010 4:09:53
PM 840 (0x0348)
resolvePkgSource(), HRESULT=80091007 (e:\nts_sms_fre\sms\client\osdeployment\applyos\installimage.cpp,1299) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)
Installation of image 1 in package RH1000DD failed to complete..
The hash value is not correct. (Error: 80091007; Source: Windows) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)
installer.install(), HRESULT=80091007 (e:\nts_sms_fre\sms\client\osdeployment\applyos\installimage.cpp,1373) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)
Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\RH1000DD ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)
The user tries to release a source directory C:\_SMSTaskSequence\Packages\RH1000DD that is either already released or we have not connected to it ApplyOperatingSystem 5/14/2010 4:09:53 PM 840 (0x0348)
InstallImage( g_InstallPackageID, g_ImageIndex, targetVolume, ImageType_OS, g_ConfigPackageID, g_ConfigFileName ), HRESULT=80091007 (e:\nts_sms_fre\sms\client\osdeployment\applyos\applyos.cpp,360) ApplyOperatingSystem 5/14/2010 4:09:53 PM 840
(0x0348)
Process completed with exit code 2148077575 TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
!--------------------------------------------------------------------------------------------! TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Failed to run the action: XP SP3 - Multi-HAL.
The hash value is not correct. (Error: 80091007; Source: Windows) TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Sending status message . . . TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Send a task execution status message SMS_TSExecution_ActionFailError TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
MP server rh1-sccm.ritehite.com and port 80. SSL=false. CRL=false. TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Site code: RH1 TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Client machine name: R842AEYa TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Client Identity: GUID:428CFC8B-1BE1-4E11-B2C4-21E31EA71572 TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Advertisement ID: RH1200C2 TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Package ID: RH1000DF TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Sending StatusMessage TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Formatted header: TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
<Msg SchemaVersion="1.1" ReplyCompression="zlib"><ID/><SourceID>56d444c9-6bf0-4ed2-86a9-5f199c90924c</SourceID><SourceHost/><TargetAddress>mp:[http]MP_StatusManager</TargetAddress><ReplyTo>direct:OSD</ReplyTo><Priority>3</Priority><Timeout>3600</Timeout><SentTime>2010-05-14T21:09:53Z</SentTime><Protocol>http</Protocol><Body
Type="ByteRange" Offset="0" Length="4246"/><Hooks/><Payload Type="inline"/><TargetHost/><TargetEndpoint>StatusReceiver</TargetEndpoint><ReplyMode>Sync</ReplyMode><CorrelationID/></Msg>
TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
CLibSMSMessageWinHttpTransport::Send: URL: sccmserver.x.com:80 CCM_POST /ccm_system/request TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
The request has succeeded. 200 OK TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Set a global environment variable _SMSTSLastActionRetCode=-2146889721 TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Clear local default environment TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Let the parent group (Apply Operating System) decides whether to continue execution TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Let the parent group (Install Operating System) decide whether to continue execution TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
The execution of the group (Install Operating System) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Failed to run the last action: XP SP3 - Multi-HAL. Execution of task sequence failed.
The hash value is not correct. (Error: 80091007; Source: Windows) TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Sending status message . . . TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)
Send a task execution status message SMS_TSExecution_TaskSequenceFailError TSManager 5/14/2010 4:09:53 PM 1896 (0x0768)

Hi Guys,
My WIM is currently sitting at 1.8 GB, so I'm not sure it is the 4 GB bug you were referring to.
I haven't tried a re-import/update DP yet mainly because the problem is occuring on only
one computer at this moment. In fact, I have deployed several computers already with the same DP, same WIM and even the same model of computer. That makes me think it isn't an issue with the WIM as
much as it is an issue with the computer itself.
Can you guys think of anything on the computer that would cause the failure?
Thanks again,
Sean

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.

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

OSD Task sequences failed in application installation step.

Hello,
I am deploying win 7 with installing app-v client application(by package), I applied this Task sequences on some of devices sometimes it worked and installed app-v client application but in some cases
Task sequences failed to installed app-v client steps.
Please provide reason for this and how to resolve this.

Certain pre-requisites need to be installed for the App-V client to successfully install.
Take a look here http://sccmentor.wordpress.com/2013/05/21/deploy-the-app-v-5-0-client-with-sccm-2012/
Note that KB2533623 has been superseeded if you are pushing out any Windows Updates as part of your OSD.
http://sccmentor.wordpress.com/2013/07/30/kb2533623-superseded-by-kb2758857/
Have these pre-reqs been applied in the Task Sequence prior to the App-V client install? If not add them in and try the push again.
Cheers
Paul | sccmentor.wordpress.com

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

OSD Task Sequence fails to install SCCM client

Hello,
Our OSD task sequence fails to install the SCCM client with certain images.
The TS gets to the "Setup Windows and Configuration" step, during which it downloads all the necessary SCCM client files (silverlight, C++ redistributable, client.msi....etc.). At this point computer restarts and in never loads back into the
task sequence, instead it enters the minisetup (setup is starting services, setup is installing devices, setup is applying system settings...preparing computer for first use), after which the computer restarts and you are back at the CTR+ALT+Del screen.
The computer has joined the domain and has run all other steps but it has failed to install SCCM client. I can also see the leftovers of an incomplete TS under c:\_SMSTaskSequence
If we change the image specified under "Apply Operating System" step, everything works ok.
It appears there is something wrong with this particular image. Any ideas?
Logs show no errors. Let me know which logs you'd like me to post (and from which location)
There is no ccm folder under c:\windows

Hoping you are using ConfigMgr 2012 R2. If a client machine Join to Domain and doesn't proceed with other steps and not installing the CCM client, then problem seems to be with the Image.Do you have any RunOnce registry setting specified in the Image? You
can mount the Image and check those settings.
RunOnce Key Reference :
https://msdn.microsoft.com/en-us/library/windows/desktop/aa376977(v=vs.85).aspx
If the above key is present in the Image, TS Engine won't resume after the reboot.
You need to use a new variable "SMSTSPostAction" at the end of the Task Sequence, to add your custom actions.
The above variable is applicable in CM 2012 SP1 and R2.
Thanks, Senthil. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. Click on "vote as Helpful" if you feel this post helpful to you. This
can be beneficial to other community members reading the thread.

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

Similar Messages

Maybe you are looking for