locked
Creating a reference image and contact local wsus seems to hang RRS feed

  • Question

  • Hi everyone

    I just want to ask if it is normal that "searching for updates" is taking a long time? I followed this guide in order to automate creating a reference image with MDT 2013 Update 1 http://trekker.net/archives/create-a-mostly-automated-reference-image-in-mdt-part-1/

    WSUS is installed on the same server and been set to auto approve updates for unassigned computers.

    The server itself is 2008 R2 and with MDT 2013 Update 1 and WSUS 3.0 SP2.

    Also running Windows Updates manually in the reference image also seems stuck at Checking for Updates.

    Not sure if this process needs 1-2 hour before seeing any changes?

    Regards

    Ronnie

    Wednesday, February 10, 2016 9:52 AM

Answers

  • Hi

    I never change the ZTIwindowsupdate file.

    I put this in my customsettings.ini WSUSServer=http://MDTserver for WSUS 3.0 and WSUSServer=http://MDTserver:8530 for WSUS 4.0

    Kind regards
    Per Larsen
    Twitter: @PerLarsen1975 | Blog: osddeployment.wordpress.com
    If this post is helpful please vote it as Helpful or click Mark for answer.

       

    Wednesday, February 10, 2016 6:04 PM

All replies

  • Hi

    What OS are you trying to Build and Capture??

    If you are using Windows 7 - then try to manually install the windows update agent or as a action in your Task Sequence.

    Kind regards
    Per Larsen
    Twitter: @PerLarsen1975 | Blog: osddeployment.wordpress.com
    If this post is helpful please vote it as Helpful or click Mark for answer.

    Wednesday, February 10, 2016 10:39 AM
  • and look in your Windows update log to see what happens in the Windows update agten.

    Kind regards
    Per Larsen
    Twitter: @PerLarsen1975 | Blog: osddeployment.wordpress.com
    If this post is helpful please vote it as Helpful or click Mark for answer.

    Wednesday, February 10, 2016 10:40 AM
  • Hi

    What OS are you trying to Build and Capture??

    If you are using Windows 7 - then try to manually install the windows update agent or as a action in your Task Sequence.

    Kind regards
    Per Larsen
    Twitter: @PerLarsen1975 | Blog: osddeployment.wordpress.com
    If this post is helpful please vote it as Helpful or click Mark for answer.

    Hi Per, I did install the latest Windows Agent 7.6 (Windows 7) as a task sequence.

    My VM reference image has now started to update which i am sure took alot longer yesterday but i will give a few more go's.

    My main concern was that i missed a vital configuration step. from what i understand i have done this

    - Updated customsettings.ini to contact my local WSUS server
    - Enabled the pre and post application windows update task sequence
    - updated windows update agent to version 7.6 in my task sequence
    - installed WSUS on my deployment server after using my other local wsus which use computer groups did not work
    - auto approve updates for all computers (+ unassigned ones)

    I am not sure but i also followed a guide for MDT on how to specify target group in WSUS and i had to edit a ZTIwindowsupdate file. This did not work yesterday hence why i installed WSUS locally now on the deployment server.

    Wednesday, February 10, 2016 12:41 PM
  • Hi

    I never change the ZTIwindowsupdate file.

    I put this in my customsettings.ini WSUSServer=http://MDTserver for WSUS 3.0 and WSUSServer=http://MDTserver:8530 for WSUS 4.0

    Kind regards
    Per Larsen
    Twitter: @PerLarsen1975 | Blog: osddeployment.wordpress.com
    If this post is helpful please vote it as Helpful or click Mark for answer.

       

    Wednesday, February 10, 2016 6:04 PM
  • Yes, it takes forever. We don't have a local WSUS server, so in our build and capture task sequence, we are just letting Windows Update handle the patching. It can take hours to fully patch a fresh Win7 SP1 install.
    Wednesday, February 10, 2016 6:34 PM
  • Hi

    I never change the ZTIwindowsupdate file.

    I put this in my customsettings.ini WSUSServer=http://MDTserver for WSUS 3.0 and WSUSServer=http://MDTserver:8530 for WSUS 4.0

    Kind regards
    Per Larsen
    Twitter: @PerLarsen1975 | Blog: osddeployment.wordpress.com
    If this post is helpful please vote it as Helpful or click Mark for answer.

       

    Hi Per,

    I followed this guide https://itmicah.wordpress.com/2014/01/16/add-wsus-target-group-option-to-mdt-deployments/ because the WSUS we use for corporate computers is configured to use computer groups and those being set via group policy.

    I am now in two minds if i should set up a new MDF 2013 Update 2 server with WDS and WSUS installed or stick the current server that was upgraded from MDT2012 to 2013.

    Wednesday, February 10, 2016 8:23 PM
  • Yes, it takes forever. We don't have a local WSUS server, so in our build and capture task sequence, we are just letting Windows Update handle the patching. It can take hours to fully patch a fresh Win7 SP1 install.
    Hi David, yeah i want to use our local WSUS and put the updates into the reference image so when we do the actual deployment we do not have to get 230+ updates which takes hours :)
    Wednesday, February 10, 2016 8:24 PM
  • We are putting the updates into our reference image. We're just using Windows Update to do it, not a local WSUS server.
    Wednesday, February 10, 2016 9:37 PM