Not Approved Updates show as Needed John 7/5/2007 5:38:01 PM All, 1) Can anyone explain why I would have machines that have Updates as Not Approved show as Needed? This making our test process on different groups quite confusing. 2) Also, in v2 (SP1) we would have Detected as an approval choice. This not not an option anymore with V3. Can anyone explain an efficient approval chioce to test different groups? I'm having to remember each update & search individually now. It seems to be more cumbersome testing & approving now with v3. Any suggestions would be appreciated. Thanks, John

Re: Not Approved Updates show as Needed "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 7/6/2007 3:49:28 AM "John" <John[ at ]discussions.microsoft.com> wrote in message news:D012ED4C-BAFC-4BFC-BD11-38722A22865C[ at ]microsoft.com... [Quoted Text] > 1) Can anyone explain why I would have machines that have Updates as Not > Approved show as Needed? Because that's the design of WSUS. If a client does not have an update installed, and that update would be installable if it were approved, it will be reported as "Needed". After the first installation event, the status will change to the more non-committed "Not Installed". > This making our test process on different groups quite confusing. How so? > 2) Also, in v2 (SP1) we would have Detected as an approval choice. This > not > not an option anymore with V3. All Updates/All Groups are "Detect" by default in WSUS 3.0 (This is why you have all of the systems reporting as "Needed" for updates that are "Not Approved".) > Can anyone explain an efficient approval > chioce to test different groups? I'm having to remember each update & > search > individually now. Frankly, I don't see how the methodology would have changed from WSUS 2.0. > It seems to be more cumbersome testing & approving now with v3. Any > suggestions would be appreciated. In fact, I think it's easier with WSUS 3.0. A group of updates is synchronized. Execute a filter view on "All Updates" to look at only "Not Approved" updates, and sort them by "Arrival Date" descending (which will put the newest arrivals at the top of the list). Select ALL Updates with an "Arrival Date" for the date of interest, and approve them for your test group. -- Lawrence Garvin, M.S., MCTS, MCP Independent WSUS Evangelist MVP-Software Distribution (2005-2007) https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E Everything you need for WSUS is at http://www.microsoft.com/wsus And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....

Re: Not Approved Updates show as Needed John 7/6/2007 1:38:01 PM Lawrence, Thank you for the reply. I'll give the filter a try. John "Lawrence Garvin (MVP)" wrote: [Quoted Text] > > "John" <John[ at ]discussions.microsoft.com> wrote in message > news:D012ED4C-BAFC-4BFC-BD11-38722A22865C[ at ]microsoft.com... > > > 1) Can anyone explain why I would have machines that have Updates as Not > > Approved show as Needed? > > Because that's the design of WSUS. If a client does not have an update > installed, and that update would be installable if it were approved, it will > be reported as "Needed". After the first installation event, the status will > change to the more non-committed "Not Installed". > > > This making our test process on different groups quite confusing. > > How so? > > > > 2) Also, in v2 (SP1) we would have Detected as an approval choice. This > > not > > not an option anymore with V3. > > All Updates/All Groups are "Detect" by default in WSUS 3.0 (This is why you > have all of the systems reporting as "Needed" for updates that are "Not > Approved".) > > > Can anyone explain an efficient approval > > chioce to test different groups? I'm having to remember each update & > > search > > individually now. > > Frankly, I don't see how the methodology would have changed from WSUS 2.0. > > > It seems to be more cumbersome testing & approving now with v3. Any > > suggestions would be appreciated. > > In fact, I think it's easier with WSUS 3.0. > > A group of updates is synchronized. Execute a filter view on "All Updates" > to look at only "Not Approved" updates, and sort them by "Arrival Date" > descending (which will put the newest arrivals at the top of the list). > > Select ALL Updates with an "Arrival Date" for the date of interest, and > approve them for your test group. > > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E > > Everything you need for WSUS is at > http://www.microsoft.com/wsus > > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com > ..... > > >