SCCM 2012 R2 cannot create Task Sequence Media

Hello,
We have installed SCCM 2012 SP1 and have trouble creating a Task Sequence Media, the error we are getting is "Media creation failed with error code -2147217406"
We have reviewed the CreateTSMedia.log and found the following errors:
* Failed to create media generator (0x80041002)
* CreateTsMedia failed with error 0x80041002, details = ''
* Unable to delete all files in temp directory. Giving up. (0x80070091)
* CreateMedia.exe finished with error code 80041002
We are trying to create the Task Sequence Media using the Capture option to use with the Media Type USB or CD / DVD, none works.
We tried to create the Task Sequence Media from a PC with Windows 7 and installed SCCM console and also we tried from the SCCM server, but it has not worked.
We have made sure to use the administrative account that SCCM installation was performed, but we have not been able to resolve this incident.
I will appreciate your advices.
Thanks in advance.
Manuel
Manuel´s Microsoft Forums Threads

This is the log with Media Type CD
Begin media creation: CreateTsMedia 4/8/2015 12:23:51 PM 456528 (0x6F750)
Media: CAPTURE CreateTsMedia 4/8/2015 12:23:51 PM 456528 (0x6F750)
Provider=serengueti.asesuisa.com CreateTsMedia 4/8/2015 12:23:51 PM 456528 (0x6F750)
'Site Code'=ASE CreateTsMedia 4/8/2015 12:23:51 PM 456528 (0x6F750)
DP(s)=SERENGUETI.ASESUISA.COM CreateTsMedia 4/8/2015 12:23:51 PM 456528 (0x6F750)
'Boot Image Package ID'=ASE00003 CreateTsMedia 4/8/2015 12:23:51 PM 456528 (0x6F750)
'Physical Media Type'=CD CreateTsMedia 4/8/2015 12:23:51 PM 456528 (0x6F750)
'Media Destination'=\\serengueti\AV\CaptureX86_ASE.iso CreateTsMedia 4/8/2015 12:23:51 PM 456528 (0x6F750)
Media label: 'Configuration Manager 2012' CreateTsMedia 4/8/2015 12:23:51 PM 456528 (0x6F750)
Creating media from Admin Console CreateTsMedia 4/8/2015 12:23:51 PM 456528 (0x6F750)
COMMAND LINE: CreateTsMedia 4/8/2015 12:23:51 PM 456528 (0x6F750)
CreateMedia.exe /K:capture /N:**** /P:serengueti.asesuisa.com /S:ASE /C:**** /D:SERENGUETI.ASESUISA.COM /L:Configuration Manager 2012 /B:ASE00003 /T:CD /F:\\serengueti\AV\CaptureX86_ASE.iso CreateTsMedia 4/8/2015 12:23:51 PM 456528 (0x6F750)
Another thread has been started to create TS media CreateTsMedia 4/8/2015 12:23:51 PM 800684 (0xC37AC)
======= CreateCaptureMedia invoked ======= CreateTsMedia 4/8/2015 12:23:51 PM 800684 (0xC37AC)
---------------------------- CreateTsMedia ---------------------------- CreateTsMedia 4/8/2015 12:23:51 PM 800684 (0xC37AC)
Requested output path: \\serengueti\AV\CaptureX86_ASE.iso (CD) CreateTsMedia 4/8/2015 12:23:51 PM 800684 (0xC37AC)
Total number of TS variables: 0 CreateTsMedia 4/8/2015 12:23:51 PM 800684 (0xC37AC)
Temporary directory 'C:\Users\ADMINI~1.ASE\AppData\Local\Temp\2\_tsmedia_800684' created, free space on drive 'C:' is 27327 MB CreateTsMedia 4/8/2015 12:23:51 PM 800684 (0xC37AC)
Opened WMI namespace '\\serengueti.asesuisa.com\root\SMS\site_ASE' CreateTsMedia 4/8/2015 12:23:51 PM 800684 (0xC37AC)
Local computer is SERENGUETI CreateTsMedia 4/8/2015 12:23:52 PM 800684 (0xC37AC)
Package manager created successfully CreateTsMedia 4/8/2015 12:23:52 PM 800684 (0xC37AC)
Local computer is SERENGUETI CreateTsMedia 4/8/2015 12:23:52 PM 800684 (0xC37AC)
Creating policy manager CreateTsMedia 4/8/2015 12:23:52 PM 800684 (0xC37AC)
Setting up Install Toolkit CreateTsMedia 4/8/2015 12:23:52 PM 800684 (0xC37AC)
Content Library: Path='D:\SCCMContentLib', Drives='D:\,C:\' CreateTsMedia 4/8/2015 12:24:04 PM 800684 (0xC37AC)
Registering package ASE00003.4 with content at D:\SCCMContentLib CreateTsMedia 4/8/2015 12:24:06 PM 800684 (0xC37AC)
VerifyContentHash: Hash algorithm is 32780 CreateTsMedia 4/8/2015 12:24:12 PM 800684 (0xC37AC)
Hash value of package ASE00003 is verified CreateTsMedia 4/8/2015 12:24:19 PM 800684 (0xC37AC)
Opening image file C:\Users\ADMINI~1.ASE\AppData\Local\Temp\2\_tsmedia_800684\Cache\ASE00003\boot.ASE00003.wim CreateTsMedia 4/8/2015 12:24:19 PM 800684 (0xC37AC)
Applying image 1 to volume C:\Users\ADMINI~1.ASE\AppData\Local\Temp\2\_tsmedia_800684\Toolkit CreateTsMedia 4/8/2015 12:24:19 PM 800684 (0xC37AC)
Closing image file C:\Users\ADMINI~1.ASE\AppData\Local\Temp\2\_tsmedia_800684\Cache\ASE00003\boot.ASE00003.wim CreateTsMedia 4/8/2015 12:24:20 PM 800684 (0xC37AC)
More than one resource file found in the media creation toolkit. Media resources may be in a different language than what was expected CreateTsMedia 4/8/2015 12:24:20 PM 800684 (0xC37AC)
Generating capture task sequence CreateTsMedia 4/8/2015 12:24:20 PM 800684 (0xC37AC)
Failed to create media generator (0x80041002) CreateTsMedia 4/8/2015 12:24:20 PM 800684 (0xC37AC)
CreateTsMedia failed with error 0x80041002, details='' CreateTsMedia 4/8/2015 12:24:20 PM 800684 (0xC37AC)
Unable to delete file C:\Users\ADMINI~1.ASE\AppData\Local\Temp\2\_tsmedia_800684\Toolkit\sms\bin\i386\1033\TsRes.dll (0x80070005). Continuing. CreateTsMedia 4/8/2015 12:24:21 PM 800684 (0xC37AC)
Unable to delete directory C:\Users\ADMINI~1.ASE\AppData\Local\Temp\2\_tsmedia_800684\Toolkit\sms\bin\i386\1033 (0x80070091). Continuing. CreateTsMedia 4/8/2015 12:24:21 PM 800684 (0xC37AC)
Unable to delete directory C:\Users\ADMINI~1.ASE\AppData\Local\Temp\2\_tsmedia_800684\Toolkit\sms\bin\i386 (0x80070091). Continuing. CreateTsMedia 4/8/2015 12:24:21 PM 800684 (0xC37AC)
Unable to delete directory C:\Users\ADMINI~1.ASE\AppData\Local\Temp\2\_tsmedia_800684\Toolkit\sms\bin (0x80070091). Continuing. CreateTsMedia 4/8/2015 12:24:21 PM 800684 (0xC37AC)
Unable to delete directory C:\Users\ADMINI~1.ASE\AppData\Local\Temp\2\_tsmedia_800684\Toolkit\sms (0x80070091). Continuing. CreateTsMedia 4/8/2015 12:24:21 PM 800684 (0xC37AC)
Unable to delete directory C:\Users\ADMINI~1.ASE\AppData\Local\Temp\2\_tsmedia_800684\Toolkit (0x80070091). Continuing. CreateTsMedia 4/8/2015 12:24:21 PM 800684 (0xC37AC)
Error deleting files in temp directory (0x80070091). Retrying after delay. CreateTsMedia 4/8/2015 12:24:21 PM 800684 (0xC37AC)
Unable to delete file C:\Users\ADMINI~1.ASE\AppData\Local\Temp\2\_tsmedia_800684\Toolkit\sms\bin\i386\1033\TsRes.dll (0x80070005). Continuing. CreateTsMedia 4/8/2015 12:24:24 PM 800684 (0xC37AC)
Unable to delete directory C:\Users\ADMINI~1.ASE\AppData\Local\Temp\2\_tsmedia_800684\Toolkit\sms\bin\i386\1033 (0x80070091). Continuing. CreateTsMedia 4/8/2015 12:24:24 PM 800684 (0xC37AC)
Unable to delete directory C:\Users\ADMINI~1.ASE\AppData\Local\Temp\2\_tsmedia_800684\Toolkit\sms\bin\i386 (0x80070091). Continuing. CreateTsMedia 4/8/2015 12:24:24 PM 800684 (0xC37AC)
Unable to delete directory C:\Users\ADMINI~1.ASE\AppData\Local\Temp\2\_tsmedia_800684\Toolkit\sms\bin (0x80070091). Continuing. CreateTsMedia 4/8/2015 12:24:24 PM 800684 (0xC37AC)
Unable to delete directory C:\Users\ADMINI~1.ASE\AppData\Local\Temp\2\_tsmedia_800684\Toolkit\sms (0x80070091). Continuing. CreateTsMedia 4/8/2015 12:24:24 PM 800684 (0xC37AC)
Unable to delete directory C:\Users\ADMINI~1.ASE\AppData\Local\Temp\2\_tsmedia_800684\Toolkit (0x80070091). Continuing. CreateTsMedia 4/8/2015 12:24:24 PM 800684 (0xC37AC)
Error deleting files in temp directory (0x80070091). Retrying after delay. CreateTsMedia 4/8/2015 12:24:24 PM 800684 (0xC37AC)
Unable to delete file C:\Users\ADMINI~1.ASE\AppData\Local\Temp\2\_tsmedia_800684\Toolkit\sms\bin\i386\1033\TsRes.dll (0x80070005). Continuing. CreateTsMedia 4/8/2015 12:24:27 PM 800684 (0xC37AC)
Unable to delete directory C:\Users\ADMINI~1.ASE\AppData\Local\Temp\2\_tsmedia_800684\Toolkit\sms\bin\i386\1033 (0x80070091). Continuing. CreateTsMedia 4/8/2015 12:24:27 PM 800684 (0xC37AC)
Unable to delete directory C:\Users\ADMINI~1.ASE\AppData\Local\Temp\2\_tsmedia_800684\Toolkit\sms\bin\i386 (0x80070091). Continuing. CreateTsMedia 4/8/2015 12:24:27 PM 800684 (0xC37AC)
Unable to delete directory C:\Users\ADMINI~1.ASE\AppData\Local\Temp\2\_tsmedia_800684\Toolkit\sms\bin (0x80070091). Continuing. CreateTsMedia 4/8/2015 12:24:27 PM 800684 (0xC37AC)
Unable to delete directory C:\Users\ADMINI~1.ASE\AppData\Local\Temp\2\_tsmedia_800684\Toolkit\sms (0x80070091). Continuing. CreateTsMedia 4/8/2015 12:24:27 PM 800684 (0xC37AC)
Unable to delete directory C:\Users\ADMINI~1.ASE\AppData\Local\Temp\2\_tsmedia_800684\Toolkit (0x80070091). Continuing. CreateTsMedia 4/8/2015 12:24:27 PM 800684 (0xC37AC)
Unable to delete all files in temp directory. Giving up. (0x80070091) CreateTsMedia 4/8/2015 12:24:27 PM 800684 (0xC37AC)
Media creation process that was started from Admin Console completed.
CreateTsMedia 4/8/2015 12:24:27 PM 456528 (0x6F750)
CreateMedia.exe finished with error code 80041002 CreateTsMedia 4/8/2015 12:24:27 PM 456528 (0x6F750)
This is the log with Media Type USB
Begin media creation: CreateTsMedia 4/9/2015 9:23:04 AM 14544 (0x38D0)
Media: CAPTURE CreateTsMedia 4/9/2015 9:23:04 AM 14544 (0x38D0)
Provider=serengueti.asesuisa.com CreateTsMedia 4/9/2015 9:23:04 AM 14544 (0x38D0)
'Site Code'=ASE CreateTsMedia 4/9/2015 9:23:04 AM 14544 (0x38D0)
DP(s)=SERENGUETI.ASESUISA.COM CreateTsMedia 4/9/2015 9:23:04 AM 14544 (0x38D0)
'Boot Image Package ID'=ASE00003 CreateTsMedia 4/9/2015 9:23:04 AM 14544 (0x38D0)
'Physical Media Type'=UFD+FORMAT CreateTsMedia 4/9/2015 9:23:04 AM 14544 (0x38D0)
'Media Destination'=G:\ CreateTsMedia 4/9/2015 9:23:04 AM 14544 (0x38D0)
Media label: 'Configuration Manager 2012' CreateTsMedia 4/9/2015 9:23:04 AM 14544 (0x38D0)
Creating media from Admin Console CreateTsMedia 4/9/2015 9:23:04 AM 14544 (0x38D0)
COMMAND LINE: CreateTsMedia 4/9/2015 9:23:04 AM 14544 (0x38D0)
CreateMedia.exe /K:capture /N:**** /P:serengueti.asesuisa.com /S:ASE /C:**** /D:SERENGUETI.ASESUISA.COM /L:Configuration Manager 2012 /B:ASE00003 /T:UFD+FORMAT /F:G:\ CreateTsMedia 4/9/2015 9:23:04 AM 14544 (0x38D0)
Another thread has been started to create TS media CreateTsMedia 4/9/2015 9:23:04 AM 14552 (0x38D8)
======= CreateCaptureMedia invoked ======= CreateTsMedia 4/9/2015 9:23:04 AM 14552 (0x38D8)
---------------------------- CreateTsMedia ---------------------------- CreateTsMedia 4/9/2015 9:23:04 AM 14552 (0x38D8)
Requested output path: G:\ (UFD+FORMAT) CreateTsMedia 4/9/2015 9:23:04 AM 14552 (0x38D8)
Total number of TS variables: 0 CreateTsMedia 4/9/2015 9:23:04 AM 14552 (0x38D8)
Temporary directory 'C:\Users\PEPEGR~1\AppData\Local\Temp\_tsmedia_14552' created, free space on drive 'C:' is 1131 MB CreateTsMedia 4/9/2015 9:23:04 AM 14552 (0x38D8)
Opened WMI namespace '\\serengueti.asesuisa.com\root\SMS\site_ASE' CreateTsMedia 4/9/2015 9:23:04 AM 14552 (0x38D8)
Local computer is JQUINTANILLAV CreateTsMedia 4/9/2015 9:23:06 AM 14552 (0x38D8)
Package manager created successfully CreateTsMedia 4/9/2015 9:23:06 AM 14552 (0x38D8)
Local computer is JQUINTANILLAV CreateTsMedia 4/9/2015 9:23:06 AM 14552 (0x38D8)
Creating policy manager CreateTsMedia 4/9/2015 9:23:06 AM 14552 (0x38D8)
Setting up Install Toolkit CreateTsMedia 4/9/2015 9:23:06 AM 14552 (0x38D8)
Content library is on remote system 'SERENGUETI.ASESUISA.COM' CreateTsMedia 4/9/2015 9:23:18 AM 14552 (0x38D8)
Connected to remote registry service on 'SERENGUETI.ASESUISA.COM' CreateTsMedia 4/9/2015 9:23:18 AM 14552 (0x38D8)
Content Library: Local Path='D:\SCCMContentLib', Remote Path='\\SERENGUETI.ASESUISA.COM\SCCMContentLib$', File Library Usable Drives='D:\,C:\' CreateTsMedia 4/9/2015 9:23:18 AM 14552 (0x38D8)
Registering package ASE00003.4 with content at
\\SERENGUETI.ASESUISA.COM\SCCMContentLib$ CreateTsMedia 4/9/2015 9:23:19 AM 14552 (0x38D8)
VerifyContentHash: Hash algorithm is 32780 CreateTsMedia 4/9/2015 9:23:23 AM 14552 (0x38D8)
Hash value of package ASE00003 is verified CreateTsMedia 4/9/2015 9:23:27 AM 14552 (0x38D8)
Failed to find ADK installation root registry key CreateTsMedia 4/9/2015 9:23:27 AM 14552 (0x38D8)
Opening image file C:\Users\PEPEGR~1\AppData\Local\Temp\_tsmedia_14552\Cache\ASE00003\boot.ASE00003.wim CreateTsMedia 4/9/2015 9:23:27 AM 14552 (0x38D8)
Applying image 1 to volume C:\Users\PEPEGR~1\AppData\Local\Temp\_tsmedia_14552\Toolkit CreateTsMedia 4/9/2015 9:23:27 AM 14552 (0x38D8)
Closing image file C:\Users\PEPEGR~1\AppData\Local\Temp\_tsmedia_14552\Cache\ASE00003\boot.ASE00003.wim CreateTsMedia 4/9/2015 9:23:28 AM 14552 (0x38D8)
More than one resource file found in the media creation toolkit. Media resources may be in a different language than what was expected CreateTsMedia 4/9/2015 9:23:28 AM 14552 (0x38D8)
Generating capture task sequence CreateTsMedia 4/9/2015 9:23:28 AM 14552 (0x38D8)
Failed to create media generator (0x80041002) CreateTsMedia 4/9/2015 9:23:28 AM 14552 (0x38D8)
CreateTsMedia failed with error 0x80041002, details='' CreateTsMedia 4/9/2015 9:23:28 AM 14552 (0x38D8)
Unable to delete file C:\Users\PEPEGR~1\AppData\Local\Temp\_tsmedia_14552\Toolkit\sms\bin\i386\1033\TsRes.dll (0x80070005). Continuing. CreateTsMedia 4/9/2015 9:23:29 AM 14552 (0x38D8)
Unable to delete directory C:\Users\PEPEGR~1\AppData\Local\Temp\_tsmedia_14552\Toolkit\sms\bin\i386\1033 (0x80070091). Continuing. CreateTsMedia 4/9/2015 9:23:29 AM 14552 (0x38D8)
Unable to delete directory C:\Users\PEPEGR~1\AppData\Local\Temp\_tsmedia_14552\Toolkit\sms\bin\i386 (0x80070091). Continuing. CreateTsMedia 4/9/2015 9:23:29 AM 14552 (0x38D8)
Unable to delete directory C:\Users\PEPEGR~1\AppData\Local\Temp\_tsmedia_14552\Toolkit\sms\bin (0x80070091). Continuing. CreateTsMedia 4/9/2015 9:23:29 AM 14552 (0x38D8)
Unable to delete directory C:\Users\PEPEGR~1\AppData\Local\Temp\_tsmedia_14552\Toolkit\sms (0x80070091). Continuing. CreateTsMedia 4/9/2015 9:23:29 AM 14552 (0x38D8)
Unable to delete directory C:\Users\PEPEGR~1\AppData\Local\Temp\_tsmedia_14552\Toolkit (0x80070091). Continuing. CreateTsMedia 4/9/2015 9:23:29 AM 14552 (0x38D8)
Error deleting files in temp directory (0x80070091). Retrying after delay. CreateTsMedia 4/9/2015 9:23:29 AM 14552 (0x38D8)
Unable to delete file C:\Users\PEPEGR~1\AppData\Local\Temp\_tsmedia_14552\Toolkit\sms\bin\i386\1033\TsRes.dll (0x80070005). Continuing. CreateTsMedia 4/9/2015 9:23:32 AM 14552 (0x38D8)
Unable to delete directory C:\Users\PEPEGR~1\AppData\Local\Temp\_tsmedia_14552\Toolkit\sms\bin\i386\1033 (0x80070091). Continuing. CreateTsMedia 4/9/2015 9:23:32 AM 14552 (0x38D8)
Unable to delete directory C:\Users\PEPEGR~1\AppData\Local\Temp\_tsmedia_14552\Toolkit\sms\bin\i386 (0x80070091). Continuing. CreateTsMedia 4/9/2015 9:23:32 AM 14552 (0x38D8)
Unable to delete directory C:\Users\PEPEGR~1\AppData\Local\Temp\_tsmedia_14552\Toolkit\sms\bin (0x80070091). Continuing. CreateTsMedia 4/9/2015 9:23:32 AM 14552 (0x38D8)
Unable to delete directory C:\Users\PEPEGR~1\AppData\Local\Temp\_tsmedia_14552\Toolkit\sms (0x80070091). Continuing. CreateTsMedia 4/9/2015 9:23:32 AM 14552 (0x38D8)
Unable to delete directory C:\Users\PEPEGR~1\AppData\Local\Temp\_tsmedia_14552\Toolkit (0x80070091). Continuing. CreateTsMedia 4/9/2015 9:23:32 AM 14552 (0x38D8)
Error deleting files in temp directory (0x80070091). Retrying after delay. CreateTsMedia 4/9/2015 9:23:32 AM 14552 (0x38D8)
Unable to delete file C:\Users\PEPEGR~1\AppData\Local\Temp\_tsmedia_14552\Toolkit\sms\bin\i386\1033\TsRes.dll (0x80070005). Continuing. CreateTsMedia 4/9/2015 9:23:35 AM 14552 (0x38D8)
Unable to delete directory C:\Users\PEPEGR~1\AppData\Local\Temp\_tsmedia_14552\Toolkit\sms\bin\i386\1033 (0x80070091). Continuing. CreateTsMedia 4/9/2015 9:23:35 AM 14552 (0x38D8)
Unable to delete directory C:\Users\PEPEGR~1\AppData\Local\Temp\_tsmedia_14552\Toolkit\sms\bin\i386 (0x80070091). Continuing. CreateTsMedia 4/9/2015 9:23:35 AM 14552 (0x38D8)
Unable to delete directory C:\Users\PEPEGR~1\AppData\Local\Temp\_tsmedia_14552\Toolkit\sms\bin (0x80070091). Continuing. CreateTsMedia 4/9/2015 9:23:35 AM 14552 (0x38D8)
Unable to delete directory C:\Users\PEPEGR~1\AppData\Local\Temp\_tsmedia_14552\Toolkit\sms (0x80070091). Continuing. CreateTsMedia 4/9/2015 9:23:35 AM 14552 (0x38D8)
Unable to delete directory C:\Users\PEPEGR~1\AppData\Local\Temp\_tsmedia_14552\Toolkit (0x80070091). Continuing. CreateTsMedia 4/9/2015 9:23:35 AM 14552 (0x38D8)
Unable to delete all files in temp directory. Giving up. (0x80070091) CreateTsMedia 4/9/2015 9:23:35 AM 14552 (0x38D8)
Media creation process that was started from Admin Console completed.
CreateTsMedia 4/9/2015 9:23:35 AM 14544 (0x38D0)
CreateMedia.exe finished with error code 80041002 CreateTsMedia 4/9/2015 9:23:35 AM 14544 (0x38D0)
Manuel´s Microsoft Forums Threads

