locked
Unable to capture new Windows 7 images after updating to MDT 2013 RRS feed

  • Question

  • We have an existing sysprep and capture image that worked with MDT 2012.

    We updated to MDT 2013 a few months ago and now are needing to capture a new image for the first time on 2013.

    The sysprep process completes, but when the system reboots to start the capture process, it just boots up to a command prompt.

    No visible errors.

    The system we are trying to capture from  is Windows 7 64-bit Virtual Box VM.  We have tried setting virtual box for both Windows 7 and Windows 8.1 hardware.

    Are there any special settings that need to be changed in MDT to capture from MDT 2013 vs 2012?

    Thursday, August 13, 2015 7:43 PM

Answers

  • It is generally a good plan to have a separate build and capture share. My MDT infra is something like:

    4 shares:

    Build and capture share

    Development Share

    Preproduction (test) share <---this is optional for most people

    Production Share


    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.

    • Marked as answer by MyGposts Wednesday, August 19, 2015 7:42 PM
    Tuesday, August 18, 2015 9:51 PM

All replies

  • There shouldn't be.  Can you try create a new sysprep and capture sequence to test?  If that does work then there is probably something with your existing TS.

    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.

    Thursday, August 13, 2015 9:27 PM
  • Cannot see anything wrong with capture TS.  I also just recreated it from scratch with default settings and the issue remains.

    I also tried creating the VM from Client Hyper-V instead of virtualbox and I see the same problem that capture never begins

    This is the end of the bdd.log.

    I don't see any error.  It just pops up a command prompt at the first reboot.

    <![LOG[BCD> Windows Boot Loader]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[BCD> -------------------]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[BCD> identifier              {d22e7e91-9ee7-46eb-89d7-c5859e4302f0}]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[BCD> device                  ramdisk=[C:]\sources\boot.wim,{ramdiskoptions}]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[BCD> path                    \windows\system32\boot\winload.exe]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[BCD> description             Microsoft Deployment WinPE]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[BCD> osdevice                ramdisk=[C:]\sources\boot.wim,{ramdiskoptions}]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[BCD> systemroot              \windows]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[BCD> detecthal               Yes]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[BCD> winpe                   Yes]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[BCDEdit returned ErrorLevel = 0]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Run Command: C:\Windows\SYSTEM32\bcdedit.exe /timeout 0]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[BCD> The operation completed successfully.]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[BCDEdit returned ErrorLevel = 0]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Run Command: C:\Windows\SYSTEM32\bcdedit.exe /displayorder {d22e7e91-9ee7-46eb-89d7-c5859e4302f0} /addfirst]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[BCD> The operation completed successfully.]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[BCDEdit returned ErrorLevel = 0]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Run Command: C:\Windows\SYSTEM32\bcdedit.exe /bootsequence {d22e7e91-9ee7-46eb-89d7-c5859e4302f0}]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[BCD> The operation completed successfully.]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[BCDEdit returned ErrorLevel = 0]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Run Command: C:\Windows\SYSTEM32\bcdedit.exe /default {d22e7e91-9ee7-46eb-89d7-c5859e4302f0}]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[BCD> The operation completed successfully.]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[BCDEdit returned ErrorLevel = 0]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Property BootPE is now = True]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[LTI Windows PE applied successfully]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Event 41019 sent: LTI Windows PE applied successfully]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[LTIApply processing completed successfully.]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Event 41001 sent: LTIApply processing completed successfully.]LOG]!><time="15:32:12.000+000" date="08-13-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Command completed, return code = -2147021886]LOG]!><time="15:32:13.000+000" date="08-13-2015" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property LTIDirty is now = FALSE]LOG]!><time="15:32:13.000+000" date="08-13-2015" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[If there is a drive letter defined, make sure we clear it now so we can *force* recalcutation.]LOG]!><time="15:32:13.000+000" date="08-13-2015" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property OSDTargetDriveCache is now = DIRTY]LOG]!><time="15:32:13.000+000" date="08-13-2015" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[LTI initiating task sequence-requested reboot.]LOG]!><time="15:32:13.000+000" date="08-13-2015" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Event 41017 sent: LTI initiating task sequence-requested reboot.]LOG]!><time="15:32:13.000+000" date="08-13-2015" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property PHASE is now = CUSTOM]LOG]!><time="15:32:13.000+000" date="08-13-2015" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property BootPE is now = ]LOG]!><time="15:32:13.000+000" date="08-13-2015" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

    Thursday, August 13, 2015 11:30 PM
  • When you upgraded did any server names or share locations or permissions change? Remember you are in the middle of a task sequence so if updates are made to the server the machine in the middle of its sequence doesn't know that and it won't make use of those updates because it's running off of what's locally stored. EDIT: Unless you're building your reference image by manually installing windows or using two separate task sequences.

    This is one of the reasons I make my TS to build a reference image as automated as possible. That way if I need to move to a different server, etc. I can start it over from scratch and have a whole new image built within a few hours.

    When I moved from 2012 to 2013 I also changed to a new server (different name) so I had to rebuild my reference images. Now though I'm using a DNS name and DFS share so I shouldn't have issues the next time I switch hardware.


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


    • Edited by Dan_Vega Friday, August 14, 2015 5:08 PM
    Friday, August 14, 2015 1:29 PM
  • Server names and permissions were not changed.  No hardware was changed. We simply updated the existing server from MDT 2012 to MDT 2013.

    All the deployment tasks work.  The only issue is the sysprep and capture TS now fails to start capturing the image and provides no errors in the logs that I can see.  

    Friday, August 14, 2015 1:57 PM
  • Did you also update your WAIK version of move up to ADK?

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

    Friday, August 14, 2015 5:18 PM
  • Check MDT variable DoCapture. You probably set it to SYSPREP, but you need CAPTURE. Track value in BDD.log.
    Friday, August 14, 2015 7:53 PM
  • Yes. It was updated to ADK.

    Everything is working the same as before except OS capture.  We have been deploying Windows 7 successfully with MDT 2013 for a few months and now we need to update the image and cannot.

    Friday, August 14, 2015 7:56 PM
  • Check MDT variable DoCapture. You probably set it to SYSPREP, but you need CAPTURE. Track value in BDD.log.
    I created a new sysprep and capture TS using the wizard.  We did not edit any settings manually.
    Friday, August 14, 2015 7:58 PM
  • When you start MDT Wizard on your virtual machine, does it display if you want to capture image and the store location? Do you have SkipCapture=True in Customsettings.ini?
    Friday, August 14, 2015 8:08 PM
  • Did you uninstall the AIK?

    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.

    Friday, August 14, 2015 8:25 PM
  • Or had you made any customizations to MDT that could have been replaced when you upgraded it?

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

    Friday, August 14, 2015 8:34 PM
  • The customsettings.ini has docapture=yeas and skipcapture=no and the backupshare is configured in that file so the capture TS doesn't ask for the capture location.  It is supposed to start sysprepping, reboot into PE and capture without asking for input when a capture TS is run.

    When I run the TS, it does the sysprep part, reboots into PE and then just goes to a command prompt after the reboot without displaying any error messages.


    • Edited by MyGposts Friday, August 14, 2015 8:43 PM
    Friday, August 14, 2015 8:40 PM
  • Did you uninstall the AIK?

    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.

    Yes.
    Friday, August 14, 2015 8:41 PM
  • The customsettings.ini has docapture=yeas and skipcapture=no and the backupshare is configured in that file so the capture TS doesn't ask for the capture location.  It is supposed to start sysprepping, reboot into PE and capture without asking for input when a capture TS is run.

    When I run the TS, it does the sysprep part, reboots into PE and then just goes to a command prompt after the reboot without displaying any error messages.



    Ok. Your settings seem to be correct. Could you post the entire BDD.log?
    Friday, August 14, 2015 8:48 PM
  • The customsettings.ini has docapture=yeas and skipcapture=no and the backupshare is configured in that file so the capture TS doesn't ask for the capture location.  It is supposed to start sysprepping, reboot into PE and capture without asking for input when a capture TS is run.

    When I run the TS, it does the sysprep part, reboots into PE and then just goes to a command prompt after the reboot without displaying any error messages.



    Ok. Your settings seem to be correct. Could you post the entire BDD.log?
    http://1drv.ms/1Jc9sTZ
    Monday, August 17, 2015 3:37 PM
  • You don't have any Backupfile setting in customsettings.ini? In bdd.log, I see only your Backupshare and backupdir settings.
    • Proposed as answer by Ty Glander Monday, August 17, 2015 9:26 PM
    • Unproposed as answer by MyGposts Tuesday, August 18, 2015 12:58 AM
    • Proposed as answer by Gaëtan Hermann Wednesday, August 19, 2015 7:39 PM
    Monday, August 17, 2015 7:28 PM
  • The customsetting.ini file has the line: BackupDir=%OSDComputerName%

    There is a space between that line and the BackupShare= line above it if that matters

    Monday, August 17, 2015 7:46 PM
  • The customsetting.ini file has the line: BackupDir=%OSDComputerName%

    There is a space between that line and the BackupShare= line above it if that matters

    The suggestion is to add
    BackupFile=MyFile.wim

    (change the name as appropriate).
    Tuesday, August 18, 2015 7:15 AM
  • Have you tried removing the capture location so that it will prompt you for a location?

    Or in your current settings try

    ComputerBackupLocation=NETWORK
    BackupShare=\\SERVER\SHARE
    BackupDir=Reference
    BackupFile=%OSDComputerName%.wim



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

    Tuesday, August 18, 2015 3:08 PM
  • Check the conditions of your task sequence steps.

    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.

    Tuesday, August 18, 2015 7:53 PM
  • Nothing works.  I don't know why it doesn't work with MDT 2013 when it worked without issue with 2012.

    I'm going to try creating a new deployment share from scratch just for capture task sequences.

    Tuesday, August 18, 2015 8:28 PM
  • It is generally a good plan to have a separate build and capture share. My MDT infra is something like:

    4 shares:

    Build and capture share

    Development Share

    Preproduction (test) share <---this is optional for most people

    Production Share


    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.

    • Marked as answer by MyGposts Wednesday, August 19, 2015 7:42 PM
    Tuesday, August 18, 2015 9:51 PM