{"id":206839,"date":"2018-07-20T02:47:03","date_gmt":"2018-07-20T00:47:03","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=206839"},"modified":"2019-02-05T15:00:03","modified_gmt":"2019-02-05T14:00:03","slug":"windows-server-2016-hohe-cpu-last-mit-update-kb4345418-kb4054566","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2018\/07\/20\/windows-server-2016-hohe-cpu-last-mit-update-kb4345418-kb4054566\/","title":{"rendered":"Windows Server 2012 R2 und 2016: Hohe CPU-Last mit Update KB4345418 \/ KB4054566"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline;\" src=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2013\/03\/winb.jpg\" width=\"58\" height=\"58\" align=\"left\" \/>[<a href=\"https:\/\/borncity.com\/win\/2018\/07\/20\/windows-server-2012-r2-2016-high-cpu-load-with-update-kb4345418-kb4054566\/\" target=\"_blank\" rel=\"noopener\">English<\/a>]Das Revisions-Update KB4345418 (oder das .NET-Framework 4.7.2 Update KB4054566) vom 16. Juli 2018 scheint unter Windows Server 2012 R2 und Windows Server 2016 zu Problemen zu f\u00fchren. Es wird in bestimmten Szenarien (Verwendung von AADConnect) von einer hohen CPU-Last berichtet. Auch RDS-Verbindungen machen wohl Probleme. Hier einige Informationen.<\/p>\n<p><!--more--><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/ssl-vg03.met.vgwort.de\/na\/d5fca89c69f5498ea9a9d81387b403d2\" alt=\"\" width=\"1\" height=\"1\" \/>Microsoft hat zum 16. Juli 2018 eine Reihe Updates f\u00fcr Windows 10 freigegeben, die unter anderem Bluescreens beheben sollen (siehe meinen Blog-Beitrag <a href=\"https:\/\/borncity.com\/blog\/2018\/07\/17\/windows-10-update-revisionen-zum-16-juli-2018\/\">Windows 10: Update-Revisionen zum 16. Juli 2018<\/a>). Mit dabei war auch Update <a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4345418\" target=\"_blank\" rel=\"noopener\">KB4345418<\/a> f\u00fcr Windows 10 V1607 (LTSB) und Windows Server 2016. Das Update sollte vor allem die nachfolgend genannten Bugs beheben:<\/p>\n<ul>\n<li>Addresses an issue that may cause some devices running network monitoring workloads to receive the 0xD1 Stop error because of a race condition after installing the July update.<\/li>\n<li>Addresses an issue with the DHCP Failover server that may cause enterprise clients to receive an invalid configuration when requesting a new IP address. This results in a loss of connectivity.<\/li>\n<li>Addresses an issue that may cause the restart of the SQL Server service to fail occasionally with the error, \"Tcp port is already in use\".<\/li>\n<li>Addresses an issue that occurs when an administrator tries to stop the World Wide Web Publishing Service (W3SVC). The W3SVC remains in a \"stopping\" state, but cannot fully stop or it cannot be restarted.<\/li>\n<\/ul>\n<p>Gerade die BlueScreens, das SQL-Server-Service-Programm, das World Wide Web Publishing Service (W3SVC)-Problem und das IP-Adress-Zuteilungsproblem bei DHCP-Failover-Servern waren in Produktionsumgebungen 't\u00f6dlich'. Das Update wurde per Windows Update verteilt, ist aber auch im <a href=\"http:\/\/catalog.update.microsoft.com\/v7\/site\/Search.aspx?q=KB4345418\" target=\"_blank\" rel=\"noopener\">Microsoft Update Catalog<\/a> erh\u00e4ltlich. Administratoren d\u00fcrften daher dieses Update zeitnah installiert haben.<\/p>\n<h2>AADConnect funktioniert nicht<\/h2>\n<p>Administratoren kamen aber schnell zum Schluss, dass AADConnect (Microsoft Azure Active Directory Connect) nach Installation dieses Updates nicht mehr funktioniert. Cryta T. Lacey (@PhantomofMobile) hat mich <a href=\"https:\/\/twitter.com\/PhantomofMobile\/status\/1019677940747911168\" target=\"_blank\" rel=\"noopener\">per Twitter<\/a> auf das Problem aufmerksam gemacht.<\/p>\n<blockquote class=\"twitter-tweet\" data-lang=\"de\">\n<p dir=\"ltr\" lang=\"en\">Azure AD Connect Health Sync Monitor High CPU Usage<\/p>\n<p>Thank You: <a href=\"https:\/\/twitter.com\/SBSDiva?ref_src=twsrc%5Etfw\">@SBSDiva<\/a><\/p>\n<p>ICYMI: <a href=\"https:\/\/twitter.com\/SBSDiva?ref_src=twsrc%5Etfw\">@SBSDiva<\/a> <a href=\"https:\/\/twitter.com\/AdminKirsty?ref_src=twsrc%5Etfw\">@AdminKirsty<\/a> <a href=\"https:\/\/twitter.com\/woodyleonhard?ref_src=twsrc%5Etfw\">@woodyleonhard<\/a> <a href=\"https:\/\/twitter.com\/thurrott?ref_src=twsrc%5Etfw\">@thurrott<\/a> <a href=\"https:\/\/twitter.com\/maryjofoley?ref_src=twsrc%5Etfw\">@maryjofoley<\/a> <a href=\"https:\/\/twitter.com\/bdsams?ref_src=twsrc%5Etfw\">@bdsams<\/a> <a href=\"https:\/\/twitter.com\/mehedih_?ref_src=twsrc%5Etfw\">@mehedih_<\/a> <a href=\"https:\/\/twitter.com\/ruthm?ref_src=twsrc%5Etfw\">@ruthm<\/a> <a href=\"https:\/\/twitter.com\/etguenni?ref_src=twsrc%5Etfw\">@etguenni<\/a> <a href=\"https:\/\/twitter.com\/SwiftOnSecurity?ref_src=twsrc%5Etfw\">@SwiftOnSecurity<\/a> <a href=\"https:\/\/twitter.com\/pcper?ref_src=twsrc%5Etfw\">@pcper<\/a> <a href=\"https:\/\/twitter.com\/SGgrc?ref_src=twsrc%5Etfw\">@SGgrc<\/a> <a href=\"https:\/\/twitter.com\/MalwareJake?ref_src=twsrc%5Etfw\">@MalwareJake<\/a> @GossiTheDog <a href=\"https:\/\/twitter.com\/ryanshrout?ref_src=twsrc%5Etfw\">@ryanshrout<\/a> <a href=\"https:\/\/twitter.com\/JobCacka?ref_src=twsrc%5Etfw\">@JobCacka<\/a> <a href=\"https:\/\/t.co\/KaDWuG0Ngg\">pic.twitter.com\/KaDWuG0Ngg<\/a><\/p>\n<p>\u2014 Crysta T. Lacey (@PhantomofMobile) <a href=\"https:\/\/twitter.com\/PhantomofMobile\/status\/1019677940747911168?ref_src=twsrc%5Etfw\">18. Juli 2018<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p>Ein Nutzer hat auf askwoody.com <a href=\"https:\/\/www.askwoody.com\/2018\/aadconnect-still-isnt-working-with-the-latest-server-2016-patch\/\" target=\"_blank\" rel=\"noopener\">hier<\/a> auf das Problem hingewiesen und folgende Informationen gepostet.<\/p>\n<blockquote><p>Just wanted to let you know of another issue that seems to be biting a lot of people with the July updates.<\/p>\n<p>Even with the updated patch on Server 2016 (KB4345418) is still causing an issue with AADConnect servers that triggers a 100% CPU spike on some of the Health and Reporting monitoring services, only fix at this point is to uninstall the latest update. It seems to impact at least 2012 and 2016 servers. \u2026<\/p>\n<p>We just cancelled of our Windows patching for the month, hope MS gets this sorted out soon. What a mess.<\/p><\/blockquote>\n<p>Der Benutzer verweist auf <a href=\"https:\/\/social.msdn.microsoft.com\/Forums\/en-US\/e9b621f6-f38c-488e-8fcb-ff85d406f256\/azure-ad-connect-health-sync-monitor-high-cpu-usage?forum=WindowsAzureAD\" target=\"_blank\" rel=\"noopener\">diesen MSDN-Forenthread<\/a>, wo weitere Informationen zum Fehler zu finden sind.<\/p>\n<blockquote><p>Hello.\u00a0 I have Azure AD Connect installed on my server to sync our on-premise domain with Office 365 and I'm noticing the Azure AD Connect Health Sync Monitoring Service is always running high CPU usage.\u00a0 The actual process is<\/p>\n<p>Microsoft.Identity.Health.AadSync.MonitoringAgent.Startup.exe<\/p>\n<p>Is there a reason for this or a way to fix it? Right now, I'm just stopping the Azure AD Connect Health Sync Monitoring Service(AzureADConnectHealthSyncMonitor) and my resources go back to normal.\u00a0 I'm running Azure AD Connect 1.1.819.0 so it is the latest version.\u00a0 If I restart the service, things are normal for a few minutes before this process spikes again.<\/p><\/blockquote>\n<p>Es kommt zu einer hohen CPU-Last, und das wird auch von anderen Nutzern best\u00e4tigt. Das gilt sowohl f\u00fcr Windows Server 2016, welcher im urspr\u00fcnglichen Post erw\u00e4hnt wurde, als auch f\u00fcr Windows Server 2012 R2.<\/p>\n<p>Ein Nutzer berichtet im Thread zu obigem Problem, dass er auf Windows Server 2012 R2 das Problem ebenfalls hatte, dieses aber durch Deinstallation des .NET-Framework 4.7.2-Update KB4054566 l\u00f6sen konnte. Vielleicht hilft das euch weiter.<\/p>\n<h2>Schwarzer Bildschirm bei RDS-Verbindungen<\/h2>\n<p>Matt Wilkinson hat <a href=\"https:\/\/twitter.com\/bigfoot780\/status\/1019616593444294656\" target=\"_blank\" rel=\"noopener\">per Twitter<\/a> auf ein weiteres Problem mit Update KB4345418 hingewiesen:<\/p>\n<blockquote class=\"twitter-tweet\" data-lang=\"de\">\n<p dir=\"ltr\" lang=\"en\"><a href=\"https:\/\/twitter.com\/woodyleonhard?ref_src=twsrc%5Etfw\">@woodyleonhard<\/a> KB 4345418 is causing issues on Server 2016 RDS with a black screen upon login. Have mitigated this issue with a script to delete firewall rules that are created per user. Black screen returned with this update.<\/p>\n<p>\u2014 Matt Wilkinson (@bigfoot780) <a href=\"https:\/\/twitter.com\/bigfoot780\/status\/1019616593444294656?ref_src=twsrc%5Etfw\">18. Juli 2018<\/a><\/p><\/blockquote>\n<p><script async src=\"https:\/\/platform.twitter.com\/widgets.js\" charset=\"utf-8\"><\/script><\/p>\n<p>Er spricht aber von Problemen mit Remote Desktop Services (RDS). Windows Server 2016 reagiert mit einem schwarzen Bildschirm, wenn man sich per RDS verbindet. Irgend jemand, der diese Probleme best\u00e4tigen kann?<\/p>\n<p><strong>\u00c4hnliche Artikel:<br \/>\n<\/strong><a href=\"https:\/\/borncity.com\/blog\/2018\/07\/11\/net-framework-update-kb4340558-fehlerhaft-error-0x80092004\/\">.Net Framework-Update KB4340558 fehlerhaft (Error 0x80092004)?<\/a><br \/>\n<a href=\"https:\/\/borncity.com\/blog\/2018\/07\/12\/windows-10-version-1607-dhcp-bug-in-update-kb4338814\/\">Windows 10 Version 1607: DHCP-Bug in Update KB4338814<\/a><br \/>\n<a href=\"https:\/\/borncity.com\/blog\/2018\/07\/13\/kb4018385-zurckgezogen-weitere-patchday-probleme\/\">KB4018385 zur\u00fcckgezogen &amp; weitere Patchday-Probleme<\/a><br \/>\n<a href=\"https:\/\/borncity.com\/blog\/2018\/07\/16\/iis-webserver-streikt-nach-updates\/\">IIS-Webserver streikt nach Update KB4338818<\/a><br \/>\n<a href=\"https:\/\/borncity.com\/blog\/2018\/07\/14\/microsoft-und-das-juli-2018-patch-desaster-updates-stoppen\/\">Microsoft und das Juli 2018-Patch-Desaster \u2013 Updates stoppen?<\/a><br \/>\n<a href=\"https:\/\/borncity.com\/blog\/2018\/08\/16\/update-rollup-fr-azure-file-sync-agent-august-2018\/\" rel=\"bookmark\">Update Rollup f\u00fcr Azure File Sync Agent (August 2018)<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>[English]Das Revisions-Update KB4345418 (oder das .NET-Framework 4.7.2 Update KB4054566) vom 16. Juli 2018 scheint unter Windows Server 2012 R2 und Windows Server 2016 zu Problemen zu f\u00fchren. Es wird in bestimmten Szenarien (Verwendung von AADConnect) von einer hohen CPU-Last berichtet. &hellip; <a href=\"https:\/\/borncity.com\/blog\/2018\/07\/20\/windows-server-2016-hohe-cpu-last-mit-update-kb4345418-kb4054566\/\">Weiterlesen <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[185,2557],"tags":[7113,7140,24,4315,4364],"class_list":["post-206839","post","type-post","status-publish","format-standard","hentry","category-update","category-windows-server","tag-kb4054566","tag-kb4345418","tag-problem","tag-update","tag-windows-server"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/206839","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/comments?post=206839"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/206839\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=206839"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=206839"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=206839"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}