tbsky

Thanks for the info. that's what I need. as you mentioned, now lowest ESET PROTECT Entry include ESET Endpoint Security. so there is nothing like ESET PROTECT Essential which include Antivirus only. we are afraid to use Endpoint Security instead of Antivirus since there seems more problems when there are more functions. we saw that with forum posts.

I don't understand. currently our situation is the opposite. we can not buy antivirus license anymore. so we need to activate antivirus software with security license. we haven't renew yet. distributors told us it is doable. but I am not sure now.

@Marcos is it true that windows endpoint antivirus is no longer be sold and maybe retired in the near future? we need to plan the upgrade if necessary.

Hi: I wonder if this will be fixed. but let's keep some hope. the latest eset agent which support win7/2008r2 is 10.1. but when create upgrade task, ERA want to upgrade it to 11.2. which will always fail.

sorry I forgot to mention we are using windows. we will buy endpoint security license. but currently we are using endpoint antivirus.

Hi: it's sad that our distributor told us endpoint antivirus is no longer be sold. we can only buy endpoint security license. but we can chose to install endpoint antivirus with the license. I wonder if endpoint antivirus will continue since it is no more be sold. should we upgrade to endpoint security soon or later? I always prefer endpoint antivirus since it cause fewer problems. but I need to plan upgrade if it will be dead in the near future.

Thanks again for the great info!

Thanks for the clarification. so could I said that the general multilingual msi is also suitable for Japanese windows? (although maybe the later version has better Japanese localization) I don't mind more upgrade data. I have only a few Japanese users. it is convenient for me if I can treat all users the same when installation, and let endpoint auto-upgrade to the best version.

Hi: we have users using different windows os language. long time ago the endpoint msi installer was specific to every language and hard to maintain. these years the endpoint msi become multilingual so I can push single msi package to every os language except Japanese. I notice that endpoint Japanese version is always different. for example, currently the latest version of endpoint is "11.0.2044.0", but latest Japanese version is "11.0.2044.1". so I made an all-in-one installer with Japanese language selection for users need it. I think the multilingual msi installer can also installed at Japanese windows. but I am not sure. I don't understand Japanese and I don't have Japanese windows environment to test. I want to know what will happen with the msi installer. if I use "11.0.2044.0" msi installer at Japanese windows, will it installed successfully and upgrade to "11.0.2044.1" automatically later? thanks a lot for clarification!

Hi: I need to change the administrator password to the previous one. but eset protect console told me "Unable to save data: You have attempted to set a password to one that was used in the past. Please select a different password." I tried several new password then tried to return the original password, but can not get rid the message. how can I set the password I want? I can not find the history data in the database. can you tell me where the data stored or how to remove the password history?

Hi: we don't care what the url is (with or without version number). the problem is we need multiple policies to set the correct url path to multiple eset client version. it is easy to solve as I said but Eset didn't do it. Eset update with Eset server will download update files automatically with correct version. why can't this be done when update with mirror server?

Hi: I want to create the batch file as you said. so this time I carefully compare ep9 and ep11. most file names of them are different (so no conflict). but there are four files with the same name and different content. could you tell me how to merge the four files to one directory? thanks a lot for help!! >diff -rqu ep9 ep11 | grep -v ^Only Files ep9/dll/nod3852.dll.nup and ep11/dll/nod3852.dll.nup differ Files ep9/dll/nodAFA3.dll.nup and ep11/dll/nodAFA3.dll.nup differ Files ep9/dll/nodC2A5.dll.nup and ep11/dll/nodC2A5.dll.nup differ Files ep9/dll/update.ver and ep11/dll/update.ver differ

Hi: this is news to me. I had compare directory content of ep7/8/9/10/11, and there are many different files. I don't know they can be merged into a single directory. then why not let mirror tools itself to do the merge? would Eset consider add a parameter like "-g" so content could be merged and policy can be simple for every Eset version?

I am sorry. I thought it was very clear. no problem to create the mirror. the problem is how to push the mirror path to client. every time when eset version upgrade, the mirror location path need to change, that's fine. but the policy also need to modified to the new path, that's very bad. we don't need a path policy like below: hxxp://nod32.example.com/nod32-update/eset_upd/ep11 (the path policy need to changed for every eset version) we need a path policy like below: hxxp://nod32.example.com/nod32-update/eset_upd (and client should append ep7,ep8,ep9,ep10,ep11 automatically) or a path policy like below: hxxp://nod32.example.com/nod32-update/eset_upd/ep%eset_version% (a server marco which push the correct path to client)

the mirror location policy is poorly designed. I hope it can be changed since v7,v8,v9,v10, and now v11. currently I need to use "hxxp://nod32.example.com.nod32-update/eset_upd/ep11" for win10/win11 and "hxxp://nod32.example.com.nod32-update/eset_upd/ep9" for win7. the mirror location policy should be auto-completed by eset version.