locked
MDT 2013 & WSUS, poor performances with ZTIWindowsUpdate.wsf RRS feed

  • Question

  • Hello Guys

    Here are the config ;
    - Server HP DL380e Gen8 / 2704v2 (4 cores) / 96 GB RAM / 6 HDD 15k SAS RAID 10
    - Windows 2012 R2, WORKGROUP
    - WDS standalone mode (no AD), WSUS with SQL 2012 SP2 database, MDT 2013 update 1
    - Customsettings.ini configured with variable WSUSServer=http://myserver:8530
    - HP PC with SSD / 8 GB RAM / Core I5

    Here are the issue ;
    - Deployment works perfectly (no error at the end)
    - The time for Windows Update in pre-app mode and post-app mode takes an extended time to finish...

    Example ; Windows 8.1 deployment + Office 2013 + 4/5 freewares = 4h30 from the PXE boot to the successfull message... 3H30 are used only for the "Downloading updates", about 30 minutes for the installing updates (which is normal)

    If I disable the Updates steps in the task sequence, the deployment takes max 30 minutes to finish.

    The WSUS works perfectly ;
    - If I configure the WSUS settings from the gpedit.msc console into Windows, and told Windows to use my server as a WSUS Server, the download works great and takes max 1 minutes to finish.

    It's look like that the issue only occur when using WSUS from the ZTIscript while a task sequence is pushed on the PC.

    Does anyone has already seen this issue ? Any idea ?
    I has already seen that problem on the old server (which used SATA drive in RAID 1...) with MDT 2013 (no U1). So the issue is repeatable.

    Thanks a lot

    HisteriQal

    • Edited by HisteriQal Tuesday, November 17, 2015 1:33 PM
    Tuesday, November 17, 2015 1:30 PM

All replies

  • Well for one I'd recommend building your reference image with Office and all updates already included as that will really speed up deployments to your client machines.

    Other than that it'd be hard to say what the issue is without seeing logs.


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

    Tuesday, November 17, 2015 2:56 PM
  • I work for an IT company, we use WDS / MDT with many scenario (inc refresh with USMT).

    We already use capture / deploy master with all MS updates when we need to deploy a lot of same model PC.
    MDT / WSUS is used for the one-PC scenario, like I just said for a refresh scenario, upgrading a Win 7 Customer to Win 8.1 for the exemple.

    We use  sometimes MDT too for preparing the first PC which will be the master... So I have many workaround like modify manually the reg key or local strategy but I just want to find the solution to this specific issue because use it into the task sequence should work and is prettiest :)

    Which log can help ?

    Thanks

    Tuesday, November 17, 2015 3:33 PM
  • IF you are still having problems, please upload your bdd.log file to a public share like OneDrive and share the link.

    Otherwise it would then be a good idea to analyize the windowsupdate.log file to see why it's running so slow.


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

    Tuesday, November 17, 2015 8:39 PM
  • Hello,

    Sorry for my late answer but I'm not working on this issue everyday.

    Here is a public link to the deploymentlogs folder which contain bdd.log and ztiwindowsupdate.log
    I don't see anything in relation with this issue.

    Thank you for your help.

    https://sync.oci.fr//views/public/lienPublic.xhtml?id=429&hash=9c6b8478d55dd801cc13db37fc2c20729ebf2dbd

    HisteriQal

    Tuesday, November 24, 2015 4:52 PM
  • There is a problem with one of the "Windows Defender" updates.

    Since Windows Defender is updated almost daily, you can most likely disable the bad update listed in the bdd.log and continue.

    https://keithga.wordpress.com/2015/05/10/some-practical-notes-on-wsus-early-2015/


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

    • Proposed as answer by Ty Glander Monday, November 30, 2015 10:06 PM
    Tuesday, November 24, 2015 5:04 PM
  • Thanks for your answer.

    I saw it in the log but Windows Defender updates are probably not the only cause for this because if you take a look at other moment (in the log), you can see some period (even 30 minutes sometimes !) where the log is empty, like if the PC is doing nothing (I test with a SSD drive so the reboot takes less than one minute)

    However I will block WD updates into the WSUS and check again. I will keep you informed about that ASAP.

    Thanks

    Monday, November 30, 2015 3:05 PM
  • If you read the rest of Keith's blog post there you might be able to use that to help you find whatever else updates are being an issue.

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Monday, November 30, 2015 10:12 PM