Display ESET for Windows Server machines in ERA

[JRV 1]

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

[PatrickL 21]

JRV,

 

  The update action and the Remote Administration (communication with and consequently visibility in the clients tab of the Remote Administrator) are two seperate actions. You described making the necessary changes to the Update settings. Now you need to make similar changes to the Remote Administrator section with is located in the "Advanced Settings">Miscellaneous>Remote Administration. Please ensure the check-box is marked and that the primary servier is populated with the Remote Administrator console servername (no http or port number necessary in the server name field). Once you commit that by saving, it will report back to the console within the standard timeframe of 10 minutes.

 

Please let me know if I can help further in regards to this issue.

 

Patrick

[JRV 1]

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

[karlisi 26]

Am I correct that--

• The console will only display the number of clients for which there are licenses in license manager?

 

When client count reaches the number of clients in license, ERAS stops adding new clients.

[JRV 1]

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.

[CB530 70]

JRV,

 

There is a chance that you still need to configure your clients for remote administration the way that PatrickL pointed out. Check out this article, the steps in part I describe how to properly configure clients such as your EFSW machines.

[JRV 1]

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?

[CB530 70]

Hi JRV,

 

You need to upload the license file to ERA, it should recognize that you have File Security installed.

[JRV 1]

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

[karlisi 26]

If you view the license keys in a text editor, does the CUSTOMER_NAME field match?

https://forum.eset.com/topic/1098-multiple-issues-with-era/#entry5899

 

Contact your reseller to correct Customer name.

 

Another option is to make embedded license, in this case you will get one license with expiration date from original license which expires earlier.

Edited October 9, 2013 by karlisi

[JRV 1]

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?

Edited October 9, 2013 by JRV

[PatrickL 21]

JRV,

 

   I do appologize for the scenario that the third party vendor (reseller) has put you into. It is indeed awkward when someone outside a direct relationship causes the system to slow down. At the tail end of this, I will certainly have someone from my side contact the vendors and work to improve their processes to minimize the chances of this occuring again.

 

I would like to put myself out there to assist in a slightly more direct fashion. If you would please PM me a message with the EAV usernames from both of your licenses, I can use that to determine where the mistake is occuring, correct it, and (if you provide me an email address) send it back to you revised as well as the steps to remove the current offending license files and replace them.

 

At the end of the day, we are looking to ensure you a smooth transition from where you are now (not entirely working) to where you want to be (entirely working and secure).

[JRV 1]

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.

Edited October 10, 2013 by JRV