Wsus issues...
-
27 Juni 2012 14:17Hi everyone, i have a problem with my WSUS Server, all my windows 7 and vista cant find the updates from Wsus, but in the screen of my Wsus Software they appear like they already updated, even with the actual date.....i have Wsus 3.0 SP2 installed on a W2k3 32 Bits. So whats is wrong with my WSUS ? The XP machines works fine...thanks for the help.
Semua Balasan
-
27 Juni 2012 15:10
Hi everyone, i have a problem with my WSUS Server, all my windows 7 and vista cant find the updates from Wsus, but in the screen of my Wsus Software they appear like they already updated, even with the actual date.....i have Wsus 3.0 SP2 installed on a W2k3 32 Bits. So whats is wrong with my WSUS ? The XP machines works fine...thanks for the help.
Check out the new Diagnostic tool for WSUS Agent from Solarwinds. NOTE : I do NOT work for Solarwinds.
Running this on one of the Windows 7 or Widows Vista clients should help.
- Diedit oleh antwesor 06 Juli 2012 15:27
-
27 Juni 2012 15:40
U really DONT ? :P ahaha thanks i run this tool and i get this msg error:
content | Error: Forbidden | Incorrect proxy client configuration - use settings tab to test proxy configuration settings; may also be caused by misconfigured SSL implemetation or access rights on WSUS Server
I dont have a proxy configuration or any kind of proxy...so what could it be the problem?
-
27 Juni 2012 15:54
U really DONT ? :P ahaha thanks i run this tool and i get this msg error:
content | Error: Forbidden | Incorrect proxy client configuration - use settings tab to test proxy configuration settings; may also be caused by misconfigured SSL implemetation or access rights on WSUS Server
I dont have a proxy configuration or any kind of proxy...so what could it be the problem?
I am having the same issue, there are five updates showing as needed and all are approved for install but the client will not download them from the server. The Solarwinds tool is showing the same error message as above. -
01 Juli 2012 20:32Moderator
If the diagnostic tool reports that there is a proxy error, then that means your client systems
- ARE being routed through a proxy and that proxy is blocking access, or
- they're configured to use a proxy server and that proxy server doesn't exist, or
- they're not being routed through a proxy and they NEED to be routed through that proxy correctly.
The first thing to determine is whether the client is configured to use a proxy server (and maybe should not be).
On Windows Vista and Windows 7 systems, run the command netsh winhttp show proxy and post the results here.
[Added 7/17] -or-, if the diagnostic tool reports the proxy error ONLY on the Content resource, then that would indicate that the Directory Browsing role service of the Web Server role on the WSUS server has been enabled. The Directory Browsing role service is not required for a WSUS server, and it should be disabled. If you cannot disable it due to other applications, then you'll have to make accomodations for this proxy error, which is normal in that case, as the /Content v-dir is returning an HTTP 403.14 (Directory Browsing not permitted) error when the Diagnostic Tool tests for the existence of that v-dir.
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Product Manager, SolarWinds
Microsoft MVP - Software Distribution (2005-2012)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin- Ditandai sebagai Jawaban oleh Clarence ZhangModerator 10 Juli 2012 2:25
- Diedit oleh Lawrence GarvinMVP, Moderator 17 Juli 2012 17:51 Added exception concerning Directory Browsing role service
-
05 Juli 2012 16:39
I did get the same error with the client tool and netsh result from client device is
C:>netsh winhttp show proxy
Current WinHTTP proxy settings:
Direct access (no proxy server).
I have checked the IE settings also. Is there something else we need to check?
Thanks
Note: I dont see any issues on this client device for checking or downloading updates from the wsus. But the tool returns this error.(i am evaluating this tool to use it on other clients). Is this something i can ignore?
- Diedit oleh Marimuthu Ramakrishnan 05 Juli 2012 16:45
-
05 Juli 2012 20:28Moderator
So, I make three observations:
- Clients cannot communicate with the WSUS server.
- The Diagnostic Tool says there is an incorrect proxy configuration.
- The netsh winhttp tells us there is no proxy configuration.
That pretty much leaves us with two possibilities:
- There should be a proxy server (there IS a proxy server) and it's not configured
- The URL for the WSUS server is not correct.
The real question now is to inspect what one of these Windows 7 systems is actually doing. Please do the following:
- Record the system time.
- Reboot the machine.
- After restart, run this command: wuauclt /resetauthorization /detectnow.
- Wait 30 minutes.
- Post the entries from the WindowsUpdate.log starting at the time recorded in Step #1.
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Product Manager, SolarWinds
Microsoft MVP - Software Distribution (2005-2012)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin -
06 Juli 2012 18:10
Thanks for the quick response.
================WINDOWSUPDATE.LOG====================================================
Reboot time : 13:17
executed command @13:19
wuauclt /resetauthorization /detectnow
collected logs @ 13:49
2012-07-06 13:19:07:531 1204 13d4 Misc =========== Logging initialized (build: 7.6.7600.256, tz: -0400) ===========
2012-07-06 13:19:08:509 1204 13d4 Misc = Process: C:\Windows\system32\svchost.exe
2012-07-06 13:19:08:583 1204 13d4 Misc = Module: c:\windows\system32\wuaueng.dll
2012-07-06 13:19:07:531 1204 13d4 Service *************
2012-07-06 13:19:11:078 1204 13d4 Service ** START ** Service: Service startup
2012-07-06 13:19:13:910 1204 13d4 Service *********
2012-07-06 13:19:16:901 1204 13d4 Agent * WU client version 7.6.7600.256
2012-07-06 13:19:17:021 1204 13d4 Agent * Base directory: C:\Windows\SoftwareDistribution
2012-07-06 13:19:17:072 1204 13d4 Agent * Access type: No proxy
2012-07-06 13:19:17:725 1204 13d4 Agent * Network state: Connected
2012-07-06 13:19:18:855 1204 664 Report CWERReporter::Init succeeded
2012-07-06 13:19:18:855 1204 664 Agent *********** Agent: Initializing Windows Update Agent ***********
2012-07-06 13:19:18:868 1204 664 Agent *********** Agent: Initializing global settings cache ***********
2012-07-06 13:19:18:868 1204 664 Agent * WSUS server: http://10.20.2.1:80
2012-07-06 13:19:18:868 1204 664 Agent * WSUS status server: http://10.20.2.1:80
2012-07-06 13:19:18:868 1204 664 Agent * Target group: (Unassigned Computers)
2012-07-06 13:19:18:868 1204 664 Agent * Windows Update access disabled: No
2012-07-06 13:19:18:883 1204 664 DnldMgr Download manager restoring 0 downloads
2012-07-06 13:19:18:885 1204 664 AU ########### AU: Initializing Automatic Updates ###########
2012-07-06 13:19:18:907 1204 664 AU # WSUS server: http://10.20.2.1:80
2012-07-06 13:19:18:907 1204 664 AU # Detection frequency: 22
2012-07-06 13:19:18:907 1204 664 AU # Approval type: Pre-download notify (Policy)
2012-07-06 13:19:19:638 1204 13d4 Setup Service restarting after SelfUpdate
2012-07-06 13:19:19:784 1204 664 Report *********** Report: Initializing static reporting data ***********
2012-07-06 13:19:20:245 1204 664 Report * OS Version = 6.1.7600.0.0.65792
2012-07-06 13:19:20:245 1204 664 Report * OS Product Type = 0x00000004
2012-07-06 13:19:20:444 1204 664 Report * Computer Brand = Hewlett-Packard
2012-07-06 13:19:20:445 1204 664 Report * Computer Model = HP Compaq 6000 Pro MT PC
2012-07-06 13:19:20:472 1204 664 Report * Bios Revision = 786G2 v01.09
2012-07-06 13:19:20:472 1204 664 Report * Bios Name = Default System BIOS
2012-07-06 13:19:20:472 1204 664 Report * Bios Release Date = 2009-08-25T00:00:00
2012-07-06 13:19:20:472 1204 664 Report * Locale ID = 1033
2012-07-06 13:19:20:532 1204 13d4 Setup Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256
2012-07-06 13:19:20:533 1204 664 AU Successfully wrote event for AU health state:0
2012-07-06 13:19:20:691 1204 664 AU Initializing featured updates
2012-07-06 13:19:20:707 1204 664 AU Found 0 cached featured updates
2012-07-06 13:19:20:708 1204 664 AU Successfully wrote event for AU health state:0
2012-07-06 13:19:20:712 1204 664 AU Successfully wrote event for AU health state:0
2012-07-06 13:19:20:712 1204 664 AU AU finished delayed initialization
2012-07-06 13:19:20:712 1204 664 AU Triggering AU detection through DetectNow API
2012-07-06 13:19:20:712 1204 664 AU Triggering Online detection (non-interactive)
2012-07-06 13:19:20:816 1204 13d4 AU #############
2012-07-06 13:19:20:816 1204 13d4 AU ## START ## AU: Search for updates
2012-07-06 13:19:20:816 1204 13d4 AU #########
2012-07-06 13:19:20:856 1204 13d4 AU <<## SUBMITTED ## AU: Search for updates [CallId = {D4AD82F8-0C99-4FC7-9F6B-ABE2E4BB4338}]
2012-07-06 13:19:21:618 1204 12e0 Agent *************
2012-07-06 13:19:21:618 1204 12e0 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2012-07-06 13:19:21:618 1204 12e0 Agent *********
2012-07-06 13:19:21:618 1204 12e0 Agent * Online = Yes; Ignore download priority = No
2012-07-06 13:19:21:618 1204 12e0 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2012-07-06 13:19:21:618 1204 12e0 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2012-07-06 13:19:21:618 1204 12e0 Agent * Search Scope = {Machine}
2012-07-06 13:19:21:619 1204 12e0 Setup Checking for agent SelfUpdate
2012-07-06 13:19:21:619 1204 12e0 Setup Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256
2012-07-06 13:19:21:653 1204 12e0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2012-07-06 13:19:21:707 1204 12e0 Misc Microsoft signed: Yes
2012-07-06 13:19:24:855 1204 12e0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2012-07-06 13:19:24:859 1204 12e0 Misc Microsoft signed: Yes
2012-07-06 13:19:24:884 1204 12e0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2012-07-06 13:19:24:919 1204 12e0 Misc Microsoft signed: Yes
2012-07-06 13:19:25:011 1204 12e0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2012-07-06 13:19:25:017 1204 12e0 Misc Microsoft signed: Yes
2012-07-06 13:19:25:100 1204 12e0 Setup Determining whether a new setup handler needs to be downloaded
2012-07-06 13:19:25:226 1204 12e0 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe:
2012-07-06 13:19:25:232 1204 12e0 Misc Microsoft signed: Yes
2012-07-06 13:19:25:232 1204 12e0 Misc WARNING: Digital Signatures on file C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe are not trusted: Error 0x800b0001
2012-07-06 13:19:25:232 1204 12e0 Setup WARNING: Trust verification failed for WuSetupV.exe. It will be deleted and downloaded, error = 0x800B0001
2012-07-06 13:19:25:232 1204 12e0 Setup SelfUpdate handler update required: Current version: 7.6.7600.256, required version: 7.6.7600.256
2012-07-06 13:19:25:232 1204 12e0 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2012-07-06 13:19:26:998 1204 12e0 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2012-07-06 13:19:26:998 1204 12e0 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2012-07-06 13:19:27:239 1204 12e0 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2012-07-06 13:19:27:239 1204 12e0 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2012-07-06 13:19:27:636 1204 12e0 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2012-07-06 13:19:27:638 1204 12e0 Setup SelfUpdate check completed. SelfUpdate is NOT required.
2012-07-06 13:19:32:531 1204 12e0 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2012-07-06 13:19:32:531 1204 12e0 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://10.20.2.1:80/ClientWebService/client.asmx
2012-07-06 13:19:32:562 1204 12e0 PT WARNING: Cached cookie has expired or new PID is available
2012-07-06 13:19:32:563 1204 12e0 PT Initializing simple targeting cookie, clientId = 1693765575, target group = , DNS name = jmclean-w7.office.ABCInc.com
2012-07-06 13:19:32:563 1204 12e0 PT Server URL = http://10.20.2.1:80/SimpleAuthWebService/SimpleAuth.asmx
2012-07-06 13:19:57:455 1204 12e0 Agent WARNING: Failed to evaluate Installed rule, updateId = {189A8F50-0C3A-4FDF-8BC2-BC23A3EB11FB}.101, hr = 80242013
2012-07-06 13:20:05:037 1204 12e0 PT +++++++++++ PT: Synchronizing extended update info +++++++++++
2012-07-06 13:20:05:037 1204 12e0 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://10.20.2.1:80/ClientWebService/client.asmx
2012-07-06 13:20:06:046 1204 12e0 Agent * Found 0 updates and 76 categories in search; evaluated appl. rules of 1938 out of 5358 deployed entities
2012-07-06 13:20:06:089 1204 12e0 Agent *********
2012-07-06 13:20:06:089 1204 12e0 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2012-07-06 13:20:06:089 1204 12e0 Agent *************
2012-07-06 13:20:06:118 1204 11a4 AU >>## RESUMED ## AU: Search for updates [CallId = {D4AD82F8-0C99-4FC7-9F6B-ABE2E4BB4338}]
2012-07-06 13:20:06:118 1204 11a4 AU # 0 updates detected
2012-07-06 13:20:06:119 1204 11a4 AU #########
2012-07-06 13:20:06:119 1204 11a4 AU ## END ## AU: Search for updates [CallId = {D4AD82F8-0C99-4FC7-9F6B-ABE2E4BB4338}]
2012-07-06 13:20:06:119 1204 11a4 AU #############
2012-07-06 13:20:06:120 1204 11a4 AU Successfully wrote event for AU health state:0
2012-07-06 13:20:06:120 1204 11a4 AU Featured notifications is disabled.
2012-07-06 13:20:06:120 1204 11a4 AU AU setting next detection timeout to 2012-07-07 11:25:24
2012-07-06 13:20:06:121 1204 11a4 AU Successfully wrote event for AU health state:0
2012-07-06 13:20:06:123 1204 11a4 AU Successfully wrote event for AU health state:0
2012-07-06 13:20:06:135 1204 12e0 Report REPORT EVENT: {6C3A427D-B783-42F2-9C38-E8799DDF2362} 2012-07-06 13:19:20:811-0400 1 199 101 {0011B9ED-9189-4D58-BE25-FA2F13FC3D6C} 1 240005 SelfUpdate Success Content Install Installation successful and restart required for the following update: Windows Update Aux
2012-07-06 13:20:06:189 1204 12e0 Report CWERReporter finishing event handling. (00000000)
2012-07-06 13:20:12:125 1204 12e0 Report REPORT EVENT: {679F1BFE-63A8-4E00-A14C-55349B6ABBDF} 2012-07-06 13:20:06:088-0400 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates.
2012-07-06 13:20:12:125 1204 12e0 Report REPORT EVENT: {8946394C-9D26-43B3-937D-F70A360D80B3} 2012-07-06 13:20:06:088-0400 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2012-07-06 13:20:12:126 1204 12e0 Report CWERReporter finishing event handling. (00000000)
2012-07-06 13:35:42:841 1204 12e0 Report Uploading 3 events using cached cookie, reporting URL = http://10.20.2.1:80/ReportingWebService/ReportingWebService.asmx
2012-07-06 13:35:43:218 1204 12e0 Report Reporter successfully uploaded 3 events.
==============================================================================executed the diagnostic tool again
==================================================
# Solarwinds® Diagnostic Tool for the WSUS Agent
# 7/6/2012
Machine state
User rights: User has administrator rights
Update service status: Running
Background Intelligent Transfer service status: Running
OS Version: Windows 7 Enterprise
Windows update agent version: 7.6.7600.256 (WU Agent is OK)
Windows Update Agent configuration settings
Automatic Update: Enabled
Options: Notify before download and installation
Use WSUS Server: Enabled
Windows Update Server: http://10.20.2.1:80
Windows Update Status Server: http://10.20.2.1:80
WSUS URLs are identical: Identical
WSUS URL is valid: Valid URL
WSUS Server Connectivity
clientwebservice/client.asmx: OK
simpleauthwebservice/simpleauth.asmx: OK
content: Error: Forbidden (Incorrect proxy client configuration - use settings tab to test proxy configuration settings; may also be caused by misconfigured SSL implementation or access rights on WSUS server)
selfupdate/iuident.cab: OK
iuident.cab: OK
========================================================================================Will you be able to provide the details of what the tool is checking for "content"? (with default wsus installation the directory browsing is not enabled in the IIS server for the contents folder)
Thanks
-
07 Juli 2012 19:20Moderator
==OR==
2012-07-06 13:19:07:531 1204 13d4 Misc =========== Logging initialized (build: 7.6.7600.256, tz: -0400) ===========
2012-07-06 13:19:25:232 1204 12e0 Misc WARNING: Digital Signatures on file C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe are not trusted: Error 0x800b0001
The Windows Update Agent on the client has been updated to v7.6.7600.256 and you've not yet installed KB2720211 to the WSUS server. Install KB2720211!
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Product Manager, SolarWinds
Microsoft MVP - Software Distribution (2005-2012)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin- Disarankan sebagai Jawaban oleh Marimuthu Ramakrishnan 10 Juli 2012 14:45
- Ditandai sebagai Jawaban oleh Lawrence GarvinMVP, Moderator 17 Juli 2012 17:49
-
07 Juli 2012 19:27Moderator
content: Error: Forbidden (Incorrect proxy client configuration - use settings tab to test proxy configuration settings; may also be caused by misconfigured SSL implementation or access rights on WSUS server)
I don't think this is related to the WUAgent v7.6 and KB2720211 issue, but it is possible that this scenario is causing this failure reading from the /content store. I saw this message one other time on one my own systems, before this update was a factor, which I also at that time knew to be a false indication -- well false in that nothing was actually dysfunctional on my system -- but maybe true in terms of how the analysis logic is written inside the tool.
Let's get your WSUS server updated and see if this message persists. If it does, then I'll ask you to take that issue over to the SolarWinds Thwack forums where we have a forum dedicated to this tool. In the meantime, I'll take another look at my systems and see if I can reproduce it.
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Product Manager, SolarWinds
Microsoft MVP - Software Distribution (2005-2012)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin -
10 Juli 2012 14:33
after installing the KB 2720211 the "not trusted" issue got fixed. thank you
2012-07-10 10:21:58:464 1320 10ec Misc =========== Logging initialized (build: 7.6.7600.256, tz: -0400) ===========
2012-07-10 10:21:58:514 1320 10ec Misc = Process: C:\Windows\system32\svchost.exe
2012-07-10 10:21:58:563 1320 10ec Misc = Module: c:\windows\system32\wuaueng.dll
2012-07-10 10:21:58:464 1320 10ec Service *************
2012-07-10 10:21:58:663 1320 10ec Service ** START ** Service: Service startup
2012-07-10 10:21:58:763 1320 10ec Service *********
2012-07-10 10:21:59:027 1320 10ec Agent * WU client version 7.6.7600.256
2012-07-10 10:21:59:077 1320 10ec Agent * Base directory: C:\Windows\SoftwareDistribution
2012-07-10 10:21:59:579 1320 10ec Agent * Access type: No proxy
2012-07-10 10:21:59:745 1320 10ec Agent * Network state: Connected
2012-07-10 10:22:27:139 1320 9f0 Report CWERReporter::Init succeeded
2012-07-10 10:22:27:139 1320 9f0 Agent *********** Agent: Initializing Windows Update Agent ***********
2012-07-10 10:22:27:139 1320 9f0 Agent *********** Agent: Initializing global settings cache ***********
2012-07-10 10:22:27:139 1320 9f0 Agent * WSUS server: http://10.20.2.1:80
2012-07-10 10:22:27:139 1320 9f0 Agent * WSUS status server: http://10.20.2.1:80
2012-07-10 10:22:27:139 1320 9f0 Agent * Target group: (Unassigned Computers)
2012-07-10 10:22:27:140 1320 9f0 Agent * Windows Update access disabled: No
2012-07-10 10:22:27:160 1320 9f0 DnldMgr Download manager restoring 0 downloads
2012-07-10 10:22:27:174 1320 9f0 AU ########### AU: Initializing Automatic Updates ###########
2012-07-10 10:22:27:175 1320 9f0 AU # WSUS server: http://10.20.2.1:80
2012-07-10 10:22:27:175 1320 9f0 AU # Detection frequency: 22
2012-07-10 10:22:27:175 1320 9f0 AU # Approval type: Pre-download notify (Policy)
2012-07-10 10:22:27:627 1320 10ec Report *********** Report: Initializing static reporting data ***********
2012-07-10 10:22:27:627 1320 10ec Report * OS Version = 6.1.7600.0.0.65792
2012-07-10 10:22:27:627 1320 10ec Report * OS Product Type = 0x00000004
2012-07-10 10:22:27:669 1320 10ec Report * Computer Brand = Hewlett-Packard
2012-07-10 10:22:27:669 1320 10ec Report * Computer Model = HP Compaq 6000 Pro MT PC
2012-07-10 10:22:27:702 1320 10ec Report * Bios Revision = 786G2 v01.09
2012-07-10 10:22:27:702 1320 10ec Report * Bios Name = Default System BIOS
2012-07-10 10:22:27:702 1320 10ec Report * Bios Release Date = 2009-08-25T00:00:00
2012-07-10 10:22:27:702 1320 10ec Report * Locale ID = 1033
2012-07-10 10:22:27:728 1320 9f0 AU Successfully wrote event for AU health state:0
2012-07-10 10:22:27:728 1320 9f0 AU Initializing featured updates
2012-07-10 10:22:27:728 1320 9f0 AU Found 0 cached featured updates
2012-07-10 10:22:27:728 1320 9f0 AU Successfully wrote event for AU health state:0
2012-07-10 10:22:27:730 1320 9f0 AU Successfully wrote event for AU health state:0
2012-07-10 10:22:27:730 1320 9f0 AU AU finished delayed initialization
2012-07-10 10:22:27:731 1320 9f0 AU Triggering AU detection through DetectNow API
2012-07-10 10:22:27:731 1320 9f0 AU Triggering Online detection (non-interactive)
2012-07-10 10:22:27:731 1320 10ec AU #############
2012-07-10 10:22:27:731 1320 10ec AU ## START ## AU: Search for updates
2012-07-10 10:22:27:731 1320 10ec AU #########
2012-07-10 10:22:27:733 1320 10ec AU <<## SUBMITTED ## AU: Search for updates [CallId = {803CD32A-9DB5-4200-B390-794466068E25}]
2012-07-10 10:22:28:064 1320 620 Agent *************
2012-07-10 10:22:28:064 1320 620 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2012-07-10 10:22:28:064 1320 620 Agent *********
2012-07-10 10:22:28:064 1320 620 Agent * Online = Yes; Ignore download priority = No
2012-07-10 10:22:28:064 1320 620 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2012-07-10 10:22:28:064 1320 620 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2012-07-10 10:22:28:064 1320 620 Agent * Search Scope = {Machine}
2012-07-10 10:22:28:064 1320 620 Setup Checking for agent SelfUpdate
2012-07-10 10:22:28:065 1320 620 Setup Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256
2012-07-10 10:22:28:074 1320 620 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2012-07-10 10:22:28:105 1320 620 Misc Microsoft signed: Yes
2012-07-10 10:22:30:659 1320 620 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2012-07-10 10:22:30:663 1320 620 Misc Microsoft signed: Yes
2012-07-10 10:22:30:700 1320 620 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2012-07-10 10:22:30:721 1320 620 Misc Microsoft signed: Yes
2012-07-10 10:22:30:803 1320 620 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2012-07-10 10:22:30:808 1320 620 Misc Microsoft signed: Yes
2012-07-10 10:22:30:862 1320 620 Setup Determining whether a new setup handler needs to be downloaded
2012-07-10 10:22:30:862 1320 620 Setup SelfUpdate handler is not found. It will be downloaded
2012-07-10 10:22:30:862 1320 620 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
2012-07-10 10:22:32:139 1320 620 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2012-07-10 10:22:32:139 1320 620 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2012-07-10 10:22:32:159 1320 620 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2012-07-10 10:22:32:159 1320 620 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
2012-07-10 10:22:32:187 1320 620 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
2012-07-10 10:22:32:188 1320 620 Setup SelfUpdate check completed. SelfUpdate is NOT required.
2012-07-10 10:22:34:668 1320 620 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2012-07-10 10:22:34:668 1320 620 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://10.20.2.1:80/ClientWebService/client.asmx
2012-07-10 10:22:34:688 1320 620 PT WARNING: Cached cookie has expired or new PID is available
2012-07-10 10:22:34:688 1320 620 PT Initializing simple targeting cookie, clientId = 1693765575, target group = , DNS name = jmclean-w7.office.ABCInc.com
2012-07-10 10:22:34:688 1320 620 PT Server URL = http://10.20.2.1:80/SimpleAuthWebService/SimpleAuth.asmx
2012-07-10 10:22:34:936 1320 620 PT WARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
2012-07-10 10:22:34:936 1320 620 PT WARNING: SOAP Fault: 0x00012c
2012-07-10 10:22:34:936 1320 620 PT WARNING: faultstring:Fault occurred
2012-07-10 10:22:34:936 1320 620 PT WARNING: ErrorCode:ConfigChanged(2)
2012-07-10 10:22:34:936 1320 620 PT WARNING: Message:(null)
2012-07-10 10:22:34:936 1320 620 PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
2012-07-10 10:22:34:936 1320 620 PT WARNING: ID:44e1c560-aba9-421e-b55c-6d51c175d652
2012-07-10 10:22:35:058 1320 620 PT WARNING: Cached cookie has expired or new PID is available
2012-07-10 10:22:35:058 1320 620 PT Initializing simple targeting cookie, clientId = 1693765575, target group = , DNS name = jmclean-w7.office.ABCInc.com
2012-07-10 10:22:35:058 1320 620 PT Server URL = http://10.20.2.1:80/SimpleAuthWebService/SimpleAuth.asmx
2012-07-10 10:22:48:188 1320 620 Agent WARNING: Failed to evaluate Installed rule, updateId = {189A8F50-0C3A-4FDF-8BC2-BC23A3EB11FB}.101, hr = 80242013
2012-07-10 10:22:52:369 1320 620 PT +++++++++++ PT: Synchronizing extended update info +++++++++++
2012-07-10 10:22:52:370 1320 620 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://10.20.2.1:80/ClientWebService/client.asmx
2012-07-10 10:22:53:348 1320 620 Agent * Found 0 updates and 76 categories in search; evaluated appl. rules of 1936 out of 5454 deployed entities
2012-07-10 10:22:53:365 1320 620 Agent *********
2012-07-10 10:22:53:365 1320 620 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2012-07-10 10:22:53:365 1320 620 Agent *************
2012-07-10 10:22:53:389 1320 828 AU >>## RESUMED ## AU: Search for updates [CallId = {803CD32A-9DB5-4200-B390-794466068E25}]
2012-07-10 10:22:53:389 1320 828 AU # 0 updates detected
2012-07-10 10:22:53:390 1320 828 AU #########
2012-07-10 10:22:53:390 1320 828 AU ## END ## AU: Search for updates [CallId = {803CD32A-9DB5-4200-B390-794466068E25}]
2012-07-10 10:22:53:390 1320 828 AU #############
2012-07-10 10:22:53:391 1320 828 AU Successfully wrote event for AU health state:0
2012-07-10 10:22:53:391 1320 828 AU Featured notifications is disabled.
2012-07-10 10:22:53:392 1320 828 AU AU setting next detection timeout to 2012-07-11 09:11:35
2012-07-10 10:22:53:392 1320 828 AU Successfully wrote event for AU health state:0
2012-07-10 10:22:53:393 1320 828 AU Successfully wrote event for AU health state:0
2012-07-10 10:22:53:418 1320 620 Report CWERReporter finishing event handling. (00000000)
2012-07-10 10:22:58:384 1320 620 Report REPORT EVENT: {05913828-23BD-48A1-ACF7-02AEA2823DAE} 2012-07-10 10:22:53:364-0400 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates.
2012-07-10 10:22:58:384 1320 620 Report REPORT EVENT: {ED05D21F-44A1-4175-8CB0-7A5071A23079} 2012-07-10 10:22:53:364-0400 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
2012-07-10 10:22:58:387 1320 620 Report CWERReporter finishing event handling. (00000000)
-
10 Juli 2012 14:44
You are right. The KB doesnt have any impact on this, but its something to do with the "directory browsing" settings.
I have enabled the directory browsing on contents folder and i verified the "http://localhost/Content/" availability and then ran the report. The result is all success. Please see the results below.
Now my question is, what is the expected setting on this folder? the settings were untouched since the install of WSUS and now i have enabled it. Does it have any impact on functionality? (i didnt see any issue)
# Solarwinds® Diagnostic Tool for the WSUS Agent
# 7/10/2012
Machine state
User rights: User has administrator rights
Update service status: Running
Background Intelligent Transfer service status: Running
OS Version: Windows 7 Enterprise
Windows update agent version: 7.6.7600.256 (WU Agent is OK)
Windows Update Agent configuration settings
Automatic Update: Enabled
Options: Notify before download and installation
Use WSUS Server: Enabled
Windows Update Server: http://10.20.2.1:80:80
Windows Update Status Server: http://10.20.2.1:80:80
WSUS URLs are identical: Identical
WSUS URL is valid: Valid URL
WSUS Server Connectivity
clientwebservice/client.asmx: OK
simpleauthwebservice/simpleauth.asmx: OK
content: OK
selfupdate/iuident.cab: OK
iuident.cab: OK
I am going to post the results in to the Solarwinds forum also, but please clarify on the settings required for this contents folder.
-
12 Juli 2012 16:53Moderator
i run this tool and i get this msg error:
content | Error: Forbidden | Incorrect proxy client configuration - use settings tab to test proxy configuration settings; may also be caused by misconfigured SSL implemetation or access rights on WSUS Server
I dont have a proxy configuration or any kind of proxy...so what could it be the problem?
I just identified one (unexpected) cause of this particular message.
In a typical WSUS/IIS installation, the Directory Browsing role service on IIS7 is not enabled. As such, when you test a v-dir URL that has no returnable content, such as the ~/content v-dir on WSUS, IIS just returns an HTTP 200 and a blank response.
However if you enable the Directory Browsing role service, and then try to access the same resource, IIS returns an HTTP 403.14 result code -- because there is a directory, but browsing is not enabled for that v-dir.
The resolution for this is NOT to enable Directory Browsing!!!
The resolution is to confirm that you have a justified reason for having the Directory Browsing role service enabled -- and if not, to disable it.
Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Product Manager, SolarWinds
Microsoft MVP - Software Distribution (2005-2012)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin- Disarankan sebagai Jawaban oleh antwesor 13 Juli 2012 16:22
- Ditandai sebagai Jawaban oleh Lawrence GarvinMVP, Moderator 17 Juli 2012 17:48
-
16 Juli 2012 20:25
Thanks Lawrence and sorry for the late answer...i paste the results like u said to me...
C:\Users\msifuentes>netsh winhttp show proxy
Configuración actual del proxy WinHTTP:
Acceso directo (sin servidor proxy). -
17 Juli 2012 17:48Moderator
Thanks Lawrence and sorry for the late answer...i paste the results like u said to me...
C:\Users\msifuentes>netsh winhttp show proxy
Configuración actual del proxy WinHTTP:
Acceso directo (sin servidor proxy).
As noted above, the 'content' error you experienced in the Diagnostic Tool, in the absence of a real proxy error (which would also be flagged on the other four resource tests as well), is likely caused because the Directory Browsing role service has been enabled in the Web Server role of the WSUS server. If you do not have a specific need for the Directory Browsing role service, then you should disable it. If you do need it, then just understand that this would be a normal indication in that situation, since the /content v-dir is returning an HTTP 403.14 to the Diagnostic Tool.Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
Product Manager, SolarWinds
Microsoft MVP - Software Distribution (2005-2012)
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin -
20 Juli 2012 13:52Sorry Lawrence, it was long time ago when i post this and no one answer me, so i forget to read it all....im gonna try all the solutions that you propose and i let you know later how is working. Thank you so much.
-
18 Oktober 2012 14:45
i got rid of the error by enabling directory browsing on the content directory
thats on IIS 6 on Server 2003 SP2 standard edition
- Diedit oleh colm_sm 18 Oktober 2012 14:45
.png)
