none
Question about filtering unneeded updates

    Question

  • I am fairly new at WSUS so forgive me if this has been asked (I did search on the blog first but didn't not see a discussion on it:-) We have no x64, itanium, or Vista PC's but notice that we receive updates to install them. I do not approve the updates, however I do not decline them either. Is there some way to filter out these type of updates before they are emailed to me? Please let me know if this is too vague or more information is needed. Thanks all!
    Thursday, January 27, 2011 8:29 PM

Answers

  • I am fairly new at WSUS so forgive me if this has been asked (I did search on the blog first but didn't not see a discussion on it:-) We have no x64, itanium, or Vista PC's but notice that we receive updates to install them. I do not approve the updates, however I do not decline them either. Is there some way to filter out these type of updates before they are emailed to me?

    If you do not have Vista systems, you should not synchronize the Vista product categories.

    You cannot filter out Itanium or x64 updates; if you do not have Itanium or x64 systems, declining the updates upon receipt would be the appropriate action. You could also decline the x64 updates, but I would recommend against that.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Friday, January 28, 2011 6:51 PM
    Moderator

All replies

  • I am fairly new at WSUS so forgive me if this has been asked (I did search on the blog first but didn't not see a discussion on it:-) We have no x64, itanium, or Vista PC's but notice that we receive updates to install them. I do not approve the updates, however I do not decline them either. Is there some way to filter out these type of updates before they are emailed to me?

    If you do not have Vista systems, you should not synchronize the Vista product categories.

    You cannot filter out Itanium or x64 updates; if you do not have Itanium or x64 systems, declining the updates upon receipt would be the appropriate action. You could also decline the x64 updates, but I would recommend against that.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Friday, January 28, 2011 6:51 PM
    Moderator
  • You cannot filter out Itanium or x64 updates; if you do not have Itanium or x64 systems, declining the updates upon receipt would be the appropriate action. You could also decline the x64 updates, but I would recommend against that.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    That is exactly how I handle the itanium updates. Decline after WSUS syncs.
    Tuesday, February 1, 2011 5:06 PM
  • Here is a great little SQL script (which could be set up as a regularly scheduled SQL job) to decline Itanium updates:

    http://www.flamingkeys.com/2010/10/bulk-declining-updates-in-wsus/

     

    Also found a Powershell script to accomplish the same thing (I have not tested this one myself):

    http://pulsarit.net/cs/files/folders/scripts/entry16.aspx

    Tuesday, April 26, 2011 3:51 PM
  • Here is a great little SQL script (which could be set up as a regularly scheduled SQL job) to decline Itanium updates:

    http://www.flamingkeys.com/2010/10/bulk-declining-updates-in-wsus/

    It is worthy of note that directly executing SQL code against the WSUS database is not a supported activity, and because the database schema may change at any time, without notice, such activities could be catastrophic if such changes are implemented.

    Also found a Powershell script to accomplish the same thing (I have not tested this one myself):

    http://pulsarit.net/cs/files/folders/scripts/entry16.aspx

    This is likely the correct way to achieve this objective, as the PowerShell script most likely utilizes the WSUS API to invoke the declinations, which IS a supported methodology.

    One should also note that calling the DELETE() method instead of the DECLINE() method is also a viable option, which would result in the physical removal of the Itanium updates, rather then merely declining them and still taking up the table space.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Tuesday, April 26, 2011 9:25 PM
    Moderator
  • Here is a great little SQL script (which could be set up as a regularly scheduled SQL job) to decline Itanium updates:

    http://www.flamingkeys.com/2010/10/bulk-declining-updates-in-wsus/

    It is worthy of note that directly executing SQL code against the WSUS database is not a supported activity, and because the database schema may change at any time, without notice, such activities could be catastrophic if such changes are implemented.

    Hi Lawrence, This is a good point, however the T-SQL in my script is merely borrowed straight from the inbuilt stored proc "spDeclineUpdate" within WSUS itself. I'll update the blog post to make mention of the fact it's not supported.
    Wednesday, June 15, 2011 1:59 PM
  • however the T-SQL in my script is merely borrowed straight from the inbuilt stored proc "spDeclineUpdate" within WSUS itself.

    Which does not exclude that stored proc from being updated concurrent with a schema update, and thus rendering the code from the "older version" dangerous, if not irreversibly destructive, if used on a newer version. :-)

    As noted, the preferred and supported methodology is to call the WSUS API decline() method, as is done in the PowerShell script, which will properly implement whatever stored procs and schema actually exist within the database.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Wednesday, June 15, 2011 4:53 PM
    Moderator