P
Peter Crickman
I have been using MSAS for over a month now and have periodically
checked/downloaded definition and software updates manually. The
auto-update feature does not seem to work.
I have four user accounts on the machine. For user #1's account, MSAS
identifies a registry change to the My Documents setting. This was changed
when the computer was first setup to point to a network share. MSAS
incorrectly identifies this change because it reports this user's My
Documents folder as being replaced by user #2's local My documents folder.
This is not true.
A number of warning popup that MSAS reports with a blue-shaded (not red)
occur when each user logs in. The majority of these have been set to
"Allow". When the machine is rebooted, the same warnings appear and have to
be acknowledged again one time when each user logs on. Why don't these
accepted warnings stick across reboot cycles.
Fortunately no more than one user stays logged on at any given time even
though Fast User Switching is in place to see any evidence of the multi-scan
problem which has been reported previously. If that in fact does happen, I
would expect that the virtual memory problem to be evident as well.
Are significant updates expected to the beta before it goes live in July?
Peter
checked/downloaded definition and software updates manually. The
auto-update feature does not seem to work.
I have four user accounts on the machine. For user #1's account, MSAS
identifies a registry change to the My Documents setting. This was changed
when the computer was first setup to point to a network share. MSAS
incorrectly identifies this change because it reports this user's My
Documents folder as being replaced by user #2's local My documents folder.
This is not true.
A number of warning popup that MSAS reports with a blue-shaded (not red)
occur when each user logs in. The majority of these have been set to
"Allow". When the machine is rebooted, the same warnings appear and have to
be acknowledged again one time when each user logs on. Why don't these
accepted warnings stick across reboot cycles.
Fortunately no more than one user stays logged on at any given time even
though Fast User Switching is in place to see any evidence of the multi-scan
problem which has been reported previously. If that in fact does happen, I
would expect that the virtual memory problem to be evident as well.
Are significant updates expected to the beta before it goes live in July?
Peter