Connection Failed error observed in C:/ProgramData/ESET/RemoteAdministrator/Agent/EraAgentApplicationData/Logs/status.html

ESET Protect

Dashboard ---> Computers

Human Error - during the deployment of GBR813 certain steps were missed

steps missed
Page 10
    Step-by-step procedure:
    1) Login to ESET Protect Web Console
    2) Click More  from the left-side menu, then Certification Authorities
    3) Click the Actions button at the bottom, then Import Public Key
    4) Select the new Certification Authority file (C:\sz_install\AV\Data\CertificationAuthority.der), fill in the Description field, and click Import
Page 11 
    8) Click on Change Certificate under Connection options
Page12
    9)Select Custom Certificate and click the folder icon to choose the certificate:
    10) Select CertificateAgent (C:\sz_install\AV\Data\CertificateAgent.pfx), then Click OK to finish selection
Page 13
    11) Click Continue to move to Assign tab
    12) Click the Assign button and select All Group
Page 14
    13) Click OK to confirm, then click Finish to create the policy
    A warning was received in reference so may want to do a cluster at a time.  It worked in reference with the warning.
    14) A new certificate will be delivered to ESET Clients according to the connection interval set in ESET Management Agent policies.
    In reference they connect every 10 minutes.  Before pushing this new policy they all had 7 policies applied.  After they all connected they now had 8 policies applied.  I created a simple report to see the policy count.  I had to wait for 2 replication cycles (20 minutes) for them all to now have 8 policies 
Page 15
    15) After all clients are updated, go to the More tab and select Server settings
    16) Click on the Change certificate

• DIMETRA
• D9.2
• GBR#813
• ESET 8

Reload the original certificate to alllow all clients to replicate, then re-deploy GBR#813.