none
MDT Capture task doesn't display the capture screen during wizard RRS feed

  • Question

  • Hi,

    New to MDT with MDT 2013 Update 1.

    My capture task sequence works but it doesn't display the capture screen.

    I think this is due to JoinDomain being in the customsettings.ini file.

    I tried to have different options dependent on TaskSequnceID per the below config but this never worked.

    Priority=TaskSequenceID, Default

    [TaskSequenceID1]

    [TaskSequenceID2]

    Things look to be working better now I'm using the below config, capture is working but the capture screen still doesn't show. I found several posts advising of the above but it never worked, found posts advising above didn't work and option was to edit MDT script files or go with the below fix, I went with the later. 

    Priority=TaskSequenceID1TaskSequenceID2, Default

    [TaskSequenceID1]

    [TaskSequenceID2]

    Below is my customsettings.ini, my TaskSequenceIDs are CAPTURE, SOFTWARE and INSTALL all of which work fine.

    [Settings]
    Priority=CAPTURE, SOFTWARE, INSTALL, Default
    Properties=MyCustomProperty

    [CAPTURE]
    SkipCapture=NO
    ComputerBackupLocation=\\%servername%\DeploymentShare$\Captures
    BackupFile=%OSDComputerName%.wim
    AdminPassword=%password%

    [SOFTWARE]
    SkipAdminPassword=YES

    [INSTALL]
    OSInstall=Y
    SkipCapture=YES
    SkipAdminPassword=NO
    SkipProductKey=YES
    SkipComputerBackup=YES
    SkipBitLocker=YES
    SkipLocaleSelection=NO
    SkipUserData=YES
    SkipTimeZone=NO
    DoCapture=YES

    OSDComputerName=%COmputerName%
    JoinDomain=%domain%.local
    DomainAdmin=%WDSuser%
    DomainAdminDomain=%domain%
    MachineObjectOU=OU=%Path%

    UILanguage=en-US
    UserLocale=en-GB
    KeyboardLocale=en-GB
    TimeZoneName=GMT Standard Time

    AdminPassword=%password%

    [Default]
    SkipBDDWelcome=NO
    KeyboardLocalePE=0809:00000809

    Am I going about this the wrong way? If not, how do I get the CAPTURE TS to show the capture section in wizard.





    Thursday, March 24, 2016 10:18 AM

All replies

  • Also, MDT deploys image successfully and adds it to the domain but with the below result. Why is it running sysprep?

    Failure ( 7002 ): Computer is a member of a domain, should be in a workgroup when sysprepping.

    Litetouch deployment failed, Return Code =- 2147467259 0x80004005

    I think this is due to below in customsettings.ini.

    Why isn't customsettings.ini splitting by TS>?

    Thursday, March 24, 2016 11:38 AM
  • Using a TaskSequenceID in priority won't work as-is because MDT processes the rules BEFORE you choose a task sequence. When it comes to which rules win, keep this handy - http://renshollanders.nl/2014/01/mdt-unattended-xml-customsettings-ini-task-sequence-variable-which-settings-takes-precedence-over-which-setting/

    If I want different task sequences to have different settings, then I just add the variable directly to the task sequence.

    Here's a simple example:


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Thursday, March 24, 2016 2:41 PM
  • Interesting.

    I added Set Task Sequence Variable "SkipCapture" with Value of "NO" to my CAPTURE TS but the capture screen in wizard still doesn't show.

    Moved "JoinDomain=%mydomain%.local" from customsettings.ini to my INSTALL TS and now CAPTURE TS is showing the capture section in wizard.

    So the below must NOT be Task Sequence Variables:

    SkipCapture=
    SkipAdminPassword=
    SkipProductKey=
    SkipComputerBackup=
    SkipBitLocker=
    SkipLocaleSelection=
    SkipUserData=
    SkipTimeZone=

    Maybe is a way can add these to a TS, or a better solution if possible to have a customesettings.ini per task sequence.

    Thursday, March 24, 2016 3:26 PM
  • I reverted those changes.

    Adding "JoinWorkgroup=Workgroup" to [CAPTURE] section of CS.ini got my capture screen back.

    Now to find out how to get rid of the sysprep in my install TS.

    Thursday, March 24, 2016 3:47 PM
  • For simplicity and for the sake of automation I have a secondary deployment share configured solely for creating reference images. There is a way to have MDT process your rules but some hacks are required. I'm not sure if this is still the process - http://blog.mikewalker.me/2013/04/mdt-2012-use-different-settings-per.html


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Thursday, March 24, 2016 3:51 PM