Search the Community
Showing results for tags 'solved'.
Found 2 results
Hello, Is there any recommend way to deal with 6.X agents prior to 6.5. In particular, I would like to upgrade the agents to the latest SCM agent. Problematic agents are versions 6.2 and 6.4. The target devices are a mix of Windows XP,Vista,7,10. Some are within the Windows domain and others are not. The SCM server is not on the domain. Options I have tried: - deployment tool. Does not work: - network path not found (tried both with a local path and a public network share on the same subnet) - GPO for Domain-aware computers - never upgrades to agent 7.2 even after gpupdate and multiple reboots. gpupdate always mentions that some tasks need to be done prior to logon. - the GPO is working to some extent, because computers without any ESET product are getting the latest Agent installed. 32-bit and 64-bit Right now I have wasted a bunch of time that I could have used manually updating agents to 7.2 by waking up at 7AM before users get on their computers. These are the notes I wrote while reading documentation: - cannot upgrade ERA agent to SCM Management Agent on client computers pre-6.5 - the task runs successfully but https://help.eset.com/esmc_admin/71/en-US/client_tasks_upgrade_components.html - does it work or not ... https://support.eset.com/en/kb7465-upgrade-eset-remote-administrator-agents-65-or-eset-management-agents-70-to-the-latest-eset-management-agents-71-using-the-components-upgrade-task - ah, does not work because it is not 6.5: https://support.eset.com/en/kb6819-upgrade-eset-remote-administrator-63-and-later-to-eset-security-management-center-version-7-using-the-web-console - I imagine this is why the GPO deployment of SCM Agent did not install on computers with existing existing ERA installations (6.4 or older) I am attaching versions of SCM. Thanks, mmadeira EDIT: further context on agent environment: - around 60 outdated agents (some crossover between domain-aware and not) - total of 140 agents that I want to deploy for now (a bit more than half are domain) - more agents to come in the future, so it would be interesting to use the remote deployment tool on the latest versions of Windows 10 both domain-aware and not
Hello, Is there any way to disable the warning "Backup user not set up" in the status overview page? Seems pretty silly when I have multiple administrative users as a backup. I have event tried creating users named 'mutealertX' without success. Maybe the SQL query is not correct 😆 See attachments for version and error details. Thanks, mmadeira