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