Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
Capture and Deploy XP SP3 as it is (without sysprep and any unnecessary steps in TS)

Unanswered Capture and Deploy XP SP3 as it is (without sysprep and any unnecessary steps in TS)

  • Thursday, September 27, 2012 11:26 AM
     
     
    Sign In to Vote
    0
    Currently, we use Zenworks bootcd to install the OS. We create referns client manually, even running sysprep manually when everything is ready (Sysprep shuts down the computer), and capture the image in .ZMG format. Now we urgently need to transfer this to .Wim and deploy it with MDT 2012 or SCCM 2012.

    Is there any way that with MDT capture this installation just as it is? Not do all that MDT does usual (sysprep and everything else)?

    Then we need to deploy this image without any unnecessary steps in TS. All that is needed, computer name, domain membership etc. runs through embedded scripts that start automatically.

    Is this possible? If yes, can someone help me with how?

    The reason we want to do like this is that it needs to be fixed yesterday! Next, we create an image build in accordance with best practices and deploy it properly.

    TWP


    • Edited by tp_tp Thursday, September 27, 2012 11:29 AM
    •  
     

All Replies

  • Thursday, September 27, 2012 1:20 PM
     
     
    Sign In to Vote
    0

    Not directly, but all you need to do is boot the system to a WinPE and run imagex manually to create the WIM on a connected network location.

    As for the task sequence, just strip out the unnecessary steps (and test, test, test).

    Jason | http://blog.configmgrftw.com

    • Proposed As Answer by Stephan Schwarz Thursday, September 27, 2012 10:31 PM
    • Unproposed As Answer by tp_tp Friday, September 28, 2012 7:34 AM
    •  
     
  • Friday, September 28, 2012 7:36 AM
     
     
    Sign In to Vote
    0
    Would be nice with some tips and examples of how

    TWP

     
  • Friday, September 28, 2012 9:42 AM
     
     
    Sign In to Vote
    0

    1.In MDT create a generic .iso its under the rules tab.

    2.make a bootable USB drive or burn a CD with the generic .iso

    3.put it in your machine you want to capture and start from usb/cd

    4.when PE is started type "imagex /capture c: c:\winxp.wim"

    5.copy your c:\winxp.wim to your solution

    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.

     
  • Wednesday, October 03, 2012 1:36 PM
     
     
    Sign In to Vote
    0

    I've tried this and it seems to work just fine until I try to deploy it.Then I get 8 errors in Deployment Summary and some in logfiles:

    smsts.log
    Failed to run the action: Install Operating System.
    Unknown error (Error: 000015F8; Source: Unknown)
    The execution of the group (Install) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)
    Failed to run the last action: Install Operating System. Execution of task sequence failed.
    Unknown error (Error: 000015F8; Source: Unknown)
    Task Sequence Engine failed! Code: enExecutionFail
    Task sequence execution failed with error code 80004005
    Error Task Sequence Manager failed to execute task sequence. Code 0x80004005

    bdd.log
    FAILURE ( 5624 ): 2: Run ImageX:  /apply "\\mdtserver\MDTTestDepXp$\Operating Systems\WinXpPro_Sp3_x86_002\WinXpPro_Sp3_x86_002.wim" 1 C:
    Litetouch deployment failed, Return Code = -2147467259  0x80004005

    I get the same error when I make a capture with MDT from a logged in system with Sysprep and all standard steps in Capture TS, and then deploy it with a standard TS.

    TWP


    • Edited by tp_tp Wednesday, October 03, 2012 1:49 PM
    •  
     
  • Wednesday, October 03, 2012 2:53 PM
     
     
    Sign In to Vote
    0

    I'm not entirely sure why the last picture is included in your post. WSIM is not used at all for Windows XP wim files.

    Can you verify that this image can be deployed properly when you're running imagex manually in order to apply the image? You can use the same boot image that you used to capture WinXP, or you can do it from within the LiteTouch PE (you can open the command line prompt using F8).

    Kind regards,
    Stephan Schwarz

    If one of these posts answered your question or issue, please click on "Mark as answer".

    My Blog | Twitter: @Schwarz_Stephan | MCTS, MCITP, MCSA, MCC-2011.
    How to configure Windows RE/OEM Recovery Partition with MDT

     
  • Wednesday, October 03, 2012 2:55 PM
     
     
    Sign In to Vote
    0

    Should I test with the following command:
    ImageX:  /apply "\\mdtserver\MDTTestDepXp$\Operating Systems\WinXpPro_Sp3_x86_002\WinXpPro_Sp3_x86_002.wim" 1 C:

      

    TWP


    • Edited by tp_tp Wednesday, October 03, 2012 2:56 PM
    •  
     
  • Wednesday, October 03, 2012 3:07 PM
     
     
    Sign In to Vote
    0

    Yes you can use that command (if you're doing this from within the MDT boot image it should not be an issue since it already has the network credentials for the deployment share).

    Kind regards,

    Stephan Schwarz

    If one of these posts answered your question or issue, please click on "Mark as answer".

    My Blog | Twitter: @Schwarz_Stephan | MCTS, MCITP, MCSA, MCC-2011.
    How to configure Windows RE/OEM Recovery Partition with MDT

     
  • Wednesday, October 03, 2012 3:41 PM
     
     
    Sign In to Vote
    0
    Cant find the imageX on the MDT bootcd! How can that be?

    TWP

     
  • Wednesday, October 03, 2012 3:47 PM
     
     
    Sign In to Vote
    0

    It's not located on the MDT boot image, it's located on the deployment share.

    When booting into MDT, open F8 once the connection has been made to the deployment share, it will be accessible through drive letter Z:

    In the \Tools\x86 and \Tools\x64 folder you can find Imagex.exe

    If one of these posts answered your question or issue, please click on "Mark as answer".

    My Blog | Twitter: @Schwarz_Stephan | MCTS, MCITP, MCSA, MCC-2011.
    How to configure Windows RE/OEM Recovery Partition with MDT


     
  • Wednesday, October 03, 2012 3:52 PM
     
     
    Sign In to Vote
    0
    I am using MDT 2012 and I can see that the step Install Operating System is running and applying the image.

    TWP

     
  • Wednesday, October 03, 2012 4:21 PM
     
     
    Sign In to Vote
    0

    Sorry, did not think about that:)
    It did't work with imageX:

    TWP

     
  • Thursday, October 04, 2012 8:16 AM
     
     
    Sign In to Vote
    0

    I get the same error when Im trying to deploy as when trying to mount the image with ImageX:

    TWP

     
  • Thursday, October 04, 2012 8:22 AM
     
     
    Sign In to Vote
    0

    In such a case it's not unlikely that the image is actually corrupt.

    Please try to recapture the image and try again.

    Kind regards,

    Stephan Schwarz

    If one of these posts answered your question or issue, please click on "Mark as answer".

    My Blog | Twitter: @Schwarz_Stephan | MCTS, MCITP, MCSA, MCC-2011.
    How to configure Windows RE/OEM Recovery Partition with MDT

     
  • Thursday, October 04, 2012 7:05 PM
     
     
    Sign In to Vote
    0
    I have tried to recapture the image a few times, even from different servers. There are no errors at the Capture stage but unfortunately I always get the same error when I run Apply or Mount:(

    TWP

     
  • Friday, October 05, 2012 11:05 AM
     
     
    Sign In to Vote
    0

    When I create a Build and Capture TS that creates the image of XP Source Files (no patches or any changes), and captures it, it works fine.But when I try to manually patch and modify the reference computer, image gets corrupted according to the previously mentioned description.

    Are there any known patches/fixes for XP that makes this not work on MDT/SCCM?

    TWP

     
  • Friday, October 05, 2012 11:33 AM
     
     
    Sign In to Vote
    0

    Not that I'm aware of.

    Not sure if this was one of the things that you've tried already, but what's the result of the following..?

    Install XP using Zenworks, then once Windows XP has been installed, start a capture task sequence of MDT. What's the result of trying to deploy that wim image?

    Kind regards,

    Stephan Schwarz

    If one of these posts answered your question or issue, please click on "Mark as answer".

    My Blog | Twitter: @Schwarz_Stephan | MCTS, MCITP, MCSA, MCC-2011.
    How to configure Windows RE/OEM Recovery Partition with MDT

     
  • Friday, October 05, 2012 12:24 PM
     
     
    Sign In to Vote
    0
    Zenworks was one of the first things I tried and receive the same error there. It's very difficult to see what could be causing the error. The only thing I can see are patches.

    TWP

     
  • Tuesday, October 16, 2012 3:37 PM
     
     
    Sign In to Vote
    0

    Hi TWP,

    I just had error 0015F8 when applying a normal Windows 7 wim, so am looking into what's wrong.

    To recap, you are capturing a machine, and either mounting or applying the WIM you get this error:

    "C:\WINDOWS\assembly\GAC_32\System.EnterpriseServices\2.0.0.0__b03f5f7f11d50a3a (Error = 4392)
    Error restoring image.
    The data present in the reparse point buffer is invalid."

    That is normal imagex behaviour for a corrupt image. It always seems to fail at that point if a WIM is corrupt for any reason.

    Causes of corrupt WIM could be:

    • corrupt source OS
    • corrupt physical disk
    • corrupt network
    • something else!

    I've found it best to reduce things to as simple as possible, to troubleshoot this. So as the comments from the guys above correctly say, try to eliminate suspects.

    1) try capturing another machine

    2) Use your boot disk to capture the image to the local disk. This cuts out the whole network path, which could be failing in many places. It also has the benefit that it's much, much faster (unless you have Gigabit networks)

    3) capture a different OS

    For troubleshooting I use a generic bootable USB with imagex on it. This means I don't need to connect to the MDT share. If the USB stick is 8GB you can capture the image to it too, which avoids writing anything to your reference machine.

    Sorry I don't have a better answer. I have captured a "used" fat image of XP SP3 with both MDT and SCCM many, many times so I know they are both capable of doing an XP capture for you.

    I'm not familiar with Zenworks at all, but if there's a client agent installed you need to remove it before running sysprep if you have not already done so.

    Best practise is to use MDT to create the reference image, using a virtual machine as the source machine.

    I hope that helps a little,

    Mike

    MikeT