Cisco Secure Endpoint (formerly AMP for Endpoints) will decommission legacy cloud servers, which results in Legacy Windows Connector Versions 3.x/4.x and Mac Connector Version 1.0.x ceasing to operate on 17th December 2021.
The decommissioning of legacy Cloud servers scheduled for 17th December 2021 will impact the continued use of Legacy Windows Connector 3.x/4.x and Mac Connector 1.0.x. Please make immediate plans to upgrade affected Connectors to currently supported versions.
Legacy Windows Connector 3.x/4.x and macOS Connector 1.0.x will cease to register to the Cisco cloud and operate unless they are updated before the deadline
This is the 3rd and Final Notice since Nov 19 2020
Deadline: 17th December 2021
In order to help ensure performance and security compliance, moderncloud servers were introduced in 2016 along with modern connector versions to communicate with enhanced protocols. Legacy cloud servers were sustained to allow customers time to migrate to modern connector versions that are fully supported and leverage the new cloud server infrastructure. Console announcements were made on Nov 19 2020 and Feb 01 2021 respectively, alerting customers of the pending infrastructure change and cloud server decommission.
Nov 19th 2020 / Feb 01st 2021 Console Announcements
The time has come to decommission the legacy cloud servers as a majority of customers have since migrated to the modern connector and cloud server infrastructure.
The following Secure Endpoint services will be specifically impacted by this scheduled decommissioning of legacy cloud servers:
Impacted Legacy Connector Versions:
Cisco Secure Endpoint/AMP for Endpoint Windows Connector 3.x/4.x
Cisco Secure Endpoint/AMP for Endpoint macOS Connector 1.0.x
Legacy connector versions identified above will fail to register to the cloud servers and cease to provide any related functionality including core endpoint security functions. Legacy connectors will also show “Disconnected” status on the endpoint and will no longer be able to upgrade via the automatic policy-based product update functionality. Customers will need to manually deploy a supported connector on the respective endpoints after the deadline. We anticipate that error logs will increase on the impacted endpoints as they log failed attempts to communicate with the legacy cloud servers.
There is no workaround for this problem. The recommended solution for impacted customers is to migrate to modern supported Secure Endpoint connector versions. Refer to currently supported Windows versions and macOS versions.Customers are recommended to install the latest version (a reboot will be required).
For More Information
If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:
A: Legacy Windows Connector 3.x/4.x and macOS Connector 1.0.x will cease to operate on 17th December 2021
Q: What's working now?
A: Connectors continue to register to the cloud to allow in-product connector version updates. Core security functions like Tetra will have stopped updating or failed.
Q: What stops working for customers when the deadline is reached?
A: TheEndpoint will fail to register to the Cisco cloud and will no longer be able to leverage in-productupdates. After the deadline, any product version upgrades require the out of band deployment of a supported connector installer fileon the endpoint directly.
Q: What are the upgrade paths?
A: Refer to the OS Compatibility page for supported Connector versions for your OS platform.
GreetingsI've been playing around with FDM and an FTD 7.0.1 and I'm having trouble understanding how to reach a NATed host from the inside network. It's a pretty basic setup with 192.168.1.0/24 as my inside network and 10.10.10.0/24 as an DMZ with some ho...
Hello everyone, We faced this issue more than year ago. Software version is ASA 9.12.4 or 9.6.4. We had few cases in Cisco (like 692054705) and in our local support partner. But it looks like nobody have real willing to do anything with this bug.&nbs...
disclosure: I don't think so; the default inflation of 3 may or may not be valid, but it doesn't actually represent what happens on the system. Maybe it's good for internal marketing? So I see this post is more of a recommendation than a quest...
All, I have 1 client (entire organization) that when computers resume for hibernate, Secure Endpoint will start scanning. Anyone seen this behavior before? When a laptop goes into hibernate mode and then enters resume, SE will scan. We have several o...
Hi Everyone, Does anyone know if we can configure Cisco ASA Remote Access VPN using ISE as a Radius server with Yubikey as a two factor authentication? I read that there might be a password limitation of 32 characters and the Yubikey uses 132 c...