Similar Messages

Create Task Sequence Media Wizard Fails

When attempting to create a bootable media for a task sequence I get the error: Media creation failed with the error message: A required privilege is not held by the client. Refer to createTSMedia.log file to find more details. Upon looking in
this log file I see the following in red:
Unable to apply (0x80070522)
Closing image file C:\Users\sccmadmin\AppData\Local\Temp\_tsmedia_7156\Cache\LSA00022\WinPE.LSA00022.wim
Failed to create media generator (0x80070522)
CreateTsMedia failed with error 0x80070522, details=''
Media creation process that was started from Admin Console completed.
CreateMedia.exe finished with error code 80070522
I get this error with trying to create an iso as well as trying to create a bootable USB drive.
The SCCM Console was started with admin privileges. I get this same error trying it on the console installed on my workstation and the console installed on the sccm server. I am a local administrator on my workstation and sccm console. I
recall successfully creating media before but for some reason this doesn't work any longer and I am not sure what changed.
SCCM Server: OS and SCCM version are 2012 R2
Workstation: Windows 7 pro

OK, I would explain the symptoms you have as you have shown at the beginning of this post, explain the difference in policies between the Dev and Prod boxes. Ask that they create a temporary policy to add the default setting of Administrators back
in for you to do some testing.
I am guessing as this is applied to your servers and workstations, based on what you have said, that this setting resides in your Default Domain Policy GPO. Which is possibly the exact issue that Hai Deep had in the post Jórgen posted here
https://social.technet.microsoft.com/Forums/systemcenter/en-US/83b11a23-24ec-46b1-9a5f-52d335dc92b5/unable-to-create-task-sequence-media-privilege-not-held-by-client?forum=configmgrosd
The above post also says it was a user right which caused the issue, so there is a fair amount of justification to apply the test.
Is your Dev instance in the same Domain or is it a completely separate lab?
let me know if you have issues,
Thanks,

