Arthur (24th March 2011)
Thanks @Innatius. I just had a play with that and it works! Yeah.
how does this work? do you run it from an admin pc and put the pc name in?
2. Put it into your system32 folder
3. Pull up a domain admin shell (via <runas /useromainName\Administrator cmd.exe> or whatever you need to do on your OS). This ensures that you have access rights to the remote PC
4. From the domain admin shell: psexec \\RemotePCIPAddress cmd.exe (this brings up the remote PC's shell to your local PC)
5. Run quser.exe - this shows the usernames and IDs of those logged in to the remote PC as if you were sitting at that PC
6. Run logoff.exe <user or ID>
I must admit it took me a few minute with step 4 to figure out that my command prompt was actually that of the remote machine OH:
But I did have a few enjoyable minutes logging off my technician.
can you not use the remote shutdown command to log the user off (not tried this)
shutdown -f -l -t 01 -m \\computername
Perhaps AdmnGurl could integrate SasLibEx to make her program compatible with modern OSs?
Existing code to simulate the Secure Attention Sequence (SAS),which most people refer to as control alt delete or ctrl-alt-del, no longer works in Windows Vista. It seems that Microsoft offers a library that exports a function called SimulateSAS(). It is not public and one is supposed to request it by sending a mail to firstname.lastname@example.org. Mails to this address remain unanswered though.
I researched how other people (including Microsoft) have solved this task and was unhappy with the results: some solutions work only with (or without) UAC, most solutions work only for the current or console Terminal Server sessions or need a kernel mode driver.
So I decided to create my own Saslib with the following goals:
- Should work both with and without User Account Control (UAC)
- Should support current, console and any Terminal Server session
- Does not need a driver
- The calling application does not need to be signed or have a special manifest
- Support multiple programming languages
I have succeeded and thus SasLibEx was born: not only can it successfully simulate the SAS sequence it can do this for any/all Terminal Server sessions. It can also lock the workstation (again for all sessions) and switch between the normal desktop and the secure desktop (the desktop that UAC runs on). SasLibEx was successfully tested both with and without User Account Control (UAC).
It is quite a frustrating thing this problem, in our school we cannot run fast user switching either, so we basically have to disable workstation locking for all the pupils on the school now that we are migrating to windows 7 to prevent them locking off computers and just leaving the classrooms, I cannot understand M$ logic behind removing that function of allowing an admin to log off a user.
I would have disabled locking for students from the get go!
There are currently 1 users browsing this thread. (0 members and 1 guests)