carmik

In that case, how would one go to update from 32-bit ERA 6.5 to 64-bit ESMC? Can I backup the database and certificates, and feed them into a 7.1 installation?

Hello, we've got an ERA 6.5.522.0 installation on Windows, that was originally performed with Microsoft SQL. Since we had to upgrade to ESMC 7.x, we were considering upgrading to a ESMC VA appliance (which is MySQL-based). Is such an upgrade possible? That is, can an ERA 6.5 MS-SQL backup be converted properly for import to a 7.x MySQL database?

Also please note the need to go extra-conservative here: this is the ESMC VA server I'm talking about. I can recall at least 3-4 times whereas updating the server actually broke it and had to restore the entire VA from a previous backup...

This menu.

Thanks Marcos, just what I was looking for!

For the record, I found the feature immensely useful, especially while upgrading my systems.

Hello, got this ESMC VA server that was upgraded (no migrate) from 7.1. It indicates that it needs an operating system update, but I'm offered two options: update operating system and update operating system (custom settings). I recall I could find info about these two options, but now I can't find anything that explains the difference. Could you point out some links and/or advice on which option I should choose? Thanks in advance!

Just updated my ESMC VA to 7.2.2233.0 and discovered that multiple sorting as per the following does not work. My ESMC server details: ESET Security Management Center (Server), Version 7.2 (7.2.2233.0) ESET Security Management Center (Web Console), Version 7.2 (7.2.221.0)

@Marcos good news and bad news: ran certfix yesterday via GPO on around 150 PCs. At the time went smoothly, all clients have started updating virus bases and messages about phishing not operational have disappeared from all. Status on ESMC console was either all-ok or yellow (due to ESMC agent being an older version for example, nothing serious). Today, I've received at least 3 calls from users whose systems I personally checked that were ok. In all 3 cases: * the phishing problem came up * along with a new one, pop/http scanners do not work So far it's 3 systems, not sure if this is a regression of some sort. WIll install 6.5.2132.5 as per: https://support.eset.com/en/alert7396-legacy-products-startup-issue

@MarcosI've PM'ed you.

Hoping that I've not deleted them yet, will do so in the evening. Ok to PM you a link to my MEGA share? Expected so, then perhaps try the following:

Does the ESET uninstaller delete the c:\programdata\eset directory as well? If I were to enter safe mode, I'd do so to eradicate the actual cause of the problem, ie the files residing under c:\programdata\eset\eset security\IPM Perhaps the issue appears even on clean installations: upon execution of a license-expiring ESET app, c:\programdata\eset\eset security\IPM gets populated and causes the issue. In this case safe mode cleaning with the uninstaller won't help (since upon new installation the entire C:\programdata\eset directory will be re-created along with problematic IPM entries). Suggestion: with nod32 already installed and the issue existing, enter safe mode, only to delete those files residing under IPM. Is the issue resolved in that scenario?

What I meant is that in order to get to advanced setup, you must be able to open the eset application window; if you have this issue, you simply can't!

@itmanNot sure if that would work. In my case, I could not "hold" the eset window long enough to even open the settings... @Marcossetting this to "Solved", considering a solution has been found.

That solved the problem in all 3 systems I had issues with.

FYI, no such folder in my setup.

I've opened a ticket already, do you want me to pm you the ref number? For the record I re-posted some of the information you've asked because I was looking for them in Program Files, instead of ProgramFiles. Is it a problem if I do the safe-mode move on my daughter's system? I'd like to avoid shutting down my main rig... <offtopic>There is a problem with your ticket submission system, it does not accept mailboxes of the form mailname+alias@gmail.com. It treats the plus sign as an invalid character. This is incorrect handling as per the SMTP specification. Due to the bug right now, my browsing is very slow for some reason. Google "plus sign in mail", there's a Rutgers CS link that contains both informal explanations as well as the BNF of RFC822 (IIRC) which clearly shows + is a valid character, and widely used in Google to create pseudo-emails.</offtopic>

There is an ECP directory, but it is empty. Can not tell, sorry There are 3 directories, 2, 3, and 5.

100% sure!

I'll open a ticket right afterwards, as discussed.

@Marcos I think perhaps you should try to reproduce this in your lab, with a license close to expiration...

Just checked my son's and my daughter's laptops, which have the same windows and the same nod32 and license: the same issue is exhibited!

Yes, this is exactly what I've been encountering. @Marcos, since @NicoW stated that he corrected things by pushing back the date, could this be related to the issue encountered on Endpoint Security 6.5, some kind of regression? @NicoW can you also open a ticket and provide logs, as discussed above please, to accelerate a solution?

I'm happy to say that the issue seems to be resolved on the PCs I've made a test run on. Furthermore, on Windows Server 2003 AD, it suffices to create a new gpo with a startup script the fix file itself, provided that the file is placed in files section of the gpo. It ran via group policy without issues on 3 systems, so I'm now deploying globally. Will let you know how that goes.

@Marcosafter running this tool manually on a XP box (6.5.2132.1): 1) Endpoint Antivirus seemed fixed, but the fix window remained open for some reason. Is that expected behaviour? 2) Before applying the fix, I had the system removed from my ESMC console (VA, latest version). I expected that the system would reappear in lost and found, after applying the fix. It doesn't and I'm a bit clueless on what happened here. The system does respect the "use specific proxy to download ESET updates" policy, as I can watch from running netstat -a -p tcp. But it is invisible on the ESMC console (tried searching for it with system name and ip address). Has anyone else encountered something like that?