nhesetnod32

Members
  • Content count

    21
  • Joined

  • Last visited

About nhesetnod32

  • Rank
    N/A

Profile Information

  • Gender
    Female

Recent Profile Visitors

523 profile views
  1. Enhancement

    Can a setting be added as a policy to determine the default setting of the deslock tray icon? The default is to logout/login the user. It would be great if there was a policy where we could pick what the default value could be such as Do Nothing. The more items we can lock down for end users could prevent additional help desk calls :-)
  2. Console enhancements

    When in the Workstations container and looking at a team can the columns that display be modified? For example can the deslock version be a column you can sort by?
  3. ESET Remote Administrator 6.5 private BETA signup

    Hi Peter, please provide me the link to the 6.5 beta. It is greatly appreciated!
  4. Try using a filter to filter the OS type by windows and then sorting by language. You should find the 6.2 version in the language you are looking for.
  5. foneil - the link hxxp://support.eset.com/kb3668/ explains that the Microsoft Hotfix 2664888 is a prerequisite to update to the latest version of 6.x. Is this still true prior to deploying this latest version of the agent (6.2.190.0)? I just want to be clear if I still need to deploy that hotfix first. Thanks!
  6. That is correct that will not install if the AV software is already installed.
  7. Could a parameter be added to Eset to activate using the license (.ls) file? I can create an offline license file through the license administrator and use this file to manually activate Eset EAV. It would awesome if I could automate that process by using a parameter.
  8. ERA 6.2?

    Wonderful news! Will there be release notes for this version posted in the forum?
  9. I agree there are a multitude of requirements and I was just offering up an alternate solution to deploying the agent outside of using GPO. In our environment with the number of nodes and testing we did prior to full deployment we had little to no downtime and minimal interruption to our users by using the agent deployment task, assigning the EEAV software install task to a group, to deploy once the agent was installed, we had about a 95% success rate. We also had great success running the software uninstall task to remove our old AV using the Third-party antivirus software (Built with OPSWAT). It literally wiped the old AV out. Files and registry settings were completely gone! I was impressed with that process.
  10. Actually, i cant seem to find the option you have for first connect to console etc.. I click my OU for workstations.. then new tasks.. task software install.. the only option for the static group "workstations" lists trigger type static group and Execute asap once then join the "workstations group".. I even tried creating a dynamic group, though one for "no agent installed" and set the parent group to be "workstations", for some reason it didnt populate the machines not installed, but all machines pretty much that had an agent.. something is amiss Yes, those options for the new task are OK. Once you complete all the settings in the task and save it any device that is either in that group or gets placed in the that group will have that task run against it. This assumes that the agent is already installed on the PC. I have found that if the task fails it will run the task again at a later time. Not sure if the time is hours later, next time it checks in based on your agent connection interval or if it is once a day. If you want to adjust the Expiration date select the static group by checking the box in the target list and click the Assign Trigger button.
  11. That is interesting. I created an exclusion on a single client and still multiple days later and a couple of reboots the exclusion still exists. I am curious if I change the policy to force the exclusion policy setting it would clear my single client policy. I will have to test this out.
  12. I deployed the agent using Admin - Server Tasks - All Task Types - Agent Deployment. You can create a task to deploy the agent to devices within your network. If the computers to deploy to are on a domain and you have added a group from your Domain with admin capabilities to access/manage the ERA console you can use that account in the Username/password fields when creating the Agent deployment task. Otherwise you can use a local admin account for the username/password. I have seen GPO used for the deployment as well but the agent deployment worked well for our environment.
  13. I should have been more clear. You would run EEAV as admin from the client. When you get to the advanced setup, in the antivirus setttings the Exclusions section should now be enabled. Any exclusion added here will only apply to this client.
  14. If I understand correctly you are trying to get the AV installed once the agent is deployed to the workstation? There are a few ways to create this but if you go navigate to Admin - Groups - select a group in the right hand pane there is a Tasks Tab. In here you can create a new tasks that will run the install once the machine connects to the console. I have one task that I use for each group within the network. The task will deploy Eset AV usually within minutes of connecting after the agent install. Attached are two screens that show the admin location and one for additional details on the task itself. Hope this is helpful for you.
  15. Is there a command line parameter that can be used to activate Eset by specifying the license (.ls) file? For instance If I place the offline license file (.ls) in the same location as the installer is there a way to specify that license file as a parameter? I can use a program such as nsis to package and deploy Eset. In the command line I include the following parameters ADMINCFG="cfg.xml" I can add the parameter INSTALLED_BY_ERA=1 which supresses the activation screen. It would be tremendous if there could be another option to point to an offline license file as well. Microsoft has a command line to activate Windows and MS Office. I have used the MS Office command line to mass deploy Office and autoactivate. This would be a great feature for Eset for those of us that have devices that cannot see the ERA console.