Command IT 7 Posted August 21, 2018 Share Posted August 21, 2018 We still have some old XP and 2003 machines around that are running the latest V6 ESET. ESMC 7 reports them as outdated versions even though V7 is not supported on them and the V7 agent id correctly identifying the OS on them. Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted August 21, 2018 ESET Staff Share Posted August 21, 2018 Just to let you now: we are working on new ESET repository server configuration, that should resolve this issue. Once deployed, it will instantly work for all ERA/ESMC. Link to comment Share on other sites More sharing options...
Command IT 7 Posted August 22, 2018 Author Share Posted August 22, 2018 Thanks Link to comment Share on other sites More sharing options...
Command IT 7 Posted September 2, 2018 Author Share Posted September 2, 2018 (edited) The repository changed worked and both XP and Server 2003 no longer report as outdated, but I have erroneously pushed a V7 upgrade out to both a 2003 and XP machine and both successfully upgraded. Does the non-support of XP and 2003 just mean there is no support, or is it an installer bug that let me install V7 on these machines? Edited September 2, 2018 by Command IT Link to comment Share on other sites More sharing options...
ESET Staff MichalJ 434 Posted September 2, 2018 ESET Staff Share Posted September 2, 2018 As of now, the versions were installable, and should be working just fine. However, when problems arise, tech support will most probably advice to downgrade. We will adjust the installer behavior for future versions to prevent installing on XP. Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted October 11, 2018 ESET Staff Share Posted October 11, 2018 This issue should be resolved no automatically. Latest version reported for Windows XP / Windows 2003 Server clients is EES/EEA 6.5. Link to comment Share on other sites More sharing options...
Recommended Posts