none
MDT 2012 \ WinPE 3.0 Slow Install Operating System RRS feed

  • Question

  • I have an issue with a custom wim I have incorporated into my Task sequence. When I use a custom Wim, at the point where the MDT Tasksequence begins to "Install Operating System" it slows down to a crawl. What previously took 5-10 minutes on a previous wim, is now taking 30-50. When the "Install Operating System" task begins, it starts a at a very decent rate, you can see the percentage or time increasing/changing every few seconds with out issue, but when it gets to 30% completion, it starts to slow down dramatically. Eventually it will get to 100% Completion, where it will stay for the next 5 minutes, at which point it will apply the unattend.xml which will also take a very very long time to complete.


    Once it reboots from applying the Unattend.xml everything runs normal.


    My Setup:

    I am using MDT 2012 - with WinPE3.0

    To create my Custom Wim I did the following:

    I created a brand new standard tasksequence, to deploy an OS to a machine, install updates then sysprep and capture to a wim. I set a custom variable in the tasksequence which set DoCapture=Yes. This allowed me to Capture the Operating system after the windows updates were done without having to do any additional steps. I then imported the Image into the operating systems section of my MDT Deployment share, and incorporated it into my previous Tasksequence.

    I have also noticed that the size of the wim file I created is about 1.5 gigs larger than my previous wim.

    Steps I've Taken for remediation:

    I've tried rebuilding my boot.wim several times.

    Increased the scratch size from 32 -> 64 -> 256 -> 512MB  

    Removed unnecessary drivers from the boot.wim

    Any ideas you guys might have with regard to getting my Install Operating System phase to speed up to normal speeds with be greatly appreciated.  Is there an extra step with the install.wim that I importing into MDT that I should be doing?

    Tuesday, July 22, 2014 10:20 PM

Answers

  • Download of the image takes 21 minutes, not perfect, but not out of the question slow. What is the speed when performing a Robocopy from the file server when in the full OS? Verify you are running at Gigabit speeds, you should be able to open the task mgr within WinPE to see what is going on.

    As for the apply unattend.xml phase, yea, it's taking 28 minutes, which is excessive, but that's because you have a large number of patches in the MDT console. If deployment speed is important to you, I would recommend creating a reference image with all the patches included, and deploy that instead.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Wednesday, July 23, 2014 3:47 PM
    Moderator

All replies

  • Can you copy a bdd.log file from a slow run to a public site like OneDrive, and copy the link here?


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Wednesday, July 23, 2014 3:24 AM
    Moderator
  • Thanks for the reply Keith,  I changed the name on some of the variables to not release account names and servers from our internal network.  This should not affect anything though.

    You'll See imagex start at 11:54am and the reboot finally occurs at 12:44pm (50 minutes)

    I will also note that while imagex is running, the system seems to slow down to a crawl.  If I press F8 to bring up the command prompt it takes anywhere between five seconds to a minute for it to display.

    Link to BDD.log


    MCSA Server 2008R2 \ 2012 MCSE Server Infrastructure CCNA

    Wednesday, July 23, 2014 1:58 PM
  • Download of the image takes 21 minutes, not perfect, but not out of the question slow. What is the speed when performing a Robocopy from the file server when in the full OS? Verify you are running at Gigabit speeds, you should be able to open the task mgr within WinPE to see what is going on.

    As for the apply unattend.xml phase, yea, it's taking 28 minutes, which is excessive, but that's because you have a large number of patches in the MDT console. If deployment speed is important to you, I would recommend creating a reference image with all the patches included, and deploy that instead.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Wednesday, July 23, 2014 3:47 PM
    Moderator
  • I completed a robocopy in the full blown OS to download the 4.9g wim, it takes 1 minute and 36 seconds.  It does have gigabit connection active in the full blown os.

    When I am running WinPE, Task Manager is showing my local area connection is running at 1Gbps.

    Another discrepancy I'm noticing is that @ 12:16:04 [Line1801] the task sequence finishes apply the wim.  It takes 10 minutes for it to start the next task found on Line 1807.  Any Ideas on why it taking so long to apply the  bootsect.exe command?

    I did disable the "Apply Patches" task, and it did remove 20 minutes by not applying those patches.  Thank you for that suggestion.


    MCSA Server 2008R2 \ 2012 MCSE Server Infrastructure CCNA

    Wednesday, July 23, 2014 6:58 PM