Sophos EAP 10.0.2 is not compatible with Google Drive File Stream on Big Sur. Mac CPU go spike and the computer hang when both Sophos and Google File Stream is running.
.
[edited by: FloSupport at 10:33 PM (GMT -8) on 18 Jan 2021]
Sophos EAP 10.0.2 is not compatible with Google Drive File Stream on Big Sur. Mac CPU go spike and the computer hang when both Sophos and Google File Stream is running.
This is a big priority to release - I wasted many hours trying to get this to work, and now I'm running without the endpoint at all.
I'm happy to say that we have identified the issue and are currently testing a fix for inclusion in our GA release.
Thank you for all the feedback, it really is appreciated, and we apologize for the inconvenience.
Ahh thanks!! I mistook "crypto guard" for "encryption" - Got it, thanks I will try!
Hey Jonatan, disable in the policy cryptoguard in the policy and the macs will work normal again.
I have tested this for 3 days and so far it’s good on 30 computers.
I have tested this by disabling Endpoint Encryption. I have created a new policy, turned off Device Encryption and assigning a Google Drive File Stream user to the policy - confirmed the policy has been applied too.
Unfortunately we still receive errors in File Stream and the MacBook locks up. I will try adding exclusions to Endpoint Protection Scanning to the following locations to see if that makes a difference:
"/Volumes/GoogleDrive"
"/Users/username/Library/Application Support/Google/DriveFS/cGF0cmljay5sZW1vaW5IQG85c29sdXRpb25zLmNvbQ/content_cache"
EDIT: Just confirming the exclusions did not make a difference.
This is being tested today 01/25.
Can you please test by disabling the CryptoGuard feature in the policy and advise if the behavior changes.
I am discussing this further with our development department - confirming where the issue actually is and what can be done about it. I will keep you advised.
Have you discussed this with Apple and are able to provide a timeline from Apple? As of right now, suspending scanning of files is the only way to make this work. Also I'd like to know what part of Apple's api is causing this.
Alright, thanks for clarifying. I appreciate your responses.