M
manrubble
Scenerio...
W2K Server running AD in a college setting. All student, faculty,
staff accounts have been imported into AD. Single forest, single
domain.
Question...
1.) I have AD configured to automatically install Office XP (all
clients are XP) when a user logs in. However, if a user goes to
another users computer, authenticates to the domain, it installs
Office XP again. Is there a way to prevent this from happening.
Perhaps Publishing the software would be a better solution?
2.) I have the "my documents" folder set up to redirect to a network
share for each user. However, again, when that user logs onto another
computer, synchonization takes place and stores all the users docs on
someone elses computer. Is there a way to prevent this from happening?
Perhaps mapping to an "m" drive for example would be a better
practice?
3.) We are using AD for all our authentication. Users from off-campus
can connect to our intranet site, authenticate, and then have access
to personal info (grades, transcipts, etc..). For security sake, is
there a way to implement an inactivity timer so the session logs the
user off after so many minutes of inactivity?
4.) can you recommend a few good AD on-line resources?
Thanks!
W2K Server running AD in a college setting. All student, faculty,
staff accounts have been imported into AD. Single forest, single
domain.
Question...
1.) I have AD configured to automatically install Office XP (all
clients are XP) when a user logs in. However, if a user goes to
another users computer, authenticates to the domain, it installs
Office XP again. Is there a way to prevent this from happening.
Perhaps Publishing the software would be a better solution?
2.) I have the "my documents" folder set up to redirect to a network
share for each user. However, again, when that user logs onto another
computer, synchonization takes place and stores all the users docs on
someone elses computer. Is there a way to prevent this from happening?
Perhaps mapping to an "m" drive for example would be a better
practice?
3.) We are using AD for all our authentication. Users from off-campus
can connect to our intranet site, authenticate, and then have access
to personal info (grades, transcipts, etc..). For security sake, is
there a way to implement an inactivity timer so the session logs the
user off after so many minutes of inactivity?
4.) can you recommend a few good AD on-line resources?
Thanks!