Windows Server 2008 R2上的WSUS 3.0 SP2。
我build立了一个新的盒子来取代旧的WSUS盒子，它仍然在Server 2003上。
所有使用WSUS服务器的客户端都无法find更新，也不会报告状态。
C：\ Windows \ WindowsUpdate.log其中一个客户端上：
2013-05-09 10:04:48:629 764 494 AU Triggering AU detection through DetectNow API 2013-05-09 10:04:48:629 764 494 AU Triggering Online detection (non-interactive) 2013-05-09 10:04:48:630 764 7b0 AU ############# 2013-05-09 10:04:48:630 764 7b0 AU ## START ## AU: Search for updates 2013-05-09 10:04:48:630 764 7b0 AU ######### 2013-05-09 10:04:48:630 764 7b0 AU <<## SUBMITTED ## AU: Search for updates [CallId = {E7AC5D1F-612A-4879-9B77-83C692868D11}] 2013-05-09 10:04:48:630 764 64c Agent ************* 2013-05-09 10:04:48:630 764 64c Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates] 2013-05-09 10:04:48:630 764 64c Agent ********* 2013-05-09 10:04:48:630 764 64c Agent * Online = Yes; Ignore download priority = No 2013-05-09 10:04:48:630 764 64c 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" 2013-05-09 10:04:48:630 764 64c Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed 2013-05-09 10:04:48:630 764 64c Agent * Search Scope = {Machine} 2013-05-09 10:04:48:630 764 64c Setup Checking for agent SelfUpdate 2013-05-09 10:04:48:630 764 64c Setup Client version: Core: 7.6.7600.256 Aux: 7.6.7600.256 2013-05-09 10:04:48:630 764 64c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab: 2013-05-09 10:04:48:637 764 64c Misc Microsoft signed: Yes 2013-05-09 10:04:50:897 764 64c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab: 2013-05-09 10:04:50:901 764 64c Misc Microsoft signed: Yes 2013-05-09 10:04:50:902 764 64c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab: 2013-05-09 10:04:50:907 764 64c Misc Microsoft signed: Yes 2013-05-09 10:04:50:909 764 64c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab: 2013-05-09 10:04:50:913 764 64c Misc Microsoft signed: Yes 2013-05-09 10:04:50:927 764 64c Setup Determining whether a new setup handler needs to be downloaded 2013-05-09 10:04:50:927 764 64c Setup SelfUpdate handler is not found. It will be downloaded 2013-05-09 10:04:50:928 764 64c Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" 2013-05-09 10:04:50:931 764 64c Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed. 2013-05-09 10:04:50:931 764 64c Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" 2013-05-09 10:04:50:955 764 64c Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed. 2013-05-09 10:04:50:955 764 64c Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" 2013-05-09 10:04:50:990 764 64c Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed. 2013-05-09 10:04:50:990 764 64c Setup SelfUpdate check completed. SelfUpdate is NOT required. 2013-05-09 10:04:51:205 764 64c PT +++++++++++ PT: Synchronizing server updates +++++++++++ 2013-05-09 10:04:51:205 764 64c PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://wsus-server.company.local/ClientWebService/client.asmx 2013-05-09 10:04:51:266 764 64c PT WARNING: Cached cookie has expired or new PID is available 2013-05-09 10:04:51:266 764 64c PT Initializing simple targeting cookie, clientId = 9f4df40d-f61e-41d5-9fd2-3cdce1823f45, target group = Servers, DNS name = wsus-server.company.local 2013-05-09 10:04:51:266 764 64c PT Server URL = http://wsus-server.company.local/SimpleAuthWebService/SimpleAuth.asmx 2013-05-09 10:04:51:286 764 64c PT WARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200 2013-05-09 10:04:51:286 764 64c PT WARNING: SOAP Fault: 0x00012c 2013-05-09 10:04:51:286 764 64c PT WARNING: faultstring:System.Web.Services.Protocols.SoapException: Fault occurred at Microsoft.UpdateServices.Internal.SoapUtilities.ThrowException(ErrorCode errorCode, String message, String[] clientIds) at Microsoft.UpdateServices.Internal.ClientImplementation.GetCookie(AuthorizationCookie[] authCookies, Cookie oldCookie, DateTime lastChange, DateTime currentClientTime, String protocolVersion) 2013-05-09 10:04:51:286 764 64c PT WARNING: ErrorCode:ConfigChanged(2) 2013-05-09 10:04:51:286 764 64c PT WARNING: Message:(null) 2013-05-09 10:04:51:286 764 64c PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie" 2013-05-09 10:04:51:286 764 64c PT WARNING: ID:f50afcf7-2117-495c-9123-9aa4bf683520 2013-05-09 10:04:51:296 764 64c PT WARNING: Cached cookie has expired or new PID is available 2013-05-09 10:04:51:296 764 64c PT Initializing simple targeting cookie, clientId = 9f4df40d-f61e-41d5-9fd2-3cdce1823f45, target group = Servers, DNS name = wsus-server.company.local 2013-05-09 10:04:51:296 764 64c PT Server URL = http://wsus-server.company.local/SimpleAuthWebService/SimpleAuth.asmx 2013-05-09 10:04:55:116 764 64c PT +++++++++++ PT: Synchronizing extended update info +++++++++++ 2013-05-09 10:04:55:116 764 64c PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://wsus-server.company.local/ClientWebService/client.asmx 2013-05-09 10:04:55:170 764 64c PT WARNING: GetExtendedUpdateInfo failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200 2013-05-09 10:04:55:170 764 64c PT WARNING: SOAP Fault: 0x000190 2013-05-09 10:04:55:170 764 64c PT WARNING: faultstring:System.Web.Services.Protocols.SoapException: Fault occurred at Microsoft.UpdateServices.Internal.SoapUtilities.ThrowException(ErrorCode errorCode, Exception e, Int32 eventLogEntryId, String[] clientIds, Boolean logToEventLog) at Microsoft.UpdateServices.Internal.ClientImplementation.GetExtendedUpdateInfo(Cookie cookie, Int32[] revisionIds, XmlUpdateFragmentType[] fragmentTypes, String[] locales) 2013-05-09 10:04:55:170 764 64c PT WARNING: ErrorCode:InternalServerError(5) 2013-05-09 10:04:55:170 764 64c PT WARNING: Message:(null) 2013-05-09 10:04:55:170 764 64c PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetExtendedUpdateInfo" 2013-05-09 10:04:55:170 764 64c PT WARNING: ID:37740867-4b9f-4394-b58b-12aad48d7b97 2013-05-09 10:04:55:170 764 64c PT WARNING: PTError: 0x8024400e 2013-05-09 10:04:55:170 764 64c PT WARNING: GetExtendedUpdateInfo_WithRecovery: 0x8024400e 2013-05-09 10:04:55:170 764 64c PT WARNING: Sync of Extended Info: 0x8024400e 2013-05-09 10:04:55:170 764 64c PT WARNING: SyncServerUpdatesInternal failed : 0x8024400e 2013-05-09 10:04:55:171 764 64c Agent * WARNING: Exit code = 0x8024400E 2013-05-09 10:04:55:171 764 64c Agent ********* 2013-05-09 10:04:55:171 764 64c Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates] 2013-05-09 10:04:55:171 764 64c Agent ************* 2013-05-09 10:04:55:171 764 64c Agent WARNING: WU client failed Searching for update with error 0x8024400e 2013-05-09 10:04:55:180 764 bf4 AU >>## RESUMED ## AU: Search for updates [CallId = {E7AC5D1F-612A-4879-9B77-83C692868D11}] 2013-05-09 10:04:55:180 764 bf4 AU # WARNING: Search callback failed, result = 0x8024400E 2013-05-09 10:04:55:180 764 bf4 AU # WARNING: Failed to find updates with error code 8024400E 2013-05-09 10:04:55:180 764 bf4 AU ######### 2013-05-09 10:04:55:180 764 bf4 AU ## END ## AU: Search for updates [CallId = {E7AC5D1F-612A-4879-9B77-83C692868D11}] 2013-05-09 10:04:55:180 764 bf4 AU ############# 2013-05-09 10:04:55:180 764 bf4 AU Successfully wrote event for AU health state:0 2013-05-09 10:04:55:180 764 bf4 AU AU setting next detection timeout to 2013-05-09 13:04:55 2013-05-09 10:04:55:181 764 bf4 AU Successfully wrote event for AU health state:0 2013-05-09 10:04:55:181 764 bf4 AU Successfully wrote event for AU health state:0 2013-05-09 10:05:00:171 764 64c Report REPORT EVENT: {1C2D6590-41BD-464D-AE18-289CB7D6E254} 2013-05-09 10:04:55:171+0200 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024400e AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x8024400e. 2013-05-09 10:05:00:191 764 64c Report CWERReporter::HandleEvents - WER report upload completed with status 0x8 2013-05-09 10:05:00:191 764 64c Report WER Report sent: 7.6.7600.256 0x8024400e 00000000-0000-0000-0000-000000000000 Scan 101 Managed 2013-05-09 10:05:00:191 764 64c Report CWERReporter finishing event handling. (00000000) 我发现了几个旧的博客和论坛条目，将其链接到Office 2003 SP1中的一个错误，修复是拒绝/批准/拒绝更新，但这并没有解决这个问题。
Microsoft WSUS客户端和服务器诊断工具不能在x64系统上运行。
有没有人有这个运气？
更新 ：我在C：\ Program Files \ UpdateServices \ LogFiles \ SoftwareDistribution.log中find它：
2013-05-13 14:02:46.437 UTC Warning w3wp.6 SoapUtilities.CreateException ThrowException: actor = http://wsus-server.company.local/ClientWebService/client.asmx, ID=4db89865-40da-4520-a126-d196e3db07b6, ErrorCode=ConfigChanged, Message=, Client=d9ce7281-379b-49b8-8944-7f593c32397b 2013-05-13 14:02:50.867 UTC Error w3wp.6 ClientImplementation.GetExtendedUpdateInfo System.ArgumentException: The database does not contain a URL for the file 3F7E7915F44A6133B990A22A87604854C34BDF4E.
如果我search“3F7E7915F44A6133B990A22A87604854C34BDF4E”，谷歌就完全失败了，所以我不确定它到底是什么东西，但是似乎它的数据库条目是不完整的。 与上游WSUS同步日志显示没有错误。
更新2 ：所以好像我的上游有些奇怪的东西。 我发现，如果我安装一个新的WSUS实例并从Microsoft同步它，所有工作都很好。 如果我将其作为现有WSUS服务器的下游副本，无论是在configuration期间还是之后，都会中断。 更奇怪的是，我的上游本身和另一个现有的副本似乎运作良好。 看起来好像我只是要在所有3个站点中构build新的WSUS实例，并开始新的，忽略现有的上游。
更新3 ：我build立了一个新的WSUS上游服务器，开始清理，以避免在原始上游的数据库中发生任何奇怪的事情。 在我的新上游指出我的2个副本。 一切都很好，好几天。 5天前，副本再次停止从客户端获取状态更新。 WTF？！？！
更新4 ：我已经logging了与微软在这方面的支持请求，希望有一些好的会出来的。
更新5 ：在微软产品支持花费了无数小时检查和重新检查所有我已经检查过的东西之后，我怀疑我已经偶然find了原因。 我们的Junior系统pipe理员最近发现了Local Update Publisher，并开始使用它将Adobe和Java更新推送到工作站。 Local Update Publisher的安装时间与下游客户端上次报告的时间完全一致。 我正在通过产品文档来确定我需要做什么来解决这个问题。
在Windows Server 2008 R2上迁移到WSUS 3.0 SP2时，我也遇到过类似的问题。 经过几个令人沮丧的时间，我终于用KB2720211解决了这个问题。 我不确定它为什么起作用，因为它似乎没有直接解决我当时从客户端收到的错误代码（800b0001），但是在进一步进行诊断之前确保WSUS版本已完全修补似乎是合乎逻辑的。
您可以使用http://support.microsoft.com/kb/2720211中的说明
由于我的设置只涉及一个WSUS服务器，因此我只需要在下载补丁程序后使用网站上的以下说明。
1.设置WSUS。 为此，请在命令提示符处键入以下适用于您的系统的以下命令之一：
WSUS-KB2720211-x64.exe /q C:\MySetup.log
WSUS-KB2720211-x86.exe /q C:\MySetup.log
该更新将立即安装，没有任何提示。
2.查看安装日志以validation升级是否成功。 为此，请在命令提示符处键入C:\MySetup.log 。
3.确保IIS和WSUS服务已停止。 为此，请在命令提示符处键入以下命令：
iisreset/stop
net stop wsusservice
0x8024400D / SOAP 0x12c错误几乎总是（现在）是具有重复的SusClientID的客户端的performance。 请参阅Microsoft KB903262了解补救说明。
0x8024400E / SOAP 0x190错误通常是WSUS数据库中错误更新的performanceforms。 确保已经拒绝了所有过期的更新（通常是“坏的”），并拒绝所有被取代/不需要的更新。
所以，差不多3个月后，微软PSS花了几十个小时就这样，我终于偶然发现了答案。
事实certificate，根本原因是本地更新发布者的不完整实现。
实施Local Update Publisher时，应该将WSUS SSL证书作为受信任的发布者和受信任的根证书颁发机构分发给所有WSUS客户端 。 事实certificate，我的同事实施它只分发到工作站，而不是服务器。
我不清楚底层的具体细节，但只要将SSL证书分发给所有WSUS客户端，他们就开始按照正常方式接收其更新和报告状态。