The Sessions view is designed to display and manipulate user connections on your network.
The following types of sessions can be managed and monitored by ControlUp:
1. Local console sessions (users working physically at the computer)
2. Remote console sessions (RDP connections to the console of the computer)
3. RDS connections (Sessions established using RDP on a Terminal / Remote Desktop Services host)
4. Citrix HDX/ICA sessions on XenApp / Presentation Server computers
5. Citrix HDX/ICA sessions on XenDesktop VDI stations
6. VMware View Horizon user sessions (PCoIP or RDP)
7. System and Services sessions (not displayed by default – use the “View Options” > “Show System Sessions” checkbox on the Ribbon Bar to change the default behavior)
When you switch to the Sessions view using the Sessions button on the Navigation Bar, the Information Grid will display all of the established user sessions on all of the computers you are currently connected to.
Note: Your active ControlUp license determines the number of sessions you may manage concurrently. For more information, please refer to the “ControlUp Licensing” chapter.
You can also switch to the Sessions view by double-clicking a computer’s row in the Information Grid of the Computers view. In this case, the Information Grid will display only the user sessions established on the computer you selected.
Sessions View Column Reference
The following information columns are available in the Information Grid while using the Sessions View.
|Column Name(sorted alphabetically)||Explanation|
|Citrix Receiver Version||The current version of the Citrix Receiver installed on the client’s machine|
|Client IP||IP address of the computer from which the session was initiated|
|Client Name||Name of the computer from which the session was initiated|
|Connect Time||Time of session’s last switch to the “Active” state|
|CPU||Percentage of CPU consumed by this session|
|Desktop Load Time||The interval between the beginning of desktop initialization and the time the desktop became available to the user. This column is only applicable to full desktop sessions, not published application launches.|
|Disconnect time||Time of session’s last switch to the “Disconnected” state|
|Domain DNS||The name of the Active Directory domain of the user|
|Group Policy Load Time||The loading time of the user logon group policies, not including logon scripts.|
|ICA Latency – Last Recorded||For an active ICA session, the last reading of the protocol latency between the client and the server.
When the session is idle for more than 1 minute, this column will show N/A. Please see the following Citrix forum post for more details on the reasons for this computation:
|ID||Session ID number|
|Idle Time||Time elapsed since last user input was received in session|
|Initial Program||Name of the published application used in the session (if appl.)|
|Logon Duration||The interval between the end of the user’s authentication and the time when the desktop became available to the user, or when a published application was launched.|
|Logon Duration – Other||The time taken by logon scripts, 3rd party profile management solutions, and other components that delayed the logon process.|
|Logon Time||Time of session establishment|
|Machine||Name of the computer hosting the session|
|Memory (Private Bytes)||Non-sharable memory committed to processes in session|
|Memory (Working Set)||Total Working Set of all processes in the session|
|Page Faults/sec||Number of Page Faults per second in the session|
|Processes||Number of processes currently running in this session|
|Profile Load Time||The loading time of the Windows user profile for the session.|
|Session name||Session name (protocol, number)|
|State||Current state of the session (active, disconnected, etc.)|
|Stress Level||An aggregated measure of the session’s performance columns, as configured for the current record in the Stress Settings Pane.|
|User||User name of the session’s owner|
|View Client Connection Server URL||In VMware Horizon View, the URL of the View Connection Server the View Client is attached to.|
|View Client Domain||In VMware Horizon View, the AD domain of the workstation running the View Client|
|View Client Protocol||In VMware Horizon View, the protocol used by the View Client to attach to the VM|
|View Client Tunnel||In VMware Horizon View, whether or not the View Client is using a secure tunnel|
|View Client Type||In VMware Horizon View, the OS type of the workstation running the View Client|
These actions are available when selecting a session or a group of sessions. The actions can be invoked using either the Ribbon Bar “Actions” button, the context menu (right-click), or the Actions Panel.
When invoked from the Sessions view, the Registry Controller enables viewing and editing the HKEY_CURRENT_USER registry hive(s) corresponding to the selected user session(s). For more information about the Registry Controller, please see the Controllers Pane chapter.
Manage Programs and Updates
When invoked from the Sessions view, the Programs and Updates Controller enables viewing the programs installed for each user who has a session established on one of your managed computers. For more information about the Programs and Updates Controller, please see the Controllers Pane chapter.
Remote Desktop to Computer
Switches the display to the Remote Desktops pane and establishes a Remote Desktop session on the computer on which the selected user session is hosted.
With ControlUp, you can open a text chat session with any user currently logged on in your system. Both you and the end user will be presented with a chat window and the chat session will continue until terminated by closing the window.
ControlUp can be used to establish Remote Assistance sessions for support and troubleshooting purposes. Upon first use of this action, you will be required to configure a password for the remote assistance invitation. During the connection attempt, the end user will receive a confirmation dialog box requesting permission for you to connect to the assistance session. Please keep in mind that this action utilizes the built-in Windows Remote Assistance capabilities, which should be enabled on the target computer. If the Remote Assistance is blocked by policy or is not installed as a feature, ControlUp is capable of enabling / installing it remotely with your approval.
Note: A known issue exists when establishing Remote Assistance sessions on Windows XP and Windows Server 2003 computers that were cloned without using the Microsoft Sysprep utility. If your Remote Assistance request fails, please verify that the Sysprep utility has been executed after cloning / imaging the target system.
Terminal Services (sessions actions category)
This action Issues a disconnect command for the selected session(s). The session(s) will then be handled according to your Terminal Services configuration and Group Policy (left disconnected or logged off after a timeout). The end user is not notified of this action.
Log Off Session
This action invokes a log off process for the selected session(s), closing all currently open programs. The end user is not notified of this action.
Using this action, you can establish a remote control session that will allow you to view the activity and collaborate with the target user. This is achieved using the session shadowing mechanism, which needs to be enabled on the target RDS. In order to shadow Citrix ICA sessions, the Citrix Online Plugin needs to be installed on the computer on which you are running the ControlUp console.
Note: When shadowing a user session on a RDS, a new session will be opened for you on that server. This session will log off automatically when the session shadowing is finished.
Note: Various issues not related to ControlUp may prevent your session shadowing from working correctly. Please see the Troubleshooting chapter in this document to check for possible resolutions.
A Super-Message is a rich-text message that can include graphics, text formatting, and various display options. Super Messages can be configured to allow user feedback, to disappear automatically after a configured period of time, or to be displayed on top of other windows.
This action sends a standard “net send”-style message to the selected user session.
Get Session Screenshot
This action allows you to get a quick screenshot of the user’s activity for support or troubleshooting purposes. The selected session has to be active and unlocked for this operation to complete successfully. This operation can be performed in the following modes:
1. User approval – the end user(s) will be presented with a warning message asking for approval of the administrator’s attempt to receive a screenshot of the user’s current activity.
2. User notification – the end user(s) will be presented with a warning message stating that the administrator has requested to receive a screenshot of the user’s current activity. No user approval is needed.
3. No notification – the end user(s) will not be notified of the action.
Note: Please respect the regulations effective in your region and/or organization in regard to the users’ privacy. From a privacy standpoint, it is general practice to request the users’ permission before obtaining a screenshot of their activity. If your user environment involves sensitive or classified activity, it is recommended that you configure the screenshot restriction, as explained below.
If your company policy states that users must be notified before taking a screenshot of their activity or if taking screenshots of user activity is prohibited altogether, you can restrict this action using ControlUp’s Security Policy. This can be achieved either by denying the relevant “Get Session Screenshot” permission explicitly or by configuring it to “Not set”.
Organizations in which ControlUp was upgraded from version 2.0 may have a server-side restriction on taking screenshots of user activity, resulting from an explicit request from the organization. In such a case, the Security Policy will not allow you to change the “Get Session Screenshot” permission. In order to remove or alter this restriction, please contact Smart-X Support.
If you are using ControlUp in Offline Mode, you may restrict this functionality when requesting an Offline License file. In your request e-mail, please state that you would like to restrict taking screenshots of user activity, including the restriction level (without the user’s permission or altogether), and your Offline License file will be issued with the restriction you require.
Group Policy (sessions actions category)
Refresh User Group Policy
This action triggers a Group Policy update on the remote user session using Windows built-in GPUPDATE utility with /Target:User parameter. You can manipulate the “Force” and “Timeout” parameters using the action window.
This action removes any group policy restrictions applied to the target user(s) environment, such as start menu restrictions, blocked locations in Windows Explorer, etc. This can be useful during support sessions in order to allow a user to perform actions normally blocked by Group Policy.
Since the user’s shell (explorer.exe) is restarted when this action is performed, the user will experience a brief disappearance of the Start Manu and taskbar as well as the closing of any open Windows Explorer windows.
Reapply Group Policy
Reapplies Group Policy restrictions previously removed by the “Kill User Group Policy” action. The user’s shell will be restarted again when this action is performed.
Registry (sessions actions category)
This action performs an import of a given .reg file to the HKEY_CURRENT_USER hive of the target user session(s). This action is not available as part of the Registry Controller in the Sessions View.
Processes (sessions actions category)
Start Process in Session
This action allows you to launch a process inside the selected user session(s). You can run any executable that is accessible by the user(s) on the target computer(s). If using a command-line expression or a batch file, please prepend “cmd.exe /c ” to your command. This action will work correctly only if the target end user(s) has appropriate permissions to launch the selected process.
Note – processes started using ”Run Process” action are executed interactively inside the user’s session, so all command output and launched windows will be visible to the user. In order to launch system-level tasks that will be invisible to the user, use the “Run As” command in the Computers view.
Invokes any Script-based Actions downloaded or created for use in your organization and configured to be applicable to Sessions. For more details, please refer to the Script-based Actions chapter.
Using this submenu, you can quickly switch the current view to the Computers View, while selecting the computer on which the selected user session is hosted.