Lack of Networking Capabilities

Obviously, there's little networking capabilities (at
least that I can detect). One problem is that the
program seems to run as the local user so ...
administrative rights would have to be granted to the end
user for it to be effective with regard to any registry
edits. There's no centralized way to monitor the
program. Also, there's a few nag screens that come up
when it's not an administrative user.

At this time we have not finalized guidance on installing without being an
admin or power user. The issue arises when a user does not have write
access to the program files directory. We recommend that users installing
the beta be admins of their machine. There is also not a way to centralize
log files at this time.

- steve


Steve Dodson [MSFT]
MCSE, CISSP
PSS Security

--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
--------------------
>Content-Class: urn:content-classes:message
>From: <anonymous@discussions.microsoft.com>
>Sender: <anonymous@discussions.microsoft.com>
>Subject: Lack of Networking Capabilities
>Date: Wed, 19 Jan 2005 05:37:30 -0800
>Lines: 8
>Message-ID: <050101c4fe2c$05c43f60$a401280a@phx.gbl>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="iso-8859-1"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Thread-Index: AcT+LAXEUamlFFWFSzGleLmoTKc9FA==
>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
>Newsgroups: microsoft.private.security.spyware.networking
>Path: cpmsftngxa10.phx.gbl
>Xref: cpmsftngxa10.phx.gbl
microsoft.private.security.spyware.networking:367
>NNTP-Posting-Host: tk2msftngxa12.phx.gbl 10.40.1.164
>X-Tomcat-NG: microsoft.private.security.spyware.networking
>
>Obviously, there's little networking capabilities (at
>least that I can detect). One problem is that the
>program seems to run as the local user so ...
>administrative rights would have to be granted to the end
>user for it to be effective with regard to any registry
>edits. There's no centralized way to monitor the
>program. Also, there's a few nag screens that come up
>when it's not an administrative user.
>