WSUS 3.0 Beta regarding updates approval and installation

Discussion in 'Update Services' started by Pablo, Oct 24, 2006.

  1. Pablo

    Pablo Guest

    I have started using the WSUS 3.0 in my production environment of about 70
    PCs and 8 servers.

    In the previous WSUS version I was able to set it up to install but DO NOT
    reboot my "server" group and it worked out great, but on the new WSUS 3.0 it
    seems like that function is missing? All groups are rebooting automatically
    after updates that require it. Maybe I am doing something wrong.

    I have setup the rules properly -- I think. I am not sure but it seems like
    now I have to make some changes to the GPO in order for this to work and
    setup my PCs and Servers to have 2 different WSUS GPOs. Has anyone had this
    Pablo, Oct 24, 2006
    1. Advertisements

  2. Pablo, one thing I'm certain of -- you were not able to configure WSUS to
    "not reboot". You might have configured it to "not reboot if somebody is
    logged on", but that is the closest you could get. The functionality has not
    changed between WSUS v2 and WSUS v3 in that regard.
    Nope. This is, and has been, since the introduction of the AutomaticUpdates
    service way back in Windows 98 the normal/by-design functionality of updates
    The common, conventional, and recommended configuration is to separate
    desktops and servers into separate OUs and separate GPOs. For one, updates
    on workstations are almost always installed by a scheduled event (Option
    #4), whereas servers are usually updated interactively, by a server admin,
    sitting at the console or an RDC session (Option #3).

    Plus, you probably wantt to have one or more TEST groups, so that you don't
    find out about a 'problem' with an update after you've installed it on a
    couple hundred systems.

    Lawrence Garvin, M.S., MVP-Software Distribution
    Everything you need for WSUS is at
    And, everything else is at
    Lawrence Garvin \(MVP\), Oct 25, 2006
    1. Advertisements

  3. Pablo

    Pablo Guest

    Thanks Lawrence, I don't know how it worked before then. But I guess I can
    make some changes to my GPO. Any idea where I can find more info on "GPO
    settings" for WSUS?

    Could the "client-side targeting" setting be used to distiguish the
    different WSUS groups? Or I guess my question is what is the best way to
    configure GPO. Because I've never set up GPO for grouping of PCs/servers only
    Pablo, Oct 25, 2006
  4. The history of this newsgroup is replete with conversations about policy
    settings for WSUS.

    What you cannot get online (should be 60 days of history, IIRC), you can get
    from a Google Groups search on this newsgroup:

    Search on the keywords "GPO" and/or "policy".
    Absolutely. That is the primary purpose of target groups. However, to do
    this without OUs and GPOs, you would have to run your WSUS server using
    server-side targeting, and manually place each and every computer system
    from "Unassigned Computers" into the desired computer target group. In the
    GPO you would DISABLE the policy setting "Enable client-side targeting"

    Lawrence Garvin, M.S., MVP-Software Distribution
    Everything you need for WSUS is at
    And, everything else is at
    Lawrence Garvin \(MVP\), Oct 25, 2006
  5. Pablo

    Dave Mills Guest

    WSUS Deployment guide and op's guide.
    Spot on, that exactly what it is for, together with little difference like
    having a different detection frequency for the "Under Construction" group.
    Dave Mills, Oct 25, 2006
    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.