avielc

Hey Peter, Unfortunately, this is a PC solution, I"m looking for the Mac OS X solution (eventually I have figured it via policy, but it's a good to know if such option exist)

Hi All I need a command line options to force start eset web access protection and such for Mac OS X Tried to look it up, couldn't find something. and on a general thought, is there a way to force the user to not be able to disable any AV related options? Thanks.

Excellent, Thanks for the quick answer Michal, i have put that tab into action as well as add dynamic group under All with the relevant entries to filter Computers with older agents. Thanks for that.

+1 @Marcos @MartinK @MichalJ I'm refreshing this topic as it is especially helpful on the new ERA 6.5. is there a proper and better approach to make a dynamic group that can tell me which agents\EAV\EES isn't updated to the latest (this is counted as alerts under the installed applications) would appreciate filtering the ones I haven't done in the mass upgrade staging.

well, i can think of the following two options: 1. the credential's permissions level is incorrect (though I'd assume it would return an error) 2. maybe something to do with the first setting? (sync only computers instead of groups and computers) other than that, i'm out of options really...

hahah, completely understandable, I'm sometimes feeling the same when trying to figure the log :-) could be that specifically the installation on that system got corrupted and will need a fresh manual installation on that system to be able and stand better for another uninstall task. (i'm working with elimination function on these issues, trying to simulate how to solve everything step by step from all the options available, long, but QA certified ha!) Also, if you are using Device control policy that might require you to restart that computer to remove any left over drivers. and one more thing, Uninstall task on ESET 6.4 could include uninstall older AV version, sometimes you might wanna try that or the all AV uninstall option there. maybe you need to try a different uninstall procedure Fruit for thought of course, you don't have to take anything from that, and can just wait for the real support to examine and report back on the logs. :-)

haha, no surprise, I do wonder though what's the cause of that. I have this weird issue on my side as well ERA 6.4 trying to upgrade MacEAV 6.2.7 directly to 6.4.168, fails on inability to find the http package (usually means no package found in the web repo) but i am able to upgrade from 6.3.85.1 to 6.4.etc maybe, just maybe, if I understood your issue well, trying to upgrade from a client that doesn't have a proper uninstall client\proper msi package on repo just fails to some bug in the repository, and simple 2 client tasks, one for uninstall another for fresh installation should solve it?

Thanks man, appreciate your assuring words, However, as you're aware, we (IT) LOVE to be 200% sure, even if everything should work as expected. Since these are still the first days of the roll out, I'm waiting to find more info through topics that raise in the forum, (and assist where possible) to get the grasp of the full issues that I may run into. As you say though, it looks quite solid, only the SQL seems to be a small hiccup, (I'll move on to backups soon enough and upgrade it soon after. Thanks again man, really appreciate it. Aviel

any errors? (check the execution or dashboard with server tasks to see any info)

@dasasdas - Could be that "USE LDAP instead of AD" function? I don't have it marked at my place

@Marcos - either you get the better answer, beat me to it in a split second ;-) Nice going man, I was aiming for the Device control policy

@a3pl - It all depends on the ESET configuration From experience I can share with you that the Media control policy requires a computer restart to integrate the policy into the computer. So when you upgrade such computer who is under certain aspects of ESET configuration it is required to restart the computer restart = shut down\reboot to the computer. Sleep\hibernate\closing the lid doesn't count as restart. as for a fix, check the policy of your system, see what required a system restart, usually this would also apply to upgrading.

@jdashn, @MartinK - Any updates about the issue? If ERA 6.5 has some problem installing\upgrading EAV 6.5 I might prefer to delay the upgrade until a solution is found and implemented. Thanks by the way for sharing the findings, and Martin thanks for helping!

@MartinK - Always stealing the spotlight buddy ;-)

Sure mate I don't have either(currently), but I used to have my computer list duplicated (when I first moved to ERA 6) and occasionally when I change computer names or have this little glitches I get the same name (or one with FQDN and another without) one in the AD OU and another in Lost & Found

@hungtt @MartinK Hungtt - I think Martin tries to tell you "SQL Server Agent" is not suppose to be in "running" state all the time. only when "SQL Server" requires it will be running. so don't worry about it. IF "SQL Server" is not running, it would be a problem, because all the database is working through this process. Hope this clears this one out.

@Marvin - Assuming it may be related to the auto computer renaming task that runs under server tasks. which does the correction every now and then. Or perhaps your AD synchronization task find those computer objects as a duplicate to the names it has in the AD OU and moves them to lost and found. You should use the rename computers task to correct all computers to a single convention, and remove duplicates keeping only the objects with Agents\AV installed and copying them over to the right place in the AD OU (while those who exist with the duplicate name should be deleted) also, deny ERA from keeping computers with duplicate names, thus eliminating the possibility of having duplicate computers where one is related to the AD while the other related to the lost and found.

Clearly

@Futura - as always its in this forum, they make a sticky of announcements that are released.

Thanks Michal, sounds awesome! (I'll wait for the official announcement before upgrading)

@MichalJ - Thanks for that, Updating it should be as smooth as "upgrade server" task on ESET?

@Marcos - Could it be its out version 6.5.522.0?

Sorry Michal, been busy with work, I couldn't get a chance to respond to this thread. I'm leaving this subject for the time being, as i've came up with my own solution with an email with the columns i found has the most information if issue was handled or not, (I think its action description or something, e.g.: file deleted, etc) That was good enough for my reports. I would however like to suggest remodel that, there are way too many columns which some don't even return any information that is user friendly \ readable. not to mention "threats" under the web console has different information compared to different reports you can find under reports generations. Don't get me wrong, some reports are quite useful, but they aren't as easy to work with as clicking "threats" and seeing what happens with your current state of network. (and you are limited in some to specific conditions which can't be added in others, e.g. : range of dates for threats, i don't remember exactly which report you couldn't choose a date range of results, so I had to take a range of 40-60 entries and manually choose which dates are good for me and what aren't) Thanks again for all the support, i really appreciate all your help in that (that goes to all the staff as well). Aviel

Thanks Michal, appreciate it.

*bump* any comment?