- Copy internal post link
- Copy external post link
- Report article
https://administrator.de/forum/wsus-probleme-nach-upgrade-auf-windows-server-2016-384371.html
[content:384371]
WSUS Probleme nach Upgrade auf Windows Server 2016
hatte bis vor kurzem einen WSUS mit Windows Server 2012.
Vor kurzem ein Upgrade auf Windows Server 2016 durchgeführt
Sieht soweit eigentlich alles gut aus, allerdings wollen meine Clients keine Updates mehr installieren (sei es Server 2016 oder Windows 7 Clients)
Beide zeigen den Windows Update Fehlercode 0x80244019
Jemand eine Idee, woran das liegt?
Content-Key: 384371
Url: https://administrator.de/contentid/384371
Printed on: April 17, 2024 at 22:04 o'clock
- Comment overview - Please log in
- Copy internal comment link
- Copy external comment link
- To the beginning of the comments
https://administrator.de/forum/wsus-probleme-nach-upgrade-auf-windows-server-2016-384371.html#comment-1306433
[content:384371#1306433]
Jemand eine Idee, woran das liegt?
Gruß
- Copy internal comment link
- Copy external comment link
- To the beginning of the comments
https://administrator.de/forum/wsus-probleme-nach-upgrade-auf-windows-server-2016-384371.html#comment-1306462
[content:384371#1306462]
- Client wie auch WSUS neu gestartet
- geprüft ob der Client den WSUS erreichen kann
- den Client am WSUS entfernt und neu anmelden lassen
- Copy internal comment link
- Copy external comment link
- To the beginning of the comments
https://administrator.de/forum/wsus-probleme-nach-upgrade-auf-windows-server-2016-384371.html#comment-1306463
[content:384371#1306463]
https://der-eigelb-laden.de/anniversary-upgrade-1607-ueber-wsus-schlaegt ...
- Copy internal comment link
- Copy external comment link
- To the beginning of the comments
https://administrator.de/forum/wsus-probleme-nach-upgrade-auf-windows-server-2016-384371.html#comment-1306469
[content:384371#1306469]
Noch nicht mal der WSUS kann Updates installieren - selber Fehlercode
- Copy internal comment link
- Copy external comment link
- To the beginning of the comments
https://administrator.de/forum/wsus-probleme-nach-upgrade-auf-windows-server-2016-384371.html#comment-1306480
[content:384371#1306480]
Hast du mal in das WindowsUpdate log am Client geschaut:
https://support.microsoft.com/en-in/help/902093/how-to-read-the-windowsu ...
Gruß
em-pie
- Copy internal comment link
- Copy external comment link
- To the beginning of the comments
https://administrator.de/forum/wsus-probleme-nach-upgrade-auf-windows-server-2016-384371.html#comment-1306546
[content:384371#1306546]
2018-08-25 14:12:15:652 464 1210 Misc =========== Logging initialized (build: 7.6.7601.24085, tz: +0200) ===========
2018-08-25 14:12:15:652 464 1210 Misc = Process: C:\Windows\system32\svchost.exe
2018-08-25 14:12:15:652 464 1210 Misc = Module: c:\windows\system32\wuaueng.dll
2018-08-25 14:12:15:652 464 1210 Service *************
2018-08-25 14:12:15:652 464 1210 Service ** START ** Service: Service startup
2018-08-25 14:12:15:652 464 1210 Service *********
2018-08-25 14:12:15:677 464 1210 Agent * WU client version 7.6.7601.24085
2018-08-25 14:12:15:677 464 1210 Agent * Base directory: C:\Windows\SoftwareDistribution
2018-08-25 14:12:15:677 464 1210 Agent * Access type: No proxy
2018-08-25 14:12:15:678 464 1210 Agent * Network state: Connected
2018-08-25 14:12:25:148 464 b88 Report CWERReporter::Init succeeded
2018-08-25 14:12:25:148 464 b88 Agent *********** Agent: Initializing Windows Update Agent ***********
2018-08-25 14:12:25:148 464 b88 Agent * Prerequisite roots succeeded.
2018-08-25 14:12:25:148 464 b88 Agent *********** Agent: Initializing global settings cache ***********
2018-08-25 14:12:25:148 464 b88 Agent * WSUS server: http://DE-NE-S-WSUS.xxx.dom:8530
2018-08-25 14:12:25:148 464 b88 Agent * WSUS status server: http://DE-NE-S-WSUS.xxx.dom:8530
2018-08-25 14:12:25:148 464 b88 Agent * Target group: DE-NE-Workstation
2018-08-25 14:12:25:148 464 b88 Agent * Windows Update access disabled: No
2018-08-25 14:12:25:149 464 b88 DnldMgr Download manager restoring 0 downloads
2018-08-25 14:12:25:150 464 b88 AU ########### AU: Initializing Automatic Updates ###########
2018-08-25 14:12:25:150 464 b88 AU # WSUS server: http:{{comment_single_line_double_slash:0}}
2018-08-25 14:12:25:150 464 b88 AU # Detection frequency: 22
2018-08-25 14:12:25:150 464 b88 AU # Target group: DE-NE-Workstation
2018-08-25 14:12:25:150 464 b88 AU # Approval type: Pre-install notify (Policy)
2018-08-25 14:12:25:150 464 b88 AU # Auto-install minor updates: No (User preference)
2018-08-25 14:12:25:150 464 b88 AU # Will interact with non-admins (Non-admins are elevated (User preference))
2018-08-25 14:12:25:449 464 1210 Report *********** Report: Initializing static reporting data ***********
2018-08-25 14:12:25:449 464 1210 Report * OS Version = 6.1.7601.1.0.65792
2018-08-25 14:12:25:449 464 1210 Report * OS Product Type = 0x00000030
2018-08-25 14:12:25:459 464 1210 Report * Computer Brand = Dell Inc.
2018-08-25 14:12:25:459 464 1210 Report * Computer Model = OptiPlex 790
2018-08-25 14:12:25:461 464 1210 Report * Bios Revision = A21
2018-08-25 14:12:25:461 464 1210 Report * Bios Name = Default System BIOS
2018-08-25 14:12:25:461 464 1210 Report * Bios Release Date = 2018-02-12T00:00:00
2018-08-25 14:12:25:461 464 1210 Report * Locale ID = 1031
2018-08-25 14:12:25:521 464 b88 AU Successfully wrote event for AU health state:0
2018-08-25 14:12:25:521 464 b88 AU Initializing featured updates
2018-08-25 14:12:25:521 464 b88 AU Found 0 cached featured updates
2018-08-25 14:12:25:521 464 b88 AU Successfully wrote event for AU health state:0
2018-08-25 14:12:25:522 464 b88 AU Successfully wrote event for AU health state:0
2018-08-25 14:12:25:522 464 b88 AU AU finished delayed initialization
2018-08-25 14:12:26:636 464 b88 AU Triggering AU detection through DetectNow API
2018-08-25 14:12:26:636 464 b88 AU Triggering Online detection (interactive)
2018-08-25 14:12:26:637 464 1210 AU #############
2018-08-25 14:12:26:637 464 1210 AU ## START ## AU: Search for updates
2018-08-25 14:12:26:637 464 1210 AU #########
2018-08-25 14:12:26:639 464 1210 AU <<## SUBMITTED ## AU: Search for updates [CallId = {8D6B0EBF-9761-4D8E-9873-BF5251D27C30}]
2018-08-25 14:12:26:639 464 ff4 Agent *************
2018-08-25 14:12:26:639 464 ff4 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2018-08-25 14:12:26:639 464 ff4 Agent *********
2018-08-25 14:12:26:639 464 ff4 Agent * Online = Yes; Ignore download priority = No
2018-08-25 14:12:26:639 464 ff4 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"
2018-08-25 14:12:26:639 464 ff4 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2018-08-25 14:12:26:639 464 ff4 Agent * Search Scope = {Machine}
2018-08-25 14:12:26:639 464 ff4 Setup Checking for agent SelfUpdate
2018-08-25 14:12:26:640 464 ff4 Setup Client version: Core: 7.6.7601.24085 Aux: 7.6.7601.24085
2018-08-25 14:12:26:677 464 ff4 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
2018-08-25 14:13:06:691 464 ff4 Misc Microsoft signed: NA
2018-08-25 14:13:06:703 464 ff4 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMPACB5.tmp with dwProvFlags 0x00000080:
2018-08-25 14:13:36:715 464 ff4 Misc Microsoft signed: NA
2018-08-25 14:13:36:726 464 ff4 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
2018-08-25 14:13:36:739 464 ff4 Misc Microsoft signed: NA
2018-08-25 14:13:36:778 464 ff4 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
2018-08-25 14:13:36:792 464 ff4 Misc Microsoft signed: NA
2018-08-25 14:13:36:842 464 ff4 Setup Determining whether a new setup handler needs to be downloaded
2018-08-25 14:13:36:842 464 ff4 Setup SelfUpdate handler is not found. It will be downloaded
2018-08-25 14:13:36:842 464 ff4 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320"
2018-08-25 14:13:36:845 464 ff4 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
2018-08-25 14:13:36:845 464 ff4 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
2018-08-25 14:13:36:860 464 ff4 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
2018-08-25 14:13:36:860 464 ff4 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
2018-08-25 14:13:36:882 464 ff4 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
2018-08-25 14:13:36:882 464 ff4 Setup SelfUpdate check completed. SelfUpdate is NOT required.
2018-08-25 14:13:37:007 464 ff4 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2018-08-25 14:13:37:007 464 ff4 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://DE-NE-S-WSUS.xxx.dom:8530/ClientWebService/client.asmx
2018-08-25 14:13:37:047 464 ff4 PT WARNING: Cached cookie has expired or new PID is available
2018-08-25 14:13:37:047 464 ff4 PT Initializing simple targeting cookie, clientId = 237949a1-c51e-4c5a-bf3f-d8702a56ce31, target group = DE-NE-Workstation, DNS name = de-ne-pc-0029.xxx.dom
2018-08-25 14:13:37:047 464 ff4 PT Server URL = http://DE-NE-S-WSUS.xxx.dom:8530/SimpleAuthWebService/SimpleAuth.asmx
2018-08-25 14:14:20:553 464 ff4 PT WARNING: Exceeded max server round trips: 0x80244010
2018-08-25 14:14:20:553 464 ff4 PT WARNING: Sync of Updates: 0x80244010
2018-08-25 14:14:20:553 464 ff4 PT WARNING: SyncServerUpdatesInternal failed: 0x80244010
2018-08-25 14:14:20:553 464 ff4 Agent * WARNING: Failed to synchronize, error = 0x80244010
2018-08-25 14:14:20:554 464 ff4 Agent * WARNING: Exit code = 0x80244010
2018-08-25 14:14:20:554 464 ff4 Agent *********
2018-08-25 14:14:20:554 464 ff4 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2018-08-25 14:14:20:554 464 ff4 Agent *************
2018-08-25 14:14:20:554 464 ff4 Agent WARNING: WU client failed Searching for update with error 0x80244010
2018-08-25 14:14:20:556 464 948 AU >>## RESUMED ## AU: Search for updates [CallId = {8D6B0EBF-9761-4D8E-9873-BF5251D27C30}]
2018-08-25 14:14:20:556 464 948 AU # WARNING: Search callback failed, result = 0x80244010
2018-08-25 14:14:20:556 464 948 AU # WARNING: Failed to find updates with error code 80244010
2018-08-25 14:14:20:556 464 948 AU #########
2018-08-25 14:14:20:556 464 948 AU ## END ## AU: Search for updates [CallId = {8D6B0EBF-9761-4D8E-9873-BF5251D27C30}]
2018-08-25 14:14:20:556 464 948 AU #############
2018-08-25 14:14:20:556 464 948 AU Successfully wrote event for AU health state:0
2018-08-25 14:14:20:556 464 948 AU AU setting next detection timeout to 2018-08-25 17:14:20
2018-08-25 14:14:20:556 464 948 AU Successfully wrote event for AU health state:0
2018-08-25 14:14:20:557 464 948 AU Successfully wrote event for AU health state:0
2018-08-25 14:14:25:554 464 ff4 Report REPORT EVENT: {945C0043-A5EE-49CB-B303-FFEB2B9A5F90} 2018-08-25 14:14:20:553+0200 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244010 AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x80244010.
2018-08-25 14:14:25:584 464 ff4 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
2018-08-25 14:14:25:584 464 ff4 Report WER Report sent: 7.6.7601.24085 0x80244010(0) 0000000-0000-0000-0000-000000000000 Scan 0 1 AutomaticUpdates {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0
- Copy internal comment link
- Copy external comment link
- To the beginning of the comments
https://administrator.de/forum/wsus-probleme-nach-upgrade-auf-windows-server-2016-384371.html#comment-1306583
[content:384371#1306583]
Problem bleibt :/
- Copy internal comment link
- Copy external comment link
- To the beginning of the comments
https://administrator.de/forum/wsus-probleme-nach-upgrade-auf-windows-server-2016-384371.html#comment-1306739
[content:384371#1306739]
Wenn Du den neu aufsetzt, wird dir vermutlich nahegelegt worden sein, https zu verwenden, was du auch unbedingt tun solltest. Danach muss die GPO, welche die Clienteinstellungen für WSUS verteilt, auf https angepasst werden.
Teste bitte auch mal mit Windows 10 als Client.
- Copy internal comment link
- Copy external comment link
- To the beginning of the comments
https://administrator.de/forum/wsus-probleme-nach-upgrade-auf-windows-server-2016-384371.html#comment-1306896
[content:384371#1306896]
wichtiger ist erst mal, dass der WSUS Server wieder funktioniert :/
bekomme den Fehler allerdings nicht weg
Es hat ja vorher ohne SSL auch funktioniert.
Tatsächlich konnt ein Windows 10 Client die Updates ohne Probleme herunterladen und installieren Oo
- Copy internal comment link
- Copy external comment link
- To the beginning of the comments
https://administrator.de/forum/wsus-probleme-nach-upgrade-auf-windows-server-2016-384371.html#comment-1306899
[content:384371#1306899]
Alle Clients uns Server bekommen nun Updates und installieren diese auch.
Aber keine Ahnung wieso oO
- Copy internal comment link
- Copy external comment link
- To the beginning of the comments
https://administrator.de/forum/wsus-probleme-nach-upgrade-auf-windows-server-2016-384371.html#comment-1306901
[content:384371#1306901]