Turned off "Feature Packs" but still detecting <-> 12/22/2008 7:12:10 PM I rebooted the server but still the machines want to download the feature packs. I've been declining them as I see them but I really need this to stop detecting because I only want critical and security updates and nothing else. Any ideas?

Re: Turned off "Feature Packs" but still detecting "Lawrence Garvin \(MVP\)" <lawrence[ at ]news.postalias> 12/22/2008 11:36:09 PM <-> wrote in message news:%23q$BykGZJHA.3844[ at ]TK2MSFTNGP03.phx.gbl... [Quoted Text] >I rebooted the server but still the machines want to download the feature >packs. I've been declining them as I see them but I really need this to >stop detecting because I only want critical and security updates and >nothing else. Any ideas? There are three contradictory points in this post. Let's see if first we can get a grasp on the actual situation. [1] You've stated the machines want to download Feature Packs. Do you have an example of an entry from a WindowsUpdate.log showing any update in "Features Packs" that's being detected and queued for download by the WUA? If not, on what do you base your conclusion that "...the machines want to download the feature packs..."? [2] You've stated that you've declined the updates. If you're declining all of the updates in the "Feature Packs" classification -- why are you even synchronizing "Feature Packs"? Furthermore, if you are declining all of these updates, then it is *impossible* for a client system to download any update in that classification. [3] =Detecting= is the normal behavior of a client based on the presence of an undeclined update in WSUS. If you do not want a client to detect whether an update is NEEDED; then you have two options: [a] Do not synchronize the Product and/or Classification that contains the update(s), or [b] Ensure the updates are declined (once declined, the client will not detect the update as available). Conclusion: If you only want CRITICAL and SECURITY Updates, then you should only be synchronizing CRITICAL and SECURITY updates! (Which, btw, is the default configuration of a freshly installed WSUS Server.) -- Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP Principal/CTO, Onsite Technology Solutions, Houston, Texas Microsoft MVP - Software Distribution (2005-2009) MS WSUS Website: http://www.microsoft.com/wsus My Websites: http://www.onsitechsolutions.com; http://wsusinfo.onsitechsolutions.com My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

Re: Turned off "Feature Packs" but still detecting <-> 12/23/2008 12:02:12 AM Hello, Thank you for your reply. I did uncheck the boxes for Feature Packs and Updates but I am under the impression now that all previously synchronized Feature Packs and Updates will be detected and that unchecking it only prevents future Feature Packs and Updates from being detected. Since I did the initial synchronization with Feature Packs and Updates checked, that's when the bulk of them are going to be synchronized. So I think at this point I can either uninstall WSUS which I don't want to do, or just live with it and decline any found Feature Packs/Updates as I come across them. "Lawrence Garvin (MVP)" <lawrence[ at ]news.postalias> wrote in message news:uqctS4IZJHA.684[ at ]TK2MSFTNGP04.phx.gbl... [Quoted Text] > <-> wrote in message news:%23q$BykGZJHA.3844[ at ]TK2MSFTNGP03.phx.gbl... >>I rebooted the server but still the machines want to download the feature >>packs. I've been declining them as I see them but I really need this to >>stop detecting because I only want critical and security updates and >>nothing else. Any ideas? > > There are three contradictory points in this post. Let's see if first we > can get a grasp on the actual situation. > > [1] You've stated the machines want to download Feature Packs. Do you have > an example of an entry from a WindowsUpdate.log showing any update in > "Features Packs" that's being detected and queued for download by the WUA? > If not, on what do you base your conclusion that "...the machines want to > download the feature packs..."? > > [2] You've stated that you've declined the updates. If you're declining > all of the updates in the "Feature Packs" classification -- why are you > even synchronizing "Feature Packs"? Furthermore, if you are declining all > of these updates, then it is *impossible* for a client system to download > any update in that classification. > > [3] =Detecting= is the normal behavior of a client based on the presence > of an undeclined update in WSUS. If you do not want a client to detect > whether an update is NEEDED; then you have two options: [a] Do not > synchronize the Product and/or Classification that contains the update(s), > or [b] Ensure the updates are declined (once declined, the client will not > detect the update as available). > > Conclusion: If you only want CRITICAL and SECURITY Updates, then you > should only be synchronizing CRITICAL and SECURITY updates! (Which, btw, > is the default configuration of a freshly installed WSUS Server.) > > > -- > Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP > Principal/CTO, Onsite Technology Solutions, Houston, Texas > Microsoft MVP - Software Distribution (2005-2009) > > MS WSUS Website: http://www.microsoft.com/wsus > My Websites: http://www.onsitechsolutions.com; > http://wsusinfo.onsitechsolutions.com > My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin >

