bbraunstein

I've been in the process of migrating and updating my AV solution to ERA v6 (from v5,x). I've successfully set up my CentOS server by hand. I've also successfully migrated and upgraded 59 out of 60 of my clients, located in 3 separate countries. Client #60 is being a real pain in the . This computer is Windows 7 Professional and formally used to have ESET v5.x, which was configured to communicate with my other server. I never had any issues with this computer when I originally set up my ERA v5 server last year. I am able to remotely deploy an Agent to this computer. The Agent Deployment logs shows the task finishes successfully but it never reports back and updates with the server. It remains grayed out and no information gets updated on it. I remotely log into the machine and I see that the EraAgent service is running on the computer, however I cannot figure out why it isn't talking to the server. ESET v5.x was still installed on it, but about 70% of my company is Windows devices and I was able to successfully deploy the Agent (and upgrade) while the original was still installed. Either way, I tried uninstalling the original package, and redeploying the Agent, but no changes. I tried going through the "Troubleshooting Agent Deployment" section in the documentation, but I have no errors to go by. Anyone encounter this? or have suggestions? Thanks!

Well first things first, let me get the first question out of the way: You do have Agents installed on the clients, right? If not, deploy the Agents and then wait for the polices to update. I find that things in ERA v6 run a bit slower than they did in 5.x. Whenever I make any updates, I try to wait about 10-15 minutes to wait for the Agents to get back to me. Otherwise... When you're looking to see which policies are applied, how are you checking? Are you clicking on the client and then selecting 'Manage Policies...' from the dropdown menu? I'm not sure why, but my best guess is that this is just a local policy manager for that one specific client only. You will not see the applied policies this way. If you want to see all the 'global' policies applied to a client, click on a client and select 'Details' from the dropdown menu. Select 'Configration' (Gear icon) from the left hand side of the new Window and select 'Applied Policies' Tab. Here you should see all the polices, and the order, that is applied on that client. Hope this helps!

I don't mean to piggyback on uglyB0b's post, but I'm also encountering the same issue as well. It's not on all of my Windows machines, which kind of makes it a bit more annoying. I have ESET installed on all of my computers and I have an administratively set Firewall on all computers too. I know WHY I'm getting the error: Windows Security Center is bugging out because my Firewall is modified differently than what Windows recommends. I tried disabling the Network Firewall security messages in Action Center, but the Web Console is still displaying this errors. Now I know exactly why I'm getting these errors. Is there a way to implement acknowledgements or ignoring of warnings/errors on client computers? I think that would be a neat and helpful feature. EDIT: I want to give more information how I figured this out and to paint a better picture of my environment. If you click on a client and go to Details > Alerts, it will list more information on the error. There is a "Subproduct" column that indicates what the specific feature it's talking about. In my case, the subproduct is "Firewall". If I log into the client and open Windows Firewall in the Control Panel, there's an error that says, "Update your Firewall Settings: Windows Firewall is not using the recommended settings to protect your computer." But, like I explain in my original post, since I've made a bunch of modifications, Windows is freaking out. ' EDIT #2: I just deployed to my OSX devices. All of them say Operating System is out of date. When I go to App Store to update, the only update that exists is the upgrade to the latest OS. Some of these computers do not have the hardware for the upgrade and I have no need to upgrade them yet. It really would be great to be able to acknowledge or ignore warnings/errors.

Yeah, since no one bothered to post an update, I'll do it: This "bug" has to do with directly connecting to the ESXi Console. The OVF template is for vCenterServers only. So you will need to connect directly to a vCenter server using a vSphere Client. If you do not have a vCenter server, it will not work and you'll get all the missing settings. The other alternative is to spin up your own CentOS (or other linux distro of your choice) and manually install. I ran into a bunch of blocks, but it wasn't tremendously difficult to work out.

