![]() Below is the mail we sent to them, feel free to have a read: We do our own malware testing, now in our test environment we came across some questionable actions regarding LiveGuard/LiveGrid that we are concerned about and maybe we need better explanation or training maybe?. Not sure if this post is in the correct place, but we logged a ticket with our ESET region but though we will post it here as well. If it works for me in the first variant - I could turn off the old server, set the new one to the IP address of the old server and if the certificates were OK - workstations should report as if it were the old server. The only thing is that I need to have both servers online for some time to give all stations time to download the new policy and contact the new server. It works if I export the certification authority and the agent certificate from the new server > I import the certification authority on the old one > create a new policy on the old one and attach the agent certificate of the new server to it. Unfortunately, it doesn't work - the logs show an error in communication with the new server - the certificate is invalid. I will create a new policy on the old server addressed to the new server and attach the agent certificate to it. I will export the agent certificate from the old server. I will import this certificate on the new server. I had an idea that I would export the certification authority from the old one. I came up with the idea of combining the Protect update to version 11 with changing the server to Windows Server 2022. ![]() I am currently using Protect version 10 on CentOS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |