DougS

Ah! The management agent policy that points clients to the new ESMC server finally got applied to the new ESMC server and the agent is communicating with the server! It showed up as a new and separate entry in the list of computers. So i deleted the older entry (after following steps to stop managing, et al). Reflecting on this, I realized that when I reinstalled ESMC on the new server, it probably reset the management policy to point to the older server (recall the use of AUTOSELECT?). So it was trying to connect with the old server all along. Lesson learned. Onward to decommissioni

One more thing. The status.log indicates that the configuration is as follows: Use of HTTP proxy for ESET services is disabled HTTP proxy used for replication: squid.example.com:3128 Repository hostname is: AUTOSELECT Update server is set to: AUTOSELECT with "delayed" update type I'm assuming that the agent is looking for the old ESMC server under the present scenario as it hasn't been decommissioned yet. How do I make it point to the new ESMC server (i.e. itself)? ~Doug

I reinstalled ESET Management Agent on the new ESMC server. Here is a clip from the trace.log showing that the Agent service on the new ESMC server is trying to reach the old ESMC server! 2020-02-26 20:03:16 Information: CSystemConnectorModule [Thread 2c14]: StatusLog_NETWORK_IPWINSSERVERS_STATUS: "Rows":[] 2020-02-26 20:03:16 Information: CSystemConnectorModule [Thread 2c14]: Retrieving installed applications list 2020-02-26 20:03:16 Information: CAgentSecurityModule [Thread 103c]: Agent peer certificate with subject 'CN=Agent at *, OU=Operations Support, O=DawnSignPress, L=San Diego, S=C

I have one apparently serious issue and two small issues that I cannot seem to resolve in the aftermath of a migration of SMC from one server to another. These issues are as follows: * The new ESMC server is not being recognized as having ESMC installed and running even though I can connect to the ESMC services on it using my web browser and manage it. The ESMC icon is missing from the new server entry; * ESMC thinks the ESMC server is running File Security 7.1.12006 when it actually runs 7.1.12008; * ESMC thinks the same ESMC server is running Management Agent 7.0.577.0 when it is