No Available distribution points when i create task sequence media wizard

Hi All,
I need your support with the following issue
when I try to Create task sequence media and choose the location and boot image x64 or x86 I found this issues
FYI: I am using the administrator and i cheeked the permissions and i have the full permissions for all roles

For this issue, You can refer below link
http://blogs.technet.com/b/configurationmgr/archive/2012/08/28/troubleshooting-missing-management-points-when-creating-a-bootable-media-task-sequence-in-system-center-2012-configuration-manager.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

Create task sequence media fail. User must be local admin on DP's

We've been running into this error recently:
Failed to open to WMI namespace '\\DP-01.DOMAIN.COM\root\default' (80070005)
CreateTsMedia 5/29/2014 1:24:08 PM
11196 (0x2BBC)
Unable to open WMI namespace '\\DP-01.DOMAIN.COM\root\default' (0x80070005)
CreateTsMedia 5/29/2014 1:24:08 PM
11196 (0x2BBC)
Failed to connect to namespace 'root\default' needed to read remote registry values. The user who creates media has to be local administrator on remote DP on 'DP-01.DOMAIN.COM' which contains media content.
CreateTsMedia 5/29/2014 1:24:08 PM
11196 (0x2BBC)
The "fix" right now is to add the user needing to create task sequence media to the local admins group on the DP, which isn't necessarily ideal.
Has anyone else run into this? We create TS media every so often, so this could have started around the April timeframe. We have not changed any roles or rights on the servers, no new GPO's, no role / rights changes within SCCM etc. Only
'changes' have been the normal critical & security updates that all workstations & servers receive.

