"ITMORA" <> wrote in message
news:A92B0DA4-BCDF-4AE5-A983-...
> How long do you store windows updates on a WSUS server?
It's really not a choice. Once you synchronize the update, the update
definition is a permanent item in the database. You can delete the *files*
associated with previously approved updates, and I'd suggest doing that as
soon as you've confirmed the update is deployed to 100% of the targets.
1. After 100% deployment, mark the update as Declined.
2. Run the Server Cleanup Wizard to delete the associate files.
3. Reset the update to Not Approved in the event a subsequent system needs
the update, or the update is uninstalled from a previously deployed system.
4. (Re)Approve the update should it become needed again (which will trigger
a fresh download of the content).
5. Repeat with Step #1 as necessary.
>I was thinking of
> getting rid of all my old 2000 updates because none of my machines are on
> 2000.
This would be a good reason to:
1. Remove Windows 2000 from your selected products for synchronization.
2. Mark all updates exclusively in the "Windows 2000" product category as
Declined.
3. Run the Server Cleanup Wizard.
> I'm just not sure how far back I should go with the XP updates, has
> anyone dealt with this?
My recommendation is to define, by organizational policy, a service pack
level that is the baseline installation for all machines in your
organization. Require that Service Pack to be installed before the machine
is deployed to a user. (Given the age, there's almost no reason XP SP3
should not be this baseline.) Then identify updates declined by that
service pack and decline/delete them.
--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
My Blog:
http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website:
http://www.microsoft.com/wsus
My MVP Profile:
http://mvp.support.microsoft.com/pro...awrence.Garvin