Jump to content

EURO-LOG

Members
  • Posts

    11
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by EURO-LOG

  1. Hello,

    since ESET File Security for Windows seems to be deprecated now and Version 7.2 will soon be not supported anymore, what should we do about older server products? Of course, replace them with a newer version - but we still have some special servers that can't be upgrade at all, but have to run anyways, at least for another while.

    Which ESET Product can be recommended for eg. Windows Server 2008 SP2, 32-bit?

    ESET Protect tells me that even File Security 7.3. 32-bit version is not available on the repository.

  2. I am currently testing Upgrade from v6 to the new v7. We always used to download updates from a local webserver (the way it was done in ERA v5) - in ESMC v7 Policies I cannot find the setting for customizing the update server. On the client with Endpoint AntiVirus v7 installed I also cannot find this. Did the update mechanism completely change in v7 - I believe not because the current version of the mirror tool is creating directories and downloading updates for v7. So how do I get my endpoint to update from our local mirror?

     

  3. Recently we replaced our installation of ESET Mail Security for Exchange v4 with the current version 6. Since then we get a lot of error messages saying:

    " Beim Ausfuhren von Kernel auf dem Computer XXX ist folgendes Ereignis aufgetreten: Keine Verbindung zur Spamschutz-Cloud moglich, Spamschutz ist nicht vollstandig funktionsfahig"

    This message shows up 5 or 6 times a day - I wonder if this is normal?

  4. Well, ok, I found out myself analyzing the IIS Logfiles.

    The Mirror Tool creates a directory structure with epd_upd as the main directory and subdirectories ep4, ep5 and ep6. To make the update work on the client I have to add the subdirectory to the update server path - in my case hxxp://10.5.100.132:2221/eset_upd/ep6

    To allow the files to be downloaded the extensions .ver and .nup also need to be added to the IIS Mime Types.

    To simplify the client configuration I might create some virtual directories in IIS pointing directly to the subdirectory needed. Unfortunately this would also require configuring different update server addresses for different client versions

  5. Hello,

    I plan to migrate our ERA5 installation with Endpoint v5 Clients to ERA6 and Endpoint v6 on the clients. I have setup a test system to try out the new versions, understand functionality and test it. The first problem I have is about updating clients - I would like to handle this in an identical way as v5 does. That means I create a local mirror on the ERA server and configure clients to use the local server as Update source.

    What I have done is:

    - Created a task that uses the Mirror Tool to download and save the update files to a directory on the server

    - Pointed an IIS7 Instance to the Directory that Mirror Tool is configured for

    - Set the IIS instance address as Update Server on the Endpoint v6 client

    The Mirror Tool is downloading the updates and creating subdirectories without errors. My client cannot update and tells me "File not found on server"

    So where is the client looking for the updates files? I can browse the directories with Internet Explorer just fine...

×
×
  • Create New...