locked
List and approve update (script) RRS feed

  • Question

  • Hello,

    We have 2 environments (test and production), with there own wsus server.
    We approve updates in test and let the user test there applications, when the test is okay, then the updates can be approved in production.

    Can we list all the approved updates and export it to a file. And can we use this file for an import to approve it in production ?

    Wednesday, February 4, 2015 10:36 AM

Answers

  • Can we list all the approved updates and export it to a file.

    Not really. There is some sample code from the WSUS v2 days that purports to export approvals, but I've yet to hear of anybody actually use that successfully.

    Most organizations do this with one server and WSUS Target Groups. Then it's trivial to clone the approvals from the Test GROUP to the Production GROUP.

    The other way you could conceivably do this is to make the TEST server an Upstream Server, the PRODUCTION server a replica server, and set the replica server to Manual Synchronization. Then, when your testing is done, perform a sync on the replica, which will sync all of the updates, content, and approvals from the TEST server.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Wednesday, February 4, 2015 2:39 PM

All replies

  • Can we list all the approved updates and export it to a file.

    Not really. There is some sample code from the WSUS v2 days that purports to export approvals, but I've yet to hear of anybody actually use that successfully.

    Most organizations do this with one server and WSUS Target Groups. Then it's trivial to clone the approvals from the Test GROUP to the Production GROUP.

    The other way you could conceivably do this is to make the TEST server an Upstream Server, the PRODUCTION server a replica server, and set the replica server to Manual Synchronization. Then, when your testing is done, perform a sync on the replica, which will sync all of the updates, content, and approvals from the TEST server.


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Wednesday, February 4, 2015 2:39 PM
  • You can export approvals and / or group configuration from one WSUS to another. You will need the WSUS "Update  Services 3.0 API Samples and Tools," update installed and you can then script exports of approvals using the command below.

    C:\Program Files (x86)\Update Services 3.0 API Samples and Tools\WsusMigrate\WsusMigrationExport\WsusMigrationExport.exe" "E:\export\wsus_approvals.xml" > "E:\export\wsus2.log"

    You then use the same tools on the target WSUS server using the WsusMigrationImport command to import the approvals.


    Thursday, February 5, 2015 10:38 AM
  • You can export approvals and / or group configuration from one WSUS to another. You will need the WSUS "Update  Services 3.0 API Samples and Tools," update installed and you can then script exports of approvals using the command below.

    As I noted in my previous replies, that sample code was actually written for the WSUS v2 API in 2005, and simply "renamed" for WSUS v3 in 2007. It's built on the .NET Framework v2 so will, at a minimum, likely require notable additional coding effort to get it to work. Most people who have tried to use that utility have met with less-than-desirable results -- many of them, of course, because they compiled it out-of-the-box with no modifications.

    If you have a *WORKING* instance of that utility, I'm sure the community would greatly appreciate it if you shared your working source code.

    Otherwise, I'm going to stand by my original response: Not Really. :-)


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Thursday, February 5, 2015 7:33 PM
  • You can export approvals and / or group configuration from one WSUS to another. You will need the WSUS "Update  Services 3.0 API Samples and Tools," update installed and you can then script exports of approvals using the command below.

    As I noted in my previous replies, that sample code was actually written for the WSUS v2 API in 2005, and simply "renamed" for WSUS v3 in 2007. It's built on the .NET Framework v2 so will, at a minimum, likely require notable additional coding effort to get it to work. Most people who have tried to use that utility have met with less-than-desirable results -- many of them, of course, because they compiled it out-of-the-box with no modifications.

    If you have a *WORKING* instance of that utility, I'm sure the community would greatly appreciate it if you shared your working source code.

    Otherwise, I'm going to stand by my original response: Not Really. :-)


    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    It does work for us, we have several disconnected networks and this process works as advertised, no modification to the code was required. They are all Windows 2008 R2 servers. I am unsure what else I can add.

    Edit: This was working up until August when an update broke it on all disconnected networks. We are expecting a fix from Microsoft within the next month or so. They have identified how to resolve it but it requires to be installed as Trusted Installer which creates other issues.


    • Edited by MikeeMiracle Thursday, February 12, 2015 4:36 PM
    Thursday, February 12, 2015 4:28 PM