Here's a few ideas. I would run this command to a file, find the remote desktop ID, then run the reset command.
http://www.howtogeek.com/howto/windows/command-line-hack-for-terminal-server-has-exceeded-the-maximum-number-of-allowed-connections/ --- On Thu, 10/2/08, Paul McNett <[EMAIL PROTECTED]> wrote: > From: Paul McNett <[EMAIL PROTECTED]> > Subject: Re: VFP app and terminal server > To: [email protected] > Date: Thursday, October 2, 2008, 11:34 AM > [EMAIL PROTECTED] wrote: > > I have and app, installed in a Windows 2003 server, > that is accessed locally by a number of machines, and using > remote desk top by one branch of the company. > > > > I set up the access in a manner such that when the > user clicks the RDT connection icon, my app starts and when > he closes the app, the RDT connection is closed, and > everything works normally. > > > > However, the branch is in a small town, with a very > poor internet connection, or rather, a very unreliable ISP. > Very often, we suffer disconnections, without previous > warning. > > > > In this case, it is very usual that the maximum of two > RDT connections is reached in one day (the branch manager > starts the app again) and the following morning the branch > cannot connect, because, when the internet connection is > lost, the Windows Server does not close the session > automatically. And then I have to access the server and > close those open connections manually. > > > > I would like to set up a script in the server, so by > just clicking on an icon, all open connections are closed. > This is to be done by the company manager only, but I do not > want to teach him how to do this manually. Therefore, my > need for a script to be launched from an icon on the server. > > > > I would appreciate to be shown how to write that > script (code please!!) > > Off the top of my head (I always look for the simple > solution first > although this one may be brutal), what about: > > NET STOP TerminalService > NET START TerminalService > > (not sure that's the actual correct name of the > service). > > Or... look at the process list before you manually close > the connections > and watch for processes that disappear. Now write a script > to kill such > processes. You may need to google for "windows process > kill" to download > a program to do that, as Windows (last time I looked) was > fairly > crippled in this regard. > > Paul > > > _______________________________________________ > Post Messages to: [email protected] > Subscription Maintenance: > http://leafe.com/mailman/listinfo/profox > OT-free version of this list: > http://leafe.com/mailman/listinfo/profoxtech > Searchable Archive: http://leafe.com/archives/search/profox > This message: > http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] > ** All postings, unless explicitly stated otherwise, are > the opinions of the author, and do not constitute legal or > medical advice. This statement is added to the messages for > those lawyers who are too stupid to see the obvious. _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
