1.Automatically approve new revisions of updates that are already approved
2.Automatically decline updates when a new revision causes them to expire
One of the KB's (KB947319) in MS09-043 was revised on 10/27/2009; however,
if I look in Security Updates on my server, I see 2 versions of the KB.
1.The original from 8/11/2009 -- set to Install. Labelled as "This update is
superseded by another update"
2.The update from 10/27/2009 - set to Not Approved. Labelled as "This update
supersedes another update"
Since the Aug version of the KB was set to install, I expected for
"Automatic Revision of Updates" to set the Oct version to install, but this
did not happen.
1.Do I have an incorrect understanding of the "Revision of Updates" settings?
2.If not, are others experiencing this same?
In your newsreader:
news://msnews.microsoft.com/microsoft.public.windows.server.update_services
]]
Supersedance is not the same thing as revision. This is expected behaviour.
In the majority of cases when an update has changed for some reason, a new
package is released which supersedes the old package. Packages are revised only
relatively infrequently, if you exclude package expiration.
Harry.