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

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

  • 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

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

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

  • Where to put firmware files when using hwdetect

    I am using release 0.7.1. AFAIK in 0.7.1 hwdetect is used instead of hotplug. Where hwdetect expect to find firmware files? In the case it can be changed, please tell me where.

    it's udev that is handling firmware files, and I placed mine for atmel wireless in /lib/firmware works fine

  • SInce i installed Lion, my desktop icons are lining up like regimented Windows icons!  how do i get them to stay where i put them, like they used to do?  thanks! ellen

    SInce i installed Lion, my desktop icons are lining up like regimented Windows icons! 
    how do i get them to stay where i put them, like they used to do? 
    thanks!
    ellen

    In that case, there may be a problem with your Finder preferences or window settings.
    Try removing these files, then restarting:
    ~/Library/Preferences/com.apple.finder.plist
    ~/Desktop/.DS_Store
    Let me know if you're not sure how to do that.

  • Where are my designs stored when using Adobe CC and can i access them if i cancel ?

    where are my designs stored when using Adobe CC and can i access them if i cancel ?

    This is answered in the CC FAQ: http://www.adobe.com/products/creativecloud/faq.html

  • Deploying the SCCM 2012 Client to WES 7 devices that are locked down with the FBWF using 2007 task sequence via WEDM.

    I'm wondering how people are migrating their embedded devices that are using the FBWF. I've done some googling and it seems like most people are just re-imaging the devices and after migrating a single device i see why. Its not a pretty process. This will
    be a long description but ultimately my question stems more from trying to find a better way to execute the device migration from 2007 to 2012.
    Some back ground on my situation might be in order here. I'm in the process of wrapping up our 2007 to 2012 migration. We have a 2007 infrastructure that was a central server with 2 primaries and 286 secondary site servers. I've consolidated that to a single
    2012 primary site server that hosts all the main roles. There are 2 more servers in the data centers both operating solely as push distribution points I'll refer to them as 2012 01 02 and 03. I'm over half way through the migration and so far haven't needed
    to offload any site roles. There are almost 10,000 clients now reporting to the 2012 site server and almost a 100 field servers pulling content from 2012 02 as their source dp as pull dp is the only way forward for this many devices. I've read the horror stories
    of trying spin up 200 plus push dps. We are running PKI. I'm at the point now where i need to start migrating the Windows Embedded Seven Standard clients that have the 2007 sccm client on them with WEDM for write filter handling.
    What i'm wondering is if anyone has any pointers for me regarding migrating the WES 7 devices. My plan that i've come up with is to somehow script the process using a 2007 WEDM Task Sequence to try and migrate them over to 2012. Things are complicated as
    I need to somehow script the install, the policy checkin, hardware inventory, software inventory, and validate the SCEP client installs before I reboot the device one last time to enable the FBWF. How I handled the SCCM 2007 client install on these devices
    when they were provisioned was to just create a batch file that would sleep for ten minutes then check to see if the inventoryagent.log file had been created yet. I realize now that is inefficient as i can kick off the inventory using a WMI method once the
    client has installed. Also I need to make sure the machine gets its first policy as that is how it creates the communication using PKI through that first policy transfer and that also finalizes the client install. The biggest piece i'm uncertain about in this
    regard is the SCEP client.
    I had to change the SCEP client install from yes to no in the default client settings as we have some Mcaffee servers that can't have the SCEP client on them. I have incremental updates enabled on the collection that has the policy that installs the SCEP
    client but this will take an unknown amount of time unless i force the environment to update as the device starts in 2012 install, or if I could kick off the SCEP isntall... IDK. I'm also wondering if i should keep the device in the migration process until
    i validate it has its proper scep policy applied which I believe can be validated by a registry key somewhere.
    Once the 2012 client gets installed will that cause it to lose its place within the 2007 Task Sequence? Considering its going to take a minimum of 2 reboots I'd normally use the task sequence to handle its progression through the process.
    I'm also considering trying to use an Orchestrator runbook, as that would be a good way to keep track of the migration process as each device migrates. Especially since this might take several seperate scripts.
    I'm going to take a stab at scripting the migration process, but if anyone has any pointers that might make this a less complicated I'd really appreciate it as I've got about 3000 of these devices that need to be migrated over. The other things i've learned
    the hard way is any time you have something this complicated over the course of 3000 devices you will run into unknowns and the failure rate increases. I'm in the precarious position of having to not only build this process out but in some situations have
    it complete in the shortest amount of time possible as we have sites running 24x7. I know the end users behavior all to well and they will just keep hitting the power button sometimes even though their not supposed to so they can get their device functional
    again. In those situations i'd end up, if i'm lucky with a device that no longer has a healthy SCCM client in either environment and the write filter disabled.
    So like i said any pointers anyone could throw my way i'd really appreciate. I manually went through the migration process on a single device for proof of concept and ended up with almost 2 pages of pseudo code for my migration script/scripts.
    Thanks,
    -K.R.

    Hi,
    In R2 there are some new variables you can use to solve this,
    http://ccmexec.com/2014/12/smstsmplistrequesttimeout-value-in-milliseconds/
    In Sp1 though adding a step to sleep for 2-5 minuter after reboot and before the application install step is a common workaround.. a powershell command with "Start-Sleep
    -s 120" should do it. 
    /Jörgen
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

  • The configuration file did not contain well formed AppV configuration XML - When using Office 2013 ODT package

    All,
    I'm experiencing an issue where when using the Office 2013 package pulled down from ODT, that if I try to change the locations of either InfoPath Filler 2013 or Publisher 2013 from the default of Microsoft Office 2013 then I receive the message "The
    configuration file did not contain well formed AppV configuration XML. Please check the management server event log for more information". If I check Applications and Services\Microsoft\AppV\Server-Management\Admin the error displayed there is "An
    error was encountered parsing dynamic configuration file '0'. However I am able to change the shortcut location for all other applications except the above 2. I've tried redownloading the files using the ODT and also changing the version number (so far I've
    tried both the 15.0.4631.1002 and 15.0.4659.1001 with the same result).
    As all I'm interested in so far is having a package which contains Visio and Project I've tried following the article to exclude all the other Office elements:
    http://technet.microsoft.com/library/jj219426(v=office.15).aspx#BKMK_ExcludeAppElement. However the package looks to be the same and when I load it into the management console all the options and elements to Office 2013 are available like they were before
    when I hadn't set the exclude tags so I'm not sure whether the ExcludeApp parameters actually work correctly.
    This then brings me onto the 3rd issue I've experienced. I have a group for the Visio users and I've set custom security for them to have Visio delivered to them but not Project and then a seperate group for just Project users who will have Project delivered
    to them but not have Visio. When testing this sometimes seems to work but other times it seems to trip out and a user just in the Project or Visio group will get all of the Office 2013 applications and under the default location of Microsoft Office 2013. When
    trying to spot correlation with this it appears random and can happen to any user on any device. We have sequenced a few applications ourselves where different parts are needed for different users and we have successfully managed this using different security
    groups for different applications, just as I'm trying here with Office 2013.
    Has anyone else experienced the issue with the "did not contain well formed XML" as at the start of the post and how were you able to resolve this? Also has anyone any advice on how to troubleshoot the issue with the security seeming to trip out
    and publish all applications within a package to a user regardless of whether they are in the correct group or not?
    The management / publishing servers are 5.0.1224.0 which is SP1 HF4 and the clients are on SP2 HF5.
    Thanks

    Nicke,
    The config files are UTF-8. I did find the same article as yourself, however when searching for the value ‘TakeoverExtensionPointsFrom46=’ within either of the configuration.xml files that text isn’t found.
    No sinister reason not to share the file used, just it’s the same structure as referenced in the article:
    http://technet.microsoft.com/en-us/library/dn745895(v=office.15).aspx. The only difference being that I’m using ProPlusVolume and I’ve set a version number (which is the October
    2014 update). I’ve even looked to follow the above example as closely as possible in just using the ExcludeApp ID of Access and InfoPath, just to try and prove the process. However I still get the usual full package. The version of the Click-to-Run setup.exe
    I’m using is 15.0.4623.1001, so later than the version specified at the end of that article which is 15.0.4619.1000. Where can I expect to see the elements excluded? Will it be when loading the package into the management console or would it just not appear
    on the machine when delivered?
    <Configuration>
      <Add SourcePath="C:\OfficeDeploymentToolV2" Version="15.0.4659.1001" OfficeClientEdition="32">
        <Product ID="ProPlusVolume">
          <Language ID="en-us" />
    <ExcludeApp ID="Access" />
    <ExcludeApp ID="InfoPath" />
        </Product>
      </Add>
    </Configuration>
    3). We’ve not used global publishing in our environment yet so I will try that. I’ve set both GlobalRefreshEnabled and GlobalRefreshOnLogon to True and when using the command Get-AppvPublishingServer on the client I’m testing with I can see this is pulled
    through correctly. I’ve also added the client name to the AD group used to grant access to the package and it is published. However nothing is pulling through onto the Client, so are there any steps I’ve missed or misinterpreted when looking to set this up?
    I guess the global publishing is there to keep in with licensing for Office being per device? On a slight aside, as Windows licensing is being changed to allow per user licensing
    http://www.zdnet.com/microsoft-to-make-per-user-windows-licensing-available-to-enterprise-customers-7000035401/ does anyone know if there are any plans to allow for Office / Project / Visio licenses to go per user as well? We’re a volume license customer
    rather than subscription based so I think a lot of the options to selectively deploy Visio and Project are excluded for us.
    Dan,
    Ok that explains why the security could be tripping out then and leading to this result. As above I’ll try with global publishing and see how I get on.
     From what I’ve read / watched  I think only one Office 2013 package can be published to a machine, so we would be unable to have a separate package for Visio and a separate package for Project and then attempt to deliver
    them both together. If a user wanted both Project and Visio then I guess we’d need to have a combined Project and Visio package to cover than scenario, but then 2 more separate Project and Visio packages for those who would only want either Project and Visio
    (I think).
    The scenario we’re looking at is to see whether we are able to deliver Project and / or Visio to different users through an AppV package and this will then cover users on XenApp or on fat clients. Only a small proportion of our
    users will need access to Project and / or Visio so therefore we’d only have a small amount of Project and Visio licenses.
    However from what I’ve tested up to this point and from what I’ve picked up from Forum posts / watched on TechEd sessions is that as publishing is Global and is unable to use different security groups for different elements of the
    suite, then using Office through AppV is only suitable if you will be delivering the whole suite (including Project and Visio) to all of your users. So in a scenario where you’d only want certain elements to be delivered to a handful of users then you’d need
    to keep with traditional ESD methods to have this installed onto fat clients and steer clear of XenApp. If wanting to install to XenApp then a lockdown tool like AppSense or AppLocker would also need to be brought into the equation.
    Is my understanding above correct or have I missed some options / methods?
    If the full Office package is always delivered but a company only has Office licenses and no Project and Visio licenses for all its users, how do they stop Project and Visio being delivered and being available? Or again if you have
    this use case is the AppV method one which will be unsuitable?
    Thanks

  • Data Corrupted when using CREATE AS SELECT * FROM over DB LINK

    Hi ,
    I wonder if anyone has suffered a simillar issue as this:
    I have a DB Link Between a 10gR1 (Base install not patched) database on Windows 2003, and a 10gR2 (with latest Patch Database ) on Sun Solaris. The 10.1 DB is the SOURCE 10.2 is TARGET
    When using a statement like the following on the Target :
    CREATE TABLE a AS SELECT * FROM TABLE a@SOURCE
    The statement completes, however for some (not all) tables, the data content is seriously corrupted, I noticed this when trying to apply a UKey on the newly created table in TARGET. The data was completely messed up for around 600 out of 450000 rows, I could not easily tell which rows were messed up as it was the columns that build the UKey that were affected :-(
    The same happens if I precreate the table and use INSERT /*+APPEND*/ INTO AS SELECT.... etc
    I realise that using an unpatched 10.1 is not nessasarily advisable, however currently it is difficult for us to patch or upgrade the DB...
    If anyone has seen this before an/or has any ideas what might be the cause , I would appreciate any help I can get.
    Cheers
    JAmes

    The Problem Manifest itsself in that some fileds are created with incorrect Values, specificaly in easy to identify cases NULL where the original values where not NULL.
    These field do not contain special chars like ä or ß , so it does not seem to indicate a charset issue.
    JAmes

  • When using "create outlines" on type, gradient goes wacky & outlines look strange (InDesign CS6)

    Hi,
    I'm working on a logo in InDesign CS6 where I'm trying to "create outlines" from type I've set so I can have some final artwork to hand over to a sign company. The type has a gradient applied, along with a white stroke added to the outside. When I "create outlines" of the font, the gradient mysteriously changes angle and the white outline around the type no longer connects correctly. Hard to describe, so have a look at the image below:
    The goal is to have the blend and logo look like #1. So, my questions:
    a) how do I "create outlines" of the type and also keep the gradient the same angle as #1? I can manually adjust this using the gradient tool, but this is inaccurate and kludgy.
    b) how can I get the white outlines on the new, converted logo to look like 1 (nicely connected), rather than the mess in #2?
    Many thanks in advance for your help and insight!
    Kris

    @Kris – For getting the outlines right after "Create Outlines" you need some additional steps to merge the overlapping "ogo" part of your logo to one path.
    Maybe what you cannot do is getting the outlines totally right. That will depend of the number of inner forms. For that I recommend Adobe Illustrator.
    What you can do in InDesign:
    1. Release the compound path of all outlined characters
    2. For some paths you have to change the direction of the path and do compound again
    3. Then you can use path finder to add paths together
    And: You'll need a new gradient with a different start/stop point.
    Here some steps illustrating the problem:
    (left the outlined text, right the "live" text)
    1. Gradient applied to the "live" text is different from the converted outlines
    (Outline at left is already postprocessed with the path finder)
    Path situation immediately after the conversion.
    Gradient newly applied with -90° (will not match the original)
    Original gradient applied to outline (will not match original):
    New gradient applied to match original:
    Also look at the position of the outline; now "inner" instead of "middle".
    As I already said, for things like that I'd rather use Adobe Illustrator…
    Uwe

  • Where is the text stored when we create a discussion under Urgent Requests?

    Hello,
    Under the Urgent Requests when we create the discussions
    where is the text stored. Under which folder is the text stored? I would like to modify the text. Can anyone help me?
    Thnx in advance.

    hi murali,
    actually discussions are of two types in portal...one you start at any folder or document level and second is you start under ur HOME role in discussion .
    First type of discussion is stored in /collaboration repository and second type of discussion is stored in /discussiongroup repository.   you can find these repository in   content admin -> km content
    hope this will help you.

Maybe you are looking for