SuroopMC SonicWall Employee
Comments
-
The right portal is https://captureclient-36.sonicwall.com. The bad gateway is a symptom of the Infra issue we are seeing.
-
Folks - please see the recent announcement posted in the Capture Client forum. Apologies for the delayed response!
-
Folks - please see the recent announcement posted in the Capture Client forum. Apologies for the delayed response!
-
@b1ntech - creating multiple tenants to manage different customers is always recommended but may not be necessary. Particularly if you have a low number of tenants with fairly standard policies across all endpoints, and the only person logging into the portal is you and your team, then you can have a single tenant with…
-
@Mickey - please disable the Inheritance switch and then you will be able to enable Content Filtering.
-
@b1ntech - we have CC Advanced coexisting with other backup solutions fairly well. The Quest Backup seems to be a little uique in this matter. In general, we recommed applying exclusions for Backup solutions. See this page for some applications that we have already seen in the field and addressed: An alternative way to…
-
@jramsey - it is expected in April but watch for official comms next week with more details on what all the release will entail. A major goal is to converge customers currently on 3.1 and 3.5 into a single experience.
-
@Bret - unfortunately we don't have an ETA commit on that and its something on S1. We're working with them, but it's likely before they fix the upgrade issue, we will launch support for their latest agents which will eliminate the need for that.
-
@Bret - the steps to uninstall the client are accurate. My recommendation is to raise a support ticket so that a Support engineer can help you get through this or collect data for investigation. .
-
@Bret - check out this KB article. But to be specific: Uninstall Capture Client from the Server (CC and S1 agents) Create a new Threat Protection policy for those servers and set the version to be the "Self-managed 4.1.6 for Windows" seletion. Create a new Capture Client policy with the client version set to "Self-Managed…
-
@ThK - This isn't an issue of it being not ready or untested. The bug was in fact identified only when we rolled out to a few customers in the field. However, those customers needed the client for the VSS challenges they ran into. And from their perspective, uninstalling and reinstalling the client was a smaller problem…
-
@BWC - yes, this is a one-off case. however, the 4.1.6 engine itself only targets one specific bug related to VSS and backup software on Windows. If that isn't something you have encountered in your environment, there is no real need for you to even attempt the upgrade.
-
@Bernhard_Winter - there are a number of 3rd party applications out there and it is infinitely impossible to keep track of all applications that may get blocked by the SentinelOne engine. This is why we maintain and update this list as much as we can whenever we identify new applications. If you are willing to share the…
-
@Jürg - did you try decommissioning or deleting the device? In such situations, a delete is recommended, not a decommission.
-
@FFG - I would recommend working with Support. They will need to determine what the current status of the threat and quarantined file is. To troubleshoot this further, they will need more information which obviously cannot be shared on this forum.