As stated above, the Replacement definition was posted within 30 minutes of the original problematic definition. This happened before 17:00 UTC on February 6. The versions are also referenced above. ... View more

Which version of the Connector are you running? Are you running the Command Prompt as Administrator?   The top of the thread is updated with Uninstall via Command Line: <installer path> /r /S /stopservicecoe 1 /remove 1   Uninstall via Command Line with Connector Protection Enabled: <installer path> /r /S /stopservicecoe 1 /remove 1 /uninstallpassword <password>   If those do not work, try running <path, likely C:\Program Files\Cisco\AMP\>sfc.exe -k <password> ... View more

Please see below Todd ... View more

Rather than manually touching each endpoint, please remember you can push uninstalls and reinstalls via SCCM or any other deployment  tool using Command Line Switches. These are listed in the latest Deployment Strategy Guide on page 26.  https://docs.amp.cisco.com/en/A4E/AMP%20for%20Endpoints%20Deployment%20Strategy.pdf   /remove 1       Uninstalls the Connector and removes all associated file So you can use these commands: <installer> /r /S /stopservicecoe 1 /remove 1  <installer> /r /S /stopservicecoe 1 /remove 1 /uninstallpassword <INSERT YOUR PASSWORD>  to remove the application. The <installer> should be the original installation file for the AMP for Endpoints Connector.   Todd   ... View more

CWS acts as a proxy server, so the destination web server will see the CWS Tower IP as the connection/client source IP.     Respectfully,     Todd Everett, ATS CSE, SLED Central/Mid-Atlantic SNR:         408-895-3425 WebEx:    https://acecloud.webex.com/join/toeveret   6-minute video on how Cisco’s Email Security solution tackles relevant email borne threats     View now FREE Email Health Check     http://www.cisco.com/web/products/security/email-health-checkup.html FREE Web Health Check       http://www.cisco.com/web/products/security/web-health-checkup.html http://www.cisco.com/tac TAC: 800-553-2447 ... View more

MKirbyII, Workaround option: Rather than hard-coding the explicit proxy settings, you can use either a hosted PAC file or a combination of PAC and WPAD files with your internal DNS and DHCP settings to do "dynamic explicit" redirection. We have whitepapers on PAC file creation and deployment. 2nd Workaround option: Have you tried (I am in process of getting the change order in to test this) creating a CWS bypass list for the entries instead of controlling it at the WSAs? The bypass settings in theory will prevent decryption, reputation, anti-virus, etc. inspection, so it should be a viable option, correct? I shall try to update everyone after testing. CWS Team, Any word on the fix release for this? Should the 9.0.1 code, with its fixes and optimizations for https in general, resolve this? Thank you T ... View more

As Michal stated, you can redirect web traffic via WCCP to WSA or via ASA Cloud Connector settings to CWS for advanced web filtering, including URL categorization and one or more AV engines. The ASA is able to perform both FirePower IPS inspection and redirection to a proxy inspection solution using 2 contexts. Effectively, making the system 2 ASAs in a row. Make sense? ... View more

Aslak, What device are you redirecting traffic from (aka the WCCP router)? Using ASAs and Switches, I have never had to manually change the mask, as part of the WCCP v2 process is to manage adding and removing WCCP clients as they become available/unavailable. I have some device specific WCCP documents I can share if you can summarize your sho ver for me. Respectfully, Todd Content Security Specialist ... View more

Would it be possible to get clarification on 1. updates since Feb 2013 and 2. which options support what capabilities of https redirection and inspection? Thank you in advance! Todd ... View more

Gautam, Not today. Each of IPS and Content require a dedicated SSP today. Having both is on the short term road map ... View more