I am configuring a system for a client running XP Pro. The system will auto
login to a limited account. When I have MSAS installed the limited account
has access to the System Explorers. This allows the Limited account to make
changes to startup items ie: Disabling Anti-Virus. Is there any way to lock
down MSAS or disable access to these features. Other wise this leaves a huge
security gap in the program by allowing Limited Accounts to have features
that are not normaly available.


Thanks,

Nicholas Lyle

I don't know of a way to do this. This kind of issue is related to the one
in this KB article--the second written about the beta1 product:

http://support.microsoft.com/kb/892375 End users may be prompted to allow or
block administrative actions that originate from a central management tool
after they install Windows AntiSpyware (Beta) on a computer that is managed
by Systems Management Server 2003

This is one reason that Microsoft advises not installing this beta in
managed environments or on production equipment.

You can use the workaround paragraph in that KB article to disable all
real-time protection, but I wouldn't expect that to disable the System
Explorers.

--

"Nicholas Lyle" <Nicholas (E-Mail Removed)> wrote in message
news:5AA4A7CF-0C52-46C3-98C6-(E-Mail Removed)...
>I am configuring a system for a client running XP Pro. The system will auto
> login to a limited account. When I have MSAS installed the limited account
> has access to the System Explorers. This allows the Limited account to
> make
> changes to startup items ie: Disabling Anti-Virus. Is there any way to
> lock
> down MSAS or disable access to these features. Other wise this leaves a
> huge
> security gap in the program by allowing Limited Accounts to have features
> that are not normaly available.
>
>
> Thanks,
>
> Nicholas Lyle