timnolte-spi

I have about 60 clients to migrated to a new 6.x ERAS appliance instance from an existing 6.x ERAS Windows Server install. I tried the the Policy change option from the knowledgebase (hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN3701). While I can see that proxy settings are updated I see no reflection in the new ERAS server that these clients are connected to it in any way, from a ERA Agent perspective. It appears that my only option is to manually touch each client as the new ERAS has been unsuccessful in doing any server tasks deployments. This is very frustrating.

@verus what did you change in your my.ini? Trying to track this down and the ESET error and my Google searches for "big blocks" and MySQL don't seem to turn up anything helpful. For anyone else looking for this I found this in the documentation: Q: How do I configure MySQL to accept large packet size? A: Locate your MySQL configuration file (my.ini for Windows and my.cnf for Linux, exact location of the .ini file might differ from one operating system to another), open this file and find the section [mysqld]. Add a new line max_allowed_packet=33M (value must be at least 33M or greater).

@verus what did you change in your my.ini? Trying to track this down and the ESET error and my Google searches for "big blocks" and MySQL don't seem to turn up anything helpful.

Honestly feel likes it's pretty poor to release a new version, then come off and say that it's really just a public beta. I had high hopes for what I saw in ESET, as we just came from TrendMicro. This sort of shoddy work is not becoming of a software company that is serious about their products. I don't even understand what the point of them putting out the OVF appliance version if essentially it's unsupported and doesn't even work.

So the latest issue I see in the configuration setup is now with the ODBC driver: Error: ODBC connector compatibility check failed. Please install connector with 64bit wide SQLLEN/SQLULEN types.

I'm know that my previous post is still pending moderation however I was able to connect remotely (via SSH) and get logged in. Here are a couple of issues I've found. 1. Passwords: I had a randomly generated password that included a '%' in it. I don't think the console management likes that character in the password. I've since redeployed using a password with both '*' and '@' and that password is working. 2. Windows Domain: If you attempt to setup the Windows Domain configuration the way it is generating the smb.conf and then trying to join the ERAS to the domain is at least incorrect for our environment. When I manually change the smb.conf file to use the <DOMAIN> in the 'Workgroup' (as it is doing) and <domain.com> in the 'realm', then the 'net join' command worked just fine. The automated smb.conf setup puts <DOMAIN> in both the 'Workgroup' and 'realm' parameters which does not work for our environment.

@eBriggs care to share any tips on how you got it working and anything special you needed to do, as well as any items you perhaps didn't fill out in the configuration step? (i.e. Windows Domain/DNS)