Is the intent for this to become pay software in the future

  • Thread starter Thread starter KGuy
  • Start date Start date
K

KGuy

I really like the way this software works and as an IT
professional I havebegun installing it on all 2K and XP
Machines that come through my shop. I am ready to pay
for it if need be but I hope if it does become pay
software Microsoft does not require more then about $30
for it because it is already hard enough to push
antivirus on some new users. Basically I was just
wondering if anyone new whether the intion is to have the
release be pay software or not.
 
You're an IT "Professional" & you're *already* installing this on ALLthe
machines in your shop?

1. It's "beta" software. Know what that means?
2. Half the functionality that's supposed to be in this product isn't
actually there at the moment. By using this product you may be misled into
a false sense of security because it's not alerting you to what's there when
it's actually there.

The answer to your question - which you'll find by reading back - is that
it's going to be free for individuals but at a price for corporations.
 
I do the same thing he does.

Want to give some examples of what you mean by your second point?
 
Bill -

In all the IT Shops I've worked at (I'm a consultant) you would be fired or
your contract would be abruptly terminated if you installed beta software on
a production machine let alone ALL of the production machines in the
client's environment. Are you saying that this IS something that you do?

(Sure you would have one or more test machines and install it there for
evaluation purposes).

With regard to 2nd point:

