tbsky 8 Posted January 17 Share Posted January 17 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. Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 4,550 Posted January 17 Administrators Share Posted January 17 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. Anyways, rather then using a mirror we strongly recommend using ESET HTTP proxy to cache downloaded files if the machines are not completely offline and have access to a machine with Internet connection at least. This would enable them to take advantage of both LiveGrid and streamed updates every few minutes. It would also save the traffic since only files actually needed by clients would be downloaded and cached whereas the mirror downloads a lot of unnecessary files not needed by clients with each update. Quote Link to comment Share on other sites More sharing options...
tbsky 8 Posted January 17 Author Share Posted January 17 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? Quote Link to comment Share on other sites More sharing options...
tbsky 8 Posted January 23 Author Share Posted January 23 On 1/17/2023 at 3:09 PM, 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.. is there new idea about the problem? or should I create a support ticket? Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 4,550 Posted January 23 Administrators Share Posted January 23 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. Quote Link to comment Share on other sites More sharing options...
tbsky 8 Posted January 25 Author Share Posted January 25 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? Quote Link to comment Share on other sites More sharing options...
tbsky 8 Posted yesterday at 05:13 AM Author Share Posted yesterday at 05:13 AM On 1/23/2023 at 8:14 PM, tbsky said: is there new idea about the problem? or should I create a support ticket? I create a support ticket from https://www.eset.com/int/support/contact/ but I didn't get any response or any ticket number. is that a correct place to create ticket? Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 4,550 Posted yesterday at 05:43 PM Administrators Share Posted yesterday at 05:43 PM Did you receive a confirmation email with a ticket number after opening a ticket with tech support? Quote Link to comment Share on other sites More sharing options...
tbsky 8 Posted 17 hours ago Author Share Posted 17 hours ago 11 hours ago, Marcos said: Did you receive a confirmation email with a ticket number after opening a ticket with tech support? no, I got nothing. so I think I need to create it again? Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 4,550 Posted 15 hours ago Administrators Share Posted 15 hours ago 1 hour ago, tbsky said: no, I got nothing. so I think I need to create it again? Yes, try again please. Did you use your forum email address when creating the ticket? Quote Link to comment Share on other sites More sharing options...
tbsky 8 Posted 15 hours ago Author Share Posted 15 hours ago 10 minutes ago, Marcos said: Yes, try again please. Did you use your forum email address when creating the ticket? yes. I use the forum email address. I will try again later. thanks a lot for your help!! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.