cgal

How and in what conditions is updating ESMC v7 in a Hyper -V installation ? It was installed on 26 june. Untill now seems no update. In web console, agent existing on ESMC is reported as outdated but there is no way to update it. I've updated webmin and obsolete packages as root, nothing from ESET.... Agent is not listed in About menu... ESET Management Agent ESET, spol. s r.o. 7.0.471.0 www.xxx.org Computers 10.n.n.n 10.n.n.0 7.1.367.0 en_US -------------------------------------------------------------------------------------------------------- ESET Security Management Center (Server), Version 7.0 (7.0.471.0) ESET Security Management Center (Web Console), Version 7.0 (7.0.429.0) Copyright (c) 1992-2018 ESET, spol. s r.o. All Rights Reserved. End-user license agreement CentOS (64-bit), Version 7.6.1810 License used for module updates of this ESMC: Public ID:zzz-zzz-zzz Expires: 2037 Dec 31 14:00:00 Connected Clients: 67 Active Licenses: 1 License Management Installed Components: Name Version Update module 1072.1 (20190626) Translation support module 1746 (20190530) Configuration module 1740.3 (20190326) SysInspector module 1274 (20180918) SSL module 1031 (20190405) Push Notification Service module 1053 (20190321)

E.g. when 2053 update show up 2-3 desktops shows on ESMC gui that next upgrade for an individual push task is from .2045 ro to .2053 en, despite the fact that all are win 7 ro prof desktops with EES 7.1. ro 32 or 64 bits. After some time at least one of that desktops suggested update revert to ro. It doesn't bother me to much as I have a lot to do here (like OrthoC...). By the way, ESMC VM self agent is reported outdated but refuse to update itself. I discovered today that after update packages on ESMC VM last week , I can't create installation packages no more. I will come back with details as time permits.

For ESET staff... Please take care for automatic language detection when coding for auto-upgrade. When creating tasks for update in my ESMC VM v7, some of my Windows 7 Rom endpoints are selecting English version for upgrading instead of Romanian, depending how soon agents are connecting to ESMC and the moment you release a new version. After a few hours and checking for that specific desktops seems that upgrading tasks do the right thing.... Repository is selected to Automatic so the problem might be at sync. somewhere...