The majority of th time I have seen this error is when the drive you are imaging is in the wrong format. try it by cleaning the drive just before you start the image by doing F8 and running diskpart. This worked every time when deploying
win7, other problem I have had is when deploying win8 and not setting the BIOS to UEFI.
Hope one of these works for you.
Peyia1 ID

OSD SCCM 2012 R2: MDT integrated task sequence central logging not working

Hi,
Please advise on making dynamic logging work for SCCM 2012 R2 MDT integrated tasks sequence.
This is what I specified in customsettings.ini
[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=NO
SkipProductKey=YES
; Copy Logs if en error occurs or when deployment is successfully completed
SLSHARE=\\sccmserver\OSD\Logs\MDT
; Enable Dynamig Logging
SLSHAREDynamicLogging=\\\sccmserver\OSD\Logs\MDTDynLogs\%OSDComputername%
UserID=administrator
UserDomain=ourdomain
UserPassword=ourpassword
Jan Hoedt

I keep on getting access denied though when I connect in a dosprompt with the credentials I can make a connection.
Mapping server share: \\ourdomain.com\share   ZTIValidate   4/03/2014 0:08:14   0 (0x0000)
<Message containing password has been suppressed>   ZTIValidate   4/03/2014 0:08:14   0 (0x0000)
Access is denied.
   ZTIValidate   4/03/2014 0:08:14   0 (0x0000)
Unable to connect to \\ourdomain.com\share. Sleeping for 5 seconds.   ZTIValidate   4/03/2014 0:08:14   0 (0x0000)
<Message containing password has been suppressed>   ZTIValidate   4/03/2014 0:08:19   0 (0x0000)
Access is denied.
   ZTIValidate   4/03/2014 0:08:19   0 (0x0000)
Unable to connect to \\ourdomain.com\share. Sleeping for 10 seconds.   ZTIValidate   4/03/2014 0:08:19   0 (0x0000)
<Message containing password has been suppressed>   ZTIValidate   4/03/2014 0:08:29   0 (0x0000)
Access is denied.
   ZTIValidate   4/03/2014 0:08:29   0 (0x0000)
Unable to connect to \\ourdomain.com\share. Sleeping for 15 seconds.   ZTIValidate   4/03/2014 0:08:29   0 (0x0000)
<Message containing password has been suppressed>   ZTIValidate   4/03/2014 0:08:44   0 (0x0000)
Access is denied.
   ZTIValidate   4/03/2014 0:08:44   0 (0x0000)
Unable to connect to \\ourdomain.com\share. Sleeping for 20 seconds.   ZTIValidate   4/03/2014 0:08:44   0 (0x0000)
<Message containing password has been suppressed>   ZTIValidate   4/03/2014 0:09:04   0 (0x0000)
Access is denied.
   ZTIValidate   4/03/2014 0:09:05   0 (0x0000)
Unable to connect to \\ourdomain.com\share. Sleeping for 25 seconds.   ZTIValidate   4/03/2014 0:09:05   0 (0x0000)
ERROR - Unable to map a network drive to \\ourdomain.com\share.   ZTIValidate   4/03/2014 0:09:30   0 (0x0000)
An invalid SLShareDynamicLogging value of \\ourdomain.com\share\PackageSources\OSD\Logs\MDT-DynLogs\computername was specified.   ZTIValidate   4/03/2014 0:09:30   0 (0x0000)
Jan Hoedt

Where to put unattend.xml when using create task sequence media

SCCM 2012 R2.
I created a capture task sequence media to a flash drive. I noticed the capture media does run sysprep even though it is not located on the flash drive. Where do I put my customized unattend.xml for sysprep? Does it go in c:\sysprep
There is no documentation on this that I can find.

sysprep doesn't use an unattend.xml file so you don't put it anywhere. You supply a custom unattend.xml during the deployment task sequence which in turn is delivered as part of the TS for use by WIndows Setup (which is what actually uses an unattend.xml
file). Task Sequence media has nothing to do with sysprep either. I think you may be confusing sysprep with Windows mini-setup. sysprep is the process of generalizing a system generally preparing it to be captured. Windows mini-setup is what runs the first
time a syspreped system is booted. They are two different things.
You *can* place an unattend.xml file the image for use by Windows mini-setup -- the locations mini-setup will look for this file are detailed at
http://technet.microsoft.com/en-us/library/cc749415(v=WS.10).aspx . But that is rarely done anymore with task sequences because you generally want to dynamically inject an unattend.xml
file into the process instead of statically placing one in the image -- that defeats the purpose of having a generic reference image. This is done by configuring the Apply Windows step in a deployment task sequence.
Still, that begs the question posed by narcoticoo. Your reference image(s) should be hardware agnostic, built on a VM, and automated. What you are doing will cause you pain in the long run.
Jason | http://blog.configmgrftw.com | @jasonsandys

Sccm 2012 simulate deployment for task sequence / OS or applications

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

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

Create Task Sequence Media Issue

I am 1 of 2 people that have full admin access to our config manager environment and when I create a bootable USB stick I get an error, "80004005", after I complete the HTA which indicate a certificate issue.
However if I have my colleague create it, who is the other full admin, using the same configuration I do not get the error and see the deployments. Any suggestions?

Sorry as i re-read my message I see that I was not clear. I do not get an error while creating the bootable media, I receive that error when I attempt to use the bootable media
to OSD a device.
I am getting the 0x80004005 error post boot after I complete the HTA's questions, in the boot image, and before it looks for the available task sequences deployed to that device.

Remove sccm 2012 client package from task sequence

Hello, is possible to remove the sccm client package from task sequence ? i am deploying OS to workgroup computers and i dont want install the sccm client . I am using MDT to create the task sequence.
Erickson Martinez

No, if you are using a task sequence in ConfigMgr (MDT integrated or not) then a client package is mandatory. The only way to get rid of the client is to deinstall it at the end of the task sequence (for example by using the SMSTSPostAction variable).
Another option, if you don't want the client, is to use MDT to deploy those machines. But that would cause an extra deployment mechanism to maintain.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

MDT Task Sequence with standard "Create Task Sequence Media" image capture?

Hello,
After much research and a lot of exhausted attempts/hours between two of us we have broken down and decided to ask a very direct question. Is it possible to run an MDT Task Sequence with an image captured within SCCM and not MDT?
Reason for asking is the sequence fails every time with the error:
“Task Sequence: NAME has failed with the error code (0x80070490).”
I should note that there is no smsts log because it fails during the install and comes back with "no OS available" and there is no sccm client on the machine either. From what I could gather the error code is related to the HDD and I have tried
every setting within the task sequence I know of in different combinations to no avail. Which led us to wondering if maybe the whole process isn't even possible since we are using an MDT task sequence with an sccm image capture.
The standard task sequences work fine with the sccm image capture, but as soon as we try to the MDT sequence it fails. ANy advice/information/help on this is much appreciated.

I can't thank you enough, that was exactly it. I should have known that it would be something so simple, I've been going crazy looking through the task sequence properties trying to figure out what I could be missing.
No problem at all, happy to help! I was in the same boat driving myself crazy looking at the task sequence properties. I just happened to stumble upon that setting and decided to give it a shot since I had exhausted seemingly every other avenue.
Also, to answer your other question, in a standard task sequence, you can name the computer by using the collection variable "OSDComputerName". Just right click the collection you have your task sequence deployed to, choose properties, and then the collection
variables tab. Click the starburst, enter the variable name OSDComputerName, uncheck the box for "do not display" (I think that's the setting) and apply your changes. When you run your task sequence again, you'll choose your TS from the list, click next, double
click OSDComputerName (just clicking next will skip it and begin the TS), enter the computer name, click OK, and kick off your TS.
I'm still finding my way around SCCM since it was thrown into my lap with no prior experience so I'm happy to help when someone is stuck. I've been there more times than I can count and others have helped me.

SCCM 2012 R2 - Error with Task Sequence relating to Multicast issues

Using a copy of a working task sequence; we have deployed a new v.6.3.9600.16384 boot image with latest Intel I217-LM driver.
The task sequence runs perfectly fine, then stops after running "Setup Windows and Configmgr" task with an 0x80004005 error.
Upon examination of the smsts.log file there appears to be a problem with multicast; can anyone help?
Below is the extract of the smsts.log error:

Found this in the smsts.log;
<![LOG[==============================[ OSDSetupWindows.exe ]===========================]LOG]!><time="09:52:42.977+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="setupwindows.cpp:1627">
<![LOG[Command line: "OSDSetupWindows.exe"]LOG]!><time="09:52:42.977+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="setupwindows.cpp:1628">
<![LOG[Installing BOOTMGR bootsector]LOG]!><time="09:52:42.993+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="bootsector.cpp:73">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="09:52:43.009+480" date="03-25-2014" component="OSDSetupWindows" context="" type="0" thread="1924" file="commandline.cpp:228">
<![LOG[Set command line: "bootsect.exe" /NT60 SYS /MBR]LOG]!><time="09:52:43.009+480" date="03-25-2014" component="OSDSetupWindows" context="" type="0" thread="1924" file="commandline.cpp:731">
<![LOG[Executing command line: "bootsect.exe" /NT60 SYS /MBR]LOG]!><time="09:52:43.009+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="commandline.cpp:827">
<![LOG[Process completed with exit code 0]LOG]!><time="09:52:45.510+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="commandline.cpp:1123">
<![LOG[ResolveSource flags: 0x00000000]LOG]!><time="09:52:45.510+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="resolvesource.cpp:3201">
<![LOG[SMSTSPersistContent: . The content for package LTC00011 will be persisted]LOG]!><time="09:52:45.510+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="resolvesource.cpp:3212">
<![LOG[The package LTC00011 is found locally in the cache C:\_SMSTaskSequence\Packages\LTC00011]LOG]!><time="09:52:45.510+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="resolvesource.cpp:3242">
<![LOG[!Directory::Exists(sNormalizedPath), HRESULT=800700b7 (e:\nts_sccm_release\sms\framework\core\ccmcore\path.cpp,156)]LOG]!><time="09:52:45.510+480" date="03-25-2014" component="OSDSetupWindows" context="" type="0" thread="1924" file="path.cpp:156">
<![LOG[Setting hive location to "C:\_SMSTaskSequence\OSD\Vista\Windows\System32\SMI\Store\Machine"]LOG]!><time="09:52:45.510+480" date="03-25-2014" component="OSDSetupWindows" context="" type="0" thread="1924" file="smiinterface.cpp:812">
<![LOG[Loading existing answer file "C:\_SMSTaskSequence\unattend.xml"]LOG]!><time="09:52:45.865+480" date="03-25-2014" component="OSDSetupWindows" context="" type="0" thread="1924" file="xmlanswerfile.cpp:578">
<![LOG[Adding "C:\_SMSTaskSequence\drivers" to plug and play driver path.]LOG]!><time="09:52:45.943+480" date="03-25-2014" component="OSDSetupWindows" context="" type="0" thread="1924" file="xmlanswerfile.cpp:1894">
<![LOG[Getting namespace "Microsoft-Windows-PnpCustomizationsWinPE" for architecture "amd64"]LOG]!><time="09:52:45.943+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="smiinterface.cpp:222">
<![LOG[Writing configuration information to C:\_SMSTaskSequence\unattend.xml]LOG]!><time="09:52:45.943+480" date="03-25-2014" component="OSDSetupWindows" context="" type="0" thread="1924" file="smiinterface.cpp:860">
<![LOG[Successfully saved configuration information to C:\_SMSTaskSequence\unattend.xml]LOG]!><time="09:52:45.959+480" date="03-25-2014" component="OSDSetupWindows" context="" type="0" thread="1924" file="smiinterface.cpp:925">
<![LOG[Successfully initialized driver information]LOG]!><time="09:52:45.959+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="setupwindows.cpp:1205">
<![LOG[Command line for extension .EXE is "%1" %*]LOG]!><time="09:52:45.959+480" date="03-25-2014" component="OSDSetupWindows" context="" type="0" thread="1924" file="commandline.cpp:228">
<![LOG[Set command line: "C:\_SMSTaskSequence\Packages\LTC00011\SOURCES\SETUP.EXE" "/unattend:C:\_SMSTaskSequence\unattend.xml" /noreboot]LOG]!><time="09:52:45.959+480" date="03-25-2014" component="OSDSetupWindows" context="" type="0" thread="1924"
file="commandline.cpp:731">
<![LOG[Executing command line: "C:\_SMSTaskSequence\Packages\LTC00011\SOURCES\SETUP.EXE" "/unattend:C:\_SMSTaskSequence\unattend.xml" /noreboot]LOG]!><time="09:52:45.959+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924"
file="commandline.cpp:827">
<![LOG[Process completed with exit code 31]LOG]!><time="10:00:45.306+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="commandline.cpp:1123">
<![LOG[Windows Setup completed with exit code 31]LOG]!><time="10:00:45.306+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="setupwindows.cpp:1526">
<![LOG[ReleaseSource() for C:\_SMSTaskSequence\Packages\LTC00011.]LOG]!><time="10:00:45.306+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="resolvesource.cpp:3564">
<![LOG[reference count 1 for the source C:\_SMSTaskSequence\Packages\LTC00011 before releasing]LOG]!><time="10:00:45.306+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="resolvesource.cpp:3574">
<![LOG[Released the resolved source C:\_SMSTaskSequence\Packages\LTC00011]LOG]!><time="10:00:45.306+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="resolvesource.cpp:3612">
<![LOG[exitCode == 0, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,440)]LOG]!><time="10:00:45.306+480" date="03-25-2014" component="OSDSetupWindows" context="" type="0" thread="1924" file="setupwindows.cpp:440">
<![LOG[Windows setup failed, code 31]LOG]!><time="10:00:45.306+480" date="03-25-2014" component="OSDSetupWindows" context="" type="3" thread="1924" file="setupwindows.cpp:440">
<![LOG[setup.run(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\setupwindows\setupwindows.cpp,1650)]LOG]!><time="10:00:45.306+480" date="03-25-2014" component="OSDSetupWindows" context="" type="0" thread="1924" file="setupwindows.cpp:1650">
<![LOG[Exiting with code 0x80004005]LOG]!><time="10:00:45.306+480" date="03-25-2014" component="OSDSetupWindows" context="" type="1" thread="1924" file="setupwindows.cpp:1696">
<![LOG[Process completed with exit code 2147500037]LOG]!><time="10:00:45.306+480" date="03-25-2014" component="TSManager" context="" type="1" thread="1048" file="commandline.cpp:1123">
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="10:00:45.306+480" date="03-25-2014" component="TSManager" context="" type="1" thread="1048" file="instruction.cxx:804">
<![LOG[Failed to run the action: Setup Windows and ConfigMgr.
Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="10:00:45.306+480" date="03-25-2014" component="TSManager" context="" type="3" thread="1048" file="instruction.cxx:895">
<![LOG[MP server http://Darwin.ltcharity.org.uk. Ports 80,443. CRL=false.]LOG]!><time="10:00:45.321+480" date="03-25-2014" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:5881">
<![LOG[Setting authenticator]LOG]!><time="10:00:45.337+480" date="03-25-2014" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:5903">
<![LOG[Set authenticator in transport]LOG]!><time="10:00:45.353+480" date="03-25-2014" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:7734">
<![LOG[Sending StatusMessage]LOG]!><time="10:00:45.434+480" date="03-25-2014" component="TSManager" context="" type="1" thread="1048" file="libsmsmessaging.cpp:4023">
<![LOG[Setting message signatures.]LOG]!><time="10:00:45.436+480" date="03-25-2014" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:1295">
<![LOG[Setting the authenticator.]LOG]!><time="10:00:45.444+480" date="03-25-2014" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:1325">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: Darwin.ltcharity.org.uk:80 CCM_POST /ccm_system/request]LOG]!><time="10:00:45.444+480" date="03-25-2014" component="TSManager" context="" type="1" thread="1048" file="libsmsmessaging.cpp:8604">
<![LOG[Request was successful.]LOG]!><time="10:00:45.476+480" date="03-25-2014" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:8939">
<![LOG[Set a global environment variable _SMSTSLastActionRetCode=-2147467259]LOG]!><time="10:00:45.476+480" date="03-25-2014" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:668">
<![LOG[Set a global environment variable _SMSTSLastActionSucceeded=false]LOG]!><time="10:00:45.476+480" date="03-25-2014" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:668">
<![LOG[Clear local default environment]LOG]!><time="10:00:45.476+480" date="03-25-2014" component="TSManager" context="" type="0" thread="1048" file="executionenv.cxx:807">
<![LOG[Let the parent group (Setup Operating System) decides whether to continue execution]LOG]!><time="10:00:45.491+480" date="03-25-2014" component="TSManager" context="" type="0" thread="1048" file="instruction.cxx:1004">
<![LOG[Let the parent group (Install Operating System) decide whether to continue execution]LOG]!><time="10:00:45.491+480" date="03-25-2014" component="TSManager" context="" type="0" thread="1048" file="instruction.cxx:254">
<![LOG[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)]LOG]!><time="10:00:45.491+480" date="03-25-2014" component="TSManager" context="" type="3" thread="1048" file="instruction.cxx:217">
<![LOG[Failed to run the last action: Setup Windows and ConfigMgr. Execution of task sequence failed.
Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="10:00:45.491+480" date="03-25-2014" component="TSManager" context="" type="3" thread="1048" file="engine.cxx:213">
<![LOG[MP server http://Darwin.ltcharity.org.uk. Ports 80,443. CRL=false.]LOG]!><time="10:00:45.491+480" date="03-25-2014" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:5881">
<![LOG[Setting authenticator]LOG]!><time="10:00:45.522+480" date="03-25-2014" component="TSManager" context="" type="1" thread="1048" file="utils.cpp:5903">
<![LOG[Set authenticator in transport]LOG]!><time="10:00:45.522+480" date="03-25-2014" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:7734">
<![LOG[Sending StatusMessage]LOG]!><time="10:00:45.539+480" date="03-25-2014" component="TSManager" context="" type="1" thread="1048" file="libsmsmessaging.cpp:4023">
<![LOG[Setting message signatures.]LOG]!><time="10:00:45.539+480" date="03-25-2014" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:1295">
<![LOG[Setting the authenticator.]LOG]!><time="10:00:45.539+480" date="03-25-2014" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:1325">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: Darwin.ltcharity.org.uk:80 CCM_POST /ccm_system/request]LOG]!><time="10:00:45.539+480" date="03-25-2014" component="TSManager" context="" type="1" thread="1048" file="libsmsmessaging.cpp:8604">
<![LOG[Request was successful.]LOG]!><time="10:00:45.570+480" date="03-25-2014" component="TSManager" context="" type="0" thread="1048" file="libsmsmessaging.cpp:8939">
<![LOG[Executing command line: X:\windows\system32\cmd.exe /k]LOG]!><time="10:03:20.975+480" date="03-25-2014" component="TSBootShell" context="" type="1" thread="776" file="bootshell.cpp:860">
So according to this log "Windows setup failed, CODE 31", Which then produced the more generic 8004005 error.

Permissions to Run Task Sequence Media

We have a task sequence media on a USB drive. When I run the autorun as a user it never launches. When I log on as domain admin the task sequence media runs. What permissions are needed to run a task sequence media?
J Gruber

Are your users denied running autorun/autoplay, or denied running executables from removable media?
This discussion may help:
http://social.technet.microsoft.com/Forums/en-US/bef8a10b-7ac0-4b61-88a0-c8d41697c44a/configmgr-2012-capture-media-does-not-run?forum=configmanagerosd
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Cannot Create Full Task Sequence Media

------------------------------------------- CreateTsMedia 18/03/2015 13:38:20 14880 (0x3A20)
Omitting AppContent source \\server1.fqdn because server1.fqdn has not been selected by user as a DP to use in creating media CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
Omitting AppContent source \\server2.fqdn because server2.fqdn has not been selected by user as a DP to use in creating media CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
Omitting AppContent source \\server3.fqdn because server3.fqdn has not been selected by user as a DP to use in creating media CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
Omitting AppContent source \\server4.fqdn because server4.fqdn has not been selected by user as a DP to use in creating media CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
Omitting AppContent source \\server5.fqdn because server5.fqdn has not been selected by user as a DP to use in creating media CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
Omitting AppContent source \\server6.fqdn because server6.fqdn has not been selected by user as a DP to use in creating media CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
Omitting AppContent source \\server7.fqdn because server7.fqdn has not been selected by user as a DP to use in creating media CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
Omitting AppContent source \\server8.fqdn because server8.fqdn has not been selected by user as a DP to use in creating media CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
Content Library: Path='F:\SCCMContentLib', Drives='F:\,G:\,C:\,H:\,E:\' CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
Found contentID Content_c5cc628a-fafe-4d7f-bcaa-2b44cebf1bfa.1 of App package SiteCode00790, size 24 Mb CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
CContentDefinition::GetFileProperties failed; 0x80070003 CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
CContentDefinition::TotalFileSizes failed; 0x80070003 CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
Failed to find size of contentID Content_0ba3179e-0762-494f-bdaf-b4a16794e07c.1 of App package SiteCode00790 CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
Failed to download app content CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
Failed to get App content info CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
Failed to create media (0x80070003) CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
CreateTsMedia failed with error 0x80070003, details='[Application]' CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
MediaGenerator::~MediaGenerator() CreateTsMedia 18/03/2015 13:38:21 14880 (0x3A20)
[Application] CreateTsMedia 18/03/2015 13:38:22 14880 (0x3A20)
Media creation process that was started from Admin Console completed.
CreateTsMedia 18/03/2015 13:38:22 7152 (0x1BF0)
CreateMedia.exe finished with error code 80070003 CreateTsMedia 18/03/2015 13:38:22 7152 (0x1BF0)
The content path for the App is valid, the files are in that folder, the app installs fine, this is a live task sequence, i cannot see anything wrong with this application.
Why is this failing?

Seems as if the application cannot be found on the DP(s) you selected for creating the TS media.
Torsten Meringer | http://www.mssccmfaq.de
Thats what i assumed, so i check the path, repushed a new version of the source to DPs, that succeeded, and as i mention that Application is in use so devices are pulling and installing it in the same boundary.
I have tried creating the ISO on a remote machine and the server with the same error.
Seems to me like another issue that exists with applications but not with packages.......grumble grumble.....

Create Task Sequence Standalone media help required

Hi,
Environment is SCCM 2012 SP1
I have a Win 8.1 & Win7 OS image captured from reference machine and able to deploy to machines without any issues using TS.
Now I am trying to create Standalone media in USB/DVD.
1. I am able to create .iso file when I select 8.5GB DVD type in the wizard. What steps should I perform to burn it to DVD? The normal burn from .iso does not work as it does not make it bootable.
2. When I tried to create a USB standalone media it errors out indicating Not enough space on disk. The USB is 16GB of size and the Createmedia.exe formats the USB to FAT32. Hence, the install image does not get copied.
Please advice.

More info:
How to create a Bootable DVD
http://blogs.msdn.com/b/cesardelatorre/archive/2009/03/08/how-to-create-a-bootable-dvd-windows-7-or-windows-vista.aspx
How to make a bootable DVD?
http://www.winiso.com/support/tutorials/make-bootable-dvd.html
Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

SCCM's OSD (not MDT): Task sequence can be tweaked into imaging Windows+VHD Native Boot, but can it go all the way and deploy?

Hello All,
What I am trying to do is use SCCM's own OSD Task Sequence / Windows PE to deploy an operating system that boots using VHD Native Boot. (C:\ = VHD File with Windows, D:\ Data drive with BCDBoot).
MDT 2013 Can do it I've been told, but I am putting off MDT until Windows 10 if I can get away with it.
TechNet VHD Native Boot on Windows 8.1:
http://technet.microsoft.com/en-us/library/hh825689.aspx
http://technet.microsoft.com/en-us/library/hh825691.aspx
The good news is it is working up to the "Apply Operating System" phase, but that apply operating system phase is reported as an error even though it completes successfully. It can't clean up the SMSTS folder it's looking for on the C:\ because
it's been moved over to the D:\ by a diskpart script. We are left with the deployment working but requiring IT staff to deal with the OOBE Personalization wizard and adding each PC to the domain manually. From that point on the SCCM client can do the rest,
which works for US before we upgrade to Windows 10 with utilizing MDT.
I am not talking about deploying an OS to a VHD file and putting that file on a network share i.e.
http://blogs.technet.com/b/configurationmgr/archive/2013/10/31/new-in-system-center-2012-r2-configuration-manager-deploying-an-operating-system-to-a-virtual-hard-drive-vhd.aspx
I reported getting the diskpart script working first here:
https://social.technet.microsoft.com/Forums/en-US/ff124f09-1d2e-4fc4-a5b6-63b683f3d208/native-vhd-boot-deployments-from-sccm-2012-r2?forum=configmanagerosd
Here it is:
rem work around any USB disk left in or any CDROM detected by PE as drive D
select volume D
assign letter=F noerr
rem select the formatted volume and reassign it's drive letter
select volume C
assign letter=D
rem create and setup VHD file
create vdisk file=D:\DEV_WIN81.VHD maximum=250000 type=expandable
select vdisk file=D:\DEV_WIN81.VHD
attach vdisk
create partition primary
active
format FS=NTFS quick label="Developer Win81 VHD"
assign letter=C
rescan
exit
(type=fixed is better for performance - we'll surely activate when we have dual boot 8.1 / Windows 10 later for the Win10 VHD's)
The Task Sequence looks like this:
I'd like to add a few more steps after apply operating system if I can, but I have to resolve this error with "Apply Operating system before I can go further."
Question:
Can an OSD guru tell me if there are any Task Sequence Variables we could throw at this to make the Apply Operating System sequence complete without error so we can do all SCCM OSD Deployment steps?
If we can, then someone (not me) gets to add a new TechNet blog post about this being possible. It's my understanding presently that only MDT can support deploying WIM files into VHDs on Workstations, that boot them.
The install image was created using dism to convert a VHD from a Hyper-V host into a wim. I know I'm meant to use SCCM to capture it, but I don't think that's causing this problem because when we are deploying from that image to a HDD without VHD we don't
get any issues.
I'm only allowed enough characters to paste the tail end of the apply operating system phase only:
<![LOG[Execution engine result code: Success (0)]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:929">
<![LOG[Cleaning Up.]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:675">
<![LOG[Removing Authenticator]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:686">
<![LOG[shKey.DeleteValue( c_szRegValue_SecurityToken ), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\ccmutillib\ccmutillib.cpp,1660)]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="ccmutillib.cpp:1660">
<![LOG[Cleaning up task sequence folder]LOG]!><time="18:29:37.691-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:2329">
<![LOG[Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="ccmfile.cpp:1056">
<![LOG[hr, HRESULT=80070091 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmfile.cpp,1218)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="ccmfile.cpp:1218">
<![LOG[Failed to delete directory 'C:\_SMSTaskSequence']LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="ccmfile.cpp:1218">
<![LOG[(dwRet = ::SetNamedSecurityInfoW ((WCHAR*) pszObjectName, objectType, OWNER_SECURITY_INFORMATION, pOwnerSID, NULL, NULL, NULL)) == ERROR_SUCCESS, HRESULT=80070005 (e:\qfe\nts\sms\framework\tscore\utils.cpp,6675)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:6675">
<![LOG[SetNamedSecurityInfo() failed.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6675">
<![LOG[SetObjectOwner() failed. 0x80070005.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6687">
<![LOG[SetObjectOwner (szFName, SE_FILE_OBJECT, c_szAdministrators), HRESULT=80070005 (e:\qfe\nts\sms\framework\tscore\utils.cpp,6772)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:6772">
<![LOG[RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="3" thread="960" file="utils.cpp:6816">
<![LOG[RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:6900">
<![LOG[Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="resolvesource.cpp:506">
<![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,508)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="resolvesource.cpp:508">
<![LOG[Deleting volume ID file D:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="resolvesource.cpp:506">
<![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\resolvesource.cpp,508)]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="resolvesource.cpp:508">
<![LOG[Successfully unregistered Task Sequencing Environment COM Interface.]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="environmentlib.cpp:910">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="commandline.cpp:228">
<![LOG[Set command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="commandline.cpp:731">
<![LOG[Executing command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.738-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="commandline.cpp:827">
<![LOG[==========[ TsProgressUI started in process 8012 ]==========]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:330">
<![LOG[Command line: "X:\sms\bin\x64\TsProgressUI.exe" /Unregister]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="0" thread="8040" file="winmain.cpp:332">
<![LOG[Unregistering COM classes]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:204">
<![LOG[Unregistering class objects]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:495">
<![LOG[Shutdown complete.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TsProgressUI" context="" type="1" thread="8040" file="winmain.cpp:512">
<![LOG[Process completed with exit code 0]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="commandline.cpp:1123">
<![LOG[Successfully unregistered TS Progress UI.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:2903">
<![LOG[Sending success status message]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:784">
<![LOG[MP server http://OUR-SCCM.ourcompany.com. Ports 80,443. CRL=false.]LOG]!><time="18:29:37.754-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:5881">
<![LOG[Setting authenticator]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="utils.cpp:5903">
<![LOG[Set authenticator in transport]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:7734">
<![LOG[Sending StatusMessage]LOG]!><time="18:29:37.785-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="libsmsmessaging.cpp:4023">
<![LOG[Setting message signatures.]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:1295">
<![LOG[Setting the authenticator.]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:1325">
<![LOG[CLibSMSMessageWinHttpTransport::Send: URL: OUR-SCCM.ourcompany.com:80 CCM_POST /ccm_system/request]LOG]!><time="18:29:37.801-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="libsmsmessaging.cpp:8604">
<![LOG[Request was successful.]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="libsmsmessaging.cpp:8939">
<![LOG[::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,811)]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="0" thread="960" file="utils.cpp:811">
<![LOG[RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:811">
<![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="2" thread="960" file="utils.cpp:842">
<![LOG[End program: ]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tsmanager.cpp:805">
<![LOG[Finalize logging request ignored from process 856]LOG]!><time="18:29:37.832-420" date="12-26-2014" component="TSManager" context="" type="1" thread="960" file="tslogging.cpp:1737">
<![LOG[Process completed with exit code 0]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="commandline.cpp:1123">
<![LOG[Task Sequence Manager returned code 0x00000000]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="tsmediawizardcontrol.cpp:2180">
<![LOG[Exiting with return code 0x00000000]LOG]!><time="18:29:37.863-420" date="12-26-2014" component="TSPxe" context="" type="1" thread="592" file="tsmbootstrap.cpp:1238">
<![LOG[Execution complete.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:693">
<![LOG[hMap != 0, HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentscope.cpp,493)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentscope.cpp:493">
<![LOG[m_pGlobalScope->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,335)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentlib.cpp:335">
<![LOG[this->open(), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\environmentlib.cpp,553)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="environmentlib.cpp:553">
<![LOG[::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,811)]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="utils.cpp:811">
<![LOG[RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="2" thread="760" file="utils.cpp:811">
<![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="2" thread="760" file="utils.cpp:842">
<![LOG[End program: ]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="bootshell.cpp:725">
<![LOG[Finalizing logging from process 752]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1741">
<![LOG[Finalizing logs to root of first available drive]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1583">
<![LOG[Successfully finalized logs to D:\SMSTSLog]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="1" thread="760" file="tslogging.cpp:1640">
<![LOG[Cleaning up task sequencing logging configuration.]LOG]!><time="18:29:37.879-420" date="12-26-2014" component="TSBootShell" context="" type="0" thread="760" file="tslogging.cpp:584">
MCSE,MCNE,SCO,Sair Linux/GNU, Open source-enthusiast.

I have already set it to FALSE. The solution to this will be some different OSD Task Sequence variables or a statement that it can't be made to work.
I believe that setting defines what volume will be the BOOT / OS Drive Letter. Some people were getting D:\WINDOWS as their boot volume drive letter. Setting to true means whatever was the System Drive letter (usually C) in the image will remain as such
after it was was applied, setting it to false will make the system have the same drive letter arrangement as what Windows PE detects. In my case I set it to false so that no matter what the new VHD file setup as drive C will be the system drive. I'll set it
to true on the next deployment but I expect there to be no difference, because in both PE and the WIM the installation volume is the C:.
We are talking about the DRIVE LETTERS Windows PE SCCM OSD is using for it's temporary files - and how we can manipulate these locations using OSD Task Sequence Variables, so the Apply OS doesn't try and clean up files that are not there
- and fail with an error if you have added a VHD Native Boot volume.
This OSDPreserveDriveLetter setting isn't having any effect on the problem here.
I believe that Format step is setting some task variables used by the OSD Deployment process - telling it where to store it's temporary files. However between the Format Disks and Apply operating system steps the OSD Task Sequence isn't picking up on the
fact what was the C:\ after Format HDD step is now the D:\ .
A developer who has an understanding of how the OSD boot process executes in order would be able to see what's going on here.
MCSE,MCNE,SCO,Sair Linux/GNU, Open source-enthusiast.

SCCM 2012 R2 cannot create Task Sequence Media

Similar Messages

Maybe you are looking for