Best answer by coscooper
So, to answer your question about are overrides are aren't overrides in effect, it's quit easy.
1) the block/allow will actually show if the override is in effect as if the application in question has an override applied in the console, that list, when the application in question is running, will display in the allow. Again, it's an "ACTIVE" processes list, not an at rest override list.
2) If you create an override and the "cloud" determination is "unknown" - then it's in effect. No magic and the agent will not interfere with the software.
3) If the determination is set to "good", then delete the override as its irrelevant.
To help even further, there is a "undetermined software" report that is available at the site level. In our best practice guide, we do not suggest you go through and proactively make an override for everything, rather look at the converse. Review the undetermined report and see what the agent isn't aware or is unknown and create an override accordingly.
In that report, if you notice the "last seen" date, it's a reference to when the agent last determined it was an unknown. After an override is created, that date will stop updating.
There is no issue with Windows 10 updates, unless you use the -clone switch which is applied through CW Automate. Which, we recommend turning off "use unique identifier" in the settings. That setup will be deprecated in the next plugin.
Otherwise, normal updates without an additional MID switches will update fine and not duplicate.
As far as the overrides discussion, there is nothing broken and there is usually no need to display to the end user what is set/configured to override if it's fully managed by an MSP. It's not been nor is an issue with many other MSPs given most do not build a lot of overrides once they know whether the LOB is in the undetermined report or not.
Just so you're aware, duplications is due to many factors that are all based upon how the agent creates MID (Machine ID) and to modify that is not an easy feat with 40M endpoints deployed today, so it's a challenging issue, not a will we or wont we issue. Dev has been working on several modified methods of creating that uniqueness and retaining reference to the old method during transition. Again, no easy task and may change under the hood sometime in the future.