Jump to content

itman

Most Valued Members
  • Posts

    12,333
  • Joined

  • Last visited

  • Days Won

    325

Posts posted by itman

  1. 1 hour ago, Marcos said:

    A license becomes active as of the date of purchase. We never supported start of license validity from the date of activation

    I believe this is in reference to an online purchase from an Eset affiliated e-commerce web site. At that time, the license would be automatically be added to the Eset License Manager server.

    Eset software purchases from third party e-commerce sites such as newegg.com, etc.. since Eset has no knowledge of same, would become active at actual software installation or license renewal time by entry of the license key.

    In any case, Eset License Manager only maintains data on active licenses. What the OP requested was the ability to enter info on non-activated; i.e. unused licenses. I believe this request is out of the scope for which Eset's License Manager was created for.

  2. 4 minutes ago, zfactor said:

    i asked like a dozen different people this in the past at eset and every one including the support person today said they would work. today he said this is something they JUST changed. which is why im wondering if he was correct or not.

    I would then make an inquiry to Eset corporate offices in Slovakia for a clarification.

  3. 25 minutes ago, zfactor said:

    you can use any previous smart security to activate current internet security. so no im not installing old versions.

    I assume you are referring to the non-premium version of Smart Security. As I posted previously, the only versions of it that are not "End of Life" are versions 9 & 10. Those both have EOL dates of 12/2019 and 12/2020 respectively. Therefore, unused licenses for those versions and only those versions are still valid.

    Finally, it can be assumed that license validity is something governed by the in-country Eset valued added retailer. So it is very likely policies can and will vary by country.

  4. If you don't want to use Autoruns to determine what is starting AtBroker.exe at boot time, do the following. Create on a test basis an Eset HIPS rule to allow the startup of AtBroker.exe.  Make sure you enable logging for the rule and set its severity level to "Warning." After you boot, check the Eset HIPS log for any log entries from this rule. Those entries will inform you what process is starting AtBroker.exe. You can now delete the HIPS rule for AtBroker.exe.

    If ekrn.exe is not starting AtBroker.exe, then Eset is not the source of the activity.

  5. 27 minutes ago, TomFace said:

    The last license I activated in Dec 2018 was a ESS 2014 license.

    If you refer to the Home products link I posted, all ESS Premium versions are still under some degree of support status. Additionally, ESS 9 & 10 are still supported status-wise. When a version is marked "End of Life" status-wise is when an used license for same would no longer be valid.

  6. 40 minutes ago, katycomputersystems said:

    If I am reading the chart correctly, v6 is six years old and lost support two years ago.

    If you're referring to Endpoint Antivirus and Security, v6 and 5.5 for that matter are still supported. So old unused licenses for those would still be valid; assuming business product licenses don't have a different policy. If the status column shows "End of Life" is when an old unused product license would no longer be valid. 

  7. Are you stating that the boxed Eset versions from newegg.com have invalid licenses?

    How old are these licenses? I tried to find some definitive info on how long unused licenses are valid for, but couldn't find anything. Older forum postings state that as long as the purchased licensed version is still actively supported, the license should still be valid for that or any later Eset version.  

  8. Perhaps a bit of historical review will get things into proper perspective.

    Eset prior to ver. 9 had a "dated" but well-liked user interface. Starting with ver. 9, Eset adopted the current Metro style GUI. I assume that was for compatibility for all devices on which Win 10 could be installed on. There were a lot of complaints initially about the Metro style GUI; especially with changes made in regards to HIPS rule creation and editing. I am also one who did not like the changes made to the HIPS in regards to the Metro GUI adoption. Over time, I have adapted to the changes to the Eset GUI due to the Metro style changes.

    The point here is Eset laid out the GUI as best as it could in light of restrictions employed by use of the Metro style. Although it may be possible to perform limited changes to the Eset existing GUI, I really wouldn't expect to much in this regard.

  9. 2 hours ago, claudiu said:

    Show me ONE  user who wants ,in certain situations, "strict cleaning" and, in some other situations, "no cleaning"

    Yours truly for one.

    I use strict cleaning for everything except Web Access. For Web Access, I use Normal cleaning. Why? Because if strict cleaning is selected, you won't get an Eset alert for PUA's; they will be auto blocked. This will prohibit your ability to selective allow a download you have verified is safe.

  10. 4 hours ago, AGH1965 said:

    No improvement at all.  The last option is very weird. If there is more than "maximum protection" then "maximum protection" isn't "maximum protection".

    Believe the "inspiration" here was the old versions of Emsisoft which had such settings. Paranoid mode threw the behavior blocking into basically an interactive mode with alerts generated "up the wazoo." 

    BTW - Emsisoft  dumped those, and such capability doesn't exist in the current versions.

  11. On ‎4‎/‎3‎/‎2019 at 3:58 PM, itman said:

    My scheduled scan is scheduled for tomorrow, so we will see then if it shows.

    I said I would post back on this, so here's the result.

    My PC was in sleep mode Thursday at it's scheduled noon run time. Note I had previously set the missed scan retry option to 24 hrs.. The scan did not run at any time later on Thursday when the PC powered up. The scan did not run on Friday at boot time. The PC also happened to be powered down at noon on Friday. Upon powered up the PC later Friday, the scan still did not run.

    Bottom line - Eset scheduled scan missed time option is the same as that on prior versions; it just doesn't work. Really not a big issue for me personally.  I will just run an on-demand scan whenever. Note that Eset only recommends a full in-depth scan once a month which sounds about right to me.

  12. 26 minutes ago, PassingBy said:

    2) Add a "Simplified mode" with 3 main settings for the whole ecosystem

    MINIMUM PROTECTION

    AVERAGE PROTECTION

    MAXIMUM PROTECTION

    PARANOID MODE AVAILABLE.

    By default, Eset when installed with default settings provides maximum protection. The only optional setting is to enable PUA/PUP protection.

    The other settings you mentioned will never be provided since they require a frame of reference; in this instance, how security paranoid a user is. Eset's policy has always been you are free to modify it to "your heart's content." However by doing so, you assume all responsibility for any adverse malware activity resulting from any change from the recommended default settings. The same assumption applies to any adverse system operational impact.

    Bottom line - no one is going "to spoon feed you" how to modify Eset. You're going to have to find that out through reference to Eset online documentation and self-testing.

  13. If your question is if your can scan another HDD w/Win 7 x(64)  installed from Ubuntu, I would say the answer is yes. An AV is scanning for malware on the drive regardless of what is stored on the drive. However, whatever malware that is found will be in the context of Linux malware and not Windows malware I would imagine. Simply because NOD32 is installed on a Linux OS.

    What you need to do is install NOD32 x(64) on Win 7 x(64) and scan its boot drive for Windows based malware.  

     

×
×
  • Create New...