Please use this space to create a new post for issues you are having if you do not see a post already created for your issue. We will also welcome feature functionality feedback, enhancement requests, and general questions.
Just wanted to give an update on this. I think this should be something that is added to the instructions.
The fix was after installing the plugin through Automate, you have to go assign the Sophos Plugin…
This did not work for us, possibly because we have our Automate hosted with the newer CW Cloud offering. After beating on support for a while and with Steve Weber's assurances, Automate Support finally agreed to load the .DLL from their end and it's working like a top now.
President - Moebius Technology Solutions, Inc.
We're also getting the same error. We've unblocked, and we're on premise. I'm trying support now but not getting anywhere unfortunately. They had me move it to the plugins folder, and try to add it again, but I'm getting the same error.
I managed to pry the following from them, but it won't work for us. They're bouncing us back to Sophos.
Candace, are you Cloud Hosted with CW for your Automate instance? We are and they kept pushing us back to Sophos too, but we finally found an Automate Tech that would truly look into the issue and he loaded the .DLL for us (and it's working smoothly). If this fits your scenario and you'd like to email me at firstname.lastname@example.org I'll be happy to provide what info I can from our encounter with support. It may give you the leverage you need.
EDIT: I just noticed your earlier post that you were on-prem, so our experience with Automate Support may not apply. I guess I can maybe see why they won't assist with loading a foreign .DLL in that situation. It's frustrating though, everyone involved is owned by the same parent company... can't we all just get along! LOL.
Exactly! It's super frustrating being bounced back and forth. I understand it's not signed so they want to wash their hands of it, but it's not like it's some unknown company. I even made them go check what they did in their notes for you, which is how I got the above steps. Sadly, it's still a no-go. Thanks for responding though!
That's frustrating. Keep on fighting...it's a great Plug-in and its worth it!!!!
What error are you getting? This works with on-premise Automate without a problem. You just have to first unblock the DLL file by right-clicking it and clicking properties. Unblock the DLL and then load it again. PM, me if you need assistance.
Hi Elias and Steve - how often does the Plug-In update / sync with the Sophos Endpoint Cloud? I've made a series of deletes, and force tamper protection "on" commands. Just curious how long they take to update. Has to be more than hours, as nothing has happened. Is this a daily thing?
Hi Christian, Endpoint actions via the API are synchronous to Central. From Central back to the Endpoint however they are asynchronous, but should update within a few minutes time.
Let's try and determine first if this is an issue with Central or the Endpoint.
1. Are you seeing the API request reporting as successful or failed in the plugin Audit logs?
2. Can you attempt the same command from Central to the same Endpoints?
If the requests are successful from the plugin, and the same action from Central still doesn't update the Endpoint, I'll have you open a ticket with support.
If the request shows as failed, or the update from Central was Successful, we'll need to pull the logs and investigate where it's failing in our Central line of communication.
OK. Perfect. Let me do some testing and I will report back. For the record, the plug-in is already extremely helpful for us in identifying endpoints that need attention. The ability to see all Endpoints and Clients together is invaluable.