Is there a way to stop people from downloading

Is there a way to stop people from actually downloading
this like a registry key like with xp sp2. Thanks in
advance.

That's an interesting suggestion. Can you quantify the kind of issue you
see as needing that kind of preventative measure? What breaks, in your
environment?

"Cookie" <anonymous@discussions.microsoft.com> wrote in message
news:051f01c4f4c0$5dfff450$a501280a@phx.gbl...
> Is there a way to stop people from actually downloading
> this like a registry key like with xp sp2. Thanks in
> advance.

> "Bill Sanderson" <Bill_Sanderson@msn.com.plugh.org> wrote in message
> news:eRc9ZOM9EHA.2532@cpmsftngsa05.privatenews.microsoft.com...
>
> That's an interesting suggestion. Can you quantify the kind of issue
> you see as needing that kind of preventative measure? What breaks,
> in your environment?



I could see the detection and removal of VNC as a possible problem in
an enterprise.


--
AZC

"Andrew Z Carpenter" <azc@cirencester.ac.uk> wrote in message
news:O$X0DnM9EHA.2508@cpmsftngsa05.privatenews.microsoft.com...
>> "Bill Sanderson" <Bill_Sanderson@msn.com.plugh.org> wrote in message
>> news:eRc9ZOM9EHA.2532@cpmsftngsa05.privatenews.microsoft.com...
>>
>
> I could see the detection and removal of VNC as a possible problem in
> an enterprise.

Absolutely--and I'm sure that in an Enterprise product there will be a
provision to hide a particular RAT from display to a user, minimally. OTOH,
the default for VNC is Ignore, as I recall, and if you choose Always Ignore,
you never hear about it again. Some slicker RAT's are also
flagged--Dameware, for example.

I wouldn't expect Microsoft to provide the kind of mechanism that the OP
requested--that's a substantial investment to provide, I suspect. But I
don't know what their bar is for that kind of action, so folks should speak
up about how bad they think having this easily available for download is.

Bill Sanderson wrote:
> That's an interesting suggestion. Can you quantify the kind of issue you
> see as needing that kind of preventative measure? What breaks, in your
> environment?

Not the original poster, but requesting the same thing. In my very
limited tested in our corporate environment, we have already that this
beta with all the default settings, will freeze the Active Directory
login script written in VBScript and prompt the client for confirmation
that this is valid. While part of this is a bigger issue (namely that
clients had Administrator-equivilent access to their workstations), it's
still an issue that will cause us grief.

....that and it's not an enterprise class system with a centralized
console and can be administered through group policy. (It doesn't hurt
to keep saying this, huh?)

-crk

"Carl R. Knecht" <msprivate@rialtus.com> wrote in message
news:uwypD0P9EHA.484@CPMSFTNGSA04.privatenews.microsoft.com...
> Bill Sanderson wrote:
>> That's an interesting suggestion. Can you quantify the kind of issue you
>> see as needing that kind of preventative measure? What breaks, in your
>> environment?
>
> Not the original poster, but requesting the same thing. In my very limited
> tested in our corporate environment, we have already that this beta with
> all the default settings, will freeze the Active Directory login script
> written in VBScript and prompt the client for confirmation that this is
> valid. While part of this is a bigger issue (namely that clients had
> Administrator-equivilent access to their workstations), it's still an
> issue that will cause us grief.
>
> ...that and it's not an enterprise class system with a centralized console
> and can be administered through group policy. (It doesn't hurt to keep
> saying this, huh?)

We can keep saying it, but I don't think there's any need. Microsoft knows
this. The current beta product is oriented towards home users, and doesn't
pretend to be anything else.

I know that the network administrators among us are disappointed, but those
managed networks are also probably better managed in terms of the issues
this software addresses, as well.

My own vague understanding of how these public betas work is that Microsoft
staff are probably reading most messages here. I doubt that we'll see much
direct involvment or comment, but the feedback will be noted.

I know everybody'd like more direct involvement, but it probably isn't a
rational expectation given the scale of the beta and the work at hand to get
the product up to snuff.