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.

Similar Messages

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

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

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

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.

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

SCCM Task sequence OSD issue with windows recovery

Hi,
Just wanted to know if anyone else gets a strange issue I have sometimes during my W7 deployment. We have deployed approx. 1500 PCs using this task sequence with no problems but about 5 or so PCs get stuck after different stages and windows start automatic
repair and tries to fix an issue which fails and sticks at the recovery screen.
If you cancel the auto repair the TS continues no issue but this usually happens at our remote sites that are a days drive away. I have just had it happen on a new PC we just got that I am testing the driver pack with and just wanted to know if
anyone else has this issue?
I have a script I run out to all my PCs after SOE is applied to prevent this as we have found our users are not good a clean shutdowns and this prevents auto repair after the fact but I am thinking I might push this script after applying the image to prevent
this from happening again.
The script I use is as follows.
cmd.exe /c "%windir%\system32\bcdedit.exe" /set {default} bootstatuspolicy ignoreallfailures >c:\tempsccm\bcdedit.log
If anyone can let me know if this happens to you that would be great.
Cheers.

You PC need to be recovered error may come in below cases.
1. MAC id is wrong while importing the asset in CM.
2. BIOS date and time is improper.
3. Disk failure
4. WDS is not functional.
Regards, Shishir Kushawaha "If this thread answered your question, please click on "Mark as Answer"

Hidden Task sequences - Media vs PXE boot

Hello all -
I have a custom configuration where we have 6 different *available* (not mandatory) task sequences deployed to PXE and Boot Media (Hidden) and I'm using a small powershell forms app to select which deployment ID they are using. I get slightly different
behavior with Boot Media vs PXE.
Boot Media
I get a "Welcome to the Task Sequence Wizard" dialog before it enumerates policies (as expected)
I use the powershell form and hit submit
I get a confirmation dialog (same physical size as the first one) "The required task sequence will run be (Insert task sequence name here). Simply hit ok at this point. There is no timer or countdown.
PXE
I do not get any introductory dialog box. It immediately goes into the Powershell form.
I use the powershell form and hit submit.
The next dialog I get is a small one, informing me of the *mandatory* task sequence that will run in 180 seconds. This will count down to zero. This behavior is undesirable.
I'm fine with getting the introductory dialog box, but getting the 180 second countdown of a mandatory task sequence (no task sequence is mandatory) is not desirable.
Is this expected? When I wasn't using hidden task sequences, I still got the first dialog, it just didn't have options for DHCP/network config as before.

So, you're using pre-execution-hook, to execute your PoSH ?
We do something similar (pre-select a TS), so that we can run specific hidden OSD TS, for our "test and dev" TS.
We use TSmedia to do that, not PXE. (I'll need to check, but I use TSmedia myself. Maybe my colleague might use PXE for this. He is the real brains in my team ;)
For us, PXE is used for "regular/production-ready" OSD TS, not for dev.
We don't use mandatory/required TS - all of ours are optional/available.
We use All Systems(filtered by OS), and Unknown Computers, as the deployment target. In our organisation, end-users reimage their PC's as they see fit, on a self-service basis.
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!)

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]

Is there any way to speed up the task sequence media wizard?

Hi. I'm running SCCM 2007 R2. We mostly deploy our OS builds with USB keys. Our image is approx 7GB so it was taking a long time every time we wanted to create a new key (approx 2 hours). After looking online the solution seemed to be to visit a machine
with a DP and plug in the key directly.
I have the SCCM console on my local PC (Win7 Ultimate) and I've installer a DP on my PC. After some initial problems I got all the packages to update the DP and all looks OK. However I'm running the first key build now and it's been going for over 2 hours.
I can see files been written to the key in windows explorer and the CreateTsMedia.log isn't showing any errors. It's just really slow. Have i missed a step? Is it like this the first time you use a DP?
thanks

Yes, I know this is an old post, but I’m trying to clean them up.
Are you building the USB key locally to CM12 or remotely? I have always found that building the USB key locally on CM07 site server to be the fastest way to do this.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

2 questions - missing boot image, create mdt task sequence button missing

I'm learning SCCM 2012. I am watching a training video and the instructor shows a "Create MDT Task Sequence" button at the top of his ribbon bar when going into Task Sequence. I do not have this button - where did it go? I am
using 2012 SP1.
All I see is "Create Task Sequence" and "Create Task Sequence Media" but not "Create MDT Task Sequence".
Also - I only have an x86 boot image, and no x64. How do I get this into my inventory?
Thank you
Nathan

"Create MDT Task Sequence" will be visible after you install MDT and integrate it to SCCM.
MDT is different product and not part of default SCCM installation.
You can integrate MDT to SCCM to create advanced Task Sequence if the default is not suitable for your needs.
Integrate MDT to SCCM.
MDT latest version is 2013:
http://www.microsoft.com/en-us/download/details.aspx?id=40796
For creating x64 boot image:
http://social.technet.microsoft.com/Forums/en-US/a3877a66-d35c-49ca-95c5-1c02d1611f2f/default-x64-boot-image-not-created-during-sccm-2012-setup
Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

OSD - USB insert media #1 for the task sequence

Hi
I'm creating a standalone media for USB
Step that I did
1. Create a Standalone media to .iso files
2. Diskpart - I prepared the USB using the diskpart command
3. Extract the standalone.iso files in the USB (copy the contents)
everything is work fine, exempt the packages that I included in the stanadlone TS is NOT installed and asking for "insert media #1 for the task sequence"
This issue arise only when I used the USB
Content of T.S (stand alone task sequence)
a. Windows 7 and company standard application
b. Packages 1 : Install the 7Zip
c. Packages 2 : Install the update for the acrobat reader
I don't want to recreate the images due to minor changes and it will consume time also, that's why I added in the T.S place in USB
Please advise , what is wrong
Robert

Hi,
We also get the same problem, and at the time it occurs the USB stick does not show up in notepad, or in diskpart list disk.
It happens after the windows 7 image is apply just as it's trying to install the applications.

Create Task Sequence Media Issue

Similar Messages

Maybe you are looking for