It not suggested to use MSAS on terminal server (at least the current Beta 1
release) because it is not working as a service, but as a process in user
mode. So each connected user uses additional resources because of MSAS - and
this is source od the problem, I'm affraid.
And more - MSAS behaves (because of the same reason - being a proces, not
service) not good when run by non-administrative user.
Additional to what Mikolaj has said, the high CPU usage symptom sometimes
relates to runaway errors.log file size in the installation folder.
Check the system for errors.log files and see if any of them have become
very large--they max out at 4 gigs on NTFS, I believe, and when maxed, the
symptoms may include high cpu usage.
