WSUS 3.0 -- How to migrate approvals from one group to another?

Discussion in 'Update Services' started by ImAllEars, Oct 5, 2007.

  1. ImAllEars

    ImAllEars Guest

    If I upgrade my 2.0 server and database to 3.0, I will want to retain my
    group names and approvals on those groups until I can change them (I have a
    large WSUS enterprise). There appears to be no way to create a group tree in
    WSUS 3 and then MOVE my old groups to fit in them... I have to delete the old
    group (which deletes the approvals attached to it) and create a new one. I
    have too many groups, too many applications that have needed to be excluded
    from certain patches, to simply lose all of my approvals and start all over.
    Clinical applications at hospitals are at stake here.

    Surely, Microsoft didn't overlook the need for this. Can anyone help?
    ImAllEars, Oct 5, 2007
    1. Advertisements

  2. If I upgrade my 2.0 server and database to 3.0, I will want to retain my

    Upgrade will take care of all this. After upgrade your groups and approvals
    should exist on the 3.0 side just as they did on the 2.0 side (with the
    exception of scan approvals, because those are implicit now).

    Also since ‘Clinical applications at hospitals are at stake’ you should be
    sure to perform a DB backup before doing the upgrade. That way in the
    unlikely event something goes wrong you can easily roll back.

    Thanks -
    Bobbie Harder
    PM, WSUS
    This posting appears "AS IS" with no warranties and confers no rights
    Bobbie Harder \(MSFT\), Oct 8, 2007
    1. Advertisements

  3. ImAllEars

    ImAllEars Guest


    Please understand, I've got all the system admin stuff taken care of.
    Backups galore, in redundant and tested locations, of both 2.0 and 3.0. I
    have been searching for over a week here for the real problem. My original
    post is here:

    Again, my issue now is that I have a flat group structure, as migrated from
    2.0 to 3.0, and apparently no Microsoft-supported way of creating the group
    hierarchy that we need, and then MOVING all my computer groups into this
    "group tree" so that I can take advantage of WSUS 3's new nested group

    I want to either:

    1 - Move the groups (cut and paste would be nice, but instead all I can do
    is delete).


    2 - Copy the approval properties of one group to another, and then rename
    the new recipient once the old group is deleted (because I can't have
    duplicate group names anywhere else in the tree).

    So to wrap up, I have a WSUS 3.0 environment that is stuck with a 2.0 group
    structure (ie, flat) until I can find a way to move the groups and/or their
    approvals under the new model for our business. The only option that seems
    to come with WSUS 3.0 is to delete the group, which is not an option for us
    because we have hundreds of groups, most with granular approvals set for
    specific applications and needs for their hospitals.

    Please help! Because the approval interface is not sorted by group name
    (nor can you set it to be so), I have to hunt and peck all over the place
    when approving each update. Terrible!
    ImAllEars, Oct 9, 2007
    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.