I was hoping you would let me pretend this thread never existed :) I found the issue, the WSUS service was stopped :)
The only notice to this was accidentally hitting the homepage on the MMC snapin and seeing the warning! Sigh... Thanks for everything! jlc From: Miller Bonnie L. [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2008 11:32 AM To: NT System Admin Issues Subject: RE: WSUS Updates Hit regedit on the client and confirm all policies are applying as expected- HKLM\SOFTWARE\Policies\Microsoft\Windows\Windowsupdate If everything under that looks right, you might reset the local update cache. net stop wuauserv Delete everything under %systemroot%\softwaredistribution Net start wuauserv Then run Wuauclt /detectnow to force a detection cycle. From: Joseph L. Casale [mailto:[EMAIL PROTECTED] Sent: Friday, October 17, 2008 9:12 AM To: NT System Admin Issues Subject: RE: WSUS Updates Yea, the updates apply to the group in question. They are set to "Install" Thanks! jlc From: Eric Wittersheim [mailto:[EMAIL PROTECTED] Sent: Friday, October 17, 2008 10:03 AM To: NT System Admin Issues Subject: Re: WSUS Updates Jlc, Check the group membership of the computer in question. The computer will show that the updates are needed even if the updates are not approved for the group the computer is in. Eric On Fri, Oct 17, 2008 at 10:57 AM, Joseph L. Casale <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote: Bonnie, So in the windowsupdate.log I see: Found 0 updates and 41 categories in search; evaluated appl. rules of 553 out of 797 deployed entities But the report in the WSUS server shows it needs 6? Any ideas? Thanks! jlc From: Miller Bonnie L. [mailto:[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>] Sent: Thursday, October 16, 2008 12:59 PM To: NT System Admin Issues Subject: RE: WSUS Updates The only setting I see that I have different, and might cause what you are seeing, is the: No auto-restart with logged on users for scheduled automatic updates installations Enabled Ours is set to disabled. If a user has logged on when the re-scheduled installation starts, setting it to enabled will prevent the automatic reboot. If that doesn't quite sound like what you are seeing, start digging in logs. Some things you might check: Run gpresult on a machine you think should have updates and confirm the policy is applying correctly according to AD. Client machine event logs WSUS Server event logs WSUS server IIS logs (check for client connections) Clients' Windowsupdate.log files Reports on those updates in WSUS console -Bonnie From: Joseph L. Casale [mailto:[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>] Sent: Thursday, October 16, 2008 10:08 AM To: NT System Admin Issues Subject: RE: WSUS Updates Sorry for the delay, just wanted to see what happens after a small tweak. Everything is missing ~6 office updates that are set to install and some recent OS updates? Here is what I have: Allow Automatic Updates immediate installation Enabled Allow non-administrators to receive update notifications Enabled Allow signed content from intranet Microsoft update service location Enabled Automatic Updates detection Frequency Enabled Check For updates at the Following interval (hours): 6 Configure Automatic Updates Enabled Configure automatic updating: 4 - Auto download and schedule the install The following settings are only required and applicable if 4 is selected. Scheduled install day: 0 - Every day Scheduled install time: 11:00 Do not adjust default option to 'Install Updates and Shut Down' in Shut Down Windows dialog box Disabled Do not display 'Install Updates and Shut Down' option in Shut Down Windows dialog box Disabled Enable client-side targeting Enabled Target group name For this computer Desktops Enable recommended updates via Automatic Updates Enabled Enabling Windows Update Power Management to automatically wake up the system to install scheduled updates Enabled No auto-restart with logged on users for scheduled automatic updates installations Enabled Reschedule Automatic Updates scheduled installations Enabled Wait after system startup (minutes): 1 Specify intranet Microsoft update service location Enabled Set the intranet update service for detecting updates: http://server.domain.com:8530 Set the intranet statistics server: http://server.domain.com:8530 Thanks! jlc From: Miller Bonnie L. [mailto:[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>] Sent: Wednesday, October 15, 2008 12:32 PM To: NT System Admin Issues Subject: RE: WSUS Updates Non-admin notification shouldn't affect delayed update installation. In fact, we like to keep that disabled as I've found that if a non-admin can see the notification, they can also hide the updates by unchecking the boxes next to them. Can you list out which options you've set in the policy? I *think* what you said is that you have "Reschedule automatic updates..." enabled, with a wait time of 1. This works in conjunction with "configure automatic updates" enabled set to 4, with a scheduled installation time. If that is all set correctly, confirm that the workstations are getting the policy applied successfully. You might need to look at workstation event logs, and/or run GPResult. -Bonnie From: Joseph L. Casale [mailto:[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>] Sent: Tuesday, October 14, 2008 2:44 PM To: NT System Admin Issues Subject: WSUS Updates I have a WSUS 3.0 SP1 machine under Windows 2003 AD that isn't forcing delayed updates. I just noticed that the GPO had been set not to alert non admins of pending updates, but it was set to start install 1 minute after start if delayed? What am I missing? Thanks! jlc ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
