Jump to content

tbsky

Members
 View Profile  See their activity

  • Posts

    231

  • Joined

  • Last visited

  • Days Won

    3

 Content Type 

Posts posted by tbsky

    3 years license and MSP

    in ESET Licensing for Business

    Posted

    Hi:

        we maintain IT infrastructure for some companies. we suggest Eset and resell Eset product to them. normally we chose 3 years license which has best price. but this week we got message from our local distributor that they won't offer 3 years license anymore in the future. I wonder if this is a global policy, so we can only choose annual license?

     if that is true, I wonder if become MSP to resell the license is a better option for us. is there any price advantage to become MSP, and is there any qualification criteria for MSP?

     

    mirror location policy for both endpoing v9 and v10

    in ESET PROTECT On-prem (Remote Management)

    Posted

    13 minutes ago, Marcos said:

    A product should update from a folder with mirrored files for the product's version. Of course, it will work as long as both versions use the same modules and no new module was added in the newer version.

    so your answer is not the same as our eset local support.  folder ep9 and ep10 has many different filename and the files are very different (content and size) even with same filenames. so I don't quite understand the meaning for same module. for ex:

    diff -ruq ep9 ep10 | grep differ
    Files ep9/dll/nod1C88.dll.nup and ep10/dll/nod1C88.dll.nup differ
    Files ep9/dll/nod1CE8.dll.nup and ep10/dll/nod1CE8.dll.nup differ
    Files ep9/dll/nod324A.dll.nup and ep10/dll/nod324A.dll.nup differ
    Files ep9/dll/nod3C6E.dll.nup and ep10/dll/nod3C6E.dll.nup differ
    Files ep9/dll/nod3F6F.dll.nup and ep10/dll/nod3F6F.dll.nup differ
    Files ep9/dll/nod42BC.dll.nup and ep10/dll/nod42BC.dll.nup differ
    Files ep9/dll/nod4A79.dll.nup and ep10/dll/nod4A79.dll.nup differ
    Files ep9/dll/nod6236.dll.nup and ep10/dll/nod6236.dll.nup differ
    Files ep9/dll/nod7795.dll.nup and ep10/dll/nod7795.dll.nup differ
    Files ep9/dll/nodA067.dll.nup and ep10/dll/nodA067.dll.nup differ
    Files ep9/dll/nodB00E.dll.nup and ep10/dll/nodB00E.dll.nup differ
    Files ep9/dll/nodCC08.dll.nup and ep10/dll/nodCC08.dll.nup differ
    Files ep9/dll/nodD608.dll.nup and ep10/dll/nodD608.dll.nup differ
    Files ep9/dll/nodE1E6.dll.nup and ep10/dll/nodE1E6.dll.nup differ
    Files ep9/dll/nodF1EF.dll.nup and ep10/dll/nodF1EF.dll.nup differ
    Files ep9/dll/nodF8D8.dll.nup and ep10/dll/nodF8D8.dll.nup differ

    could you take a look at ticket 11020?

    mirror location policy for both endpoing v9 and v10

    in ESET PROTECT On-prem (Remote Management)

    Posted

    On 1/23/2023 at 8:56 PM, Marcos said:

    V10 users more modules, such as the Secure browser module, however, older versions that do not have the Secure browser feature will simply not update this module from a mirror if they update from the v10 folder.

    Hi:

        I got some responses from local support with ticket 11020 during the month.

        at first they said I should use ep10 mirror for both v9 and v10.  ep10 mirror size is smaller than ep9  because ESET withdraw some products which use the ep10 mirror. although there is no answer about what products are abandoned.

       but yesterday they told me the previous answer was a mistake. v9 should use the ep9 mirror and v10 should use the ep10 mirror.  they are not interchangeable.

       can I get a final confirm here about the question?

       maybe this should be documented. as you can see, I already spent over two months trying to get a correct answer.

     

    mirror location policy for both endpoing v9 and v10

    in ESET PROTECT On-prem (Remote Management)

    Posted

    7 hours ago, Marcos said:

    When using a mirror, how do you share the mirror folder via http for other clients? You could use an http server with the home directory set to c:\mirror\v9 (v10,v11,...) and access it via hxxp://server/nodupd which would always stay same and you'd just change the home folder in the http server setup over time.

    You could also use http proxy or ESET Bridge to cache downloaded files. It would also enable clients to take advantage of ESET LiveGrid and pico (streaming) updates.

    sorry I read your post several times, but I can not understand what you said. my current mirror directory structure which created by eset MirroTool is

    eset_upd/{ep9,ep10}

    and my policy of the update location is  hxxp://server/eset_upd/ep9

    indeed I can create a hxxp://server/nodupd to "eset_upd/ep9" or "eset_upd/ep10". but that was working because when I need to maintain only one version. now win7 need ep9 and w11 need ep10 so I need to maintain two versions but a single "hxxp://server/nodupd"  can not point to two directories.

    the best method is that endpoint can find out the right sub-directory by itself so I only need to tell the policy update location is "hxxp://server/eset_upd" . then endpoint v9 will find its file is under "hxxp://server/eset_upd/ep9" and endpoint v10 will find its file under "hxxp://server/eset_upd/ep10". but Eset didn't have this kind of design so the alternative method is let two versions share the same update directory. at first I thought ep9 and ep10 should share the "ep9" directory. but at previous post you told me ep9 and ep10 should share the "ep10" directory.  since ep10 mirror size is smaller than ep9, I don't know what part will be missing when ep9 use ep10 mirror directory. that's the confusion.

    thanks a lot for your help!

    mirror location policy for both endpoing v9 and v10

    in ESET PROTECT On-prem (Remote Management)

    Posted

    On 2/2/2023 at 7:31 PM, Marcos said:

    I'll try to prepare an environment for testing mirror updates and to compare the size of folders, however, since it may take some time, the best course of action would be creating a support ticket so that the case is tracked in the system.

     

    Hi:

          I had create ticket number 11020 and got initial reply. but there were no further response.  I am preparing to deploy version 10 soon. hope the confusion can be solved.

         thanks a lot for your help!

    mirror location policy for both endpoing v9 and v10

    in ESET PROTECT On-prem (Remote Management)

    Posted

    13 hours ago, Marcos said:

    I've learned that Version 2, your local ESET distributor, doesn't use a system integrated with ESET's global ticketing system which is why we could not find your email there. That said, the problem with receiving a confirmation email at your Gmail address would need to be investigated by Version 2.

    I'll try to prepare an environment for testing mirror updates and to compare the size of folders, however, since it may take some time, the best course of action would be creating a support ticket so that the case is tracked in the system.

     

    thanks a lot for your kindly help! I will create a ticket again.

    mirror location policy for both endpoing v9 and v10

    in ESET PROTECT On-prem (Remote Management)

    Posted

    21 hours ago, Marcos said:

    Yes, try again please. Did you use your forum email address when creating the ticket?

    Hi:

        I try again and still get no response. I change to another email address and this time I get a reply email with ticket number soon. so there is something wrong between Eset support and Gmail. with the same gmail address I can receive "ESET Knowledgebase Support News". the News mail is from "feedpress@newsletter.feedpress.com". and the support notice mail is from "support@version-2.hk". maybe the location I select is the issue.

     

    mirror location policy for both endpoing v9 and v10

    in ESET PROTECT On-prem (Remote Management)

    Posted

    On 1/23/2023 at 8:56 PM, Marcos said:

    V10 users more modules, such as the Secure browser module, however, older versions that do not have the Secure browser feature will simply not update this module from a mirror if they update from the v10 folder.

    I really like to set both v9 and v10 endpoint to v10 mirror. but you didn't answer the question that v9 mirror size is much larger than v10.  so there must be something strange. if v7-v10 can use the smaller v10 mirror, why Eset produce the larger old mirror? is there some old versions need the old mirror?

    mirror location policy for both endpoing v9 and v10

    in ESET PROTECT On-prem (Remote Management)

    Posted

    2 minutes ago, Marcos said:

    Modules are same for all Windows products, the only difference is between Endpoint v6.5 and older and Endpoint 6.6 and newer. That said, you can update Endpoint 6.6 and newer from the v10 mirror folder.

    I don't understand. for example, the ep10 mirror size is smaller than ep7. I thought that is because ep7 is older and need more update components. if client 6.6 and newer can use ep10 mirror, then why should we mirror ep7-ep9?

     

    mirror location policy for both endpoing v9 and v10

    in ESET PROTECT On-prem (Remote Management)

    Posted

    Hi:

       the endpoint version is jumping so fast from v7 to v10.  Every time when I upgrade client version, I need to set the mirror location at policy like "hxxp://nod32.example.com/nod32-update/eset_upd/ep9"

       now I need to upgrade win10/w11 client to endpoint v10. but v10 won't support win7 anymore, so win7 should stay at v9.

       now I need two mirror locations "ep10" and "ep9" for win10/11 and win7.  I wish I can use some macro at policy like "hxxp://nod32.example.com/nod32-update/eset_upd/${current_version}".  (like auto update via eset server there is no need to setup version)

     if the marco is not possible, I know that ep7-ep10 mirror contents seems forward compatible  but  there is no document about these. is it safe to set the mirror location to "hxxp://nod32.example.com/nod32-update/eset_upd/ep9" for both endpoint v9 and v10 forever?

    the last thing I want to do is setup different mirror location policy for each endpoint client. hope I don't need to do it.

     

     

     

     

     

     

      

    Version 10.0.2034 and Windows 7

    in ESET Endpoint Products

    Posted

    On 12/5/2022 at 10:46 PM, itman said:

    Good question.

    I would open a support ticket and ask this question there. My best guess is when Microsoft make a public announcement on extended support details for Win 10, Eset will make its decision on extending support.

    thanks a lot for the help. I hope it's not too hard to support these win10/win11 LTSC/IOT versions. since they were born about the same time as windows server (like windows server 2016/2019/2022). maybe they can be supported together.

    Product out of date

    in ESET Endpoint Products

    Posted

    On 12/3/2022 at 3:28 AM, itman said:

    The difference between Eset EOL and product update notifications is explained here: https://support-eol.eset.com/en/trending_eol_products.html .

    EOL notification is show in red. Product upgrade notification is shown in orange. I agree 100% that there should be a way to disable product upgrade notifications; at least on managed endpoint installations. Displaying the upgrade notification on the Eset console would be sufficient.

    Yes please make an option so EOL only shows to Administrator. it is really a bad idea to disturb end users when they are managed. 

    Version 10.0.2034 and Windows 7

    in ESET Endpoint Products

    Posted

    9 hours ago, itman said:

    Here's the relevant OS support link: https://support-eol.eset.com/en/policy_business/os_support_policy_win.html .

    My take on this is EEA/EES ver. 10.x won't even install itself on any device with Win 7 installed . As such, an existing EEA/EES installation on Win 7 will not try to auto upgrade to ver. 10.x. If did, the installation would fail anyway.

    according to the chart, win10 support will end at 2025?  but win10 1809/2021 LTSC/IOT have upstream 10 years support, so win10 will survive at least until 2028(LTSC/IOT)/2031(IOT). can eset be used at that time?

    mirror location compatibility and parameter

    in ESET Endpoint Products

    Posted

    20 minutes ago, Marcos said:

    While dll modules are shared across products, different versions may be available for specific product versions at times (e.g. we may release a module update only for v9 products and for older versions with a delay). Even if a new version of the mirror tool was not available on the day of release of a new major version, you could temporarily use the latest available. Of course, we'll do our best to make an updated version of the tool available on the day of release of new major product versions.

    thank a lot for quick reply. in my current situation, we are using ep8 and want to upgrade to ep9. so there will be some time that the environment will have two versions co-exist. should I set the "custom server" policy to "hxxp://xxxx/ep8" and then switch to "hxxp://xxxx/ep9" after all the clients have upgrade to ep9. or I can set the policy to "hxxp://xxxx/ep9" directly even if some pending-upgrade clients are still using ep8?

    mirror location compatibility and parameter

    in ESET Endpoint Products

    Posted

    Hi:

       recently endpoint 9.1 seems mature, so I begin the upgrade procedure. but  I found there is a long term confusion about the mirror server.

    currently the server mirrors product "ep7,ep8,ep9". but in history every time when new endpoint product releases, the mirror tool won't catch up. so early ep8 product need to specify mirror location to "ep7" and early ep9 product need to specify mirror location to "ep8".  what's the logic behind the scene? is ep7/ep8/ep9 mirror location some how compatible?

    I also need to specify endpoint mirror location "customer server" policy like "hxxp://nod32.example.com/nod32-update/eset_upd/ep8".  is there a way to specify the location automatically by product version? something like "hxxp://nod32.example.com/nod32-update/eset_upd/ep${version}  so ep7/ep8/ep9 will find their way home.

     

     

    Outlook really slow to open with ESET Endpoint Antivirus 9.1.2051.0

    in ESET Endpoint Products

    Posted

    9 hours ago, Marcos said:

    Yes but not to v9.1.2051 but to a newer one, depending on the feedback on the upcoming service release of Endpoint 9.1.

    that sounds great.  would you consider make announcement about these kind of event? I had subscribe "ESET Knowledgebase Support News". so every time when there is new software release I will get email. but as an administrator, there is more important things I want to know: "when will something happen to my user?". 

    like endpoint 8.0 suddenly alarm user "product end of life" by module, or client auto-upgrade to some version. I want to know these before the event happened. it's not good to be noticed by user and find out what happened.

    all-in-one-installer failed at win7

    in ESET PROTECT On-prem (Remote Management)

    Posted

    the problem is indeed AES-256-CBC. since I install eset-protect at RHEL9 with openssl 3.0, the default openssl pfx export format will be AES-256-CBC.

    I try to downgrade the system to RHEL8 with existing database and configuration. but when I try to export agent certifcate, the format is still AES-256-CBC. so I think the export procedure is not dynamic, the exported result  seems already done and stored somewhere at installation stage.

    then I try a simpler method, I transform the exported AES-256-CBC pfx to another format which win7 will accept. I modify the agent installation config file to use the new pfx and fortunately the installation procedure swallow it then everything seems become normal.

    next stage I think I should find out where is the exported agent certificate in the system and modify it. is it stored at mysql database or somewhere else?

    and since openssl 3.0 is coming to every linux distribution, I think eset-protect should modify the openssl pfx export parameter as soon as possible.  it seems a one-line thing to support win7 under openssl 3.0.

×
×
  • Create New...