Re: Fix
Even before the drop-off in quality control of MS patches there seems to have been in the last couple of years we still deploy all changes in a test environment first, instead of blindly making changes to production machines.
This was why we found it in testing. We have now delayed these patches to production 2008R2 machines and will keep an eye on the KB for more information. We don't have that many 2008R2 servers left now though anyway, we have been migrating away from it. So far we haven't found any issues with this months patches for 2012/2016.
I was just providing a fix for anyone who found themselves in the situation where the patch had gone out to a 2008R2 server with a VMXNET3 NIC.
You have 300+ 2008R2 servers to manage? I hope you test changes to them first unless they are not doing anything important.
Biting the hand that feeds IT
