Jump to content

DavidFainshtein

Members
  • Posts

    8
  • Joined

  • Last visited

  • Days Won

    1

DavidFainshtein last won the day on June 28

DavidFainshtein had the most liked content!

About DavidFainshtein

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Israel

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi. Here is a problem: I have an ESET PROTECT server on physical hardware running Windows Server 2012 R2. The time had came to upgrade the server. I've made an P2V conversion of the server and put it on Hyper-V. Then I've made an inpalce upgrade of the Windows Server 2012 R2 to Windows Server 2019. After that I've shut down the old physical server, and brought online the new VM. after dealing with some minor problems, such as Apache Tomcat service had to be re-registered, the ESET PROTECT server appears to function normally, the endpoint communicating with the server and so on. The only issue is mobile devices. Although I can push a wakeup requests to the devices, can lock/unlock them, request for configurations, location etc., and it's all works fine. But the "Last Connected" timestamp stuck on the date before the server replacement and not changing. If I'm shutting down the new server and starting up the old one - the devices communicating with him instantly. Obviously I've checked the communication part (IP address, external and internal remains the same, of course), Firewall rules etc. Any ideas?
  2. Hi. Here is a problem: I have an ESET PROTECT server on physical hardware running Windows Server 2012 R2. The time had came to upgrade the server. I've made an P2V conversion of the server and put it on Hyper-V. Then I've made an inpalce upgrade of the Windows Server 2012 R2 to Windows Server 2019. After that I've shut down the old physical server, and brought online the new VM. after dealing with some minor problems, such as Apache Tomcat service had to be re-registered, the ESET PROTECT server appears to function normally, the endpoint communicating with the server and so on. The only issue is mobile devices. Although I can push a wakeup requests to the devices, can lock/unlock them, request for configurations, location etc., and it's all works fine. But the "Last Connected" timestamp stuck on the date before the server replacement and not changing. If I'm shutting down the new server and starting up the old one - the devices communicating with him instantly. Obviously I've checked the communication part (IP address, external and internal remains the same, of course), Firewall rules etc. Any ideas?
  3. Tell me, Eset - are you insane? A few days ago you released version 8.0.2039 . We started a rollout for a few thousand endpoints and now you releasing 8.1.2031??
  4. It's relatively small update, if you're updating from the previous version, which is 8.0.16.0. Took a few minutes on the server side. The problem, as always, is the requirement to update the Management Agents as well.
  5. Hi. After upgrading the ESET PROTECT to the latest patch Version 8.0 (8.0.191.0) , the Product version status on the Mobile column is gray. Any ideas why and how to fix?
×
×
  • Create New...