Re: How do I find out who is connected via Remote Desktop to an XPP machine?

From: Sooner Al (SoonerAl_at_somewhere.net.invalid)
Date: 04/24/04 

Date: Sat, 24 Apr 2004 07:39:06 -0500

Gary,

I can't help with the script issue, but one strategy for idle sessions is to setup a Group Policy to
disconnect after a timeout period. Go to "Start -> Run"
and type gpedit.msc at the command line. Navigate to the "Local Computer Policy -> Computer
Configuration -> Administrative Templates -> Windows Components -> Terminal Services -> Sessions".
Do this on the RDP host. 

-- 
    Al Jarvi (MS-MVP Windows Networking)
Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...
"Gary Webb" <email@garywebb.co.uk> wrote in message news:Etpic.36218$Y%6.4756809@wards.force9.net...
> We have a few XP Pro PC's that act as a method of remote desktopping to
> other servers via VPN across the Internet for support purposes. We also
> access these "RD" machines via remote desktop over the LAN. Whoever connects
> to one of these machines logs on as the same (local) user. These machines
> are limited to a single RDP session that will give an error message if
> somebody is already connected (rather than disconnect them). Therefore, we
> are always aware when somebody is currently accessing one of these machines.
>
> I would like to expand this further by trying to find a method of  knowing
> WHO is connected to these machines (mainly in case somebody has forgot to
> disconnect). I have tried to write a few versions of vbscripts that will
> look at these machines and pull the user name or computer name of who is
> RDP'ing in. I seem to have reached a stage of going around in circles. Can
> anybody offer any advice on a method of getting this information?
>
> Thanks
>
> Gary
>
>

Relevant Pages

  • Re: Scanning for unsecure shared folders
    ... be of help in securing your machines and it can be used on remote machines. ... then your network will be more secure. ... and bypass any Group Policy user configuration and reconfigure the computer. ...
    (microsoft.public.win2000.security)
  • RE: Content Advisor
    ... set in Group Policy do not apply to client machines. ... I suggest we check the following registry key on both client and server. ... Enable Content Advisor on the client first then apply the group policy. ...
    (microsoft.public.windows.server.sbs)
  • Re: XP Pro - Logging on to Domain issues
    ... Active Directory Group Policy to pump this setting out to all machines in ... and click on Logon - enable the policy. ... > Group Policy and it is "Always wait for the network at computer startup ... >>> XP Pro machines that are joined on the domain and rebooted cannot ...
    (microsoft.public.windowsxp.network_web)
  • Re: Restrict computers user in an OU or Group can log on to
    ... Deny Logon Local seems to be a very good idea. ... XP machines all have local ... group policy method both Steven and I have thought of? ... > overriding local policy. ...
    (microsoft.public.win2000.security)
  • Re: Exchange OWA 2003 Trusted Root Certificate
    ... DNS looks to be fine. ... And if these machines reboot, ... and I can see this in the Group Policy Results Wizard in GPMC. ... > a network connectivity, dns name resolution, or domain computer account ...
    (microsoft.public.win2000.security)
Loading