Thread Info
  • State Not Answered
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 4 replies
  • Subscribers 15 subscribers
  • Views 10279 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

operating Apple Mac computers: Not started: SophosScanD

LHerzog

How does Sophos think we could operate your software correctly on Mac computes?

Whenever there is a Sophos Intercept-X Client update or a new user logs in on the Mac, Intercept-X is not working anymore until the Sophos services are manually allowed again.

We have no Device Management for Mac computers.

It's not possible to have a stable situation with this limitations - 30-40% of our Mac computers is always "red" in Central management.

I'm aware of doc.sophos.com/.../index.html

In your doc you wrote:

Even the notifications from Sophos are often blocked by MacOS, so the user will not notice issues with Sophos Software on the Mac.

Some Sophos services are not running/missing
Not started: SophosScanD



This thread was automatically locked due to age.
Parents Reply
  • 0 in reply to Gladys

    Yes, I've seen it. But I think this cannot be done as regular maintenance.

    If the user is not at the device when a prompt for new system extension permissions is shown, or dismisses the prompt due to lack of knowledge, it will never come again.

    Next, the Sophos endpoint icon is always black. why black? and it will not change, when there is an issue. It should show up with a coloured icon, red, orange, whatever when there is a problem. If it is always black, the user will not know if it is not working.

    When SophosScanD is disabled, the endpoint protection is useless.

Children
Unfiltered HTML