karlisi
-
Posts
149 -
Joined
-
Days Won
3
Posts posted by karlisi
-
-
System variables in exclusionsin general are OK. Perhaps I should start new thread for this problem, bug in default exclusions for Windows Active Directory domain controllers.
-
Sorry to say, in ERAS 5.1.38, released yesterday, bug still not fixed, exclusions for Windows AD controllers are wrong.
-
Received answer from ESET support. This bug will be fixed in next ERAS version.
-
"upgrade processing error, error code:(7,-112)" means "connection problem" .
Where can I find these error codes?
-
In these 3 months had some exchange of emails between me and ESET Latvian support. I gave them some additional information and that's all, no feedback. Still waiting and hope someone on ESET is working on this problem.
-
Should I just open ports 2221-2224 on the ERA server to the outside world? If I do this, then do you recommend setting a password for clients to authenticate?
Not necessarily all of them. Port 2222 for clients to connect to ERAS from outside of your network, and yes, I suggest to set password for clients. Port 2221 to connect to mirror server. Port 2223 only if you want to connect ERA console to ERA server from outside of your network.
-
I'd like to upgrade a computer via 'Upgrade Windows Client' function, but I got failed. The error message is 'Upgrade processing error. error code: (7,3)'.
ESET File Security 4.5.12011 upgrade to 4.5.12015
The same for me. Ended with manual upgrade. Previous version upgrades using ERAS were successfull.
-
In ERAS Console open 'Server Options', go to 'Advanced', Click on 'Edit Advanced Settings', go to 'Advanced' and enable 'MAC address renaming (from unknown to valid)'.
-
Reached licensed clients limit on ERAS? Just guess.
-
Hello
OK, it's time to introduce myself.
How did you find the ESET Security Forum? I was on Wilders security forum before. Found the old forum trough ESET support page
What OS are you running? Windows 7 on my workstation, also supporting more than 700 clients on Windows XP, Vista, Seven and Eight, also bunch of Windows servers, including some Windows 2000
What AV are you running? ESET Endpoint Antivirus at work, MS Security Essentials and Avast Free at home
What’s an interesting fact about you? My first computer was self made ZX Spectrum clone (beginning of 1990-ies there was ZX Spectrum clones boom in exUSSR). On Windows since 1995.
-
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.
-
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.
-
Bart, importing multiple licenses not worked for us, there was always last imported license in effect.
-
One ERAS can use only one license. Your reseller should be able to make embedded license from both of your current licenses. It will result in one license for 70 nodes. Embedded license expiration date will be the earliest from both.
Sure, you can use another options, like separate ERAS for servers or leave servers as standalone non-managed nodes.
-
Case sent to Customer Support
-
You are right, seems like bug in ESET RA.
-
If I not mistaken the ESET Automatic Exception List doesn't point at %systemroot%\Sysvol\Domain but at %systemroot%\Sysvol\Sysvol
As of your exclusions, you want to exclude exactly the same files which are in ESET automatic exclusions.
%systemroot%\Sysvol\Domain leads to the same place as %systemroot%\Sysvol\Sysvol\<your domain name>\
-
OK, you are right.
Tested your exclusions, not working for me also.
Found this
hxxp://www.wilderssecurity.com/showpost.php?p=2043414&postcount=6
Re: Setting Exceptions, wildcards and system variables.
I asked ESET's tech support the same question and here is part of their reply.So it looks like v5 will be able to handle this. For now I manually added the exceptions for each staff member (20), but once v5 is available this should be easier to configure properly.
-------
Thank you for contacting ESET Customer Care.
Unfortunately environment variables are not supported in ESET 4.x or below products. ESET version 5 products will be supporting Environment variables. Currently the only variables ESET recognises are "*" and "?" without the "".ESET File Security major version is 4 and, despite what Marcos is saying later in that thread from Wilders Security, system variables don't work on EFSW 4.5.
-
There are exclusions already defined in default ERAS policies, they are the same you try to write. See under Windows Server 4.5 -> Server protection -> Server -> Automatic exclusions. These rules will make correct exclusions no matter you have your AD folders in Windows directory or on separate partition.
-
No, sorry. We plan to migrate in next two weeks, so your experience can be useful.
-
Do we have to upgrade ERAS/ERAC first?
Yes. ERAS version 4 cannot manage clients version 5.
Is there a major change to the database?
Don't know, upgrade went smoothly, no needed to study database changes.
Are we going to lose all of our existing policies?
Policies for clients version 4 will stay unchanged, you should make new policies for clients version 5 after ERAS upgrade. There will be separate policies tree for v5 in configurator.
Will the clients upgrade from 4.0 to 5.0 directly or are there intermediary upgrades that need to take place?
From 4.0 to 5.0 you can upgrade directly
-
ESET detects Ask! toolbar bundled with Avira Free installer package and such bundles are common practice for freeware to keep software free. It is not the same as Avira toolbar, which is part of Avira antivirus and, as stated in their KB, part of web protection.
-
This is about Avira toolbar, not Ask toolbar.
-
Going to the Client workstation I had to enter the Update Server using the full name including port number.
Then under "Setup" and "Advanced Tools" I had to find "Remote Administration" and enter the server name but without http or port number. I see no reason to have to do both as one relies on the other they should have been on the same screen. For a rather "stock" setup, burying something like this under "advanced tools" isn't the way I would have done it. Ease of use is one of my priorities, and so far this isn't even close.
Not exactly. You can use ERAS as administration tool and leave ESET servers as update servers.
Almost there... I then needed to go to Windows Firewall on each client and add the anti-virus program to that list. Not a problem, but most other programs that need firewall access have a facility for doing it automatically. Again, I shouldn't have had to do this manually.
This is strange. I have more than 700 workstations and never needed to do something with Windows firewall to enable ESET remote administration.
To make configuration process easier, you can configure one client, then export settings in xml file and on other clients import these settings. Also, for new installations you can make customised msi file with configuration included, using ERAS console, Remote install tab, Actions -> Manage packages.
Upgrade Windows Client Error
in ESET PROTECT On-prem (Remote Management)
Posted
I don't understand this. It's the same major version 4.5, only minor version upgrade and You say, not possible. There was major version upgrade from 4.0 to 5.0 for workstations product and it went without problems.As for push install, my servers are on remote sites, there is no VPN or EoIP connections, so remote installation not possible (can't establish IPC connection).