Interference
- About 2 years ago I installed WSUS 2.0 in a Win2003 domain with a mix of XP and 2000 workstations. Ten servers were all Win2003 R2. The system worked well.
I left for about a year and recently returned. During my absence the new folks did not keep the servers and workstations updated. Many were 50-60 updates behind. They also installed management software specfically ScriptLogic and Spiceworks.
Recently the update process has been a nightmare. I am now using WSUS 3.0. I have group policy to use option 4 for the workstations to download and install automatically. The servers use option 3 to download and manual install. Some of the workstations mainly Win2000 work the way they should. Many of the XP machines do not. They are set for option 4 but work like they have been set to option 3. Two of the servers on the otherhand are set to option 3 but work like they use option 4 restarting without warning.
The final problem was the update on an Exchange server prevented the server from booting. We could only boot by pulling the network cable and then we could not get the key Exchanges services to start.
It is my opinion that there is some serious and very damaging interference going on by the new management software being used. But I don't know what to look at or what to do about getting the update service to run like it used to.
I need some ideas.
Réponses
The log is from an XP workstation that is supposed to download and install the updates and restart automaticlly (#4) but doesn't
2009-11-25 10:39:28:688 1116 c80 Agent * Target group: (Unassigned Computers)
2009-11-25 10:39:28:704 1116 c80 AU # Approval type: Scheduled (Policy)
2009-11-25 10:39:28:704 1116 c80 AU # Scheduled install day/time: Every day at 12:002009-11-25 10:39:45:954 1116 1d0 Agent * Found 0 updates and 47 categories in search; evaluated appl. rules of 426 out of 918 deployed entities
2009-11-25 10:39:45:985 1116 f78 AU Setting AU scheduled install time to 2009-11-25 19:00:00
Okay, so we've confirmed that this client is set with AUOptions=4, a scheduled installation time of Every Day @ NOON, and has, in fact, set the next scheduled installation event for 11/25 at noon.
So now, show me on this same client system where an update was detected and downloaded and *NOT* installed at the scheduled installation event. Also include the log entries where the logged on user was prompted to install the updates, and successfully installed them.
Part of the issue here may be in your characterization of the problem.
You're reporting that the client problem is that it's not installing updates at the scheduled time.
My observation is that the problem is more likely the client is not *DETECTING* updates because it's not assigned a target group with any approved updates.
Also, the command sequence explicitly requested the command wuauclt /resetauthorization /detectnow and I don't see any evidence in this logfile that the /resetauthorization parameter was actually used (which would be evidenced by the existence of a log entry "Initializing simple targeting cookie...").
In fact.. now that I look a bit harder... I don't even see a client call to the SimpleAuthWebService !!!
And.. oh... btw... not being able to download content at the WSUS Server -- that'll negatively impact a client's ability to detect and install updates as well!
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
My Blog: http://onsitechsolutions.spaces.live.com- Marqué comme réponseMyrt Webb mercredi 25 novembre 2009 20:31
Toutes les réponses
I am now using WSUS 3.0. I have group policy to use option 4 for the workstations to download and install automatically. The servers use option 3 to download and manual install. Some of the workstations mainly Win2000 work the way they should. Many of the XP machines do not. They are set for option 4 but work like they have been set to option 3. Two of the servers on the otherhand are set to option 3 but work like they use option 4 restarting without warning.
So, the first two steps here would be to:
[1] Determine if the WUAgent is actually logging the expected configuration, and
[2] Determine if your policy is actually being applied.
Please do the following on one or more of these WinXP and Win2003 systems:
1. Record the system time.
2. Restart the Automatic Updates service. (net stop/start wuauserv)
3. Force a detection. (wuauclt /resetauthorization /detectnow)
4. Wiat 30 minutes.
5. Post the log entries from the WindowsUpdate.log starting at the time recorded in Step #1.The final problem was the update on an Exchange server prevented the server from booting. We could only boot by pulling the network cable and then we could not get the key Exchanges services to start.
There is no known update scenario that prevents an Exchange server from booting. I would suggest investigating one or more of the other utilities installed: ScriptLogic or SpiceWorks, as having contributed something causing one or more of the Exchange Server services to have hung on shutdown -- most likely not even those products, but something in their implementation or specific uses that is not appropriate for an Exchange Server.It is my opinion that there is some serious and very damaging interference going on by the new management software being used. But I don't know what to look at or what to do about getting the update service to run like it used to.
It seems to me that the simplest diagnostic would be to uninstall the ScriptLogic and uninstall the SpiceWorks, and then perform the standard Client Diagnostics to ensure the client systems are configured as desired, and then review the WindowsUpdate.log to confirm proper operation (which is pretty much what I'm guiding you through with the above procedure).
Incidentally, the previous thread concerning XP machines ostensibly misreporting, and this behavior here, could be related. I suggest we handle them in the same thread. Knowing what I now know from this thread, I'd say there's a high probability that something else installed those updates and the WUAgent was never able to report them as "Installed" because the WUAgent did not install them (although, eventually, the WUAgent should report them as "Installed/Not Applicable" if that is the case).
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
My Blog: http://onsitechsolutions.spaces.live.comAfter doing what you suggested above I copied the log and it is below.
The log is from an XP workstation that is supposed to download and install the updates and restart automaticlly (#4) but doesn't.
2009-11-25 10:38:29:875 1116 43c AU ########### AU: Uninitializing Automatic Updates ###########
2009-11-25 10:38:30:875 1116 43c Service *********
2009-11-25 10:38:30:875 1116 43c Service ** END ** Service: Service exit [Exit code = 0x240001]
2009-11-25 10:38:30:875 1116 43c Service *************
2009-11-25 10:38:43:391 1116 354 Misc =========== Logging initialized (build: 7.4.7600.226, tz: -0700) ===========
2009-11-25 10:38:43:391 1116 354 Misc = Process: C:\WINDOWS\System32\svchost.exe
2009-11-25 10:38:43:391 1116 354 Misc = Module: C:\WINDOWS\system32\wuaueng.dll
2009-11-25 10:38:43:391 1116 354 Service *************
2009-11-25 10:38:43:391 1116 354 Service ** START ** Service: Service startup
2009-11-25 10:38:43:407 1116 354 Service *********
2009-11-25 10:38:43:407 1116 354 Agent * WU client version 7.4.7600.226
2009-11-25 10:38:43:407 1116 354 Agent * Base directory: C:\WINDOWS\SoftwareDistribution
2009-11-25 10:38:43:407 1116 354 Agent * Access type: No proxy
2009-11-25 10:38:43:407 1116 354 Agent * Network state: Connected
2009-11-25 10:39:28:688 1116 c80 Agent *********** Agent: Initializing Windows Update Agent ***********
2009-11-25 10:39:28:688 1116 c80 Agent *********** Agent: Initializing global settings cache ***********
2009-11-25 10:39:28:688 1116 c80 Agent * WSUS server: http://nvas01:8530
2009-11-25 10:39:28:688 1116 c80 Agent * WSUS status server: http://nvas01:8530
2009-11-25 10:39:28:688 1116 c80 Agent * Target group: (Unassigned Computers)
2009-11-25 10:39:28:688 1116 c80 Agent * Windows Update access disabled: No
2009-11-25 10:39:28:704 1116 c80 DnldMgr Download manager restoring 0 downloads
2009-11-25 10:39:28:704 1116 c80 AU ########### AU: Initializing Automatic Updates ###########
2009-11-25 10:39:28:704 1116 c80 AU AU setting next sqm report timeout to 2009-11-25 17:39:28
2009-11-25 10:39:28:704 1116 c80 AU # WSUS server: http://nvas01:8530
2009-11-25 10:39:28:704 1116 c80 AU # Detection frequency: 2
2009-11-25 10:39:28:704 1116 c80 AU # Approval type: Scheduled (Policy)
2009-11-25 10:39:28:704 1116 c80 AU # Scheduled install day/time: Every day at 12:00
2009-11-25 10:39:28:704 1116 c80 AU # Auto-install minor updates: Yes (Policy)
2009-11-25 10:39:28:704 1116 c80 AU # Will interact with non-admins (Non-admins are elevated (Policy))
2009-11-25 10:39:28:704 1116 c80 AU Setting AU scheduled install time to 2009-11-25 19:00:00
2009-11-25 10:39:28:704 1116 c80 AU Initializing featured updates
2009-11-25 10:39:28:704 1116 c80 AU Found 0 cached featured updates
2009-11-25 10:39:28:704 1116 c80 AU AU finished delayed initialization
2009-11-25 10:39:28:704 1116 c80 AU Triggering AU detection through DetectNow API
2009-11-25 10:39:28:704 1116 c80 AU Triggering Online detection (non-interactive)
2009-11-25 10:39:29:329 1116 354 Report *********** Report: Initializing static reporting data ***********
2009-11-25 10:39:29:329 1116 354 Report * OS Version = 5.1.2600.3.0.65792
2009-11-25 10:39:29:360 1116 354 Report * Computer Brand = Dell Inc.
2009-11-25 10:39:29:360 1116 354 Report * Computer Model = OptiPlex 745
2009-11-25 10:39:29:360 1116 354 Report * Bios Revision = 2.3.1
2009-11-25 10:39:29:360 1116 354 Report * Bios Name = Phoenix ROM BIOS PLUS Version 1.10 2.3.1
2009-11-25 10:39:29:360 1116 354 Report * Bios Release Date = 2007-05-21T00:00:00
2009-11-25 10:39:29:360 1116 354 Report * Locale ID = 1033
2009-11-25 10:39:29:423 1116 354 AU #############
2009-11-25 10:39:29:423 1116 354 AU ## START ## AU: Search for updates
2009-11-25 10:39:29:423 1116 354 AU #########
2009-11-25 10:39:29:423 1116 354 AU <<## SUBMITTED ## AU: Search for updates [CallId = {FAD6F8D7-167E-4841-A237-F51919600FB9}]
2009-11-25 10:39:30:188 1116 1d0 Agent *************
2009-11-25 10:39:30:188 1116 1d0 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2009-11-25 10:39:30:188 1116 1d0 Agent *********
2009-11-25 10:39:30:188 1116 1d0 Agent * Online = Yes; Ignore download priority = No
2009-11-25 10:39:30:188 1116 1d0 Agent * Criteria = "IsHidden=0 and IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and IsAssigned=1 or IsHidden=0 and IsInstalled=1 and DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and IsAssigned=1 and RebootRequired=1"
2009-11-25 10:39:30:188 1116 1d0 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2009-11-25 10:39:30:188 1116 1d0 Agent * Search Scope = {Machine}
2009-11-25 10:39:30:188 1116 1d0 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2009-11-25 10:39:30:235 1116 1d0 Misc Microsoft signed: Yes
2009-11-25 10:39:30:251 1116 1d0 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
2009-11-25 10:39:30:251 1116 1d0 Misc Microsoft signed: Yes
2009-11-25 10:39:30:282 1116 1d0 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab:
2009-11-25 10:39:30:282 1116 1d0 Misc Microsoft signed: Yes
2009-11-25 10:39:30:298 1116 1d0 Setup *********** Setup: Checking whether self-update is required ***********
2009-11-25 10:39:30:298 1116 1d0 Setup * Inf file: C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf
2009-11-25 10:39:30:313 1116 1d0 Setup Update NOT required for C:\WINDOWS\system32\cdm.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-25 10:39:30:313 1116 1d0 Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-25 10:39:30:313 1116 1d0 Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-25 10:39:30:313 1116 1d0 Setup Update NOT required for C:\WINDOWS\system32\wuauclt.exe: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-25 10:39:30:313 1116 1d0 Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-25 10:39:30:329 1116 1d0 Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-25 10:39:30:329 1116 1d0 Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-25 10:39:30:329 1116 1d0 Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-25 10:39:30:329 1116 1d0 Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-25 10:39:30:329 1116 1d0 Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-25 10:39:30:345 1116 1d0 Setup Update NOT required for C:\WINDOWS\system32\wups.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-25 10:39:30:345 1116 1d0 Setup Update NOT required for C:\WINDOWS\system32\wups2.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-25 10:39:30:360 1116 1d0 Setup Update NOT required for C:\WINDOWS\system32\wuweb.dll: target version = 7.4.7600.226, required version = 7.4.7600.226
2009-11-25 10:39:30:360 1116 1d0 Setup * IsUpdateRequired = No
2009-11-25 10:39:33:860 1116 1d0 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2009-11-25 10:39:33:860 1116 1d0 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://nvas01:8530/ClientWebService/client.asmx
2009-11-25 10:39:37:063 1116 1d0 PT +++++++++++ PT: Synchronizing extended update info +++++++++++
2009-11-25 10:39:37:063 1116 1d0 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://nvas01:8530/ClientWebService/client.asmx
2009-11-25 10:39:45:954 1116 1d0 Agent * Found 0 updates and 47 categories in search; evaluated appl. rules of 426 out of 918 deployed entities
2009-11-25 10:39:45:970 1116 1d0 Agent *********
2009-11-25 10:39:45:970 1116 1d0 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2009-11-25 10:39:45:970 1116 1d0 Agent *************
2009-11-25 10:39:45:985 1116 f78 AU >>## RESUMED ## AU: Search for updates [CallId = {FAD6F8D7-167E-4841-A237-F51919600FB9}]
2009-11-25 10:39:45:985 1116 f78 AU # 0 updates detected
2009-11-25 10:39:45:985 1116 f78 AU #########
2009-11-25 10:39:45:985 1116 f78 AU ## END ## AU: Search for updates [CallId = {FAD6F8D7-167E-4841-A237-F51919600FB9}]
2009-11-25 10:39:45:985 1116 f78 AU #############
2009-11-25 10:39:45:985 1116 f78 AU Featured notifications is disabled.
2009-11-25 10:39:45:985 1116 f78 AU AU setting next detection timeout to 2009-11-25 19:25:27
2009-11-25 10:39:45:985 1116 f78 AU Setting AU scheduled install time to 2009-11-25 19:00:00
2009-11-25 10:39:50:970 1116 1d0 Report REPORT EVENT: {7D521579-1DA6-4B28-9624-797D4E8F02DB} 2009-11-25 10:39:45:970-0700 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates.
2009-11-25 10:39:50:970 1116 1d0 Report REPORT EVENT: {D57755FC-A565-4B4E-8172-FC35FE88F944} 2009-11-25 10:39:45:970-0700 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
The log is from an XP workstation that is supposed to download and install the updates and restart automaticlly (#4) but doesn't
2009-11-25 10:39:28:688 1116 c80 Agent * Target group: (Unassigned Computers)
2009-11-25 10:39:28:704 1116 c80 AU # Approval type: Scheduled (Policy)
2009-11-25 10:39:28:704 1116 c80 AU # Scheduled install day/time: Every day at 12:002009-11-25 10:39:45:954 1116 1d0 Agent * Found 0 updates and 47 categories in search; evaluated appl. rules of 426 out of 918 deployed entities
2009-11-25 10:39:45:985 1116 f78 AU Setting AU scheduled install time to 2009-11-25 19:00:00
Okay, so we've confirmed that this client is set with AUOptions=4, a scheduled installation time of Every Day @ NOON, and has, in fact, set the next scheduled installation event for 11/25 at noon.
So now, show me on this same client system where an update was detected and downloaded and *NOT* installed at the scheduled installation event. Also include the log entries where the logged on user was prompted to install the updates, and successfully installed them.
Part of the issue here may be in your characterization of the problem.
You're reporting that the client problem is that it's not installing updates at the scheduled time.
My observation is that the problem is more likely the client is not *DETECTING* updates because it's not assigned a target group with any approved updates.
Also, the command sequence explicitly requested the command wuauclt /resetauthorization /detectnow and I don't see any evidence in this logfile that the /resetauthorization parameter was actually used (which would be evidenced by the existence of a log entry "Initializing simple targeting cookie...").
In fact.. now that I look a bit harder... I don't even see a client call to the SimpleAuthWebService !!!
And.. oh... btw... not being able to download content at the WSUS Server -- that'll negatively impact a client's ability to detect and install updates as well!
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
My Blog: http://onsitechsolutions.spaces.live.com- Marqué comme réponseMyrt Webb mercredi 25 novembre 2009 20:31
- The target group the workstation is suppose to be in is "workstations" not "unassigned"
I did do the resetauthorization. I will try again. I need to stop this thread and work on the download issue.