I'm in the process of migrating/upgrading my current ESET v5.x to 6.x. I have the Server, Web Console, and Database successfully set up. I have been able to install the Agents and products locally on sandbox computers with no issues. This computer used to have ESET v5 installed, which I uninstalled, and locally installed the Agent + AV, so the settings are already preconfigured to accept incoming connections from an ESET server. My company is spread across three different countries, so Remote Installation is a must. The computer is running Windows 7. I'm trying to deploy ESET Endpoint Antivirus. My server is running on a CentOS 6.5 VM. For comparison, the old ERAC was on a Windows 2012 R2 VM. I was able to successfully deploy Agent and Product locally on this computer. I uninstalled everything and now I want to deploy remotely. I followed the documentation to get a more verbose log by changing the trace log value to 'Error' and generating a report. The context of the report shows me this: 2015-01-28 17:53:52 Error: CRemoteInstallModule [Thread 7f49a41cc700]: Executing remote deployment of agent 3d1bbc18-1e40-4b3d-8cdf-597ffffb81a2 on 'chosenia.modusagency.com' Windows network remote deployment failed. - Verify that 'chosenia.modusagency.com' is responding to 'ping'. - Verify that 'chosenia.modusagency.com' can be resolved with 'nslookup' if it is a DNS name. - Verify that firewall is not blocking communication and file sharing between server and the target machine. - Verify that "File and Print Sharing for Microsoft Networks" is enabled on the target machine. - Verify that "Remote Procedure Call (RPC)" service is running on the target machine. - Make sure that simple file sharing is turned off on the target machine. - Activate sharing resource ADMIN$ on the target machine. - Verify that 'modusagency\spicescan' has administrator rights or use local 'Administrator' account that is enabled on the target machine. - Verify that 'modusagency\spicescan' password is not blank. - Verify that you can remotely log on to the workstation from the server. - Verify that from server machine you can access 'net use \\chosenia.modusagency.com\IPC$' from the Command Prompt. - Change 'ESET Remote Administrator Server' service credentials from 'Network Service' to user with domain administrator permissions temporarily for deployment. * Error details: std::exception SSH remote deployment failed because CONNECTION CAN NOT BE ESTABLISHED to the target LINUX or MAC machine. - Verify that 'chosenia.modusagency.com' is responding to 'ping'. - Verify that SSH daemon is enabled on the target machine and is running on the port 22. - Verify that firewall is not blocking SSH communication between server and the target machine. * Error details: connect: Connection refuse Now, even though all these settings were necessary for the initial install of ESET v5, I still went back and double checked each setting on the computer. All the settings are configured as the log suggest. Is there something else I am missing? Or is there 'kind of, sort of "support"' for remote deployment?

Ah, okay. There's my issue. I do not have any vCenter servers. I'll probably just spin up my own CentOS VM and mount the .iso. Thanks for the clarification.

Was there ever a resolution to this? I'm having the same issue as well.

Hi, I've been having trouble as well. Trying to deploy on VMWare ESXi 5.5 and I do not have the additional options after "Name and Location" on the set-up procedure. None of the following options show up on the sidebar: - Name and Location - Host/Cluster - Resource Pool - Network Mapping - Properties Storage and Disk Format show up, but without Properties, I cannot specify a hostname or a password. The VM boots up with a blank screen saying press <ENTER> to Enter Management mode. A password prompt pops up and nothing works. I tried a blank password or even 'password' but that did not work.

So I did lots of looking into this and managed to locate the database in C:/ProgramData/ESET/ESET Remote Administrator/Server/database. It was a .mdb file, so I opened it in Microsoft Access. I was able to make a query and get the information I wanted. I exported it to an .xml file and then tried to import it into ESET Reports tab. I received an error code 80025, 0. I know this has to do with formatting the headers but even then, I really do not know where/how to start. I referred to the test .xml I made the other day, and tried to copy the headers but it still did not work. I know I am getting closer ! I only need just a little push in the right direction. Does anyone know HOW to generate a report and IMPORT it, once they've access to the database?

I really enjoy the reporting feature to visualize any threats to my clients. However, there are certain things I'd like to be able to see that the current list of reports/templates do not offer. I also use Spiceworks, an inventory tool that monitors device status, installed applications, hardware specs, and more. They also have a reporting feature as well. If there isn't any predefined reports that has the information you are looking for, it is possible to pull your database and create a custom report in SQL. I was wondering if it is possible to create your own custom report tailored to your needs in ESET? Especially considering there is an Import button makes me think it should be possible. I exported a random predefined report and found that it is created in .XML. Is there some sort of resource or reference guide I can go to find out all the node names and values? Thanks!