Jump to content
Kelvin Ma (gmail)

Client Computers disconnect from ESMC server after migrating from Server 2008R2 to Server 2019

Recommended Posts

Dear Sir,

I am performing same IP ESMC Server migration from Server 2008R2 to Server 2019. I successfully backup the database from old server and restored the database to new server using command line. Then, I followed the below steps suggested by vendor support.

  1. Import Certificate Authority exported from old server
  2. Repair ESMC server at Programs and Features
  3. Login WebConsole
  4. Change server certificate at Server Settings using exported old cert.
  5. Restart ESMC services

Although the overview shows that the Server Certificate is valid and has two agent certs. It looks healthy. However, the client computers are still disconnected from the newly migrated server.

Please advise how to solve this problem,

 

Kelvin Madisconnect.JPG.affac525feb84e43cc57e6688bd5d54e.JPGCA.JPG.68f108da1500b08d6dccff2354f0b57b.JPGserver_cerit_import.JPG.676cf30691f7b8fa19bd8ebfcb05c35b.JPGcert_healthy.JPG.4dcfd8014a7ba30d66bdb396f538ba11.JPG

https://help.eset.com/esmc_install/70/en-US/migrated_database_same_ip.htmlInsert existing attachment

Edited by Kelvin Ma (gmail)

Share this post


Link to post
Share on other sites

Couldn't it be that the name of the ESMC server has changed and clients are attempting to connect to the old one? Does creating agent live installer and installing it on clients (or on 1 for a start) make the machine to connect to the new server? If not, what error is reported in C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs\status.html  and trace.log?

Share this post


Link to post
Share on other sites
4 hours ago, Kelvin Ma (gmail) said:

server_cerit_import.JPG.676cf30691f7b8fa19bd8ebfcb05c35b.JPG

Could you please double-check that step "4" was performed correctly? Screenshot from ESMC Server configuration (^) shows that ESMC is using certificate created on 15th February 2020, which probably means that this is not original certificate, i.e. it is probably newly generated certificate signed by new CA which is not known to clients.

Also it would help to provide us status.html from client that is not able to connect, especially in case setting old certificate in ESMC settings won't resolve connectivity issue.

Share this post


Link to post
Share on other sites
3 hours ago, Marcos said:

status_clientPC.pdfCouldn't it be that the name of the ESMC server has changed and clients are attempting to connect to the old one? Does creating agent live installer and installing it on clients (or on 1 for a start) make the machine to connect to the new server? If not, what error is reported in C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs\status.html  and trace.log?

the new ESMC server is previously installed with the name Antivirus5. Afterwards, I turn off the old ESMC Server (name: Antivirus4) and change the name of new ESMC server to Antitivirus4. I wonder if Certificate Authority is generated during the installation of ESET ESMC Server. If I change the name server to another one later, would it still follow the old name, Antivirus5?

I hereby attach the agent log of one affected client PC for your reference.

Share this post


Link to post
Share on other sites
3 hours ago, MartinK said:

Could you please double-check that step "4" was performed correctly? Screenshot from ESMC Server configuration (^) shows that ESMC is using certificate created on 15th February 2020, which probably means that this is not original certificate, i.e. it is probably newly generated certificate signed by new CA which is not known to clients.

Also it would help to provide us status.html from client that is not able to connect, especially in case setting old certificate in ESMC settings won't resolve connectivity issue.

I attach the screenshot of changing the server certificate with the exported old certificate from the old ESMC server. It is strange that the information does not update (still is valid from 15/2/2020) even it shows that the import is successful. I restart the ESMC server service. This information still does not update. Please advise if the procedure I performed to import the server certificate is correct or not. Thank you very much,

1.JPG

2.JPG

3.JPG

4.JPG

5.JPG

6.JPG

7.JPG

8.JPG

Share this post


Link to post
Share on other sites

On  my newly migrated ESMC server (Server2019), I had already successfully changed the server certificate to an old one. I succeed to do so by both selecting the certificate from folder and importing the certificate. You can see that it is valid from 9/9/2018. However, another problem arises. At Status Overview, it shows that the server certificate is invalid. What causes this problem? It even tried a much older server certificate which I backup at earlier time. The same problem occurs. It shows the server certificate is invalid.

Please kindly advise, Thank you very much.

Kelvin Ma

Server_Cert_after_Import.JPG

Invalid.JPG

invalid2.JPG

Edited by Kelvin Ma (gmail)

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...