update
4 TopicsBest Practice for Windows Server 2012 R2 and 2016 for 24/7 Operating Manufacturing System.
Hello, We have about 60 Windows 2012 R2 and 2016 servers for 24/7 operating manufacturing lines. These servers seem to have not updated at all since 2018, I have to plan how to update these servers as fast as I can but don't impact or break applications running on it. There are lots of old .Net developed applications and PLC software. Windows 2012 R2 server patch strategy: So, I liked to apply Security Only Updates to the server, but since the patch has only the month's security patches, I have to apply all security patches from 7/2016 which is almost impossible. So, I have to update the server with Monthly Rollup 3/2021 which has cumulative updates from 7/2016. Question 1. Microsoft says Monthly rollup contains other updates with security updates. Does it contain other updates such as Flash, .Net, and others which may break my old .Net applications installed on the server? I like to update the server up to date, but very least impact on the server. Question 2. For critical 24/7 operation servers, do you guys install Security Only Update or Monthly Rollup regularly? Windows 2016 server patch strategy: Microsoft seems they changed the update scheme and there's only Monthly Rollup. Question 3: If then, if you want to patch your server with the least risk, how do you patch your 2016 servers? Just apply Montly rollup and have you find any issue? Thank you in advance. Updates: I patched 30 Windows servers 2012R2/2016 with monthly rollups 1 week ago, no issue so far. -2012 R2: Feb 2021, 0.5GB, took 15 minutes -2016: Feb 2021, 1.5GB (You need to install the latest SSU (Servicing Stack update before applying monthly rollup), took 40 mintues. As I researched, Monthly rollup contains reliability update besides security update, but not .net or other application related updates, so it's quite safe that it will not break existing application states. I had lots of issues the windows update breaking applications with Windows 7/2008, but Microsoft seems doing quite well on making monthly rollup is stable. For .net, it has its own update history and separate channel.Solved3.3KViews0likes4CommentsCookieless browsing broken after update KB4580979
Upon running Windows Update KB4580979, .Net 4.7.2 projects that have the SessionStateSection.Cookiless Property set to AutoDetect no longer functions as expected. Previously, a browser that blocked cookies would be redirected to the same page with the querystring /default.aspx?AspxAutoDetectCookieSupport=1 and upon the system detecting that cookies were not supported it would redirect again to a cookiless session URL e.g. /(X(1)S(adl04pietheradyfawfaqlym))/default.aspx?AspxAutoDetectCookieSupport=1 Since the update, a browser would continously be redirected to /default.aspx?AspxAutoDetectCookieSupport=1 until the redirects exceeded the maximum redirects. Relevant Web.config section: <configuration> <system.web> <sessionState cookieless="AutoDetect" /> </system.web> </configuration> Windows Server 2019 DataCenter Version 1809 OS Build 17763.13695.1KViews2likes4CommentsWindows Server 2019 - Upgrade of certain packages fails - Repair fails as well
Situation: - Windows Server 2019 - Long Term Stable release - some upgrades work in Windows Update - specific Updates fail (regardless whether I install via Win Update or download via Microsoft Catalogue) See below (sorry for German UI) As you can see: KB4586082 -- SUCCESS KB4586839 -- FAIL I have tried repair using sfc /scannow --> no problems found dism .... (see below) --> problem found BUT repair via /restoreHealth fails Any ideas how to solve this without data loss and not too long downtime? Today again a rollback:Windows 2008R2 RAS does not works after install KB4524157
I'm using a WINDOWS 2008R2 STD as a VPN (PPTP remote access server) server. The clients are connect to the shared folder (SMB1.0) in internal network via WIN 2008 server with PPTP. Today morning, I found that every clients are can not access to the shared folder on the internal network. The clients were assigned internal IP correctly. And, the shared folders were could access at Windows 2008 server. Ping from internal server to the client was available. But, could not access to the shared folder on the internal network. I found KB4524157 had installed during the weekend. After remove the KB4524157, The access became normal. So, I removed KB4524157 temporally now. May I have advice about this? The clients are using Windows7, Windows10. Regards.1KViews0likes0Comments