Hi Eric,
Are you sure it isn't the user who is running MSAS and is blocking the
scripts manually?
I have a script that runs against one of my work PC's that I block daily
(for testing purposes).
It's on my own test PC, MSAS didn't give me an option to
allow the GPO script, and I didn't wwant to have the
choice to block it since I applied the script as a domain
Group Policy Object. Since it appears MSAS doesn't
respect the administrative hiearchy a domain administrator
makes as he/she applies a GPO, I saw this as in conflict
with security designed into AD. Hence, a bug, or at the
least a conflict in compliance with AD security design.
Any ideas on how to enforce GPO's and make MSAS respect
chnges made by a GPO?
Thanks!
Eric
-----Original Message-----
Microsoft Antispyware, in the current beta form is not suitable for use in
an environment whare GPO is an issue.
--
FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.txt
It's kind of a broad statement, but the product simply isn't designed in the
present form, with the kinds of considerations that go with such usage.
Many here are hoping to see such a product at some later time, of course.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.
