|
|
This extremely important update to XP clients was not
downloaded to recently created XP clients from WSUS3.
This prevented Verclsid.exe from being installed and
executed. As a result, significant problems with
running Internet Explorer and a number of programs on
these workstations as well as the simple "run command".
In fact, it created complete havoc for users on those
machines. I'd literally a spent hours on the Internet
tracking down how this could happen.
In opening WSUS on the server the default options to
install the following are automatically a accepted :
clinical updates, definitions, security updates, update
rollups, and updates. It is unclear to me why kb908531
was not included in the 90 or so patches that the WSUS
server downloaded to the workstations.
Does any one know why this KB would be ignored by WSUS?
|
|
GeraldF wrote:
[Quoted Text] > This extremely important update to XP clients was not
> downloaded to recently created XP clients from WSUS3.
[...]
> Does any one know why this KB would be ignored by WSUS?
Have you checked whether this update has been approved for installation on the
WSUS server?
Note that automatic approval only affects new updates, any updates that are
already on the WSUS server at the time you turn automatic approval on will still
need to be approved manually.
Harry.
|
|
In article <eGEtgl6qHHA.532[ at ]TK2MSFTNGP06.phx.gbl>,
harry[ at ]scms.waikato.ac.nz says...
[Quoted Text] > Note that automatic approval only affects new updates, any updates that are
> already on the WSUS server at the time you turn automatic approval on will still
> need to be approved manually.
All of the required updates for XP SP2 were applied by
the WSUS3 Server including any "Not expired" updates,
some of these were older updates.
As you know WSUS is like a Giant Squid with many
tenticles. Is there a way to specifcally track down this
KB in WSUS? I know it is not listed at all in the WSUS
report viewer for the XP machines. Does WSUS have a list
of all KB's downloaded to the server?
Thanks
|
|
In article <eGEtgl6qHHA.532[ at ]TK2MSFTNGP06.phx.gbl>,
harry[ at ]scms.waikato.ac.nz says...
[Quoted Text] > Note that automatic approval only affects new updates, any updates that are
> already on the WSUS server at the time you turn automatic approval on will still
> need to be approved manually.
Using WSUS3 Server under Update Services->Server->
Updates, I used search to search for this KB. WSUS
states this is a critical update which is "Not Approved
Inherited". This implies to me it is in some rollup
update which should have been applied to all machines.
|
|
This is an explicitly approvable update, so you would need to Approve this
update fro whatever target group you would like to approve it for.
Was this a clean install of WSUS 3.0 or an Upgrade?
New feature in WSUS 3.0, with respect to Auto-Approval rules, you can NOW
run these approval rules at any time on the WSUS 3.0 Server and any update
that meets the criteria for the Auto-Approval rule will get approved. it is
no longer just forward looking.
--
Cecil [MSFT]
Deployment, WSUS
Microsoft
This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"GeraldF" <me[ at ]somewhere.com> wrote in message
news:MPG.20d7e5875010c5459896a9[ at ]news.microsoft.com...
[Quoted Text] > In article <eGEtgl6qHHA.532[ at ]TK2MSFTNGP06.phx.gbl>,
> harry[ at ]scms.waikato.ac.nz says...
>
>> Note that automatic approval only affects new updates, any updates that
>> are
>> already on the WSUS server at the time you turn automatic approval on
>> will still
>> need to be approved manually.
>
> Using WSUS3 Server under Update Services->Server->
> Updates, I used search to search for this KB. WSUS
> states this is a critical update which is "Not Approved
> Inherited". This implies to me it is in some rollup
> update which should have been applied to all machines.
|
|
GeraldF wrote:
[Quoted Text] > Using WSUS3 Server under Update Services->Server->
> Updates, I used search to search for this KB. WSUS
> states this is a critical update which is "Not Approved
> Inherited".
I don't know what Inherited means, but Not Approved seems pretty clear-cut. So
approve it already!
Harry.
|
|
In article <eH3omwTrHHA.1200[ at ]TK2MSFTNGP04.phx.gbl>,
cecils[ at ]online.microsoft.com says...
[Quoted Text] > New feature in WSUS 3.0, with respect to Auto-Approval rules, you can NOW
> run these approval rules at any time on the WSUS 3.0 Server and any update
> that meets the criteria for the Auto-Approval rule will get approved. it is
> no longer just forward looking.
This was an upgrae from WSUS2.
Do you know where you run the Auto-Approval?
|
|
Auto-Approval (and most management ) is done in the "Options" node,
Automatic Approvals
--
Cecil [MSFT]
Deployment, WSUS
Microsoft
This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"GeraldF" <me[ at ]somewhere.com> wrote in message
news:MPG.20d8ed41ed7090dd9896ab[ at ]news.microsoft.com...
[Quoted Text] > In article <eH3omwTrHHA.1200[ at ]TK2MSFTNGP04.phx.gbl>,
> cecils[ at ]online.microsoft.com says...
>> New feature in WSUS 3.0, with respect to Auto-Approval rules, you can NOW
>> run these approval rules at any time on the WSUS 3.0 Server and any
>> update
>> that meets the criteria for the Auto-Approval rule will get approved. it
>> is
>> no longer just forward looking.
>
> This was an upgrae from WSUS2.
> Do you know where you run the Auto-Approval?
>
|
|
|