Question... "Craig" <craigNOSPAMvandergriff[ at ]lllow.com> 6/8/2007 12:55:37 PM Hi there, I have been using WSUS 3.0 for a while now and it is kicking some serious butt! I do have an over zealous user that will do the MS update manually and it will show up a bunch of updates. Is this because they have been released 'today' and the WSUS hasn't updated because they only 'push' updates once a week? It is usually Tuesday, as it has been doing unless there is an emergency fix/patch/update that 'must' be run. What is the schedule for updates that I need to be looking for? Do I need to have all users doing manual updates on top of the WSUS action? (Doesn't that kinda defeat the purpose?) Any input will be appreciated. Cheers Craig

Re: Question... "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/8/2007 10:58:50 PM "Craig" <craigNOSPAMvandergriff[ at ]lllow.com> wrote in message news:OsGQRxcqHHA.1288[ at ]TK2MSFTNGP06.phx.gbl... [Quoted Text] > I have been using WSUS 3.0 for a while now and it is kicking some serious > butt! I do have an over zealous user that will do the MS update manually > and it will show up a bunch of updates. Is this because they have been > released 'today' and the WSUS hasn't updated because they only 'push' > updates once a week? Nope.. WSUS doesn't "push" anything. The Windows Update Agent on the client system polls the WSUS server every 22 hours (by default) to determine if any updates are available. If they are, it downloads them, and then installs them according to the policy you have configured. So.. what is happening? There are a couple of possibilities: [1] Your "over zealous user" (who obviously has admin privileges, and maybe should not), might be browsing to Microsoft Update and installing the updates from the website, which would be subsequently reported to the WSUS server as "Installed", because of the existing WSUS policies designating the WSUS server as the "reporting server". [2] Your "over zealous user" might be interactively initiating the installation of the updates that have been detected and downloaded by that client system (subsequent to your approval for installation), but sitting in the queue for a scheduled installation (based on what you've written above), which may actually only be a =weekly= event. > It is usually Tuesday, as it has been doing unless there is an emergency > fix/patch/update that 'must' be run. Microsoft releases updates on the 2nd Tuesday of every month. Do you have auto-approval rules configured? Or are you implying that Tuesday is the day of the week that you've scheduled for installation? -- 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://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....

