询问者
Windows2008R2 WSUS同步失败报错:基础连接已关闭:发送时发生错误

问题
-
目前服务器版本是Windows2008R2,直接与互联网更新的没有代理服务器。
防火墙都关闭的,IIS里面的应用程序池的Wsuspool也是启动的
目前有这个告警:
WebException: 基础连接已经关闭: 发送时发生错误。 ---> System.IO.IOException: 无法从传输连接中读取数据: 远程主机强迫关闭了一个现有的连接。。
在 System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
在 System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
在 Microsoft.UpdateServices.ServerSync.ServerSyncCompressionProxy.GetWebResponse(WebRequest webRequest)
在 System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
在 Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetAuthConfig()
在 Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConfig(ServerSyncProxy proxy, WebServiceCommunicationHelper webServiceHelper)
在 Microsoft.UpdateServices.ServerSync.ServerSyncLib.Authenticate(AuthorizationManager authorizationManager, Boolean checkExpiration, ServerSyncProxy proxy, Cookie cookie, WebServiceCommunicationHelper webServiceHelper)
在 Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.SyncConf
然后我这边还收集了当前服务器的SoftwareDistribution.log日志
以下内容为最近的日志:
2022-07-14 03:20:54.944 UTC Info WsusService.4 ThreadEntry _ThreadPoolWaitCallback.PerformWaitCallback
2022-07-14 03:20:55.073 UTC Info WsusService.4 SusService.OnStop EventId=502,Type=Information,Category=WsusService,Message=Update Services 服务已停止
2022-07-14 03:20:56.596 UTC Info WsusService.5 ThreadEntry ThreadHelper.ThreadStart
2022-07-14 03:20:56.611 UTC Info WsusService.5 SusService.SusServiceStartUpThreadProc WSUS Server Version: 3.2.7600.325
2022-07-14 03:20:56.879 UTC Info WsusService.5 SusService.CleanUpIntermediateFileDownload CleanupIntermediateFileDownload
2022-07-14 03:20:57.571 UTC Info WsusService.7 ThreadEntry ThreadHelper.ThreadStart
2022-07-14 03:20:57.577 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: CatalogSyncAgent, EventInfo: Startup
2022-07-14 03:20:57.584 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ContentSyncAgent, EventInfo: Startup
2022-07-14 03:20:57.590 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: StateMachineReset, EventInfo: Startup
2022-07-14 03:20:57.589 UTC Info WsusService.11 ThreadEntry ThreadHelper.ThreadStart
2022-07-14 03:20:57.605 UTC Info WsusService.11 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: CatalogSyncAgent
2022-07-14 03:20:57.611 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: RollupAgent, EventInfo: Startup
2022-07-14 03:20:57.617 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: EmailNotificationAgent, EventInfo: Startup
2022-07-14 03:20:57.595 UTC Info WsusService.5 SusService.SusServiceStartUpThreadProc EventId=501,Type=Information,Category=WsusService,Message=Update Services 服务已启动
2022-07-14 03:20:57.618 UTC Info WsusService.11 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ContentSyncAgent
2022-07-14 03:20:57.637 UTC Info WsusService.11 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: StateMachineReset
2022-07-14 03:20:57.644 UTC Info WsusService.11 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: RollupAgent
2022-07-14 03:20:57.653 UTC Info WsusService.11 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: EmailNotificationAgent
2022-07-14 03:20:57.633 UTC Info WsusService.12 ThreadEntry ThreadHelper.ThreadStart
2022-07-14 03:20:57.658 UTC Info WsusService.15 ThreadEntry ThreadHelper.ThreadStart
2022-07-14 03:20:57.672 UTC Info WsusService.15 ResetStateMachineAgent.WakeUpWorkerThreadProc State Machine Reset Agent Starting
2022-07-14 03:20:57.667 UTC Info WsusService.12 CatalogSyncAgent.HandleCatalogSyncStateCorrection Handling systemStartup work...
2022-07-14 03:20:57.692 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
2022-07-14 03:20:57.699 UTC Info WsusService.17 ThreadEntry ThreadHelper.ThreadStart
2022-07-14 03:20:57.698 UTC Info WsusService.12 CatalogSyncAgent.HandleCatalogSyncStateCorrection Finished systemStartup work.
2022-07-14 03:20:57.708 UTC Info WsusService.14 ThreadEntry ThreadHelper.ThreadStart
2022-07-14 03:20:57.715 UTC Info WsusService.14 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange
2022-07-14 03:20:57.717 UTC Info WsusService.15 ResetStateMachineAgent.WakeUpWorkerThreadProc State Machine Reset Agent Finished
2022-07-14 03:20:57.704 UTC Info WsusService.17 EmailNotificationAgent.WakeUpWorkerThreadProc Email Notification Agent Starting
2022-07-14 03:20:57.705 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
2022-07-14 03:20:57.737 UTC Info WsusService.12 CatalogSyncAgent.UpdateServerHealthStatusBasedOnError ServerHealth: Updating Server Health for Component: CatalogSyncAgent, Marking as Not Running
2022-07-14 03:20:57.737 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: FileLocationChange, EventInfo: FileLocationChange
2022-07-14 03:20:57.750 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: HardwareIDChange, EventInfo: HardwareIDChange
2022-07-14 03:20:57.756 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: LanguageChange, EventInfo: LanguageChange
2022-07-14 03:20:57.779 UTC Info WsusService.14 EventLogEventReporter.ReportEvent EventId=361,Type=Information,Category=Synchronization,Message=内容同步已启动。
2022-07-14 03:20:57.797 UTC Info WsusService.17 EmailNotificationAgent.WakeUpWorkerThreadProc Email Notification Agent Finished
2022-07-14 03:20:58.255 UTC Info WsusService.14 ContentSyncAgent.WakeUpWorkerThreadProc ServerHealth: Updating Server Health for Component: ContentSyncAgent Running, Marking as Running
2022-07-14 03:20:58.458 UTC Info WsusService.14 ContentSyncAgent.WakeUpWorkerThreadProc ContentSyncAgent found no more Jobs, thread exitting
2022-07-14 03:20:58.467 UTC Info WsusService.14 EventLogEventReporter.ReportEvent EventId=363,Type=Information,Category=Synchronization,Message=内容同步成功。
2022-07-14 03:20:58.487 UTC Info WsusService.14 ContentSyncAgent.WakeUpWorkerThreadProc ServerHealth: Updating Server Health for Component: ContentSyncAgent, Marking as Not Running
2022-07-14 03:21:01.372 UTC Info WsusService.8 ThreadEntry ThreadHelper.ThreadStart
2022-07-14 03:21:01.462 UTC Info WsusService.8 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange
2022-07-14 06:51:06.384 UTC Warning WsusService.8 DBConnection.OnReceivingInfoMessage The join order has been enforced because a local join hint is used.
2022-07-14 14:52:10.754 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: CatalogSyncAgent, EventInfo:
2022-07-14 14:52:10.884 UTC Info WsusService.19 ThreadEntry ThreadHelper.ThreadStart
2022-07-14 14:52:10.890 UTC Info WsusService.19 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: CatalogSyncAgent
2022-07-14 14:52:10.904 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
2022-07-14 14:52:10.911 UTC Info WsusService.11 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
2022-07-14 14:52:10.940 UTC Info WsusService.3 ThreadEntry ThreadHelper.ThreadStart
2022-07-14 14:52:10.947 UTC Info WsusService.3 CabUtilities.CheckCertificateSignature File cert verification failed for C:\Program Files\Update Services\autest.cab with 2147942402
2022-07-14 14:52:10.953 UTC Info WsusService.3 WsusTestKeys.AreTestKeysAllowed Server test key check: test keys are NOT allowed
2022-07-14 14:52:10.943 UTC Info WsusService.11 ServerCertificateValidator.ConfigChangedHandler Update server configuration has changed. Sync against MU: True
2022-07-14 14:52:10.959 UTC Info WsusService.3 CabUtilities.CheckCertificateSignature File cert verification failed for C:\Program Files\Update Services\autest.cab with 2147942402
2022-07-14 14:52:10.972 UTC Info WsusService.3 WsusTestKeys.AreTestKeysAllowed Server test key check: test keys are NOT allowed
2022-07-14 14:52:10.993 UTC Info WsusService.3 CatalogSyncAgentCore.SyncUpdatesOutsideSubscription sync'ing 0 updates with catalog site flag
2022-07-14 14:52:11.201 UTC Info WsusService.3 EventLogEventReporter.ReportEvent EventId=381,Type=Information,Category=Synchronization,Message=计划同步已启动。
2022-07-14 14:52:11.263 UTC Info WsusService.3 AuthorizationManager.GetUpstreamServerUriHeader Found config says USS is MU site
2022-07-14 14:52:12.533 UTC Info WsusService.3 ServerSyncLib.GetWebServiceProxyInternal Found config says USS is MU site
2022-07-14 14:52:12.835 UTC Info WsusService.3 AuthorizationManager.GetUpstreamServerUriHeader Found config says USS is MU site
2022-07-14 14:52:12.849 UTC Info WsusService.3 CatalogSyncAgentCore.ExecuteSyncProtocol Server ID is 0a36661a-1c7b-4949-b9cf-724067e7a100
2022-07-14 14:52:13.955 UTC Info w3wp.28 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
2022-07-14 14:52:13.957 UTC Info w3wp.24 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
2022-07-14 14:52:13.956 UTC Info w3wp.20 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
2022-07-14 14:52:13.957 UTC Info w3wp.26 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
2022-07-14 14:52:13.982 UTC Info w3wp.25 ThreadEntry ThreadHelper.ThreadStart
2022-07-14 14:52:13.988 UTC Info w3wp.25 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
2022-07-14 14:52:13.990 UTC Info w3wp.27 ThreadEntry ThreadHelper.ThreadStart
2022-07-14 14:52:13.996 UTC Info w3wp.25 ChangeNotificationDispatcher.InternalEventHandler Get event ConfigurationChange from dispatchmanager
2022-07-14 14:52:14.002 UTC Info w3wp.27 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
2022-07-14 14:52:14.011 UTC Info w3wp.31 Client.OnConfigurationChange Creating a new ClientImplementation because the DB configuration changed
2022-07-14 14:52:14.013 UTC Info w3wp.21 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange
2022-07-14 14:52:14.019 UTC Info w3wp.31 ClientImplementation..ctor Initializing ClientWebService ProcessID = 17796, Process Start Time = 2022/7/13 21:58:14, Product Version = 3.2.7600.325
2022-07-14 14:52:13.990 UTC Info w3wp.32 ThreadEntry ThreadHelper.ThreadStart
2022-07-14 14:52:14.036 UTC Info w3wp.21 AuthorizationManager.GetUpstreamServerUriHeader Found config says USS is MU site
2022-07-14 14:52:14.039 UTC Info w3wp.31 AuthorizationManager.GetUpstreamServerUriHeader Found config says USS is MU site
2022-07-14 14:52:13.990 UTC Info w3wp.29 ThreadEntry ThreadHelper.ThreadStart
2022-07-14 14:52:14.037 UTC Info w3wp.32 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
2022-07-14 14:52:14.054 UTC Info w3wp.29 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
2022-07-14 14:52:14.060 UTC Info w3wp.32 RevisionIdCacheChangeNotificationDispatcher.InternalEventHandler Get event ConfigurationChange from dispatchmanager
2022-07-14 14:52:14.082 UTC Info w3wp.29 AuthorizationManager.GetUpstreamServerUriHeader Found config says USS is MU site
2022-07-14 14:52:14.222 UTC Warning WsusService.3 WebServiceCommunicationHelper.ProcessWebServiceProxyException ProcessWebServiceProxyException found Exception was WebException. Action: Retry. Exception Details: System.Net.WebException: 基础连接已经关闭: 发送时发生错误。 ---> System.IO.IOException: 无法从传输连接中读取数据: 远程主机强迫关闭了一个现有的连接。。 ---> System.Net.Sockets.SocketException: 远程主机强迫关闭了一个现有的连接。
在 System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
--- 内部异常堆栈跟踪的结尾 ---
在 System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
在 System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count)
在 System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
在 System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
在 System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
在 System.Threading.ExecutionContext.runTryCode(Object userData)
在 System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
在 System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
在 System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
在 System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
在 System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
在 System.Net.ConnectStream.WriteHeaders(Boolean async)
--- 内部异常堆栈跟踪的结尾 ---
在 System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
在 System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
在 Microsoft.UpdateServices.ServerSync.ServerSyncCompressionProxy.GetWebResponse(WebRequest webRequest)
在 System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
在 Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetAuthConfig()
在 Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConfig(ServerSyncProxy proxy, WebServiceCommunicationHelper webServiceHelper)
2022-07-14 14:52:15.232 UTC Warning WsusService.3 WebServiceCommunicationHelper.ProcessWebServiceProxyException ProcessWebServiceProxyException found Exception was WebException. Action: Retry. Exception Details: System.Net.WebException: 基础连接已经关闭: 发送时发生错误。 ---> System.IO.IOException: 无法从传输连接中读取数据: 远程主机强迫关闭了一个现有的连接。。 ---> System.Net.Sockets.SocketException: 远程主机强迫关闭了一个现有的连接。
在 System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
--- 内部异常堆栈跟踪的结尾 ---
在 System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
在 System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count)
在 System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
在 System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
在 System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
在 System.Threading.ExecutionContext.runTryCode(Object userData)
在 System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
在 System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
在 System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
在 System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
在 System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
在 System.Net.ConnectStream.WriteHeaders(Boolean async)
--- 内部异常堆栈跟踪的结尾 ---
在 System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
在 System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
在 Microsoft.UpdateServices.ServerSync.ServerSyncCompressionProxy.GetWebResponse(WebRequest webRequest)
在 System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
在 Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetAuthConfig()
在 Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConfig(ServerSyncProxy proxy, WebServiceCommunicationHelper webServiceHelper)- 已移动 Elevenyh 2022年7月18日 1:28
全部回复
-
你好 庆庆子,
感谢你到此论坛上贴。
我发现了以下链接很符合你当前出现的报错,请考虑参考以下链接,下载并安装推荐的更新,看是否能解决当前的问题:
WSUS doesn't sync and returns a certificate error 800B0109 - Configuration Manager | Microsoft Docs
Cause
This problem occurs because the WSUS application on the server is not SHA2-compliant. We recently changed the signing process to sign by using SHA2 only.
Resolution
To fix this problem, download and install Update for Windows Server 2008 R2 for x64-based Systems (KB4484071) that was released on November 12, 2019.
You can check the following logs for the installation progress:
%temp%
MWusCa.log
MWusSetup.log另外,Windows Server 2008R2已经结束支持了,为了避免出现意外的报错,这边还是建议升级到更高的版本。这边推荐一个简单的方式来升级WSUS。 我们可以重新在Windows Server 2016/2019/2022服务器上创建一个新的WSUS role,然后将他设置为副本模式,从将这个Windows Server 2008R2 WSUS服务器同步更新,等更新元数据都同步完成,我们可以将这个新的WSUS服务器设置自主模式, 将计算机指向新的WSUS服务器,或者干脆直接修改计算机名,将新的WSUS服务器的名字直接改成以前的WSUS服务器的名字,这样也可以。
我找到以下相关的case,关于如何迁移WSUS的和迁移的官方链接,也供你参考,希望对您有帮助:
https://community.spiceworks.com/topic/2057997-wsus-migration-from-2012r2-to-2016
https://social.technet.microsoft.com/wiki/contents/articles/508.how-to-move-wsus-from-one-server-to-another.aspx如果以上对你有帮助的话,别忘了标记为答案哦。
感谢你的时间,祝您生活愉快。
诚挚问候,
Rita
Please remember to mark as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.- 已编辑 Rita HuMicrosoft contingent staff 2022年7月18日 3:00
- 已建议为答案 Rita HuMicrosoft contingent staff 2022年7月18日 5:41
-
如果有任何问题,欢迎你随时与我们沟通。希望你一切顺利。
感谢你的时间,祝您生活愉快。
Rita
Please remember to mark as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.- 已编辑 Rita HuMicrosoft contingent staff 2022年7月19日 1:57
-
你好对应的kb补丁包我这边已经打入到2008R2服务器里面了,这边观察了一下出现了新报错
以下为报错内容:
WebException: 无法解析此远程名称: 'sws1.update.microsoft.com'
在 System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
在 System.Net.HttpWebRequest.GetRequestStream()
在 System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
在 Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetAuthConfig()
在 Microsoft.UpdateServices.ServerSync.ServerSyncLib.InternetGetServerAuthConfig(ServerSyncProxy proxy, WebServiceCommunicationHelper webServiceHelper)
在 Microsoft.UpdateServices.ServerSync.ServerSyncLib.Authenticate(AuthorizationManager authorizationManager, Boolean checkExpiration, ServerSyncProxy proxy, Cookie cookie, WebServiceCommunicationHelper webServiceHelper)
在 Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.SyncConfigUpdatesFromUSS()
在 Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect) -
麻烦你试试能不能手动导入更新呢? 现在用https://sws.update.microsoft.com 站点同步,请参考以下链接中的步骤更改WSUS同步站点,然后再确认是否能解决当前的问题:
WSUS synchronization fails with SoapException - Configuration Manager | Microsoft Docs以管理员身份打开PowerShell, 运行以下脚本:
[void][reflection.assembly]::LoadWithPartialName("Microsoft.UpdateServices.Administration") $server = [Microsoft.UpdateServices.Administration.AdminProxy]::GetUpdateServer() $config = $server.GetConfiguration() # Check current settings before you change them $config.MUUrl $config.RedirectorChangeNumber # Update the settings if MUUrl is https://fe2.update.microsoft.com/v6 $config.MUUrl = "https://sws.update.microsoft.com" $config.RedirectorChangeNumber = 4002 $config.Save(); iisreset Restart-Service *Wsus* -v
这个问题还是跟服务器的版本有关,如果可以的话,这边还是建议你升级服务器的版本。
Please remember to mark as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.- 已编辑 Rita HuMicrosoft contingent staff 2022年7月29日 2:14
-
你好 庆庆子,
有一段时间没有收到你的回复了,请问当前情况如何了呢?当前的问题是否解决了?
如果有问题,欢迎随时与我保持联系。如果问题已解决,请考虑分享答案。
Please remember to mark as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.- 已编辑 Rita HuMicrosoft contingent staff 2022年7月29日 2:13