WSUS: How to approve updates per computer for installation?

Discussion in 'Update Services' started by Wolfgang Sirges, Aug 9, 2006.

  1. Hi,

    I'm quite new to WSUS, but since about a month everything seems to be
    running fine.

    I'm running WSUS in a small workgroup, about seven PCs. There are two
    computer groups, one for the server and one for the clients.

    This week, I had to do a clean install on one of the clients (XP Pro
    SP2). I use images for this (changed SID, of course), and that PC is
    reporting fine to WSUS.

    Being a fresh install, WSUS shows 40+ patches needed for this PC (the
    list really is very long ;-)). A large portion of those updates is not
    approved for installation (yet).

    I'm in the computer | <computername> | status view of WSUS Admin.

    How can I approve those needed updates all at once? I haven't found a
    way for this yet. Of course, I could print the list and approve each
    update individually (and manually), but that's not what I'm looking
    for.

    Greetings, Wolfgang.

    Please remove the "nospam_" part of the address. Thanks.
     
    Wolfgang Sirges, Aug 9, 2006
    #1
    1. Advertisements

  2. Wolfgang Sirges

    JeffG Guest

    Wolfgang.

    Create a new computer group in WSUS. Add your new computer to it. Then go to
    Updates, highlight everything and select "Approve for Detection". Then select
    approve for installation only for the group that contains your computer and
    optionally schedule a time for the updates. The computer will install the
    ones it needs.

    My time posting to these. Good luck!
    Jeff
     
    JeffG, Aug 9, 2006
    #2
    1. Advertisements


  3. Hi Jeff,

    thanks very much for your post.

    I tried that procedure today, and it solved my problem, although it
    took some time to complete, about an hour or so (repeated cycles of
    detecting, downloading, installing and rebooting ;-))

    Why didn't I think of that? Hmm...

    While I was working on this problem I noticed that another of my
    clients hadn't reported to WSUS for some days, although I definitely
    know it had been used quite a lot.

    Turned out it was a problem with a Registry Key: once I set
    ElevateNonAdmins to the value of 1, everything works fine!

    Thanks Jeff, learned a lot through this one! ;-))

    Wolfgang.
    Please remove the "nospam_" part of the address. Thanks.
     
    Wolfgang Sirges, Aug 11, 2006
    #3
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.