Terminal Server session issue

  • Thread starter Thread starter fanny
  • Start date Start date
F

fanny

I had install windows 2000 server with Terminal Server and
Citrix Metaframe XP in the same box.

On the Client's side, I launched "Notepad" successfully
from the client windows2000 professional desktop
to the Terminal Sever via rdp protocol.
This Windows 2000 Terminal Server is not a Domain
Controller, instead is a member server.
Upon application close, the Terminal session
did not exist.
The system seem to fail after I install Citrix Metaframe
XP version.
Please advice ...
Rdgs
Fanny
 
Do you mean that the rdp-connection no longer works, or the ica-connection?
And how does it "fail"? Do you get any error messages on the client? Or in
the EventLog on the server? Did you change the drive mapping of the local
Citrix server drives when you installed MetaFrame?
 
Yes.Notepad is the starting application in Terminal server.
I defined the application path in the TS to run notepad
when a user get connected to TS.

When user connected to TS, it will launched notepad
automatically without going to Desktop, this procedure is
correct.
But when the user exit notepad, by right the windows
session should disconnect.
The user session still remain active after closing the
notepad leaving the windows session in blue screen.

And all this happening came after I install the Citrix
Metaframe XP version.

Pls advice
Thanks

Fanny
 
As I wrote: check which processes are still running in the user
context when notepad has been closed but the window is still open.

There is a workaround for this: make "notepad.bat" your starting
application. In notepad.bat, write:

start /wait notepad.exe
logoff.exe

This will force a logoff when notepad is closed. But I would first
try to find out what is still running in the user context. Could it
be an anti-virus program? If you simply use the work-around, it might
bite you later.
 
Back
Top