none
MDT 2013 and painfully slow task sequence RRS feed

  • Question

  • I'm installing Windows 8.1 to Lenovo TP10 tablets with MDT 2013. Everything is working but for some reason the task sequence runs very slow. It's been running about 20 hours now and still in phase "Windows Update Pre-Application Install". It's still making progress  so it's not crashed or anything. Windows 8.1 reference image that I'm using is created about a month ago so It's not missing many updates either that could explain this.

    I looked the tablet machines task manager and there is 2/4 gb of memory free and CPU load is only about 40%. Tablet itself is responsive and doesn't feel slow either. I also tested network connection speed by downloading 1 gigabyte file directly  from deployment share and it wasn't slow. I don't understand what's wrong with this. This problem is only with these tablets. 


    • Edited by DamonWH Wednesday, September 30, 2015 6:47 AM
    Wednesday, September 30, 2015 6:47 AM

Answers

  • There was a change made to ZTIWIndowsUpdate.wsf between MDT 2013 and MDT 2013 Update 1 to reduce the logging verbosity. I don't recall the change. You might try to take the ZTIWindowsUpdate.wsf script from MDT 2013 Update 1 and add it to your MDT 2013 share, then re-create the images. That's all I know, I haven't seen your error before.

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

    Thursday, October 1, 2015 8:25 PM
    Moderator

All replies

  • I noticed that the only slow thing is Windows Updates. 

    I also noticed that for some reason there is registry key in machines registry

    HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Trace 

    Level 3

    \COMAPI

    Flags FF

    Level 3

    \Handler

    Flags FF

    Level 3

    So there is somekind of a debugging mode turned on? But where did that come from? 

    Wednesday, September 30, 2015 10:55 AM
  • There is a bug in that the logging is enabled but, Windows Updates always take a long time.  It is the reason why people create reference images with the updates.

    Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/

    • Proposed as answer by Ty GlanderModerator Wednesday, September 30, 2015 5:30 PM
    • Unproposed as answer by DamonWH Wednesday, September 30, 2015 6:29 PM
    Wednesday, September 30, 2015 5:30 PM
    Moderator
  • Did you even read my post? Win 8.1 reference image that I'm using is only about a month old so it's not missing many updates. It's taking about 20 hours to install updates from my WSUS server. This is not normal.


    Wednesday, September 30, 2015 6:32 PM
  • A couple of things... Yes I did read your post (I don't typically have a WU step enabled on my final builds).  Look at your BDD.log and see what steps are taking a VERY long time.  I suspect the big hit is the WU step.  In that case look at: %Windir%\WindowsUpdate.log.  MDT just makes the call for detecting the updates and whatever WU does we just wait for.


    Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/


    Wednesday, September 30, 2015 8:07 PM
    Moderator
  • Oh and a little instruction on how to read the log: https://support.microsoft.com/en-us/kb/902093

    Most important details are logs. If you are unsure how to post logs or where to find them then reference https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/

    Wednesday, September 30, 2015 8:11 PM
    Moderator
  • There was a change made to ZTIWIndowsUpdate.wsf between MDT 2013 and MDT 2013 Update 1 to reduce the logging verbosity. I don't recall the change. You might try to take the ZTIWindowsUpdate.wsf script from MDT 2013 Update 1 and add it to your MDT 2013 share, then re-create the images. That's all I know, I haven't seen your error before.

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

    Thursday, October 1, 2015 8:25 PM
    Moderator
  • Thank you all for your answers. This is now resolved. I just created new reference image and it's normal now. I really don't know what was wrong with this reference image. It's automatically build with MDT as is this new one too.

    Some others have had same kind of slownes with Windows Updates as I had

    https://community.spiceworks.com/topic/907157-windows-updates-extremely-slow-to-install?page=3

    Friday, October 2, 2015 5:13 AM