Click the image to view larger in new window
There will be no notification from the Agent, but you will see warnings in the ESMC Web Console for 30 days prior to expiration. Once expired, the Agent will still attempt to connect and client computers will not be removed automatically, but they will stop connecting and the server task Delete not connecting computers will eventually remove them if configured to do so.
See the following article if you do not know how to create a new peer certificate or Certification Authority:
Agents are connecting to ESMC Server. Make sure that Agent certificate will not expire sooner than its expiration date.
Do not delete the old certificate until the new certificate is applied on all Agents.
If Agents cannot connect to ESMC Server, redeploy the ESET Management Agent on all machines that use the expired Agent certificate.
If the Certification Authority is expired too, proceed with the Scenario 5 instead of this scenario.
Agents cannot connect to ESMC Server because the Server certificate is expired. After setting up a new Server certificate, Agents with a valid certificate will be able to connect to ESMC Server.
If the Certification Authority is expired too, proceed with the Scenario 6 instead of this scenario.
Agents are connecting to ESMC Server, however, after creating a new Certification Authority (CA), all certificates you use must be replaced: Server, Agent, MDM, Virtual Agent Host.
Do not delete the expiring CA until new certificates are applied on all components.
Agents cannot connect to ESMC Server. Create a new certification authority (CA). All certificates you use must be replaced: Server, Agent, MDM, Virtual Agent Host.
When a client computer does not appear to be connecting to your ESMC Server, we recommend that you perform ESET Management Agent troubleshooting locally on the client machine. See the following ESET Online Help topic for more information.