Configure terminal server ICA protocol options to have an "idle timeout" of 15 minutes or say.Just place it the "no screen or keyboard are currently attached to that session" state.) (Note that this will NOT actually end your session. Have them start task manager and make them do right click and then "disconnect" on your username. And places the session in "disconnected state". Wait until the server finally notices on its own.Now there are some stupid workarounds that I know of: It's just that it did not do this in my case.Īlso NORMALLY reconnect-to-active-sessions SHOULD work just as well as reconnect-to-disconnected-sessions. Now NORMALLY the terminal server SHOULD detect a session interruption and change session state from "active" to disconnected" automatically. Reconnect to disconnected sessions worked fine. (See screenshot.)Īnd my Citrix installation would not allow reconnect to active sessions. There are 2 states for a Terminal server session: "active" and "disconnected". You just tell your client to "connect" and then some backend logic, that I do not understand, decides if you wind up with a reconnected or a new session.) (And I don't know of way to tell my client to FORCE reconnect. (This is usually manually configured by the admin.) So you get that popup. And you're usually not allowed to start more than one. If session reconnect does not work then the server tries to start a new terminal server session. This sounds like I problem I've had in the past. So this might not be exactly helpful to you but here's the technical background, as far as I understand it: Note: I have no solution to this problem.
0 kommentar(er)
