McAfee and MIcrosoft are still working on this WSC bug it seems, but the workaround provided now is to disable Windows Defender from GPO to prevent it from taking over. I have not tested this myself yet, and I do not know how I feel about doing that... but as a "temporary workaround" could be good enough...
Windows Security Center intermittently incorrectly reports that Endpoint Security is disabled when running on Windows 10
Slightly off topic, but 10.7 isn't appearing in my ePO software manager after a library refresh. Did it automatically appear for you all, or did you have to download it from McAfee and upload the packages to ePO?
It should appear automatically in your software manager. Could potentially be a compatibility issue depending on which ePO version you use or could otherwise be a number of things. Could you please start a new thread for new issues so we don't entangle a number of issues. Thank you @billmoller 🙂
Comes automatic. 5 customers migrated from ENS 10.6.1 OCT to ENS 10.7 and FRAME 18.104.22.168 and all FINE >
MAYBE: You done so much testing for this case and POC that your EPO is down 😉
EXCEPT you WOULD have a CORRUPT SQL EPO DB. > You can find out IF you press the UPDATE BUTTON in Softare Manager and you WOULD get an ERROR. That would be Worstcase scenario.
We do that TEST on every EPO we new manage. Nothing found in the LOGS but the UPDATE CIRCLE turned RED.
I've received a new POC build today and have completed some initial testing.
So far it seems good... have gone through 2 reboots without issue.
McAfee and Microsoft actively worked to narrow down issue and found an error in McAfee is causing the incompatibility at this point. McAfee will implement changes to resolve the incompatibility.
Was my reply helpful?
If this information was helpful in any way, or answered your question, will you please select "Accept as Solution" in my reply, or give kudos as appropriate, so together we can help other members?