Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
Capture Reference OS to WIM File

Answered Capture Reference OS to WIM File

  • Thursday, January 17, 2013 8:33 AM
     
     
    Sign In to Vote
    0

    Hi All.

    I have MDT 2012 installed. I followed a guide to create a Capture Reference OS to WIM File task sequence. I want to capture a Windows 8 pc. When I however run this task sequence it just take about 10 seconds and then get to the finish screen telling me it were successful, however, nothing is captured. What can be the problem?

    Thank you in advance. 

     

All Replies

  • Thursday, January 17, 2013 9:59 AM
     
     
    Sign In to Vote
    0

    we need some more information then this to know what might be the problem.

    what kind of task sequence did you use?

    where you in full os or did you start from winpe?

    you should also check the log files to see if you can discern where it went wrong.

    locations are

    when booted into winpe

    X:\MININT\SMSOSD\OSDLOGS

    or when in windows  logs are at

    C:\MININT\SMSOSD\OSDLOGS

     
  • Thursday, January 17, 2013 10:03 AM
     
     
    Sign In to Vote
    0

    we need some more information then this to know what might be the problem.

    what kind of task sequence did you use?

    where you in full os or did you start from winpe?

    you should also check the log files to see if you can discern where it went wrong.

    locations are

    when booted into winpe

    X:\MININT\SMSOSD\OSDLOGS

    or when in windows  logs are at

    C:\MININT\SMSOSD\OSDLOGS


    I used the Sysprep and capture task sequence and I am booting from winpe and select that task sequence that I created.
     
  • Thursday, January 17, 2013 10:09 AM
     
     
    Sign In to Vote
    1
    there is your problem with a sysprep and capture task sequence you need to start from windows with litetouch.vbs
     
  • Thursday, January 17, 2013 11:04 AM
     
     
    Sign In to Vote
    0
    there is your problem with a sysprep and capture task sequence you need to start from windows with litetouch.vbs

    That is not the solution. I get exactly the same result. Anyone know how to fix this or what the problem can be please?
     
  • Friday, January 18, 2013 12:15 PM
     
     
    Sign In to Vote
    0

    What steps are you taking exactly?

    Are you logged in as local administrator?

    The litetouch.vbs issue is interesting. I take it you are using \\servername\deployementshare\scripts\liteouch.vbs to kick off sysprep.

    When you do that, are you seeing the box popup that asks where to store the captured wim and what name to give it?

    Reason I ask is by establishing at what point it fails will help people work out why its failing.

    Are you seeing the sysprep animation?

     
  • Friday, January 18, 2013 12:24 PM
     
     Answered
    Sign In to Vote
    1
    Thanks for the suggestions. I managed to solve this. I had to remove the JoinDomain section from my custumsettings.ini. If it is in there it skip the capture part.
    • Marked As Answer by EbenFourie Friday, January 18, 2013 12:24 PM
    •