Re: Turned off "Feature Packs" but still detecting "Tom S" <me[ at ]work.com> 12/23/2008 7:17:50 AM You did 3(a), now do 3(b) for any Feature Packs that synchronized prior to 3(a). View all updates, filter for any except declined, sort by classification, select all Feature Packs and do a bulk decline. The machines should figure it out after the next detection cycle. Tom <-> wrote in message news:%23YfO2GJZJHA.5520[ at ]TK2MSFTNGP02.phx.gbl... [Quoted Text] > Hello, > > Thank you for your reply. I did uncheck the boxes for Feature Packs and > Updates but I am under the impression now that all previously synchronized > Feature Packs and Updates will be detected and that unchecking it only > prevents future Feature Packs and Updates from being detected. Since I > did the initial synchronization with Feature Packs and Updates checked, > that's when the bulk of them are going to be synchronized. So I think at > this point I can either uninstall WSUS which I don't want to do, or just > live with it and decline any found Feature Packs/Updates as I come across > them. > > "Lawrence Garvin (MVP)" <lawrence[ at ]news.postalias> wrote in message > news:uqctS4IZJHA.684[ at ]TK2MSFTNGP04.phx.gbl... >> <-> wrote in message news:%23q$BykGZJHA.3844[ at ]TK2MSFTNGP03.phx.gbl... >>>I rebooted the server but still the machines want to download the feature >>>packs. I've been declining them as I see them but I really need this to >>>stop detecting because I only want critical and security updates and >>>nothing else. Any ideas? >> >> There are three contradictory points in this post. Let's see if first we >> can get a grasp on the actual situation. >> >> [1] You've stated the machines want to download Feature Packs. Do you >> have an example of an entry from a WindowsUpdate.log showing any update >> in "Features Packs" that's being detected and queued for download by the >> WUA? If not, on what do you base your conclusion that "...the machines >> want to download the feature packs..."? >> >> [2] You've stated that you've declined the updates. If you're declining >> all of the updates in the "Feature Packs" classification -- why are you >> even synchronizing "Feature Packs"? Furthermore, if you are declining all >> of these updates, then it is *impossible* for a client system to download >> any update in that classification. >> >> [3] =Detecting= is the normal behavior of a client based on the presence >> of an undeclined update in WSUS. If you do not want a client to detect >> whether an update is NEEDED; then you have two options: [a] Do not >> synchronize the Product and/or Classification that contains the >> update(s), or [b] Ensure the updates are declined (once declined, the >> client will not detect the update as available). >> >> Conclusion: If you only want CRITICAL and SECURITY Updates, then you >> should only be synchronizing CRITICAL and SECURITY updates! (Which, btw, >> is the default configuration of a freshly installed WSUS Server.) >> >> >> -- >> Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP >> Principal/CTO, Onsite Technology Solutions, Houston, Texas >> Microsoft MVP - Software Distribution (2005-2009) >> >> MS WSUS Website: http://www.microsoft.com/wsus >> My Websites: http://www.onsitechsolutions.com; >> http://wsusinfo.onsitechsolutions.com >> My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin >> > >

Re: Turned off "Feature Packs" but still detecting <-> 12/23/2008 3:07:28 PM Good point; that is what I'm going to do. In fact it works out because there were a couple of exceptions in which I do want "Updates" like WMP11 for example. So this will give me the flexibility of saying yes or no. I'll decline 99% of them and then if there is a Feature Pack or "Update" that I really want I have the option of not declining it. "Tom S" <me[ at ]work.com> wrote in message news:uM5bO6MZJHA.4480[ at ]TK2MSFTNGP06.phx.gbl... [Quoted Text] > You did 3(a), now do 3(b) for any Feature Packs that synchronized prior to > 3(a). > > View all updates, filter for any except declined, sort by classification, > select all Feature Packs and do a bulk decline. > > The machines should figure it out after the next detection cycle. > > Tom > > <-> wrote in message news:%23YfO2GJZJHA.5520[ at ]TK2MSFTNGP02.phx.gbl... >> Hello, >> >> Thank you for your reply. I did uncheck the boxes for Feature Packs and >> Updates but I am under the impression now that all previously >> synchronized Feature Packs and Updates will be detected and that >> unchecking it only prevents future Feature Packs and Updates from being >> detected. Since I did the initial synchronization with Feature Packs and >> Updates checked, that's when the bulk of them are going to be >> synchronized. So I think at this point I can either uninstall WSUS which >> I don't want to do, or just live with it and decline any found Feature >> Packs/Updates as I come across them. >> >> "Lawrence Garvin (MVP)" <lawrence[ at ]news.postalias> wrote in message >> news:uqctS4IZJHA.684[ at ]TK2MSFTNGP04.phx.gbl... >>> <-> wrote in message news:%23q$BykGZJHA.3844[ at ]TK2MSFTNGP03.phx.gbl... >>>>I rebooted the server but still the machines want to download the >>>>feature packs. I've been declining them as I see them but I really need >>>>this to stop detecting because I only want critical and security updates >>>>and nothing else. Any ideas? >>> >>> There are three contradictory points in this post. Let's see if first we >>> can get a grasp on the actual situation. >>> >>> [1] You've stated the machines want to download Feature Packs. Do you >>> have an example of an entry from a WindowsUpdate.log showing any update >>> in "Features Packs" that's being detected and queued for download by the >>> WUA? If not, on what do you base your conclusion that "...the machines >>> want to download the feature packs..."? >>> >>> [2] You've stated that you've declined the updates. If you're declining >>> all of the updates in the "Feature Packs" classification -- why are you >>> even synchronizing "Feature Packs"? Furthermore, if you are declining >>> all of these updates, then it is *impossible* for a client system to >>> download any update in that classification. >>> >>> [3] =Detecting= is the normal behavior of a client based on the presence >>> of an undeclined update in WSUS. If you do not want a client to detect >>> whether an update is NEEDED; then you have two options: [a] Do not >>> synchronize the Product and/or Classification that contains the >>> update(s), or [b] Ensure the updates are declined (once declined, the >>> client will not detect the update as available). >>> >>> Conclusion: If you only want CRITICAL and SECURITY Updates, then you >>> should only be synchronizing CRITICAL and SECURITY updates! (Which, btw, >>> is the default configuration of a freshly installed WSUS Server.) >>> >>> >>> -- >>> Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP >>> Principal/CTO, Onsite Technology Solutions, Houston, Texas >>> Microsoft MVP - Software Distribution (2005-2009) >>> >>> MS WSUS Website: http://www.microsoft.com/wsus >>> My Websites: http://www.onsitechsolutions.com; >>> http://wsusinfo.onsitechsolutions.com >>> My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin >>> >> >> > >