You can interact directly with sessions by resetting, disconnecting or logging off sessions, or sending messages to users. You can monitor sessions through AppCenter displays or directly through shadowing.
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. (Some applications that rely on virtual channels, such as media players, may behave differently. For example, if you disconnect from a session running Media Player while playing audio, the audio stops playing because the audio virtual channel is no longer available.) When a session is disconnected, session state displays indicate Disconnected. 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.
You can 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 AppCenter 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 support the same video resolution as the disconnected session.
Resetting a session terminates all processes that are running in that session. You can reset a session to remove remaining processes in the case of a session error; however, resetting a session can cause applications to close without saving data.
When you reset a disconnected session, session state displays indicate Down. When you refresh the AppCenter display or when the next automatic refresh occurs, the session no longer appears in the list of sessions.
When special sessions listen for requests to connect to the server, the session state display specifies that it is Listening. 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 connected to the server.
To reset a session, use the ICA Listener Configuration tool to disable and then enable the ICA Listener. Access this tool at.
Sending a message that appears in user sessions can be helpful in situations such as broadcasting information about new applications and upgrades, requesting a shadowing session, or warning of a logoff or system shutdown.
|User||Name of the user account that initiated the session. For anonymous connections, the user name is a string beginning with "Anon" followed by a session number.|
|Session ID||Unique number that begins with 0 for the first connection to the console. Listener sessions are numbered from 65,537 and numbered backward sequentially.|
|Application||Name of the published application running in the session.|
|Type||Session type: ICA or RDP|
|State||Active, Listen, Idle, Disconnected, or Down.|
|Client Name||Name of the client device that is running the session.|
|Logon Time||When the user logged on.|
|Idle Time||How long the session has been idle.|
|Server||Server on which the application is running.|
You can view another user’s session on another device by using shadowing. When shadowing, you can monitor the session activity as if you are watching the screen of the client device that initiated the session. If configured, you can also use your keyboard and mouse to control the user’s keyboard and mouse remotely in the shadowed session. Shadowing a session provides a powerful tool for you to assist and monitor users. Shadowing is a useful option for your Help desk staff who can use it to aid users. Help desk personnel can view a user’s screen or actions to troubleshoot problems and can demonstrate correct procedures. You can also use shadowing for remote diagnosis and as a teaching tool. You can shadow using either the Delivery Services Console or the Shadow Taskbar.
You enable shadowing on a server when you configure XenApp and select the default option, which allows shadowing on all connections on the server. If you do not leave the shadowing option enabled during configuration, you must reinstall XenApp to get shadowing functionality.
By default, the user is notified of the pending shadowing and asked to allow or deny shadowing.
For shadowing options by connection type, such as keyboard, mouse, and user notification options, use the Remote Desktop Server Configuration tool.
Use the Shadow Taskbar to shadow multiple ICA sessions from a single location, including the server console. Use the Shadow button to start shadowing one or more users. The Shadow Taskbar uses the client to launch an ICA session to monitor a user. A separate ICA session is started for each shadowed user.
You must enter your user name and password to start an ICA session on the server running the Shadow Taskbar.
Each shadowed session is represented by a task button on the Shadow Taskbar. Use this button to switch quickly between the shadowing sessions you have open.
To close the Shadow Taskbar, right-click an empty area of the Shadow Taskbar and select Exit.
After configuring XenApp, you can enable shadow logging and configure shadow logging output to one of two locations on the server:
For ease of management, consider logging events in a central file. Only shadowing events go in to this file, so they are more centralized and easier to review.
Click Clear Log to empty the current log file.
Configure the Citrix User policy Log shadow attempts setting.
You can create a user policy to enable user-to-user shadowing, which allows users to shadow other users without requiring them to be members of the Citrix administrator group. With user-to-user shadowing, multiple users from different locations can view presentations and training sessions, allowing one-to-many, many-to-one, and many-to-many online collaboration. Also, you can enable Help Desk personnel to shadow users’ sessions or allow your Sales Department to hold an online meeting to review sales leads.
You enable user-to-user shadowing by creating policies that define users who can and cannot shadow. You then assign the policies to the users to be shadowed.
The list of users permitted to shadow is exclusive for each user for whom a policy is assigned. For example, if you create a policy that permits User A to shadow User B, this policy allows only User A to shadow User B, unless you add more users to the list of users who can shadow in the same policy’s Property sheet.
This example demonstrates how to enable user-to-user shadowing by creating a policy for your “Sales” user group that allows them to shadow the department manager for online collaboration on sales leads. This procedure shows the creation of a shadowing policy.