• No results found

Disconnecting Sessions and Terminating Processes

In document Citrix XenApp Administrator s Guide (Page 136-139)

• Ending sessions

Disconnecting Sessions and Terminating Processes

You can use the console to disconnect a user session from a server or terminate a process in a session. A disconnected session is still active and its applications continue to run, but the client device is no longer communicating with the server.

A user can reconnect to a disconnected session from a different client device without loss of data. For example, you might disconnect users’ sessions if they experience problems on their client device and do not want to lose data from their applications.

When you disconnect a session, you close the connection between the client device and the server. However, this does not log off the user, and programs that were running in the session are still running on the server. If the client user then connects to the server (by selecting a published application or custom connection to the server), the disconnected session is reconnected. When a session is disconnected, the word Disconnected appears in the State column on the tabs in the Access Management Console where session information appears.

You can use the Access Management Console to log off users from their sessions.

You can also reset a user’s client session or a disconnected session.

You can also connect to a user’s disconnected session when you are using the Access Management Console from within a client session on a XenApp server.

To connect, you must know the password of the user who started the session.

Your session must be capable of supporting the same video resolution as the disconnected session.

Resetting a session with the Reset command terminates all processes that are running in that session. You can use the Reset command to remove remaining processes in the case of a session error. However, resetting a session can cause applications to close without saving data.

If you reset a disconnected session, the word Down appears in the State column for the session. When you refresh the console display or when the next automatic refresh occurs, the session no longer appears in the list of sessions.

Special sessions that listen for requests to connect to the server are identified by the word Listen in the State column. If you reset a listener session, the server resets all sessions that use the protocol associated with the listener. For example, if you reset the ICA listener session, you reset the ICA sessions of all users who are connected to the server.

To terminate processes in a user’s session

1. In the left pane of the Access Management Console, right click the server to which the user is connected and select Change display > Users.

The right pane of the console displays all users connected to the server.

2. Select the user’s session for which you want to terminate the process.

3. In the Tasks list at the bottom of the right pane, click Show more tasks for the selected items.

4. In Available Displays, click Processes.

5. Select the process you want to terminate.

6. From the Action menu, select Terminate.

Note: Terminating a process may abruptly end a critical process and leave the server in an unusable state.

To disconnect a session

1. In the left pane of the Access Management Console, right click the server to which the user is connected and select Change display > Users.

The right pane of the console displays all users connected to the server.

2. Select the user’s session you want to disconnect.

3. From the Action menu, select Disconnect.

Note: If you disconnect a session in which a user is running multiple applications, all the applications the user is running are terminated.

To connect to a user’s session from Program Neighborhood

To connect to a disconnected or live session remotely through Program Neighborhood, your session must support the video resolution of the

disconnected session. Also, you can connect only to disconnected sessions that were disconnected from the Access Management Console.

1. Using Program Neighborhood, create a direct custom connection to the server hosting the session.

A. In Program Neighborhood, create a Custom ICA Connection directly to the server.

B. Use your new custom ICA connection to connect to the desktop of the server hosting the session.

2. After you authenticate to the host server, open the Access Management Console.

3. In the left pane of the Access Management Console, select the server to which the user was connected (that is, the server to which you just connected).

4. From the Action menu, select Change display > Sessions.

The right pane of the console displays all sessions running on the server.

5. Select the session you want to log off and from the Action menu, select Connect.

To reset a session

Caution: Resetting effectively deletes the session and results in loss of data for the user. Only reset a session when it is not responding or malfunctions.

1. In the left pane of the Access Management Console, select the server to which the user is connected.

2. From the Action menu, select Change display > Sessions.

The right pane of the console displays all sessions running on the server.

3. Select the session you want to reset, and from the Action menu, select Reset.

You can select and reset multiple sessions at the same time.

To log off from a session

Important: Ending users’ sessions with the Logoff command can result in loss of data if users do not close their applications first. Send a message to warn users to exit all applications if you need to log off their sessions.

1. In the left pane of the Access Management Console, select the server to which the user is connected.

2. From the Action menu, select Change display > Sessions.

The right pane of the console displays all sessions running on the server.

3. Select the session you want to log off and from the Action menu, select Log off.

You can select and log off multiple sessions at the same time.

4. Confirm the logoff when prompted.

In document Citrix XenApp Administrator s Guide (Page 136-139)

Related documents