|
|
I have a WSUS 3.0 server that insists that some servers need updates even though I set the approval to "Not Approved".
Example: I have a group called "Standard Servers" that has all core OS updates. Below Standard Servers is a group called "SQL Servers" that has SQL Server updates approved and inherit the approvals for all the core OS updates.
So why are servers in the Standard Servers group saying there are SQL Server updates when even the report says the approval is Not Approved?
Thanks! -- Dave
|
|
Hi Dave,
It looks like you not fully understand how this works. Approving or not approving has no influence on needed or not needed. When an update is applicable to a system, and is not yet installed, it is indicated as needed by WSUS. But you can still decide whether or not you want to install this update (yet), and this is done by approving or not approving the update. The only way to get rid of an update that is being indicated as needed by WSUS, and that you never want to install, is to manually decline that update.
Regards,
Ed "David Nelson" <DavidNelson[ at ]discussions.microsoft.com> wrote in message news:E7764548-0796-45BF-BE1C-23C286B75E2B[ at ]microsoft.com...
[Quoted Text] >I have a WSUS 3.0 server that insists that some servers need updates even > though I set the approval to "Not Approved". > > Example: > I have a group called "Standard Servers" that has all core OS updates. > Below Standard Servers is a group called "SQL Servers" that has SQL Server > updates approved and inherit the approvals for all the core OS updates. > > So why are servers in the Standard Servers group saying there are SQL > Server > updates when even the report says the approval is Not Approved? > > Thanks! > -- Dave
|
|
Hi,
I think many WSUS 2 users are confused by WSUS 3 settings
WSUS 2 -> WSUS 3 Approved -> Approved Not Approved -> --GONE-- Detect only -> Not Approved Declined -> Declined The only way to get the WSUS 2 "Not Approved" behavior is to decline. So there is no more way to "hide" and update just for one group.
BR, Malte
"David Nelson" wrote:
[Quoted Text] > I have a WSUS 3.0 server that insists that some servers need updates even > though I set the approval to "Not Approved". > > Example: > I have a group called "Standard Servers" that has all core OS updates. > Below Standard Servers is a group called "SQL Servers" that has SQL Server > updates approved and inherit the approvals for all the core OS updates. > > So why are servers in the Standard Servers group saying there are SQL Server > updates when even the report says the approval is Not Approved? > > Thanks! > -- Dave
|
|
So in WSUS3.0 if I am synchronizing the Updates category for Server OS's all of my systems will say I need any Update like .NET Framework 3.0 unless I decline the update at a global level? If this is true then in my installation this doesn't work like this for 100% of the devices. Some would say I need an update while others say I don't even when those systems don't have that update installed.
Still learning, Eric
"Ed" wrote:
[Quoted Text] > Hi Dave, > > It looks like you not fully understand how this works. > Approving or not approving has no influence on needed or not needed. > When an update is applicable to a system, and is not yet installed, it is > indicated as needed by WSUS. But you can still decide whether or not you > want to install this update (yet), and this is done by approving or not > approving the update. > The only way to get rid of an update that is being indicated as needed by > WSUS, and that you never want to install, is to manually decline that > update. > > Regards, > > Ed > "David Nelson" <DavidNelson[ at ]discussions.microsoft.com> wrote in message > news:E7764548-0796-45BF-BE1C-23C286B75E2B[ at ]microsoft.com... > >I have a WSUS 3.0 server that insists that some servers need updates even > > though I set the approval to "Not Approved". > > > > Example: > > I have a group called "Standard Servers" that has all core OS updates. > > Below Standard Servers is a group called "SQL Servers" that has SQL Server > > updates approved and inherit the approvals for all the core OS updates. > > > > So why are servers in the Standard Servers group saying there are SQL > > Server > > updates when even the report says the approval is Not Approved? > > > > Thanks! > > -- Dave > > >
|
|
Maybe this will help: If you right-click on "Updates" in the left pane, you can select "New update view...". Then select "Updates are approved for a specific group (not including inherited approvals)" in the upper pane, and select the specific group in the lower pane. Give this view specific name (like the group name). Now you created an Update view specific for that group. In this view you can filter the updates list in the large pane as appropriate, for instance with "Approval: Any Except Declined" and "Status: Failed or Needed".
Regards,
Ed "Malte" <Malte[ at ]discussions.microsoft.com> wrote in message news:1410B75E-8AC0-4AF9-9E81-1F19D7E7A273[ at ]microsoft.com...
[Quoted Text] > Hi, > > I think many WSUS 2 users are confused by WSUS 3 settings > > > WSUS 2 -> WSUS 3 > Approved -> Approved > Not Approved -> --GONE-- > Detect only -> Not Approved > Declined -> Declined > The only way to get the WSUS 2 "Not Approved" behavior is to decline. > So there is no more way to "hide" and update just for one group. > > BR, > Malte > > "David Nelson" wrote: > >> I have a WSUS 3.0 server that insists that some servers need updates even >> though I set the approval to "Not Approved". >> >> Example: >> I have a group called "Standard Servers" that has all core OS updates. >> Below Standard Servers is a group called "SQL Servers" that has SQL >> Server >> updates approved and inherit the approvals for all the core OS updates. >> >> So why are servers in the Standard Servers group saying there are SQL >> Server >> updates when even the report says the approval is Not Approved? >> >> Thanks! >> -- Dave
|
|
Yes, it is my understanding that declining an update can only be done on a "global" level. But if anybody else knows better, then please let us know.
Regards,
Ed "wickman" <wickman[ at ]discussions.microsoft.com> wrote in message news:B6018B03-47A5-4020-AC1C-14DFE714D9C4[ at ]microsoft.com...
[Quoted Text] > So in WSUS3.0 if I am synchronizing the Updates category for Server OS's > all > of my systems will say I need any Update like .NET Framework 3.0 unless I > decline the update at a global level? If this is true then in my > installation > this doesn't work like this for 100% of the devices. Some would say I need > an > update while others say I don't even when those systems don't have that > update installed. > > Still learning, > Eric > > > "Ed" wrote: > >> Hi Dave, >> >> It looks like you not fully understand how this works. >> Approving or not approving has no influence on needed or not needed. >> When an update is applicable to a system, and is not yet installed, it is >> indicated as needed by WSUS. But you can still decide whether or not you >> want to install this update (yet), and this is done by approving or not >> approving the update. >> The only way to get rid of an update that is being indicated as needed by >> WSUS, and that you never want to install, is to manually decline that >> update. >> >> Regards, >> >> Ed >> "David Nelson" <DavidNelson[ at ]discussions.microsoft.com> wrote in message >> news:E7764548-0796-45BF-BE1C-23C286B75E2B[ at ]microsoft.com... >> >I have a WSUS 3.0 server that insists that some servers need updates >> >even >> > though I set the approval to "Not Approved". >> > >> > Example: >> > I have a group called "Standard Servers" that has all core OS updates. >> > Below Standard Servers is a group called "SQL Servers" that has SQL >> > Server >> > updates approved and inherit the approvals for all the core OS updates. >> > >> > So why are servers in the Standard Servers group saying there are SQL >> > Server >> > updates when even the report says the approval is Not Approved? >> > >> > Thanks! >> > -- Dave >> >> >>
|
|
|