Hi guys, I am having trouble capturing a 2008 R2 image. The TS stops running at the Setup Windows and Configmgr step with the error 0x80070002 or 80004005 (depending on the model I’m running it from). I am running 2007 R2 in native mode. I have uploaded the smsts.log file here: https://rcpt.yousendit.com/1151134943/ee1f7e05b21be5dd72f116d2e2def52f Please let me know if there is any other information which may be helpful. Any help would be greatly appreciated. Regards, Locust12

I think you uploaded the wrong file, as it ends after the partitioning step Look in c:\_SMSTaskSequence\Logs\Smstslog\smsts.log if there is a more complete version of the file and post the contents. Miguel Rodriguez

My apolpogies. Please check this link for the correct smsts.log https://rcpt.yousendit.com/1152825899/5fa5fb1a93d119661e046d4156b32a71

Still cannot see an error. This logfile stops after the apply driver step. Are there multiple smsts files in the folder? if so you have grabbed the wrong one. The one you are interested in is named smsts.log (without any date in the filename). Eventually take a look in c:\windows\system32\ccm\logs\Smstslog\smsts.log (or c:\windows\sysWOW64\ccm\logs\Smstslog\smsts.log if you are running 64 BIT OS). Miguel Rodriguez

Thankyou for the clarification. My situation seems related to the third step you mentioned. The system reboots into Windows (I can see the grey setup background of 2008 R2) The Setup Windows and Configmgr is displayed and the status bar get to about half way Then the error message is displayed as stated above There are no /ccm folders in the sysWOW64 or system32 folders Regards Locust12

Thankyou for the clarification. My situation seems related to the third step you mentioned. The system reboots into Windows (I can see the grey setup background of 2008 R2) The Setup Windows and Configmgr is displayed and the status bar get to about half way Then the error message is displayed as stated above There are no /ccm folders in the sysWOW64 or system32 folders Regards Locust12

Hi, you're smsts.log file contains many warning about drivers that missing. http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/ee91d388-53c1-4f8a-b069-67625f874b75/ It mentions: Windows Setup is failing, most likely due to an invalid setting in the answer file. Typically, this is caused by a product key / edition mismatch. http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/d86298e7-f6c0-458b-8c67-20e6581664bc/ With many different suggestions about the Administrator password during the Task sequence and a Sysprep change needed for driver recognition. My ConfigMgr blog: http://henkhoogendoorn.blogspot.com Follow me on Twitter: @henkhoogendoorn

Hi, you're smsts.log file contains many warning about drivers that missing. http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/ee91d388-53c1-4f8a-b069-67625f874b75/ It mentions: Windows Setup is failing, most likely due to an invalid setting in the answer file. Typically, this is caused by a product key / edition mismatch. http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/d86298e7-f6c0-458b-8c67-20e6581664bc/ With many different suggestions about the Administrator password during the Task sequence and a Sysprep change needed for driver recognition. My ConfigMgr blog: http://henkhoogendoorn.blogspot.com Follow me on Twitter: @henkhoogendoorn

Please take a look at the report Advertisement status messages for a particular client and advertisement on your server to review the events for the failing machine. It should contain all the TS steps executed and the error. Post back the error message of the Setup Windows/ConfigMgr Client step.Miguel Rodriguez

Please take a look at the report Advertisement status messages for a particular client and advertisement on your server to review the events for the failing machine. It should contain all the TS steps executed and the error. Post back the error message of the Setup Windows/ConfigMgr Client step.Miguel Rodriguez

Can you post the smsts.log file for more information on the issue? In my other post the location for the smsts.log file is mentioned. Without a specific error message it's difficult to do any troubleshooting.My ConfigMgr blog: http://henkhoogendoorn.blogspot.com Follow me on Twitter: @henkhoogendoorn

Can you post the smsts.log file for more information on the issue? In my other post the location for the smsts.log file is mentioned. Without a specific error message it's difficult to do any troubleshooting.My ConfigMgr blog: http://henkhoogendoorn.blogspot.com Follow me on Twitter: @henkhoogendoorn

