Patching is important. VERY important. But quite simply, software is complex. And sometimes, even testing doesn't catch everything. This is why *I* don't apply Microsoft patches for a minimum of 10 days (second Friday after patch Tuesday):
https://blogs.msdn.microsoft.com/dotnet/2018/07/20/advisory-on-july-2018-net-framework-updates/
That said, if you have the resources to test your own systems, it's another reason you should be testing patches. Using a subset of systems, test group, etc.
https://blogs.msdn.microsoft.com/dotnet/2018/07/20/advisory-on-july-2018-net-framework-updates/
That said, if you have the resources to test your own systems, it's another reason you should be testing patches. Using a subset of systems, test group, etc.
1 Comment
Comment
I agree with Lee in large. I do updates on my machines on Patch Tuesday. Clients follow later as Lee suggests.
Do NOT overlook BIOS in 2018. BIOS, Chipset, Video and Network all need updating and that may kick off even more Windows Updates (I have seen that happen).
And we BOTH agree here: Update your systems.
Do NOT overlook BIOS in 2018. BIOS, Chipset, Video and Network all need updating and that may kick off even more Windows Updates (I have seen that happen).
And we BOTH agree here: Update your systems.
Recommended Posts
Exchange Server Roadmap Update.
MS have moved the release date for the next version of Exchange Server to the second half of 2025.
It requires Server and CAL licenses and will be accessible only to customers with Software Assurance,
https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-server-roadmap-update/ba-p/3421389
MS have moved the release date for the next version of Exchange Server to the second half of 2025.
It requires Server and CAL licenses and will be accessible only to customers with Software Assurance,
https://techcommunity.microsoft.com/t5/exchange-team-blog/exchange-server-roadmap-update/ba-p/3421389
