Can anyone tell me if there is a way to time out a deviceless connection on
the client side?
I understand that the server side will timeout after a default of 15
minutes, but this does not help me. I don't need the deviceless connection to
persist during the users logon session on the client side. I need it to
timeout to force the user to authenticate again, because the next connection
could possibly be a different user.
The PC is a domain member and is auto-logged on to a local generic account
on the PC and not to a domain account. This is necessary because this is a
multi-user PC for our hospitals surgery department with one single LOB
application loaded that connects back to the server with it's own user
management.
This application is used to chart surgical cases that may last longer than
the nurses shift, so someone else comes in and continues charting the case.
The software is on the PC (instead of a terminal server session) because if
for some reason the PC losses connection to the server, the case charting
software continues charting in local cached mode and will upload the
information when the server becomes available again, thus the charting
software must always be available during the case.
But there are times where the user needs to connect to domain resources. So,
our IT surgical support person has placed shorcuts to the necessary resources
on the "All Users" desktop of the 11 operating room PC's that we have (as
opposed to creating the shortcuts on each of the 70 support staffs desktops
in their profiles and any new users that come along)
What I need to happen is an authentication request to take place each time
the resource is opened up. This happens with the first connection attempt
because the account performing the connection is not a domain member and an
authentication request takes place.
The user will login with his own username and password which provides us
with accountability (instead of the PC being logged on with a generic domain
account with access to the resources). But once the user closes the resource,
subsequent connection attempts occur under the last successfully
authenticated user, even though their shift may have ended hours ago and the
PC's logon session is still ongoing for another person who has come along to
continue charting the surgical case.
If you go to disconnect network drives, you see a deviceless connection that
you can disconnect and this will force an authentication the next time the
resource is accessed.
How can I have this connection either locally disconnect after a length of
time (as opposed to the server disconnecting after the default 15 minutes and
still leaving the deviceless connection on the client side), or prevent the
logon credentials from being cached (via the client side deviceless
connection) for that connection so when the resource is closed, new
connections must authenticate again?
If this cannot be done via XP, can it be done in Vista?
--
Thanks,
Leonard (Bones) McCoy