2(a). Well to be honest I don't have / haven't had any spyware on my
computers to date, since I am careful about avoiding it. (I have however
fixed the machines of several people who've been inflicted with it). So
perhaps I cannot comment so authoritatively on whether MSAS can detect /
remove it. However, I do occasionally find tracking cookies in my browser
cache and I find that Lavasoft Ad-aware will flag things that MSAS will just
ignore.

2(b). As for things that aren't working in MSAS you could just look back in
the newsgroup for all the comments that others have made. Another example
I'll give is the List of Running Processes in Advanced Tools -> System
Explorers. When you select an item (one of the running processes) and then
click "Learn more about this application...", a dialogue box opens and says
"The requested information is not currently available." It did this for
every one of the applications I selected. Furthermore, in the dialogue, not
all of the UI elements are there.

With regard to 2(b) you'll probably respond "Yes, but this is beta software.
That hasn't been implemented yet." To which I'll respond "Yes."
 
2(a). Well to be honest I don't have / haven't had any spyware on my
computers to date, since I am careful about avoiding it. (I have however
fixed the machines of several people who've been inflicted with it). So
perhaps I cannot comment so authoritatively on whether MSAS can detect /
remove it. However, I do occasionally find tracking cookies in my browser
cache and I find that Lavasoft Ad-aware will flag things that MSAS will just
ignore.

Cookies aren't spyware, and besides it's been noted here time and time again
that this feature is not here yet. As for how "dangerous" a cookie is, and
whether or not I'm being misled when anti-spyware software doesn't find a
harmless text file, I suppose that's in the paranoia of the beholder.

sh
 
OK let me take out my BIG HAMMER and try to drive the point of my comments
home.

My point is that the software is still in beta, that not all the features
are there (thanks Spyware Hater for reminding me), that in using the product
(at this time) you might be led into a false sense of security that
everything on your machine is A-OK, and that it is ill-advised to deploy
beta software on all of the machines in your IT shop.

Maybe some people here work in IT shops where availability, reliability and
stability aren't major concerns. I don't.

(I just love it when people don't fully comprehend the gist of a message and
yet somehow feel compelled to reply to it.)
 
I don't recommend running pre-release software in a production environment,
especially if its beta 1 stage. I would preferrably wait until it reaches
beta 2 or Release Candidate to test out just one or two installations in a
networked environment.
 
OK let me take out my BIG HAMMER and try to drive the point of my comments

Relax guy, you're not smarter than everyone else here so let's stop
pretending you are for a moment. I was just pointing out that cookies are
not "spyware"... if you don't want cookies on your machine, guess what, you
don't need LavaSoft or any other tool for that, you can just tell IE to
block them all.
 
Ian E said:
Bill -

In all the IT Shops I've worked at (I'm a consultant) you would be fired
or your contract would be abruptly terminated if you installed beta
software on a production machine let alone ALL of the production machines
in the client's environment. Are you saying that this IS something that
you do?

(Sure you would have one or more test machines and install it there for
evaluation purposes).

I work with individuals and small offices. They trust my advice, and my
experience with Microsoft Antispyware has been such that I have, in fact,
installed it on most production machines. I have to say that I've never
been called to explain an alert--the only mention of it I get from users is
they mention seeing when it has updated. And when I look at a machine which
is on 24x7, I notice the scan result messages.

I've been personally impressed, and somewhat horrified, at the level of
requests for information about how to do unattended installs in this
beta--that should scare you!
With regard to 2nd point:

2(a). Well to be honest I don't have / haven't had any spyware on my
computers to date, since I am careful about avoiding it. (I have however
fixed the machines of several people who've been inflicted with it). So
perhaps I cannot comment so authoritatively on whether MSAS can detect /
remove it. However, I do occasionally find tracking cookies in my browser
cache and I find that Lavasoft Ad-aware will flag things that MSAS will
just ignore.

The builds distributed so far do not scan for cookies, which pretty well
explains your final sentence.
2(b). As for things that aren't working in MSAS you could just look back
in the newsgroup for all the comments that others have made. Another
example I'll give is the List of Running Processes in Advanced Tools ->
System Explorers. When you select an item (one of the running processes)
and then click "Learn more about this application...", a dialogue box
opens and says "The requested information is not currently available." It
did this for every one of the applications I selected. Furthermore, in the
dialogue, not all of the UI elements are there.

With regard to 2(b) you'll probably respond "Yes, but this is beta
software. That hasn't been implemented yet." To which I'll respond "Yes."

You're right about my response here: This beta is based on what had been an
existing commercial product. If you wish to check out another product
licensed from that same technology, look at Sunbelt Software's CounterSpy
product.

The beta was released about 3 weeks after acquisition of the technology. A
great deal of work was done rather quickly, and it is apparent when you
consider such issues as accesibility, localization, and use by multiple
users, or administrator vs limited user issues---that a great deal more work
will be required. I'm not surprised that there are some dead ends and
information missing.

However, reviews, both of the product which forms the basis (Giant
Antispyware) and of Microsoft Antispyware, have found that it performs very
well.

Groups such as this are largely composed of folks with problems--make a
count of the total number of messages in these groups--this is easy to do
via NNTP. Now, consider the 5-7 million downloads there have been of the
beta. How do you see the percentages of folks having problems? Sure there
are some in that category who may not have found these groups--but although
I find some of the issues seen here as surprising in a public beta, I think
the beta product is working routinely and effectively for the vast majority
of its users.
 
I'm not worried about cookies, in terms of maintaining production machines.
If I find those that somebodies product certifies are spyware-related, I'll
blow them away, but I don't worry about them.

I do worry about the nastier stuff--keyloggers, remote control trojans,
browser hijacks, and the general poorly-written spyware that does cause
reliability issues on machines. Microsoft Antispyware has done the job on
the few machines I work with that have such issues.

I've seen only one issue where a machine I installed Microsoft Antispyware
on had an issue in your category--i.e. it impacted reliability,
availability, uptime: My next-door neighbors home office machine had the
Winsock LSP stack disrupted by spyware removal. They fussed around for a
while before calling me, which is too bad, because on an XP SP2 machine this
is extremely easy to fix. This is a serious issue--it kills the
network--but I haven't seen it in the office machines I work with. This is
also an issue which Microsoft understands needs to be done better, and I'm
confidant that it will be.

When I install Microsoft Antispyware on a machine, I ensure that it is clean
before I leave it. Thereafter, the real-time protection should keep it that
way--so the category of issues that arise from cleaning happen when I'm on
site and can deal with them.

You and I do work in different environments--but I think you'd be surprised
at the number of knowledgable folks in your kind of shop that are deploying
this application.
 
Back
Top