locked
Sysprep & Capture completed successfully but did nothing RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    New MDT 2012 install with two Deployment shares, One used for Deployments the other for Captures. Trying to capture a Freshly deployed reference computer with Win7 only that was never joined to the domain.

    I started Litetouch.wsf from the Capture share. Select my basic Sysprep and Capture task, put in my credentials, click Begin. I am instantly presented with a Deployment Summary screen stating the Operating System Deployment Completed Successfully, 0 errors 0 warnings, click Finish. It did not sysprep or reboot.

    If I open the BDD.log, I have a yellow FAILURE: 1:Run command: NET USE /d /y listed under the LTICleanup component.

    As a test...If I create the same task in my Share that I use only for deploying, I get the same results without the failure logged. Still no sysprep or reboot.

    Deployment of a fresh win7 works fine. Just not able to sysprep and capture it.

    Any help much appreciated,

    Brad

     
    Tuesday, April 24, 2012 8:31 PM

Answers

  • Question
    Sign in to vote
    3
    Sign in to vote

    I have the following in my cs.ini which I needed to put to allow to capture:

    DoCapture=YES
    ComputerBackupLocation=NETWORK
    BackupShare=\\server\DeploymentShare$\Captures
    BackupDir=%OSDComputerName%

    • Marked as answer by bfreemanSC Thursday, April 26, 2012 7:46 PM
    Thursday, April 26, 2012 5:54 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hey Brad,

    Still pretty new to this myself, but here are a couple things you could try.

    When connecting to the Deploymentshare$ from your reference computer, connect to it using the fully qualified domain name instead of just the computer name (eg: MDTServer.domain.local\Deploymentshare$ versus MDTServer\Deploymentshare$)

    I believe you should always run the Litetouch.vbs and not use the WSF.  (The VBS does some cool stuff first then makes the call to the WSF file)

    Once prompted for your credentials to connect to network shares, again use the fully qualified name for your domain.

    Those three things resolved several problems I was having with connecting to my Deploymentshare$ across the network.  Hope some of this helps!

    Jared

    Tuesday, April 24, 2012 10:01 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Jared,

    I followed your suggestions using the FQDN and running the litetouch.vbs. Same results, successful completion but no sysprep or reboot capture. This time around, it did not cleanup the mapped drive it created to my deployment share.

    I've been using 2010 with no issues. I rebuilt my deployment computer fresh (Win7 Pro 64bit) for MDT 2012, could I have missed something?  

    Any other suggestions?

    Tuesday, April 24, 2012 10:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Couple of suggestions:-

    - As Jared mentioned, use the vbs instead of wsf. The difference is that wsf does not do any validation however vbs does initial validation. You can see that in the code.

    - Use a virtual machine incase you are using a physical computer to capture.

    - Delete the minint folder on the C drive before attempting a capture again.

    - Lastly, run the following command on cmd to delete all mapped connections before the capture:-
    net use * /d

    Once done, please post the logs under c:\minint\smsosd\osdlogs on a public storage site.

    Regards, Vik Singh "If this thread answered your question, please click on "Mark as Answer"

    Wednesday, April 25, 2012 7:23 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    The only thing i can think off is are you starting your Task sequence from winpe or while in windows?

    because you have to be in windows for the sysprep and capture to succeed.

    Wednesday, April 25, 2012 7:26 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    There appear to be some new variables in MDT 2012 with regards to Sysprep and Capture although not sure if this would affect you.

    Can you post your cs.ini?

    Wednesday, April 25, 2012 11:45 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you all for the suggestions.

    Still no luck.

    Vic, I am sold on using the VBS, but it did not change my outcome.

    Stefan, I am using windows to connect and run the task from my capture share, not PE.

    Vic, I am not too knowledgeable on the subject of 'Virtual Machines'. But you did spark my interest and I DL MS Virtual PC. This might be a topic for another Forum but the VPC will not boot from WDS. It kicks back a bootmanger message after I hit F12 to boot from WDS. I even tried adding the NIC driver for my tech computer (i assume VPC uses the NIC of the tech PC) to my PE boot image.

    So back to my physical test PC. I did run the command to remove any mapped drives. I verified that Minint was not on C: and ran the Litetouch.vbs again using FQDNs to connect. Same result, select my task, enter creds, hit begin, displays quick progress bar and successfully completes with no errors. Still not syspreped and no reboot to capture.

    Check the C: drive again....No Minint folder, therefore no logs to post. Checked the BDD.log no errors.

    My configuration is 'out of the box' fresh. Fresh win7 pro 64 MDT computer. Fresh setup of WDS on the domain controller. Not using any advanced configurations or DB. The only trick up my sleeve is that I like to have two separate shares, one for deploying and one for capturing. 

    Here is my CS from the Capture share:

    [Settings]
    Priority=Default
    Properties=MyCustomProperty

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

    Again, I appreciate all the help and I am more than willing to try any other suggestions.  

    Brad

    Wednesday, April 25, 2012 10:49 PM
  • Question
    Sign in to vote
    3
    Sign in to vote

    I have the following in my cs.ini which I needed to put to allow to capture:

    DoCapture=YES
    ComputerBackupLocation=NETWORK
    BackupShare=\\server\DeploymentShare$\Captures
    BackupDir=%OSDComputerName%

    • Marked as answer by bfreemanSC Thursday, April 26, 2012 7:46 PM
    Thursday, April 26, 2012 5:54 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    if you either insert what Andrew Manning has posted in your cs.ini or change skipcapture=YES to skipcapture=NO so the ts will ask you if you want to capture an image and on which location.
    Thursday, April 26, 2012 7:10 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have the following in my cs.ini which I needed to put to allow to capture:

    DoCapture=YES
    ComputerBackupLocation=NETWORK
    BackupShare=\\server\DeploymentShare$\Captures
    BackupDir=%OSDComputerName%

    OMG...I am so sorry for wasting everyone's time.

    I set the CS for SkipCapture=NO and working like a charm.

    Thank you Andrew and Stefan for pointing out my error.

    I guess I was thinking that since I was running Litetouch from Windows, that these CS settings didn't apply. This stems from my lack of knowledge of the steps involved in the background process. I am still learning and have many more mistakes to make.

    I appreciate all the feedback and the support of this community.

    Thank you all, Problem solved.

     

    Thursday, April 26, 2012 7:56 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello

    I had the same issue and was able to fix it by changing the Skipcapture=No.

    is this a bug or we are doing something wrong?

    should a new deployment share be created for capturing the image aside from deploying the image since the CS is assigned to deployment share  not each task?

    thanks

    Sunday, October 28, 2012 5:40 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    I have run into this before when using domain settings in CustomSettings.ini.

    Either comment out the line below like I have done, or delete it entirely.  I usually just comment it so I can revert back when I want to do super zero touch deployment.

    ;SkipDomainMembership=YES

    Tuesday, April 1, 2014 7:57 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks sprutner, this worked for me!
    Monday, November 23, 2015 6:04 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for this guys, was stumped for bit, although knew i had a ridiculously overly complicated ini file for the capture. 

    DOCAPTURE=YES 

    and disabling SkipDomainMemberShip worked like water sliding off a ducks back. 

    Cheers dudes! 

    Monday, November 13, 2017 9:11 PM