none
[MDT2013 Update 1] Task sequence not appearing when I pxe boot litetouch.wim RRS feed

  • Question

  • I've created a windows 10 standard task sequence but it wont appear when I pxe boot litetouch.wim

    The deployment share I'm creating this in was originally created in MDT2013, when I imported this deployment share into update 1 I ticked the upgrade option.

    Is there something obvious I'm missing here? I have checked the windows 10 task sequence and it's enabled and not configured to be hidden in the task sequence.

    I have also tried deleting it and recreating the task sequence and it still wont show up in the deployment wizard.

    Thursday, January 7, 2016 4:11 AM

Answers

  • Ok so I have got a bit further with this issue. I haven't done what you asked in the previous post but this is what I've found:

    If I add a windows 10 operating system to the deployment share and run the update deployment share wizard, and specify either optimize or complete regeneration of the boot images, it uses the boot.wim from the windows 10 operating system that I added to the deployment share. This wim does NOT show the windows 10 task sequence (or any other new task sequence that I create).

    If I remove the windows 10 operating system from the deployment share and update the deployment share again specifying either option, it uses the winpe.wim from the windows 10 ADK instead. This wim DOES show the windows 10 task sequence and I can install windows 10 successfully.

    So the question is, how can I tell MDT2013 U2 to build my wim using winpe.wim from the ADK instead of using my windows 10 boot.wim?

    Here's a link to my onedrive with two .log files. These are both outputs I saved from updating the deployment share. Windows10Wim.log is the one that uses the windows wim, and the Windows10ADKWim.log is the one that uses the winpe.wim from the W10 ADK.

    https://onedrive.live.com/redir?resid=56F7C23D0EB61BC3!125&authkey=!ADwvZcDSGQzlKRg&ithint=folder%2c


    • Edited by JR29 Thursday, January 21, 2016 3:30 AM
    • Marked as answer by Ty GlanderModerator Thursday, January 21, 2016 6:15 AM
    Thursday, January 21, 2016 3:30 AM

All replies

  • I am not sure why it is filtering out Windows 10.  Can you show what the OS is that is being used as well as the properties page of the Windows 10 image?

    Oh and your server Task sequences are using Client.xml as the template instead of Server.xml


    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Thursday, January 7, 2016 4:54 AM
    Moderator
  • Thanks for your reply :)

    Here's the OS, and properties:

    Friday, January 8, 2016 2:00 AM
  • Err on forgot to ask for the task sequence general tab.

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Friday, January 8, 2016 7:16 AM
    Moderator
  • Sunday, January 10, 2016 9:39 AM
  • It would be worthwhile to try the update 2 release. There are several reliability fixes.

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Sunday, January 10, 2016 10:46 PM
    Moderator
  • Another option is to modify the Unattend_PE_x64.xml and Unattend_PE_x86.xml in C:\Program Files\Microsoft Deployment Toolkit\Templates and change the line that runs wscript.exe X:\Deploy\Scripts\LiteTouch.wsf to

    wscript.exe X:\Deploy\Scripts\LiteTouch.wsf /debug:TRUE

    And post your BDD.log to something like OneDrive and share the link here.  If you do that we can see what is logged regarding not showing the Win 10 TS.


    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Sunday, January 10, 2016 11:10 PM
    Moderator
  • Are you using Selection Profiles to limit the shown Applications or Task Sequences by any chance?

    Monday, January 11, 2016 9:03 PM
  • It would be worthwhile to try the update 2 release. There are several reliability fixes.

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    I thought this too and went ahead and updated to update 2, still the same result unfortunately.

    Tuesday, January 12, 2016 4:39 AM
  • Are you using Selection Profiles to limit the shown Applications or Task Sequences by any chance?

    Nope, I only really use selection profiles for specific updates that are needed

    Tuesday, January 12, 2016 4:41 AM
  • Another option is to modify the Unattend_PE_x64.xml and Unattend_PE_x86.xml in C:\Program Files\Microsoft Deployment Toolkit\Templates and change the line that runs wscript.exe X:\Deploy\Scripts\LiteTouch.wsf to

    wscript.exe X:\Deploy\Scripts\LiteTouch.wsf /debug:TRUE

    And post your BDD.log to something like OneDrive and share the link here.  If you do that we can see what is logged regarding not showing the Win 10 TS.


    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    I can't do this until tomorrow / Thursday but I will post the BDD.log once I have done this.

    Cheers

    Tuesday, January 12, 2016 4:43 AM
  • The part I forgot to mention is you will need to update your boot images after enabling debug as well as make those boot images available.

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Tuesday, January 12, 2016 8:01 AM
    Moderator
  • Ok so I have got a bit further with this issue. I haven't done what you asked in the previous post but this is what I've found:

    If I add a windows 10 operating system to the deployment share and run the update deployment share wizard, and specify either optimize or complete regeneration of the boot images, it uses the boot.wim from the windows 10 operating system that I added to the deployment share. This wim does NOT show the windows 10 task sequence (or any other new task sequence that I create).

    If I remove the windows 10 operating system from the deployment share and update the deployment share again specifying either option, it uses the winpe.wim from the windows 10 ADK instead. This wim DOES show the windows 10 task sequence and I can install windows 10 successfully.

    So the question is, how can I tell MDT2013 U2 to build my wim using winpe.wim from the ADK instead of using my windows 10 boot.wim?

    Here's a link to my onedrive with two .log files. These are both outputs I saved from updating the deployment share. Windows10Wim.log is the one that uses the windows wim, and the Windows10ADKWim.log is the one that uses the winpe.wim from the W10 ADK.

    https://onedrive.live.com/redir?resid=56F7C23D0EB61BC3!125&authkey=!ADwvZcDSGQzlKRg&ithint=folder%2c


    • Edited by JR29 Thursday, January 21, 2016 3:30 AM
    • Marked as answer by Ty GlanderModerator Thursday, January 21, 2016 6:15 AM
    Thursday, January 21, 2016 3:30 AM
  • That is really strange. In .\Control\Setting.xml (relative to deployroot) modify UseBootWim (there is one each for x86/and x64) to False

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Thursday, January 21, 2016 6:15 AM
    Moderator