Greetings -
We got bit by this back in June, where we have a mix of 2016 and 2012R2 servers. and during the June Microsoft updates, functionality of the console started to not work. This was due to mismatched versions. We have resolved it since then to get it up and running proper but since then again, we have been very wary of doing ANY patches from Microsoft, we just been doing important updates. But its very time consuming as we look at each KB to make sure it does not contain any .net changes. Because Microsoft can't be taxed with it showing .net update it shows us KB190393913 ect. And running 2 different versions of windows on our polling environment makes it much more confusing.
I assume when we get the other polling engines to 2016 this will go away or the risk will, but what do we do in the meantime. I want to keep things updated as much as possible but don't want to risk part of our system being unusable because of a chance at a .net mismatch.
For example we made sure all polling engines had the same version, installed VIA the same source, the registry even reported them as the SAME version of .net however, this was just the label as the 2012R2 servers had a different version to match the 2016 .net versions. You could not use the same source across all servers it would create a mismatch. Which is extremely confusing.
I tried blocking .net installs but i think it only applies to 4.7 being installed and not 4.6 being updated.
Any advice is greatly appreciated while we work on getting the polling engines up to 2016, because the main polling engine is on 2012r2 is why the wait
