Justin Wood (Callek) wrote:
My proposal:
I think that's a reasonable approach.
In particular, if handling of betas is an issue, I might go even a bit
further with documentation, of advising beta users that they should
replace Norton, if they find that Norton use is generating
false-positives. In short, people who are using betas should not be
using Norton.
One thing that I've discovered with AV tools -- for people that have
paid for licenses, they're often unwilling to move to another product,
even if there's benefit to them, and no cost (other than the effort of
removal of one, and installation of another).
In our company, we do a lot of support of BYOD, and we have a corporate
license from another AV vendor, and we make individual licenses
available to our users, without charge. We don't require use of our
license, but we do have a list of AV tools that we consider to be
acceptable (NAV is explicitly not on the list). It's interesting to see
the number of users who already have Norton installed (and paid for)
that give us resistance to replacing Norton. Some of it may be
reluctance to remove pre-installed software (especially if it carries
some sort of implied "official" sanction from either Microsoft, the OEM
or the retail vendor, some of it may be reluctance to remove a all-in
one suite with a unified UI. However, most often, the resistance seems
to be in discarding a paid-for license, regardless if the alternative
has no financial cost.
* Continue to *try* getting a human contact at Norton to see if/when we
can speed up their process or fix this misidentification, and how.
One question --
Do you have interaction with any of the other Mozilla development
communities (especially Firefox and Thunderbird) to see if they may have
any contacts experience with Symantec that may be useful? Or are they
subject to the same "don't even *think* about trying to waste the
valuable time of our employees attempting personal interaction"
processes, but where they get higher-priority attention, simply by
having a user base that's much larger? Also, are there any other other
Mozilla projects with similar issues?
Smith
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
