WUS Reporting Slow to Update "Tom" <mqtesting[ at ]gmail.com> 6/13/2007 1:46:39 PM The reporting is very nice on WUS 3.0 but the issue I'm having is that the reports take a long time to update. For example we run the report and let's say it shows 2 computer failing to update so we manuallly update these PC's by running wuauclt.exe /resetauthorization /detectnow and it updates but the WUS server reports still show they need the update even after several hours have gone by. Is there a way to force a query update on the WUS server or force the client to tell WUS it has updated so the report is current/correct?

Re: WUS Reporting Slow to Update "Winfried Sonntag [MVP]" <Winfried.Sonntag[ at ]gmx.de> 6/13/2007 7:46:19 PM Tom schrieb: [Quoted Text] > Is there a way to force a query update on the WUS server or force the client > to tell WUS it has updated so the report is current/correct? wuauclt /detectnow 20 - 30 times after update. Winfried -- http://www.microsoft.com/germany/windowsserver2003/technologien/updateservices/default.mspx http://www.wsuswiki.com/Home

Re: WUS Reporting Slow to Update "Tom" <mqtesting[ at ]gmail.com> 6/13/2007 10:28:59 PM Nope that does not work. As I mentioned in my post I tried the wuauclt /detectnow and the reports in WUS 3.0 do not reflect any changes until the next day or at least more than 8hrs. There is a tool such as wuauclt /r or wuauclt /reportnow this sometimes works but not all the time. I found a script that kind of works but still working on getting the bugs worked out. Any one else have an answer on this? "Winfried Sonntag [MVP]" <Winfried.Sonntag[ at ]gmx.de> wrote in message news:x1nf8otfj39m.dlg[ at ]ID-163725.user.individual.de... [Quoted Text] > Tom schrieb: > >> Is there a way to force a query update on the WUS server or force the >> client >> to tell WUS it has updated so the report is current/correct? > > wuauclt /detectnow 20 - 30 times after update. > > Winfried > -- > http://www.microsoft.com/germany/windowsserver2003/technologien/updateservices/default.mspx > http://www.wsuswiki.com/Home

Re: WUS Reporting Slow to Update "Lawrence Garvin \(MVP\)" <onsitech[ at ]community.nospam> 6/13/2007 10:46:45 PM "Tom" <mqtesting[ at ]gmail.com> wrote in message news:e7nuYEcrHHA.3924[ at ]TK2MSFTNGP04.phx.gbl... [Quoted Text] > The reporting is very nice on WUS 3.0 but the issue I'm having is that the > reports take a long time to update. > > For example we run the report and let's say it shows 2 computer failing to > update so we manuallly update these PC's by running wuauclt.exe > /resetauthorization /detectnow and it updates but the WUS server reports > still show they need the update even after several hours have gone by. Well, the first key question is when the update actually /installs/. Are you installing these updates interactively after running the forced detection, or are the updates being installed during a scheduled installation event? If using the scheduled installation event, and the scheduled installation isn't for several hours after the detection, that would certainly explain the perceived delay in reporting updates. -- 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: WUS Reporting Slow to Update "Cecils\(MSFT\)" <cecils[ at ]online.microsoft.com> 6/13/2007 10:56:05 PM Wuauclt /detectnow /reportnow Will do a detection and send the events to the server. If it doesn't work, then we should look at the log. /r doesn't work anymore. -- 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 "Tom" <mqtesting[ at ]gmail.com> wrote in message news:u3M%23TogrHHA.4764[ at ]TK2MSFTNGP06.phx.gbl... [Quoted Text] > Nope that does not work. As I mentioned in my post I tried the wuauclt > /detectnow and the reports in WUS 3.0 do not reflect any changes until the > next day or at least more than 8hrs. > > There is a tool such as wuauclt /r or wuauclt /reportnow this sometimes > works but not all the time. I found a script that kind of works but still > working on getting the bugs worked out. > > Any one else have an answer on this? > > > "Winfried Sonntag [MVP]" <Winfried.Sonntag[ at ]gmx.de> wrote in message > news:x1nf8otfj39m.dlg[ at ]ID-163725.user.individual.de... >> Tom schrieb: >> >>> Is there a way to force a query update on the WUS server or force the >>> client >>> to tell WUS it has updated so the report is current/correct? >> >> wuauclt /detectnow 20 - 30 times after update. >> >> Winfried >> -- >> http://www.microsoft.com/germany/windowsserver2003/technologien/updateservices/default.mspx >> http://www.wsuswiki.com/Home > >

Re: WUS Reporting Slow to Update "Tom" <mqtesting[ at ]gmail.com> 6/14/2007 1:59:25 PM Thanks for the responses; I greatly appreciate them. The issue is after a forced install or manual install on the client/server the reporting doesn't consistently get updated. Often times I'm stuck waiting for several hours. I found a script online that uses tail.exe from W2K3 Resource Kit and this script seems to update the status of the client and updates the WUS reporting which will solve the issue for now. Thanks again for your time. "Lawrence Garvin (MVP)" <onsitech[ at ]community.nospam> wrote in message news:ehzP5ygrHHA.1380[ at ]TK2MSFTNGP04.phx.gbl... [Quoted Text] > "Tom" <mqtesting[ at ]gmail.com> wrote in message > news:e7nuYEcrHHA.3924[ at ]TK2MSFTNGP04.phx.gbl... >> The reporting is very nice on WUS 3.0 but the issue I'm having is that >> the reports take a long time to update. >> >> For example we run the report and let's say it shows 2 computer failing >> to update so we manuallly update these PC's by running wuauclt.exe >> /resetauthorization /detectnow and it updates but the WUS server reports >> still show they need the update even after several hours have gone by. > > Well, the first key question is when the update actually /installs/. > > Are you installing these updates interactively after running the forced > detection, or are the updates being installed during a scheduled > installation event? > > If using the scheduled installation event, and the scheduled installation > isn't for several hours after the detection, that would certainly explain > the perceived delay in reporting updates. > > -- > 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 > .... > >