That is the log file your requested from c:\_SMSTaskSequence\Logs\Smstslog\smsts.log There is another file in there with date information but the one I uploaded is just smsts.log There is no C:\Windows\sysWOW64\ccm folder listed at all. I just tested again with the same outcome. Regards Locust12

That is the log file your requested from c:\_SMSTaskSequence\Logs\Smstslog\smsts.log There is another file in there with date information but the one I uploaded is just smsts.log There is no C:\Windows\sysWOW64\ccm folder listed at all. I just tested again with the same outcome. Regards Locust12

Thank you for your assistance, I will update as soon as I can test again. Regards Locust12

Thank you for your assistance, I will update as soon as I can test again. Regards Locust12

Running the report returned these errors: The task sequence execution engine failed execution of a task sequence. The operating system reported error -2147467259: Unspecified error The task sequence manager could not successfully complete execution of the task sequence. A failure exit code of 16389 was returned. The operating system reported error 16389:

Running the report returned these errors: The task sequence execution engine failed execution of a task sequence. The operating system reported error -2147467259: Unspecified error The task sequence manager could not successfully complete execution of the task sequence. A failure exit code of 16389 was returned. The operating system reported error 16389:

Hi Henk, The smsts.log file is uploaded here: https://rcpt.yousendit.com/1152825899/5fa5fb1a93d119661e046d4156b32a71 As mentioned this is the log collected from "c:\_SMSTaskSequence\Logs\Smstslog"

Hi Henk, The smsts.log file is uploaded here: https://rcpt.yousendit.com/1152825899/5fa5fb1a93d119661e046d4156b32a71 As mentioned this is the log collected from "c:\_SMSTaskSequence\Logs\Smstslog"

The smsts.log is indeed the one which gives information about what's going wrong during deployment. During installation the smsts.log file is located at different places. Everytime the device is booted again while the Task Sequence is still running, the smsts.log will be copied to a smsts--.log file, and a new smsts.log file will be created. 1. System booted in WinPE and the local harddisk is not modified (smsts.log in the "x:\windows\temp\smstslog" folder) 2. System booted in WinPE and the local harddisk is partitioned and formatted (smsts.log in the "x:\smstslog" folder and after that in the "c:\_SMSTaskSequence\Logs\Smstslog" folder 3. System booted in Windows before the ConfigMgr client is installed (smsts.log in the "c:\_SMSTaskSequence\Logs\Smstslog" folder) 4. System booted in Windows after ConfigMgr client is installed (smsts.log in the "c:\windows\system32\ccm\logs\Smstslog" folder) (When using a x64 device, you can find it in the "c:\windows\SysWOW64\ccm\logs\Smstslog" folder)My ConfigMgr blog: http://henkhoogendoorn.blogspot.com Follow me on Twitter: @henkhoogendoorn

The smsts.log is indeed the one which gives information about what's going wrong during deployment. During installation the smsts.log file is located at different places. Everytime the device is booted again while the Task Sequence is still running, the smsts.log will be copied to a smsts--.log file, and a new smsts.log file will be created. 1. System booted in WinPE and the local harddisk is not modified (smsts.log in the "x:\windows\temp\smstslog" folder) 2. System booted in WinPE and the local harddisk is partitioned and formatted (smsts.log in the "x:\smstslog" folder and after that in the "c:\_SMSTaskSequence\Logs\Smstslog" folder 3. System booted in Windows before the ConfigMgr client is installed (smsts.log in the "c:\_SMSTaskSequence\Logs\Smstslog" folder) 4. System booted in Windows after ConfigMgr client is installed (smsts.log in the "c:\windows\system32\ccm\logs\Smstslog" folder) (When using a x64 device, you can find it in the "c:\windows\SysWOW64\ccm\logs\Smstslog" folder)My ConfigMgr blog: http://henkhoogendoorn.blogspot.com Follow me on Twitter: @henkhoogendoorn

I have unmarked this as the answer because the issue has not been properly identified let alone resolved. I can successfully capture a image using capture media but the issue remains when using Build and Capture task sequence. I would be more than happy to try any suggestions for resolving this issue. I have tested with and without an answer file with the same outcome. I have ensured that the pc is a workgroup member the admin pw is blank primary system partition is NTFS ensured that the version and key are matching Please let me know if there are any other suggestions.