DoggettOne 0 Posted April 17, 2020 Share Posted April 17, 2020 Hello I've scheduled a Remote Administrator Component Upgrade task to upgrade our server to the newest version of eset. No matter what I've done, it refused to run. I've scheduled the task at a specific time, set up Run ASAP, reboot the server itself, ensured both time stamps match-- no matter what, it will not run. What am I missing on this? (This is not the only task that will not start, but hopefully once I upgrade the other tasks will run as well) Thank you for your time. Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted April 18, 2020 ESET Staff Share Posted April 18, 2020 Could you please double check that device you targeted this task (i.e. AGENT on the same machine as ERA/ESMC is installed) is actually connecting to ESMC? If so, please check also whether there is no other device with the same name that could lead to confusion. Link to comment Share on other sites More sharing options...
DoggettOne 0 Posted April 20, 2020 Author Share Posted April 20, 2020 The device I targeted was the eset server itself and there are no other devices with that name. Thank you for your time. Link to comment Share on other sites More sharing options...
ESET Staff MartinK 378 Posted April 20, 2020 ESET Staff Share Posted April 20, 2020 4 hours ago, DoggettOne said: The device I targeted was the eset server itself and there are no other devices with that name. Eve in such case, it is crucial that ESMC Agent installed on the same machine as is ESMC is connecting to ESMC, as actually AGENT will execute upgrade process. I would recommend to check last connection of this AGENT - it is marked in main clients / devices view as your ESMC. Link to comment Share on other sites More sharing options...
DoggettOne 0 Posted April 20, 2020 Author Share Posted April 20, 2020 Both the agent is installed and connecting to the server. Link to comment Share on other sites More sharing options...
ESET Staff MichalJ 434 Posted April 21, 2020 ESET Staff Share Posted April 21, 2020 It seems that the agent is already on the version 7, however the server is on the version 6.x, which means that they are not compatible. Newer server will accept connections from older agents, but older server is not able to accept connection for newer agent. So you will have to update the server manually, ideally via all in one installer downloaded from the ESET website. Link to comment Share on other sites More sharing options...
DoggettOne 0 Posted April 21, 2020 Author Share Posted April 21, 2020 Ok, perfect. Will this all-in-one work with Windows Server Enterprise SP2? I didn't see it in the software requirements. Link to comment Share on other sites More sharing options...
Recommended Posts