Control MachineThe Control Machine page establishes a remote control session between the user's local machine and a selected machine ID.
Note: You can also use Live Connect to initiate a remote control session with a managed machine. Automatic Installation If WinVNC, K-VNC or RAdmin are not installed on a machine and a remote control session is initiated using Control Machine or Video Streaming, then these packages are automatically installed. Installation does not require a reboot. Automatic installation takes up to an extra minute. To eliminate this delay during first time use, you can pre-install WinVNC, K-VNC or RAdmin on any managed machine using Preinstall RC. Note: Uninstalling an agent does not remove the installed Remote Control package, KBU client, KES client, or KDPM client. Before you delete the agent, use Remote Control > Uninstall RC to uninstall remote control on the managed machine. Uninstall all add-on module clients as well. Initiating Remote Control Initiate remote control by clicking the name of the target machine. Icons next to the managed machine ID indicate the current connection status for that machine. Only machine IDs with an
Note: Users can disable remote control and FTP sessions by right-clicking the ActiveX Control An ActiveX control automatically configures and runs the remote control or FTP package for you. The first time you use any remote control or FTP package on a new machine, your browser may ask if it is OK to download and install this ActiveX control. Click yes when asked. If the ActiveX control is blocked by the browser from running, the user is presented with a link to manually download and run the remote control package manually. Helper Applications In setting up a remote control or FTP session, gateway and port blocking problems are eliminated by always initiating outbound connections from both the target machine and the user machine. Helper applications, unique to each supported remote control or FTP package, automatically determine the optimal routing path between the VSAuser machine and the remote machine. If a direct connection is not possible then the helper applications route the remote control traffic through the KServer on the same port used by agents to check-in (default 5721). Enable verbose relay Remote control or FTP of machines behind firewalls and NAT gateways may be relayed through the VSA server using a helper application. Checking this box displays a popup window with status information about the normally hidden helper application. Remote Controlling the KServer Clicking the KServer link starts a remote control session to the KServer itself. Use this feature to remotely manage your own KServer. Only master role users can remote control the KServer. Remote Control and FTP for Users VSA users can provide machine users with the same remote control and FTP access using Agent > Portal Access. Remote Control Malfunctions Some reasons for remote control failure—for target machines with and without an agent—are:
Check-in status These icons indicate the agent check-in status of each managed machine. Hovering the cursor over a check-in icon displays the agent quick view window.
Remote Control Package The remote control package assigned to this machine ID. Select the type of package to remote control a managed machine using Select Type.
Machine.Group ID The list of Machine.Group IDs displayed is based on the Machine ID / Group ID filter and the machine groups the user is authorized to see using System > User Security > Scopes. Only machine IDs with an Current User The user currently logged on to the managed machine. Active Admin The VSA user currently conducting a remote control session to this machine ID. | |||
Topic 443: Send Feedback. Download a PDF of this online book from the first topic in the table of contents. Print this topic. |