Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
Sysprep and Capture TS - MDT2012 Beta

Proposed Sysprep and Capture TS - MDT2012 Beta

  • Tuesday, February 07, 2012 6:17 PM
     
     
    Sign In to Vote
    0

    Has anyone had any success capture a Windows 7 image using Sysprep and Capture TS in MDT2012 Beta?

    I have not used MDT2010 so I have no previous background on how this works.  

    I have been able to create the Task Sequence and created the media for Deployment.  I modified the cs.ini to include the DoCapture=Yes

    When I map to the DeploymentShare from the resource target,  I run the elevated command prompt and manually execute the LiteTouch.wsf script.  I get the TS menu option to run the Sysprep and Capture.  After selecting this option,  it automatically goes to the screen to enter the Administrator Password.  Once I enter those credentials, I click 'begin'.   It runs in the background before telling me the Operating system deployment completed successfully.  

    It never prompted for the location to save the captured image.  

    Any suggestions on what to try?

     

All Replies

  • Tuesday, February 07, 2012 8:41 PM
     
     
    Sign In to Vote
    0

    Can you please post your full customsettings.ini?

    In general a full build and capture task sequence works the best

    / Johan

    Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

     
  • Wednesday, February 08, 2012 5:02 AM
     
     
    Sign In to Vote
    0

    ensure that "skipcapture=yes" is not in your customsettings.ini file.

    you can also hard code the location and filename into customsettings, or your task sequence.

     
  • Wednesday, February 08, 2012 12:52 PM
     
     
    Sign In to Vote
    1

    CustomSettings file:

    [Settings]
    Priority=Default
    Properties=MyCustomProperty

    [Default]
    OSInstall=Y
    DoCapture=YES
    SkipAppsOnUpgrade=YES
    SkipCapture=NO
    SkipAdminPassword=YES
    SkipProductKey=YES
    SkipDeploymentType=YES
    SkipComputerBackup=NO
    SkipBitLocker=NO

     
  • Thursday, May 17, 2012 12:44 PM
     
     
    Sign In to Vote
    0
    Can you paste the BDD.LOG from C:\Windwos\Temp folder
     
  • Thursday, May 17, 2012 1:25 PM
     
     
    Sign In to Vote
    0

    Two other questions:

    • Why are you still using MDT 2012 Beta?  We've done two releases since then (RC and RTW) and there are sysprep and capture fixes in those releases.
    • Is your computer domain-joined?  We skip the capture settings pane when we find a domain-joined machine.

    Thanks, -Michael Niehaus Senior Program Manager, Microsoft Deployment Toolkit mniehaus@microsoft.com http://blogs.technet.com/mniehaus

     
  • Wednesday, May 23, 2012 1:42 PM
     
     
    Sign In to Vote
    1

    Probably this might work:

    Keep customsettings.ini more simple. It looks somethinglike this.

    [Settings]
    Priority=Default
    Properties=MyCustomProperty

    [Default]
    OSInstall=Y
    DoCapture=YES
    SkipAdminPassword=YES
    SkipProductKey=YES
    SkipComputerBackup=YES
    SkipBitLocker=YES

    Once you have specified DOCapture=YES den SkipCapture rule is not needed. Bitlocker isnt very necessary while you are doing simple Build and capture.

     
  • Thursday, May 24, 2012 6:52 PM
     
     
    Sign In to Vote
    0

    Don't want to hijack this thread but I am having the exact same problem but I am using the RTW version of MDT 2012.  In the BDD log right after ZTIConfigure runs it jumps right to LTI Deployment Completed Successfully.  It's almost as if they TS is jumping right to the end and skipping everything else after ZTIConfigure.  I have uploaded a copy of my BDD logs here.

    The only difference is that I am trying to capture a Windows 2008 R2 image instead of Windows 7.

    Mike | http://mikecel79.wordpress.com

     
  • Thursday, May 24, 2012 7:03 PM
     
     
    Sign In to Vote
    0

    In your logs, it looks like the necessary variables for capturing an image (e.g. DoCapture) isn't set.  This is likely happening because the wizard pane to ask for this information won't display when your computer is joined to a domain - we only support capturing from a workgroup.

    Try removing the computer from the domain and then run the task sequence.  You should then get asked for the capture details.

    Thanks, -Michael Niehaus Senior Program Manager, Microsoft Deployment Toolkit mniehaus@microsoft.com http://blogs.technet.com/mniehaus

     
  • Thursday, May 24, 2012 7:12 PM
     
     
    Sign In to Vote
    0

    But the machine I am trying to capture is not joined to a domain.  I just built this machine in VMWare this morning, updated all patches, installed our AV and wanted to capture it as our reference server image.  It has never been connected to our domain before.  Below is the contents of my CS.ini file.  I should also mention that this is an upgrade from MDT 2010 Update 1. 

    [Default]
    OSInstall=Y
    SkipAppsOnUpgrade=YES
    SkipAdminPassword=YES
    SkipCapture=NO
    SkipProductKey=YES
    OSDComputerName=US-%SERIALNUMBER%
    SkipTimeZone=YES
    TimeZone=035
    TimeZoneName=Eastern Standard Time
    JoinDomain=<domainname>
    UserDataLocation=NETWORK
    UDShare=\\<server>\Share$
    UDDir=%OSDComputerName%
    MachineObjectOU=OU=OUName
    WSUSServer=<server>
    EventService=<server>

    Mike | http://mikecel79.wordpress.com


    • Edited by Mike Celone Thursday, May 24, 2012 7:15 PM removed domain name
    •  
     
  • Thursday, May 24, 2012 7:13 PM
     
     Proposed
    Sign In to Vote
    0

    You're setting JoinDomain, which indicates to the wizard that the capture wizard pane should not be displayed.  Remove that one.

    Thanks, -Michael Niehaus Senior Program Manager, Microsoft Deployment Toolkit mniehaus@microsoft.com http://blogs.technet.com/mniehaus

    • Proposed As Answer by Mike Celone Thursday, May 24, 2012 8:01 PM
    •  
     
  • Thursday, May 24, 2012 8:02 PM
     
     
    Sign In to Vote
    0
    Thank Michael that worked.  Is this a change from MDT 2010?  In 2010 I always had that listed in the [Default] section but it seemed to have ignored that setting.  Or is it because enforcement of capturing domain joined images was not done in 2010?

    Mike | http://mikecel79.wordpress.com

     
  • Thursday, May 24, 2012 8:10 PM
     
     
    Sign In to Vote
    0

    The behavior should have been the same with MDT 2010.

    Thanks, -Michael Niehaus Senior Program Manager, Microsoft Deployment Toolkit mniehaus@microsoft.com http://blogs.technet.com/mniehaus

     
  • Wednesday, May 30, 2012 3:47 AM
     
     
    Sign In to Vote
    0

    Mike C.

    I ran into a similar problem since I like having the JoinDomain property in the Default section as well but could never get the Capture Wizard to display even when the computer was joined to a workgroup or when setting the JoinWorkgroup property via database or other methods. Normally if both JoinDomain and JoinWorkgroup properties are set, the JoinWorkgroup will take precedence so you would think that would follow through to the wizard screens. Unfortunately, because of the following condition (Bold) in the DeployWiz_Definition_ENU.xml:

    <Pane id="CaptureImage" reference="DeployWiz_CaptureImage.xml">
    <Condition><![CDATA[ Ucase(Property("SkipCapture"))<>"YES" and Property("DeploymentType") <> "REFRESH" and Property ("JoinDomain") = "" and Property("DeploymentType") <> "REPLACE"]]></Condition>
    <Condition><![CDATA[ FindTaskSequenceStep("//step[@name='Create WIM']", "ZTIBackup.wsf" ) ]]></Condition>
    </Pane>

    the Capture Wizard will never be displayed.

    My workaround was to change Property ("JoinDomain") = "" to the following Property("JoinWorkgroup") <> ""

    This way it follows the default behavior of when both properties have values, and you can keep JoinDomain in the Default section and set the JoinWorkgroup whenever you want to display the Capture Wizard.

    I'm still testing this but so far it seems to be working for me.

    • Edited by scarneol Wednesday, May 30, 2012 3:53 AM
    •  
     
  • Monday, June 04, 2012 8:26 PM
     
     
    Sign In to Vote
    0

    Mike C.

    I ran into a similar problem since I like having the JoinDomain property in the Default section as well but could never get the Capture Wizard to display even when the computer was joined to a workgroup or when setting the JoinWorkgroup property via database or other methods. Normally if both JoinDomain and JoinWorkgroup properties are set, the JoinWorkgroup will take precedence so you would think that would follow through to the wizard screens. Unfortunately, because of the following condition (Bold) in the DeployWiz_Definition_ENU.xml:

    <Pane id="CaptureImage" reference="DeployWiz_CaptureImage.xml">
    <Condition><![CDATA[ Ucase(Property("SkipCapture"))<>"YES" and Property("DeploymentType") <> "REFRESH" and Property ("JoinDomain") = "" and Property("DeploymentType") <> "REPLACE"]]></Condition>
    <Condition><![CDATA[ FindTaskSequenceStep("//step[@name='Create WIM']", "ZTIBackup.wsf" ) ]]></Condition>
    </Pane>

    the Capture Wizard will never be displayed.

    My workaround was to change Property ("JoinDomain") = "" to the following Property("JoinWorkgroup") <> ""

    This way it follows the default behavior of when both properties have values, and you can keep JoinDomain in the Default section and set the JoinWorkgroup whenever you want to display the Capture Wizard.

    I'm still testing this but so far it seems to be working for me.

    Thanks for this. I will have to try it.  Having the JoinDomain property in the default section is much easier for us. What I would really like to see is that when you select a TS in MDT it should read the CS.ini file again and pull your properties and settings from the respective section. This would make some tasks like this so much easier.

    Mike | http://mikecel79.wordpress.com

     
  • Monday, June 11, 2012 10:15 PM
     
     
    Sign In to Vote
    0

    i dont understand the reasoning behind this. Why would it matter if "joindomain" is set in customsettings.ini? its a capture TS, you are going out of your way to intiate a capture so capture it! There was never an issue in 2010 with this sort of step.

    A note for others; i just commented out ";"  domainjoin=domain.local in customsettings.ini and intiated my sysprep and capture TS. I then removed the ";".

    other than this i do like mdt 2012, a lot.

    Tech with Alberta Education

     
  • Monday, June 11, 2012 11:22 PM
     
     Proposed
    Sign In to Vote
    2

    The way I get around this is by separating my task sequences in CS.ini. Adding the JoinDomain to just the deployment task sequences and not the [Default] section.

    [Settings]
    Priority=Default
    Properties=MyCustomProperty, TaskSequenceID

    [Default]
    OSInstall=Y
    SkipCapture=NO
    SkipAdminPassword=NO
    SkipProductKey=NO
    SkipComputerBackup=NO
    SkipBitLocker=NO

    [Win7Prox86]
    JoinDomain=<domainname>

    [Win7Prox64]
    JoinDomain=<domainname>

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

    • Proposed As Answer by _Joanna_ Friday, August 03, 2012 8:47 AM
    •  
     
  • Friday, August 03, 2012 8:47 AM
     
     
    Sign In to Vote
    1

    The way I get around this is by separating my task sequences in CS.ini. Adding the JoinDomain to just the deployment task sequences and not the [Default] section.

    [Settings]
    Priority=Default
    Properties=MyCustomProperty, TaskSequenceID

    [Default]
    OSInstall=Y
    SkipCapture=NO
    SkipAdminPassword=NO
    SkipProductKey=NO
    SkipComputerBackup=NO
    SkipBitLocker=NO

    [Win7Prox86]
    JoinDomain=<domainname>

    [Win7Prox64]
    JoinDomain=<domainname>

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

    I was having similar problems (for days!) with the process completing with no errors, and no capture taking place. Making these changes to my cs.ini did the trick. Thank you. 
     
  • Wednesday, September 12, 2012 1:38 PM
     
     
    Sign In to Vote
    0
    My customer settings had SkipCapture=YES. I've corrected it now to SkipCapture=NO and DOcapture=YES. This worked for me. Thank you!!