Jump to content

dlaporte

Members
  • Posts

    104
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by dlaporte

  1. Hi Gonzalo,

    I'm not sure that the last digit is the language since I have 6.2.2021.0 on all my other machines and the agent versions have always ended in 0.

    they are all English.

     

    The issue is that I have the most updated version installed on my pilot PC's and when I check in ERAS I am being told there is a newer version (6.2.2033.2)!

    That is what I was trying to show in the screenshots.

     

    The one I took with the MSI editor is just to show what version they are showing in the actual MSI

     

    Possibly they just forgot to edit the highlighted areas from 6.2.2033.0 to 6.2.2033.2...

  2. No answer from ESET huh?

    Doesnt surprise me.

     

    So I will tell you my findings..

     

    ESET pushed to a PC through ERAS - Installs 6.2.2033.0 (even though it says it is package 6.2.2033.2!)

    ESET downloaded from Website shows version as 6.2.2033.0

     

    AS far as I can tell

    1. THERE IS NO 6.2.2033.2!

    2. They didn't change the version number in the MSI

    3. Why am I still using this product!!

     

    So annoyed!

    post-6545-0-25128700-1447876443_thumb.png

    post-6545-0-13734500-1447876620_thumb.png

  3. Well

    I created my new GPO to upgrade versions (6.1.2222.0, 6.1.2227.0,6.2.2021.0)

    Applied on 3 machines

     

    we shall see...

     

     

     

     

    Changelog

    Version 6.2.2033.x

    Added: Search field for long lists and rules (for example, Antispam list, Web control list, etc.)
    Added: Plugin for Office 2016
    Fixed: Incorrect parameters displayed in overview when creating scheduled task in Scheduler with weekly repetition on Windows 10
    Fixed: Firewall profile not overtaken during migration from ESET Endpoint Security 5 to ESET Endpoint Security 6
    Fixed: SSL Certificates not overtaken after MSI upgrade from ESET Endpoint Security 5 to ESET Endpoint Security 6
    Fixed: Second scan of removable media does not start​ when started from notification
    Fixed: Web control switch indicates enabled status after permanently disabling Web access
    Fixed: Scan logs not present if product is installed in folder with non-Latin characters or folders with diacritics
    Fixed: Web access protection not working after application is repaired with MSI package on Windows 7 x64 SP1
    Fixed: Problems with reactivating product using offline license file without username and password
    Fixed: Activation fails after reactivation with offline license
    Fixed: Clicking the Default button does not return Device control to default 

    Fixed: Plugin for Microsoft Outlook 2003 is not correctly integrated
    Fixed: Revert to default in Personal firewall does not work as expected
    Fixed: Missing “add” button for SSL certificates in Czech version of Endpoint
    Fixed: Shutdown after scan does not work as expected in German version of Endpoint
    Fixed: Minor text modifications
    Fixed: Minor user experience fixes

     

  4.  

    I have set up GPO's that not only push out ESET Remote Administrator Agent and ESET Endpoint Security, but also Upgrade older versions!!

    The beauty of doing it this way is there is no pushing on my part.

     

    When a new Endpoint version is available I:

    1.  edit the MSI with ORCA create the MST

    2. Update the GPO to upgrade older version.

    3. email staff that their devices must be restarted that night.

    4. When they log in they get a verbose message that explains that ESET is getting installed.

     

    done

    When the GPO runs for the first time it creates an entry in the registry, then once the software is installed it creates a new key.

    This new key will be used for the GPO to reference in future reboots.

    the GPO will see the key is there and is the newest version and not run again.

    works quite well.

     

    I did create the GPO for each site pointing the .MSI installer and the .MST to the local DC for that site.

    It usually takes about 1-2 minutes when to finish after they do a CTRL+ALT+DEL.

     

    my 2 pennies

    Did you use the instructions from the ESET site to create the GPO?  I tried to do that, and it does not work.  I even worked with ESET support for about 4 hours and they were not able to help me setup a GPO to install the agent or the client.  I'd love to know if you did anything specific in your environment that may not be on the documentation. 

     

     

    I did use the instructions from ESET. Worked like a champ?

  5. I have set up GPO's that not only push out ESET Remote Administrator Agent and ESET Endpoint Security, but also Upgrade older versions!!

    The beauty of doing it this way is there is no pushing on my part.

     

    When a new Endpoint version is available I:

    1.  edit the MSI with ORCA create the MST

    2. Update the GPO to upgrade older version.

    3. email staff that their devices must be restarted that night.

    4. When they log in they get a verbose message that explains that ESET is getting installed.

     

    done

    When the GPO runs for the first time it creates an entry in the registry, then once the software is installed it creates a new key.

    This new key will be used for the GPO to reference in future reboots.

    the GPO will see the key is there and is the newest version and not run again.

    works quite well.

     

    I did create the GPO for each site pointing the .MSI installer and the .MST to the local DC for that site.

    It usually takes about 1-2 minutes when to finish after they do a CTRL+ALT+DEL.

     

    my 2 pennies

  6. Here is what I have done to alleviate the problem

    1. Run M$ Hotfix KB2664888

    2. Restart Machine

    3. Update ESET Agents to 6.2.190.0

    4. Update ESET Endpoint to 6.2.2021.0

     

    What does the patch do?

    It updates the file netio.sys

     

    What was causing the freezing?

    When the ERA agent was upgraded to 6.2.200.0, the new version incorporated a different kind of API.

    This new API on the server end has a fatal communication issue with client Windows 7 PCs running an old version of NETIO.SYS.

    NETIO.SYS is a Windows device driver located in C:\Windows\System32\drivers folder.

    It is used to support Windows hardware device driver Network I/O subsystem. 

     

    The ESET agent on the PCs make use of the NETIO.SYS driver when communicating over the network.

    NETIO.SYS has a function within called FwpsStreamINjectAsync.

    This function injects TCP data segments in a TCP data stream. 

    The theory is that FwpsStreamInjectAsync doesn’t work with the new API on the server, and when communication occurs between the server and PC, that function on the PC issues a IRQ (interrupt request) that is handled by the APIC (Advanced Programmable Interrupt Controller) for CPU which stops running program to allow, say communication of data from NIC card to get CPU time. 

    We don’t know exactly what operation is issued to the function that caused problems, perhaps a divide by zero or something that causes the IRQ to leak and lock system.

     

     Once you apply the patc​h (AND RESTART THE PC!) the netio.sys file will be updated (date should be 4/4/2014, version 6.1.7601.22648)

     

    .

     

    We have had no issues a​fter that.

     

    Good Luck

    I only have 500 more to​ patch.

  7. You should contact support and ask them for the link.

     

    Why you need a 6.1 when 6.2 is the latest which also correct some problems of 6.1??

     

    I need 6.1 because I can create a package of that version and add it to my GPO..

    My GPO will install the new version (if no ESET is detected, will upgrade version 6.1.222.0, and will upgrade version 6.1.2227.0)

    Well once I get the MSI's (64 nad 32 bit) for 6.1.2227.0 and edit them and add them to the GPO software package it will upgrade all existing versions I have on my network.

     

    Much better way to deploy than waiting on a push install..

     

    Dante'

  8. I have created GPO's that will:

    1 - Install the newest version of the Agent (if it doesn't exist at all)

    2 - Upgrade the agent (if it exists) to the newest version

    AND

    3 - Install the newest version of EES (if it doesn't exist at all)

    4 - Upgrade version 6.1.222.0 to newest version (if it exists)

     

     

    5 - Upgrade version 6.1.2227.0 to newest version (once i get the MSI's)

     

    Can anyone get me a link?

     

    TY

     

     

×
×
  • Create New...