gmiossi
July 6th, 2009, 04:26 PM
Hi,
We're trying to begin using ESET (business AV licenses with RAC), but we're having a horrible time trying to understand your licensing model. We've called countless times (my hold time has been over an hour many times, also) and get different answers from different people (including the resellers we're contacting) so I'm going to try posting my questions here.
We originally got one license along with an eset username (EAV-...) and password. All was well. We then got another license, but it came with a separate username and password. Trying to upload the license using Remote Administrator Console failed.
We called support, and they indicated that it failed and that we got a separate username because the license was generated with a differently formatted name for our company than the original license. I checked the contents of the license files, and that was true. We contacted the reseller, but they didn't seem to think that entering the company name differently would matter.... Eventually they had the added licenses merged with the original license (which isn't what we wanted..we'll be adding 5 or more at a time regularly over a very long period of time, up to several hundred, and merging all of them as we add them would mean we'd lose a lot of time for licenses added later on - not an option). We want to have many licenses in parallel ... 5 | 5 | 7 | 5 etc... each with their own individual expirations. With one username (because that's what we've put in the XML config for the einstaller we're sending out to clients).
So, back story aside, our questions are:
What *is* the ESET username? (EAV-...) ... what does it reflect, precisely? Can multiple licenses be associated with one? Or only a single license?
Can any business license be added to any EAV-... account? Does the license need to be coded (company name formatted exactly, etc) by the resellers to work with a particular account?
When contacting resellers and purchasing licenses, what should we tell them to avoid licenses failing to add as they just did for us?
We're about to jump ship out of necessity (we have to move ahead with things for clients right now), but I like the RAC quite a bit so I'd like not to.
I appreciate any assistance anyone could give me.
Thanks,
Graham
We're trying to begin using ESET (business AV licenses with RAC), but we're having a horrible time trying to understand your licensing model. We've called countless times (my hold time has been over an hour many times, also) and get different answers from different people (including the resellers we're contacting) so I'm going to try posting my questions here.
We originally got one license along with an eset username (EAV-...) and password. All was well. We then got another license, but it came with a separate username and password. Trying to upload the license using Remote Administrator Console failed.
We called support, and they indicated that it failed and that we got a separate username because the license was generated with a differently formatted name for our company than the original license. I checked the contents of the license files, and that was true. We contacted the reseller, but they didn't seem to think that entering the company name differently would matter.... Eventually they had the added licenses merged with the original license (which isn't what we wanted..we'll be adding 5 or more at a time regularly over a very long period of time, up to several hundred, and merging all of them as we add them would mean we'd lose a lot of time for licenses added later on - not an option). We want to have many licenses in parallel ... 5 | 5 | 7 | 5 etc... each with their own individual expirations. With one username (because that's what we've put in the XML config for the einstaller we're sending out to clients).
So, back story aside, our questions are:
What *is* the ESET username? (EAV-...) ... what does it reflect, precisely? Can multiple licenses be associated with one? Or only a single license?
Can any business license be added to any EAV-... account? Does the license need to be coded (company name formatted exactly, etc) by the resellers to work with a particular account?
When contacting resellers and purchasing licenses, what should we tell them to avoid licenses failing to add as they just did for us?
We're about to jump ship out of necessity (we have to move ahead with things for clients right now), but I like the RAC quite a bit so I'd like not to.
I appreciate any assistance anyone could give me.
Thanks,
Graham