Re: Terminal Server 2003 Sessions don't close when exiting a DOS application

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Brad Pears (donotreply_at_notreal.com)
Date: 10/05/04 

Date: Tue, 5 Oct 2004 14:50:12 -0400

Did you change to the batch file's properties to "Close on Exit"? That might
help your cause too...

If all else fails, you can always modify the Active Driectory "Session" data
as follows...

End a disconnected Session after: 1 minute...
Idle Session Limit: 1 minute

 If you set this in the Active Directory user accounts that use this
partiular DOS program you will only affect those users - not everyone...

Not a great fix but a workaround until another solution is found...

Brad

"Adam Sheppard" <anonymous@discussions.microsoft.com> wrote in message
news:00a601c4a63c$91ef8aa0$a301280a@phx.gbl...
I have tried running the dos application from a batch
file and it still didn't work.

Any other ideas
>-----Original Message-----
>Instead of setting the DOS app executable to start, try
to set a batch file
>that will call the DOS app instead.
>
>--
>Cláudio Rodrigues
>
>Microsoft MVP
>Windows Technologies - Terminal Services
>http://www.terminal-services.net
>"Adam Sheppard" <anonymous@discussions.microsoft.com>
wrote in message
>news:370801c4a615$35706960$a501280a@phx.gbl...
>> Many of my company' clients still use a 16-bit
>> application for their accounting system.
>>
>> With the ease of implementing a WAN many of these
>> customers now want to run these DOS applications via
>> Terminal Services using Windows Server 2003.
>>
>> I've encountered the same problem numerous times where,
>> when you configure a Terminal Server Client to
>> automatically run the DOS based executable it runs
fine -
>> logs onto the server automatically, launches the
program
>> and the end user can run the program.
>>
>> But, when they come to exit the 16-Bit application.
>> Instead of exiting the 16-Bit application and closing
the
>> Terminal Server session, it only closes the 16-Bit
>> application and leaves the session open with blank
window
>> displayed which is the colour of the TS Server's
desktop.
>>
>> I hope I have detailed my problem thoroughly, and I
thank
>> anyone in advance if they can help me
>
>
>.
>

Relevant Pages

  • Re: Several DC one Event Log
    ... but I need the logs to be redirected on one server in real time. ... a batch will not work. ... When a client opens a session on the domain, ...
    (microsoft.public.win2000.active_directory)
  • Re: Terminal Server 2003 Sessions dont close when exiting a DOS application
    ... I have tried running the dos application from a batch ... >that will call the DOS app instead. ... >> Terminal Services using Windows Server 2003. ...
    (microsoft.public.windows.terminal_services)
  • Re: How to submit a job?
    ... > I will run dos copy after a certain lengthy process finished. ... Skedule a [batch, cscript] job on that server that looks for this file, ...
    (microsoft.public.inetserver.asp.db)
  • Re: TCP/IP comms problems between WinXP and DOS
    ... I have written client and server versions ... In the instance where I have a problem the DOS system is running as client, ... By simple changing of i/p addresses / network names I have run the client ...
    (microsoft.public.dotnet.languages.vc)
  • Re: DOS Printing from Windows Server 2003 TS?
    ... STAT-NT03 is the TS server name. ... We will see if it works for the 5 remote users over the Internet. ... We have a customer who is still using and old DOS version of software ... could not find anything except a Kixstart script. ...
    (microsoft.public.windows.terminal_services)