Re: Question... "Les Connor [SBS MVP]" <les.connor[ at ]DEL.cfive.ca> 6/9/2007 2:17:42 PM Excuse me for butting in ... SBS Update Services sets the client polling interval at 1 hour. I have one network where I changed that to the WSUS default because of the now resolved svchost.exe issues, and I'd like to change the interval back to 1 hour but can't remember where to configure that ;-/. -- Les Connor [SBS MVP] "Lawrence Garvin (MVP)" <onsitech[ at ]community.nospam> wrote in message news:utObVCiqHHA.4180[ at ]TK2MSFTNGP04.phx.gbl... [Quoted Text] > "Craig" <craigNOSPAMvandergriff[ at ]lllow.com> wrote in message > news:OsGQRxcqHHA.1288[ at ]TK2MSFTNGP06.phx.gbl... > >> I have been using WSUS 3.0 for a while now and it is kicking some serious >> butt! I do have an over zealous user that will do the MS update manually >> and it will show up a bunch of updates. Is this because they have been >> released 'today' and the WSUS hasn't updated because they only 'push' >> updates once a week? > > Nope.. WSUS doesn't "push" anything. The Windows Update Agent on the > client system polls the WSUS server every 22 hours (by default) to > determine if any updates are available. If they are, it downloads them, > and then installs them according to the policy you have configured. > > So.. what is happening? There are a couple of possibilities: > [1] Your "over zealous user" (who obviously has admin privileges, and > maybe should not), might be browsing to Microsoft Update and installing > the updates from the website, which would be subsequently reported to the > WSUS server as "Installed", because of the existing WSUS policies > designating the WSUS server as the "reporting server". > > [2] Your "over zealous user" might be interactively initiating the > installation of the updates that have been detected and downloaded by that > client system (subsequent to your approval for installation), but sitting > in the queue for a scheduled installation (based on what you've written > above), which may actually only be a =weekly= event. > >> It is usually Tuesday, as it has been doing unless there is an emergency >> fix/patch/update that 'must' be run. > > Microsoft releases updates on the 2nd Tuesday of every month. Do you have > auto-approval rules configured? > > Or are you implying that Tuesday is the day of the week that you've > scheduled for installation? > > -- > 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://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx > > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com > .... > > >

Re: Question... "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/9/2007 9:07:35 PM "Les Connor [SBS MVP]" <les.connor[ at ]DEL.cfive.ca> wrote in message news:20C92151-D0F4-4483-B3DA-B88D95DF7833[ at ]microsoft.com... [Quoted Text] > Excuse me for butting in ... > > SBS Update Services sets the client polling interval at 1 hour. Really!? I wasn't aware of that. I'll have to check that. But, I'd say if that's true, then the SBS team that made that mod ought to have their processes and procedures examined. Why would they do something that the product team, support services, and MVPs had been recommending *against* doing, for the year before SBS2003 R2 was released? > I have one network where I changed that to the WSUS default because of the > now resolved svchost.exe issues, and I'd like to change the interval back > to 1 hour but can't remember where to configure that ;-/. You configure it in the policy setting "Automatic Updates detection frequency", but don't. Unless you're running WSUS v3 and you've set your =server= to sync with microsoft more than a couple of times a day, it serve no useful purpose at all to increase the client detection interval, except to unnecessarily increase the load on your WSUS server. -- 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://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....

Re: Question... Harry Johnston <harry[ at ]scms.waikato.ac.nz> 6/10/2007 9:38:33 PM Craig wrote: [Quoted Text] > I have been using WSUS 3.0 for a while now and it is kicking some serious > butt! I do have an over zealous user that will do the MS update manually > and it will show up a bunch of updates. Not all updates released to MU are also released to WSUS, and some updates are released to WSUS later than to MU. However in almost all cases the "missing" updates aren't likely to matter. Harry.

Re: Question... "Les Connor [SBS MVP]" <les.connor[ at ]DEL.cfive.ca> 6/11/2007 7:54:46 PM I don't remember the reasoning, allthough I think I did get an explanation at some point. -- Les Connor [SBS MVP] "Lawrence Garvin (MVP)" <onsitech[ at ]community.nospam> wrote in message news:uajs3otqHHA.4520[ at ]TK2MSFTNGP04.phx.gbl... [Quoted Text] > "Les Connor [SBS MVP]" <les.connor[ at ]DEL.cfive.ca> wrote in message > news:20C92151-D0F4-4483-B3DA-B88D95DF7833[ at ]microsoft.com... >> Excuse me for butting in ... >> >> SBS Update Services sets the client polling interval at 1 hour. > > Really!? I wasn't aware of that. I'll have to check that. > > But, I'd say if that's true, then the SBS team that made that mod ought to > have their processes and procedures examined. > > Why would they do something that the product team, support services, and > MVPs had been recommending *against* doing, for the year before SBS2003 R2 > was released? > >> I have one network where I changed that to the WSUS default because of >> the now resolved svchost.exe issues, and I'd like to change the interval >> back to 1 hour but can't remember where to configure that ;-/. > > > You configure it in the policy setting "Automatic Updates detection > frequency", but don't. > > Unless you're running WSUS v3 and you've set your =server= to sync with > microsoft more than a couple of times a day, it serve no useful purpose at > all to increase the client detection interval, except to unnecessarily > increase the load on your WSUS server. > > -- > 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://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx > > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com > .... >

Re: Question... "Matthew Wetmore \(MSFT\)" <mattwe[ at ]online.microsoft.com> 6/13/2007 8:38:43 PM Clients polling every hour means a shorter turn-around from when the admin approves the update. Polling frequency of the server to WU is not as relevant, unless you're doing auto-approval rules. Frequent polling periods for both server and client, plus auto-approvals are all part of an effort to minimize the time from release of an update to install on the client. -- Matthew Wetmore Developer, WSUS (Windows Server Update Services) 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 "Les Connor [SBS MVP]" <les.connor[ at ]DEL.cfive.ca> wrote in message news:DBE5A334-5E21-42D5-9227-C50B970D5D67[ at ]microsoft.com... [Quoted Text] >I don't remember the reasoning, allthough I think I did get an explanation >at some point. > > -- > Les Connor [SBS MVP] > > > "Lawrence Garvin (MVP)" <onsitech[ at ]community.nospam> wrote in message > news:uajs3otqHHA.4520[ at ]TK2MSFTNGP04.phx.gbl... >> "Les Connor [SBS MVP]" <les.connor[ at ]DEL.cfive.ca> wrote in message >> news:20C92151-D0F4-4483-B3DA-B88D95DF7833[ at ]microsoft.com... >>> Excuse me for butting in ... >>> >>> SBS Update Services sets the client polling interval at 1 hour. >> >> Really!? I wasn't aware of that. I'll have to check that. >> >> But, I'd say if that's true, then the SBS team that made that mod ought >> to have their processes and procedures examined. >> >> Why would they do something that the product team, support services, and >> MVPs had been recommending *against* doing, for the year before SBS2003 >> R2 was released? >> >>> I have one network where I changed that to the WSUS default because of >>> the now resolved svchost.exe issues, and I'd like to change the interval >>> back to 1 hour but can't remember where to configure that ;-/. >> >> >> You configure it in the policy setting "Automatic Updates detection >> frequency", but don't. >> >> Unless you're running WSUS v3 and you've set your =server= to sync with >> microsoft more than a couple of times a day, it serve no useful purpose >> at all to increase the client detection interval, except to unnecessarily >> increase the load on your WSUS server. >> >> -- >> 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://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx >> >> And, almost everything else is at >> http://wsusinfo.onsitechsolutions.com >> .... >> >

Re: Question... "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/14/2007 2:44:53 AM "Matthew Wetmore (MSFT)" <mattwe[ at ]online.microsoft.com> wrote in message news:O682WrfrHHA.884[ at ]TK2MSFTNGP02.phx.gbl... [Quoted Text] >>>> SBS Update Services sets the client polling interval at 1 hour. >>> Why would they do something that the product team, support services, and >>> MVPs had been recommending *against* doing, for the year before SBS2003 >>> R2 was released? >>I don't remember the reasoning, allthough I think I did get an explanation >>at some point. > Clients polling every hour means a shorter turn-around from when the admin > approves the update. > Polling frequency of the server to WU is not as relevant, unless you're > doing auto-approval rules. > > Frequent polling periods for both server and client, plus auto-approvals > are all part of an effort to minimize the time from release of an update > to install on the client. Which is really a moot point in the WSUS 2 SP1 environment, given that a client can only perform scheduled updates once a day anyway. It also introduces the database maintenance complications with regards to the tbEventInstance table, although statistically speaking, that's probably irrelevant also, since an SBS2003 installation wouldn't have more than 75 serviced client systems anyway. 75 client systems at an hour per day is the equivalent load to 1650 clients per server once per day. Well within the documented performance tolerances of WSUS 2 SP1 on WMSDE, though I'd really suggest Premium Edition with SQL Server 2000 Standard Edition would be a preferable environment to support that kind of client load. -- 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://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx And, almost everything else is at http://wsusinfo.onsitechsolutions.com .....

Re: Question... "Craig" <craigNOSPAMvandergriff[ at ]lllow.com> 6/14/2007 7:24:52 PM Hi there, Thanx for all the info, guys. I have been watching and I think I have a handle on it. I came in today and had 26 new updates to review... filtered through what I needed and all is well. Thanx again. Cheers Craig