This topic contains 5 replies, has 4 voices, and was last updated by Anonymous 1 year, 3 months ago.
March 15, 2018 at 3:42 am #167460
Just in case anyone else sees this:
After installing the March 2018 Windows Updates for server 2008 both our 2008 servers went offline. The NIC’s had been reset and static configuration had been wiped and the adaptor was configured to use DHCP instead.
Had to manually configure the adaptors and restore their previous static IP settings.
OssianModeratorMarch 15, 2018 at 1:40 pm #191954
It will make headless servers “interesting” for a while
I think it affects a wider range of OSes – Win 7 is certainly mentioned by our friendly vulture: https://www.theregister.co.uk/2018/03/14/microsoft_secures_the_servers_of_the_world/
joeqwertyModeratorMarch 15, 2018 at 8:12 pm #304623
Wow. We had the same issue today. I thought it was a fluke. Thanks for the heads up!March 16, 2018 at 3:13 am #337363
Yes, I saw other OS’s reported as being affected when I researched it later. We also have three 2012 servers and 25 Win7 clients, but it was only the 2008 servers that were affected. As luck would have it (not!), one of those was a domain controller running DHCP amd holding FSMO roles. It gave itself an APIPA address. The other 2008 server (one of our data servers + mail server), acquired a DHCP address – fine for name based resolution, but our messaging software is configured to use IP addresses and it failed spectacularly, not to mention the inbound port forwarding for IMAP and SMTP from the router…
I’ve been installing Windows Updates for more than 20 years and this is the first time a server has been affected. I guess I’ve been lucky!
AnonymousMarch 16, 2018 at 3:41 pm #372098
Just out of curiosity, were the applied updates the ‘Security and Qaulity’ variety, the ‘Preview…’ varity, or the ‘Security Only’ style? About 15 months ago I had a bad experience with a Server 2012 update which broke Explorer, and the fix was to remove the original update and install the ‘Security Only’ update. Been doing it that way ever since on my military customer system, and we’ve been safe so far.
You must be logged in to reply to this topic.