JRV

@MichalJ that sounds great! Looking forward to v7! In an ideal world, it would work something like WSUS, where updates can be approved for install or removal, and approvals could be applied per-Group, to allow us to set up a subset of computers to be used for a test. At larger sites, this would be useful. However, there are only 11 workstations at this site, and having it happen completely hands-free would be great. I don't recall ever having to downgrade ESET due to problems. As long as that never happens, the less steps it takes to manage ESET, the better!

Thanks, Michal, I can see that would work. With ESET, there always seems to be a way, however obscure, but this gets pretty opaque! Someone following behind me would be puzzled by that Application Version mask rule. Seems odd we'd use strings as criteria for the Application Name anyway. ERA should know the product IDs, which are, presumably, unique, and simply offer ESET products in a dropdown list to build the rule. We also need to be able to select "Outdated version" as a selection for "Application Version" to put this on Auto-Pilot. We should not need to edit the Dynamic Group Template with each new version.

I created a Dynamic Group Template to use with a Dynamic Group to find all servers with outdated ESET File Security for Microsoft Windows Servers. The template consists of an "Application Name" rule and an "Application Version" rule. The "Application Name" rule finds no matches for "ESET File Security for Microsoft Windows Servers". Even when I copy & paste the name from the Repository entry to avoid any typos. I changed the operator from "equals" to "contains"; still no hits. Then I removed one word at a time from the end of the name and checked for hits after each removal. None until I had dropped back to "ESET File Security". Unfortunately, this is a match for two products. Kind of moot, here, because we don't have any "ESET File Security for Microsoft Windows Servers Core" machines, so the Group will perform as intended. But I'm surprised by how loose I had to make the criteria in order to match the intended targets. Is there a more accurate way to filter for "ESET File Security for Microsoft Windows Servers"?

Excellent! Thanks Martin.

Thanks, Marcos.

ERA 6.5. Scheduled an after-hours push install of 6.6.2072.2 over the previous version via ERA Client Task. The option to Automatically Reboot if Needed was set in the Task, but none of the computers rebooted. Why? Does it not reboot if a user is logged on (as likely they were)?

ESET Remote Administrator (Server), Version 6.5 (6.5.522.0) ESET Remote Administrator (Web Console), Version 6.5 (6.5.388.0) I'm hopeful there's a way to schedule push installs similar to the way Windows Updates are scheduled: To occur at 2AM, but if a machine is not turned on at 2AM, the install will run at the first 2AM after it IS turned on. And specifically, not immediately, if missed. That's the only way to include the necessary restart in a way that it won't interrupt people. If I schedule installs to occur at 2AM daily, will it skip computers where the current ESET AV is already installed, or will it reinstall every day?

Hi Patrick Here's the vendor's response: "I'll have to call my ESET rep and see if there is some way for them to do a name change on their side. The only way for us to do it would be to do a return and rebill. Essentially, the way they're explaining it, the licenses register to the ship to name." She later confirmed that it can be changed and that is now in process. Perhaps what she said is incorrect. But if it is correct...the ship to name?? Pretty much ANY name, or even NO name, will get a package delivered. But shipping is all the Ship To name is intended for. The quality of the data being leveraged is insufficient for licensing identification. All in all, a fragile system susceptible to typos, or substitutions like "Company" vs. "Co." Thanks for your offer. It sounds like I'll have a new license file shortly, but if I have further problems, I'll take you up on your offer.

Ahhhh...that's extremely likely since the licenses originated from 2 different resellers, initiated by 2 different IT consultants, at 2 widely-separated times, and ordered by 2 different office managers! A glaring weakness in ESET's copy protection scheme, I'd say. Thanks for the tip; will pursue when I'm on site tomorrow. Copy protection: When are vendors going to accept that it's successful only at preventing legitimate customers from using legal, purchased software, greatly annoying them in the process, AND is easily bypassed by pirates. This has just cost a church a couple hundred dollars in consulting fees, over what is likely a trivial change in how someone at CDW entered the name of the legitimate customer vs. how it was done by whoever was the prior reseller. I know my rant will never be read by anyone at ESET who could (or would) do anything about it, but at least I got it off my chest! [EDIT] OK, one more rant. ESET: If the license file can't be accepted for some reason, but especially a trivial and easy-to-have-happen reason like a difference in company name, how about posting a message about WHY it can't be accepted, instead of a confirmation promising that ERA will select the most "appropriate" license. When it will, in fact, do nothing of the sort?

Thanks...that's what I did. So I guess I need to contact support again.

Hi, CB530, thanks for your reply! I did make a mistake configuring the RA server on the clients; I typed hxxp://servername instead of servername. Once I corrected that, the 2 clients that had previously registered as Endpoint clients quickly re-registered as File Security clients, and the datestamps updated. All other aspects of the article you linked to are already correct. The other 3 servers are still missing in the console. Based on the success of the others, I suspect they are trying to register, but are blocked by the licensing problem. License Manager still shows the 15 original Endpoint licenses, and shows the corresponding license file, but does not show the new license file for File Security that I imported and uploaded for the 5 File Security clients. I've tried the import & upload of the new file 3 times. This article hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN2253, a link to which was included in the email I received with the File Security download and license information, does not appear to address the File Security product. Do I import it into ERA or into File Security?

Finally returning to this. We have obtained 5 licenses for ESET File Security for Windows Servers. I installed the software on the servers (interactively, not by push) and entered the update server and RA server to match the existing ESET Endpoint clients. I imported the new license file and updated the server (no errors reported). They are updating from the server, but are not reporting. More than 10 minutes later: The only servers showing in the console are the two that took two of the 15 original licenses. The other 3 servers are still MIA. The 2 servers that are displayed are still showing as "ESET Endpoint Antivirus" clients and their last contact time was when I uninstalled ESET Endpoint. License Manager still shows the original 15 licenses, and I still get the warning when I open ERA that 15 licenses have been consumed.

Hi Patrick, thanks for your reply! I don't know where to find the "Advanced Settings">Miscellaneous>Remote Administration setting you described. But I also didn't look at the client list carefully enough. Two of the ESET/WS clients are appearing in the console. However, 3 are not, including the machine on which ERA is running. So I don't think it's a server config problem. I am now wondering if this is a license problem. We migrated from ESET 4.x on WS2003 to ESET 5.x on WS2012. The ESET 5.x install was a fresh install; the 4.x ESET server was not working properly. We had 15 licenses, and those licenses were imported into ESET 5.x. 13 of those licenses were claimed by 13 workstations. We now have 5 servers, so we purchased 5 ESET/WS licenses. However, there are still only the original 15 licenses in License Manager. I was out of town when the ESET/WS software was purchased and installed; my replacement might not have known where to import the license. I have asked him to furnish whatever information he obtained during the purchase. Am I correct that-- I will need to import a license file that would have been included with the ESET/WS purchase which will increase our license count to 20? The console will only display the number of clients for which there are licenses in license manager? TIA

ESET noob here. ERA 5.0.511.0, ESET Endpoint for Windows Server 5.0.2214.4. ESET "normal" workstation clients are appearing in the console on the Clients tab; ESET for Windows Server clients are not. The "Update" node in "Advanced Settings" on the ESET/WS client is pointing to the ESET RA server, and the ESET/WS clients are updating and running scheduled tasks from ERA. From that, it looks like communications are established; they're just not visible in the console. How can I get the console to display ESET/WS clients? TIA