Dameware's mini-remote client is seen by Microsoft Anti-Spyware as potential
spyware. If Symantec's PCAynwhere client is not seen as a threat, neither
should Dameware's client.

Hi Buckman,

Might want to read the notes:
Microsoft Windows AntiSpyware (Beta): Resources for Software Vendors
http://www.microsoft.com/athome/secu...v/default.mspx


False Positive Report Form
http://www.microsoft.com/athome/secu...sv/fpform.aspx

Engel
"(E-Mail Removed)" wrote:

> Dameware's mini-remote client is seen by Microsoft Anti-Spyware as potential
> spyware. If Symantec's PCAynwhere client is not seen as a threat, neither
> should Dameware's client.
>

Check the threat descriptions. And Engel's references.

If a remote control product can be present on the box without the user's
knowledge, and can be activated without clear notice to the user of that
happening, I believe that it should be called out.

In a managed, corporate situation, this is the vision of what will happen, I
believe: Beta2 will plug into the Microsoft Client Protection package which
will include a management console. A network admin will be able to control
whether and how users are notified about such tools in place. I suspect
that the underlying controlability via Group Policy will be there in the
basic product, but the management console will make this much easier to
implement--i.e. I think that even folks who don't go for the Client
Protection (which is a subscription package including antivirus)--will
probably be able to manage such settings, with some effort.


--

"(E-Mail Removed)"
<(E-Mail Removed)@discussions.microsoft.com> wrote in message
news:073B82C8-B743-4877-8A7A-(E-Mail Removed)...
> Dameware's mini-remote client is seen by Microsoft Anti-Spyware as
> potential
> spyware. If Symantec's PCAynwhere client is not seen as a threat, neither
> should Dameware's client.
>