Jump to content

RvW

Members
  • Posts

    84
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by RvW

  1. Meanwhile there is a KB: Server migration in ESET Remote Administrator 6.x
  2. You can check that EOL here: https://support.eset.com/kb3592/#ees
  3. Hello M_K, sorry for the late reply. If I were you I would create a support ticket or contact your ESET country distributor.
  4. Problem: Just tried to install EIS for a home client and got an error MSI.1921. There was no ESET in Control Panel > Programs. Solution: I used ESET Uninstaller in safe mode and (some traces of) ESET Smart Security (ESS) showed up. Removed that, rebooted, installed and activated EIS successfully.
  5. No. You can transfer a license from one of your PC's to another but you can't transfer a license from one client to another. Translation: Nein. Sie können eine Lizenz von einem Ihrer PCs auf eine andere übertragen, aber Sie können keine Lizenz von einem Kunde auf einen anderen übertragen.
  6. Hello Manolito, have you tried Brubra's suggestion? That should work.
  7. This seems to be an issue with the repository synchronization. Please contact support, submit a ticket and provide a trace.log with "Trace" verbosity from the server, a Wireshark log of the communication (when the content is loaded) and the PLID of the license that is used for ERA activation (can be seen in ERA’s About window).
  8. Hi, I have some additional information: Each time I log on there is an error : date | Personal firewall | Adding root certificate to all browsers on your PC failed | name of PC Also in the registry there is a field FirefoxImportFailed which is set to (1). When I mport the cert manually it is set to (0): That only works unitl I log in again: After logging in it is again (1) and the same error (Adding root certificate to all browsers on your PC failed). And we're back to Entrust instead of ESET: Any idea what may be causing this? ;-)
  9. That's not the issue. Every browser uses the "ESET SSL Filter CA" root certificate. Only Firefox uses an "Entrust" root certificate. Is there any reason for that?
  10. I'm using ESET NOD32 Antivirus (EAV) v10. When I visit a website using Edge, IE, Chrome and Opera it will usually say the root certificate is "ESET SSL Filter CA". However, when using Firefox (latest version) it says "Entrust". Is there any reason for that?
  11. Hi guys, Look at this KB: ESET Mobile Security for Android FAQ. It says: Anti-Phishing integrates with the most common web browsers available on Android OS. In general, Anti-Phishing protection is available for stock browsers that come as pre-installed on Android devices. Chrome is also supported except on Android 6 – we are currently working on the fix. If there is any news I'm sure that KB will be updated.
  12. If I'm not mistaking Chrome 64-bit is not supported. At least not all versions. Are you using the latest version? This is also mentioned in the KB: Known Issues: Microsoft Edge browser is not supported at this time 64-bit version of Chrome (x64) is not supported at this time A browser started from the Windows Metro environment is not supported Windows XP x64 is not supported
  13. Please have a look at this KB: How do I use ESET Banking and Payment protection? You may need to add some banking sites manually.
  14. Please have a look at this KB article: Which email clients are compatible with Windows ESET products? If that doesn't help please submit a support request (just open ESET > Help and support > Customer Care > Submit support request).
  15. Please provide the exact link (URL) where you noticed this. Thanks!
  16. ACT.5 is indeed an ERROR_INVALID_LICENSEKEY error. You should contact the company you bought it from and if they can't help you submit a support request (just open ESET > Help and support > Customer Care > Submit support request).
  17. Come on, guys! The Migration Tool works fine for thousands of customers. Yes, it may not work for everyone, there may be environmental issues ESET just can't know about... Just. Do. A. Clean. Install. It will allow you to familiarize yourself with the latest version. You will thank me for this afterwards.
  18. If you're getting an activation error ACT.24 most likely your regional settings are causing this. The reason could be your region was set to country A when you registered your initial license and your region is now set to country B when renewing your license. Try setting your country back to A and try to activate. This KB has some additional info: I received an activation error while installing my ESET product - what does it mean? hxxp://support.eset.com/kb2434/
  19. Hi Abdul majeed, Would you be so kind to create a new topic, please? This topic is about the ACT.32 error. You're asking about ACT.24. Thank you. I did it for you. You can find it here: ESET Activation Failed error ACT.24
  20. Hello xbures, Bbahes has a good point. Upgrading from Remote Administrator 5 to 6 is a decision that should not be taken lightly. It is imperative that you familiarize yourself with the differences between both versions as version 6 introduces a completely new architecture compared to earlier versions of ERA. Please install ESET Remote Administrator 6 on a (virtual) test machine and have a look at the new interface and its features. When upgrading from version 5 to 6 you should do it for all machines (workstations, servers, Remote Administrator, the whole shebang). Please have a look at the following article: ESET Remote Administrator 6 - FAQ / what's new? hxxp://support.eset.com/kb3590/ And now regarding your question: - did you follow the manual? hxxp://help.eset.com/era_install/63/en-US/index.html?migration_tool.htm - Is the v5 a default installation or some tweaking with ports, etc.? - User permissions? - Do you have any complex policies in v5? If not you may want to consider a clean install? Hope this helps...
  21. And in addition to Michal's post: For ESET Remote Administrator (ERA) v6.3 : hxxp://help.eset.com/era_install/63/en-US/index.html?upgrading_apache_tomcat.htm
  22. Just found this: Gustav Brock added the following: 2.1. For Windows 7 clients with Office 2007/2010 the solution was to turn on the WebClient service in combination with switching off indexing of off-line files as suggested by James Nelson. To turn on the WebClient service go into your Services (this must be done with an Administrator account). Locate the service WebClient. I will probably be set to manual. If you look at your XP machines the service is set to Automatic. Turn this service On and set it to Automatic. Now try opening your files and saving them from the shared drive. It should be much faster. 2.2. For Windows 7 clients with Office 2003 and Windows XP clients, this didn't change much (for WinXP the Web Client was already set to Automatic). However, turning off Office File Validation did the trick. This is explained here next to the bottom: hxxp://technet.microsoft.com/en-us/library/gg985445%28office.12%29.aspx Hope this helps.
×
×
  • Create New...