Jump to content

RvW

Members
  • Posts

    84
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by RvW

  1. 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).

    image002.png

    When I mport the cert manually it is set to (0):

    image001.png

    That only works unitl I log in again:

    image004.png

    After logging in it is again (1) and the same error (Adding root certificate to all browsers on your PC failed).

    image005.png

    And we're back to Entrust instead of ESET:

    image006.png

    Any idea what may be causing this?

    ;-)

  2. 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.

     

    ;)

  3. 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
  4. 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).

  5. 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/

  6. 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?

     

    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...
  7. 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:


     

    Hope this helps.

×
×
  • Create New...