Carl R. Knecht said:
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.