J
JoeC.nc
My work environment is XP pro, fully managed, regulated, audited.
Users have private accounts they access from their desktop. In
addition, there is a common account that is used on "shared"
computers, screens locked after use. This is setup is used to avoid
users locking others out of shared computers, and to avoid the time-
overhead of doing a full logon each time a shared computer is used.
Users typically use the shared computer to logon to some application,
record information, then close the appication and lock the shared
account, thereby leaving the appropriate audit trail while still
having the advantages of the common account.
Here's the rub. It is often convenient for a user to map a network
drive from a shared computer. However, the shared account has no
privleges, so the user must supply his private credentials for the
drive mapping. User opens a file, works on it saves his work and
closes the file. The conciensious user terminates the drive map and
instructs the OS not to reconnect on login, and locks the computer.
Next user opens the common account, goes to recently used file list
and double-clicks previous user's file from the list, The drive is
remapped using the prior user's credentials, no password needed!
How do I prevent this behavior? I know the user can clear the
recently used file list, but this is really asking too much! BTW, I
am a user, not an admin.
Thanks for your help!
Users have private accounts they access from their desktop. In
addition, there is a common account that is used on "shared"
computers, screens locked after use. This is setup is used to avoid
users locking others out of shared computers, and to avoid the time-
overhead of doing a full logon each time a shared computer is used.
Users typically use the shared computer to logon to some application,
record information, then close the appication and lock the shared
account, thereby leaving the appropriate audit trail while still
having the advantages of the common account.
Here's the rub. It is often convenient for a user to map a network
drive from a shared computer. However, the shared account has no
privleges, so the user must supply his private credentials for the
drive mapping. User opens a file, works on it saves his work and
closes the file. The conciensious user terminates the drive map and
instructs the OS not to reconnect on login, and locks the computer.
Next user opens the common account, goes to recently used file list
and double-clicks previous user's file from the list, The drive is
remapped using the prior user's credentials, no password needed!
How do I prevent this behavior? I know the user can clear the
recently used file list, but this is really asking too much! BTW, I
am a user, not an admin.
Thanks for your help!