2019年4月27日 星期六

WSUS Clients 無法偵測回報問題?

WSUS Clients 無法偵測回報問題?


WSUS Server安裝好某些Clients一直無法偵測回報,到最後變成所有電腦不能回報,移除WSUS Server再安裝還是一樣,這個問題擱置了很久,終於等到適當時機好好地研究一番,Google了很多資料,了解原理後反覆對照Log日誌檔,終於找出正確的解決方
式。
按照Issues with Clients Not Reporting建議,檢查WSUS Server是否能正常連接?

檢查C:\Windows\WindowsUpdate.log發現0x80244019錯誤,有很多辦法但沒有說明原理,很難判斷是否有效?只能一一嘗試,首先依照如何將 Windows Update 代理程式更新為最新版本更新Windows Update Agent7.6.7600.320無效,但卻忽略了最基本的連線問題,後來在Clients not registering with WSUS server-Completely out of ideas提到了所謂的正確的連線電腦名稱才恍然大悟,想起IPnetbios名稱與FQDN名稱的差異就很容易解決這個問題
https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiX9hP9sJBTqtJRPgyCf_31MQt86goYkzl5doZVHxe5NmE9b4PO6aTzdprs_DFHpvpT314FGsu17xewDyBu5QQ1UHmRsDGN85ZToy55bHW8iBRPx1W3e_XQhaxlSKwENWzRnlb10Km0j_KE/s400/002.jpg

-------------------------------------------------------------------------------------------------------------------
584 1c14 Agent   * WSUS server: http://10.254.254.254
584 1c14 Agent   * WSUS status server: http://10.254.254.254
-------------------------------------------------------------------------------------------------------------------
584 1ebc PT WARNING: GetConfig failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
584 1ebc PT WARNING: PTError: 0x80244019
584 1ebc PT WARNING: GetConfig_WithRecovery failed: 0x80244019
584 1ebc PT WARNING: RefreshConfig failed: 0x80244019
584 1ebc PT WARNING: RefreshPTState failed: 0x80244019
584 1ebc PT WARNING: PTError: 0x80244019
584 1ebc Report WARNING: Reporter failed to upload events with hr = 80244019.
584 1ebc PT WARNING: GetConfig failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
584 1ebc PT WARNING: PTError: 0x80244019
584 1ebc PT WARNING: GetConfig_WithRecovery failed: 0x80244019
584 1ebc PT WARNING: RefreshConfig failed: 0x80244019
584 1ebc PT WARNING: RefreshPTState failed: 0x80244019
584 1ebc PT WARNING: PTError: 0x80244019
584 1ebc Report WARNING: Reporter failed to upload events with hr = 80244019.
-------------------------------------------------------------------------------------------------------------------
接著出現如下錯誤訊息,其實應該不是錯誤,在不了解原理狀態下很容易誤判。
628 1810 PT WARNING: Exceeded max server round trips: 0x80244010
628 1810 PT WARNING: Sync of Updates: 0x80244010
628 1810 PT WARNING: SyncServerUpdatesInternal failed: 0x80244010
628 1810 Agent   * WARNING: Failed to synchronize, error = 0x80244010
628 1810 Agent   * WARNING: Exit code = 0x80244010
628 1810 Agent *********
628 1810 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
628 1810 Agent *************
628 1810 Agent WARNING: WU client failed Searching for update with error 0x80244010
628 86c AU >>##  RESUMED  ## AU: Search for updates [CallId = {E3EF2FF6-9764-47A0-9075-622CAAFBB7CB}]
628 86c AU   # WARNING: Search callback failed, result = 0x80244010
628 86c AU   # WARNING: Failed to find updates with error code 80244010
628 86c AU #########
628 86c AU ##  END  ##  AU: Search for updates [CallId = {E3EF2FF6-9764-47A0-9075-622CAAFBB7CB}]
628 86c AU #############
628 86c AU Successfully wrote event for AU health state:0
628 86c AU AU setting next detection timeout to 2016-01-22 06:42:11
628 86c AU Successfully wrote event for AU health state:0
628 86c AU Successfully wrote event for AU health state:0
-------------------------------------------------------------------------------------------------------------------
第一行應該已經提示出這一個錯誤訊息源自於WSUS Server本身的限制,在WSUS clients fail with WARNING: SyncServerUpdatesInternal failed: 0x80244010文章提到WSUS Server只允許WSUS Client一次200trip(我稱為往返)而且無法設定改數值,WSUS一次可以給200Kupdate matadata大約等於小型更新約10個,如果較大型更新的話,也許一個更新就要一個trip更新當然不只200個就會超過出現錯誤了,好消息是當第二次同步更新時不會從頭開始,會從剩下的部分繼續就放著跑就可以了,如果想要快一點可更改更新頻率讓其快一點。
https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgfa9jasl3zwCygxeB53CogbE_R8BOLdpJbRhW7KaICvGlDSZMb8y1cXJW-YodflUV-ivPQygALrukca-ZvwEnNAnCWnGfw2Vk5XBM-BDZ-YdHmDms6N_R_hemPzeEBUMsZE5S8wlFWUR-6/s400/update+frequency.jpg

最後WSUS Clients還有很多要解決的問題,官方有隻DOS Script to Reset Windows Update Agent,會把問題通通重置,算節省時間的一種做法,給各位參考。




沒有留言:

張貼留言