I’m looking for a way to filter text strings in content returned from HTTP servers, much like DLP does but for inbound traffic using ICAP RESPMOD.
Since CAS uses RESPMOD and is designed to detect and filter content, can I configure custom strings or regex to filter inbound content? It seems the right place to do this but I can’t find such a feature in CAS 1.3 – is such a thing available in 2.x?
I’m trying to run a report for a specific user using the report request section of symantec.cloud (we use messagelabs and web filtering), when I try to apply a filter for the specific user it returns empty reports. When I remove the filer it returns a report for the entire company, but some users are missing. The test user in this case is myself and I noticed when I ran the no user filter report that the only people I could tell were myself and another IT technician. However a third technician was in the report and I cannot see any difference between his account and my own, does anyone know a solution so the report returns all users or the filter will actually apply to myself?
|Article Number: 492500||Article Version: 2||Article Type: Break Fix|
CCR clone takes 2-3 days, then fails with connection error.
CCR between two DD (prod and DR)
Clone scheduled within the backup
Not supported encryption on the network link
The replication link between the two DataDomain changed from microwave link to fiber link, also, enabled the encryption from the network link.
Removed the encryption from the network link
Experts discuss the benefits and drawbacks of flexible working in today’s business landscape. In this era of rapid transformation, the answers about what’s right for your business aren’t always clear. That’s why Dell organized a thought leadership track session, moderated by Chitra Thankaswamy, Dell’s vice president of Global Client Solutions Marketing, to have an in-depth discussion about the realities of today’s connected workplaces. With the rise of video conferencing, omnipresent Wi-Fi, and email on every smartphone, flexible working is rapidly replacing the once standard office. By giving employees the option to work in their chosen environment, closer to their families … READ MORE
|Update your feed preferences|
I have edited the Reporter dbfields.cfg file to enable the ‘cs_uri_path’ as a filterable option and can now see it as an option in the Reporter GUI, but when looking in the Reports section on Management Center, the filter is not present. Is there anyway it can be enabled or synced to Management Center so the filters match what is shown on the Reporter?
Hi All, we have two Scheduled Reports created by one of our admins. The two reports are using a filter, basically filtering Workstations and Servers into 2 reports. The filter is based on the clients Group location in SEPM.
What we havenoticed is that when the reports is sent to the distribution list of admins (admins email addresses listed in the send to field), the filter is not applying, in that all clients (Workstations and Servers) are appearing in the reports, so there is not separation of workstations and servers. We basically get 2 identical reports.
Also we have noticed that when anyone other that the admin that created the report the 2 reports filters shows as default, not the name of the filter that the creator of the report name the filter.
Has anyone else experienced this issue and have you found a solution or is it a known bug that Symantec need to resolve?
SEPM Version 14.0 RU1 MP1
In some cases, the Cloud Connector may fail to update and may be unable to exit maintenance mode. Due to this, other Cloud Connectors will be unable to perform regular maintenance and update when necessary. This will eventually lead to the connectors getting into an outdated state. Connectors marked as outdated will no longer be able handle service requests, ultimately resulting in service outages.
If the Cloud Connector goes into maintenance mode but then fails to update, the Resource Location and individual connector machine will be marked with an error and a notification will be sent to the Administrator.
Resource Location View:
Cloud Connector View:
Possible causes of this include:
- Conflicting software has been installed on the Cloud Connector machine, preventing proper update.
- Unexpected error has occurred during maintenance.