Raritan Computer ACTIVE KVM CLIENT User Manual

KVM and Serial Access Clients

User Guide

Active KVM Client, Virtual KVM Client, Multi-Platform Client,
Raritan Remote Client and Raritan Serial Client

Copyright © 2011 Raritan, Inc.
KVM_Serial_Clients-0M-E
October 2011
255-62-5223-00-0I

This document contains proprietary information that is protected by copyright. All rights reserved. No
part of this document may be photocopied, reproduced, or translated into another language without
express prior written consent of Raritan, Inc.

© Copyright 2011 Raritan, Inc. All third-party software and hardware mentioned in this document are
registered trademarks or trademarks of and are the property of their respective holders.

FCC Information

This equipment has been tested and found to comply with the limits for a Class A digital device,
pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection
against harmful interference in a commercial installation. This equipment generates, uses, and can
radiate radio frequency energy and if not installed and used in accordance with the instructions, may
cause harmful interference to radio communications. Operation of this equipment in a residential
environment may cause harmful interference.

VCCI Information (Japan)

Raritan is not responsible for damage to this product resulting from accident, disaster, misuse, abuse,
non-Raritan modification of the product, or other events outside of Raritan's reasonable control or not
arising under normal operating conditions.

iii

Contents

Chapter 1 Introduction 1

Overview ........................................................................................................................................ 1

KVM and Serial Access Client Help ............................................................................................... 1

Proxy Server Configuration for Use with MPC, VKC and AKC...................................................... 1

Client Uses with Raritan Products ................................................................................................. 2

Chapter 2 Virtual KVM Client (VKC) and Active KVM Client (AKC) 4

About the Virtual KVM Client ......................................................................................................... 5

About the Active KVM Client .......................................................................................................... 5

AKC Supported .NET Framework, Operating Systems and Browsers ............................... 6

Prerequisites for Using AKC ................................................................................................ 7

Toolbar ........................................................................................................................................... 7

Connection Properties ................................................................................................................... 9

Connection Information ................................................................................................................ 11

Keyboard Options ........................................................................................................................ 11

Keyboard Macros .............................................................................................................. 11

Import/Export Keyboard Macros ........................................................................................ 12

Building a Keyboard Macro ............................................................................................... 14

Running a Keyboard Macro ............................................................................................... 15

Modifying and Removing Keyboard Macros ...................................................................... 15

Ctrl+Alt+Del Macro ............................................................................................................ 16

Setting CIM Keyboard/Mouse Options .............................................................................. 16

Video Properties .......................................................................................................................... 17

Refreshing the Screen ....................................................................................................... 17

Auto-Sense Video Settings ................................................................................................ 17

Calibrating Color ................................................................................................................ 17

Adjusting Video Settings .................................................................................................... 18

Using Screenshot from Target ........................................................................................... 21

Changing the Maximum Refresh Rate .............................................................................. 22

Mouse Options ............................................................................................................................. 22

Mouse Pointer Synchronization ......................................................................................... 23

Single Mouse Mode ........................................................................................................... 26

Tool Options ................................................................................................................................. 27

General Settings ................................................................................................................ 27

Client Launch Settings ....................................................................................................... 30

Scan Settings ..................................................................................................................... 31

View Options ................................................................................................................................ 31

View Toolbar ...................................................................................................................... 31

View Status Bar ................................................................................................................. 31

Scaling ............................................................................................................................... 32

Full Screen Mode .............................................................................................................. 32

Contents

iv

Digital Audio ................................................................................................................................. 33

Supported Audio Device Formats...................................................................................... 33

Audio Recommendations and Requirements .................................................................... 33

Audio Bandwidth Requirements ........................................................................................ 34

Connecting to Digital Audio ............................................................................................... 34

Smart Cards (VKC, AKC and MPC) ............................................................................................ 37

Supported and Unsupported Smart Card Readers ........................................................... 39

Smart Card Minimum System Requirements .................................................................... 40

Help Options ................................................................................................................................ 42

Chapter 3 Multi-Platform Client and Raritan Remote Client 43

Overview ...................................................................................................................................... 43

Requirements and Installation ..................................................................................................... 43

MPC Requirements and Installation Instructions .............................................................. 43

RRC Requirements and Installation Instructions ............................................................... 56

Operation ..................................................................................................................................... 61

Navigator ........................................................................................................................... 61

Set Scan Group ................................................................................................................. 67

Toolbars ............................................................................................................................. 69

Status Bars ........................................................................................................................ 73

Screen Modes .................................................................................................................... 76

Connection Profiles ........................................................................................................... 80

Connection Information ..................................................................................................... 93

Connecting to a Remote KVM Console ............................................................................. 96

Closing a Remote Connection ........................................................................................... 96

Shortcut Menu ................................................................................................................... 97

Keyboard Macros .............................................................................................................. 99

Digital Audio ..................................................................................................................... 104

Video Properties .............................................................................................................. 107

Changing the Maximum Refresh Rate ............................................................................ 110

Mouse Options................................................................................................................. 111

Connection and Video Properties .................................................................................... 115

Smart Cards (VKC, AKC and MPC) ................................................................................ 129

Administrative Functions ............................................................................................................ 131

Note to MPC Users .......................................................................................................... 131

General Options, Advanced Options, Client Launch Settings and Scan Settings .......... 132

Upgrading Device Firmware ............................................................................................ 141

Changing a Password ..................................................................................................... 142

Restarting a Device ......................................................................................................... 142

Backup and Restore Functions ....................................................................................... 142

Log Files .......................................................................................................................... 145

Broadcast Port ................................................................................................................. 146

Remote Power Management ........................................................................................... 148

Import/Export Keyboard Macro Definitions ...................................................................... 148

Accessing the MPC Diagnostic Interface (excluding KX II) ............................................. 156

Contents

v

Chapter 4 Virtual Media 157

Overview .................................................................................................................................... 158

Prerequisites for Using Virtual Media .............................................................................. 161

Virtual Media in a Linux Environment .............................................................................. 162

Virtual Media in a Mac Environment ................................................................................ 162

Conditions when Read/Write is Not Available ................................................................. 163

Using Virtual Media .................................................................................................................... 163

Virtual Media File Server Setup (File Server ISO Images Only) ..................................... 164

Connecting to Virtual Media ....................................................................................................... 165

Mounting Local Drives ..................................................................................................... 165

Mounting CD-ROM/DVD-ROM/ISO Images .................................................................... 166

Disconnecting Virtual Media ...................................................................................................... 168

Chapter 5 Raritan Serial Console 169

Overview .................................................................................................................................... 169

RSC System Requirements ....................................................................................................... 169

Setting Windows OS Variables ........................................................................................ 169

Setting Linux OS Variables .............................................................................................. 172

Setting UNIX OS Variables .............................................................................................. 172

Installing RSC on Windows ....................................................................................................... 173

Installing RSC for Sun Solaris and Linux ................................................................................... 173

Opening RSC from the Remote Console .................................................................................. 174

Raritan Serial Console Interface ................................................................................................ 176

Default RSC Option Values ............................................................................................. 176

Emulator .......................................................................................................................... 177

Edit ................................................................................................................................... 185

Tools ................................................................................................................................ 186

Chat ................................................................................................................................. 190

Help ................................................................................................................................. 191

Appendix A Informational Notes 192

Overview .................................................................................................................................... 192

Java Runtime Environment (JRE) ............................................................................................. 192

IPv6 Support Notes .................................................................................................................... 193

Keyboards .................................................................................................................................. 194

Non-US Keyboards .......................................................................................................... 194

Macintosh Keyboard ........................................................................................................ 196

Fedora ........................................................................................................................................ 197

Resolving Fedora Core Focus ......................................................................................... 197

Mouse Pointer Synchronization (Fedora) ........................................................................ 197

VKC and MPC Smart Card Connections to Fedora Servers ........................................... 197

Resolving Issues with Firefox Freezing when Using Fedora .......................................... 197

Audio .......................................................................................................................................... 197

Number of Supported Audio/Virtual Media and Smartcard Connections ........................ 198

Audio Playback and Capture Issues ............................................................................... 198

Audio in a Linux Environment .......................................................................................... 199

Contents

vi

Audio in a Mac Environment ............................................................................................ 199

Audio in a Windows Environment .................................................................................... 199

USB Ports and Profiles .............................................................................................................. 200

Help for Choosing USB Profiles ...................................................................................... 200

Changing a USB Profile when Using a Smart Card Reader ........................................... 202

Virtual Media .............................................................................................................................. 202

Virtual Media Not Refreshed After Files Added ............................................................... 202

Virtual Media via VKC and AKC in a Windows Environment .......................................... 203

Accessing Virtual Media on a Windows 2000 Server Using a D2CIM-VUSB ................. 204

Disconnecting Mac and Linux Virtual Media USB Drives ................................................ 204

Target BIOS Boot Time with Virtual Media ...................................................................... 204

Virtual Media Connection Failures Using High Speed for Virtual Media Connections .... 204

CIMs ........................................................................................................................................... 205

Windows 3-Button Mouse on Linux Targets .................................................................... 205

Windows 2000 Composite USB Device Behavior for Virtual Media ................................ 205

CC-SG ....................................................................................................................................... 206

Virtual KVM Client Version Not Known from CC-SG Proxy Mode .................................. 206

Single Mouse Mode - Connecting to a Target Under CC-SG Control Via VKC Using

Firefox .............................................................................................................................. 206

Proxy Mode and MPC ..................................................................................................... 206

Moving Between Ports on a Device................................................................................. 206

Index 207

1

In This Chapter

Overview .................................................................................................... 1

KVM and Serial Access Client Help .......................................................... 1

Proxy Server Configuration for Use with MPC, VKC and AKC ................. 1

Client Uses with Raritan Products ............................................................. 2

Chapter 1

Introduction

Overview

Raritan Multi-Platform Client (MPC), Raritan Remote Client (RRC),
Virtual KVM Client (VKC), and the Active KVM Client (AKC) are graphical
user interfaces for the Raritan Dominion and IP-Reach product lines,
providing remote access to target servers connected to Raritan KVM
over IP devices.

Non-Windows generation 2 users must use Raritan Multi-Platform Client,
AKC or VKC. Windows users connecting to a generation 1 Raritan
device must use RRC or MPC.

The standalone Raritan Serial Console (RSC) is used to make direct
connections to a serial target without going through the device. The user
specifies the device address and the port number (target), and is then
connected.

KVM and Serial Access Client Help

This help provides information on using Raritan's KVM and serial clients.
A PDF version of the help can be downloaded from Raritan's Firmware
and Documentation page on the Raritan website (see www.raritan.com).
Raritan recommends that you refer to the Raritan website for the most
up-to-date user guides available.

Proxy Server Configuration for Use with MPC, VKC and AKC

When the use of a Proxy Server is required, a SOCKS proxy must also
be provided and configured on the remote client PC.

Note: If the installed proxy server is only capable of the HTTP proxy
protocol, you cannot connect.

To configure the SOCKS proxy:

1. On the client, select Control Panel > Internet Options.
a. On the Connections tab, click 'LAN settings'. The Local Area

Network (LAN) Settings dialog opens.

Chapter 1: Introduction

2

b. Select 'Use a proxy server for your LAN'.

Product

Works with...

MPC

RRC

VKC

RSC

AKC

KX 1 G1

c. Click Advanced. The Proxy Settings dialog opens.
d. Configure the proxy servers for all protocols. IMPORTANT: Do not

select 'Use the same proxy server for all protocols'.

Note: The default port for a SOCKS proxy (1080) is different from
HTTP proxy (3128).

2. Click OK at each dialog to apply the settings.

3. Next, configure the proxies for Java™ applets by selecting Control
Panel > Java.

e. On the General tab, click Network Settings. The Network Settings

dialog opens.

f. Select Use Proxy Server.
g. Click Advanced. The Advanced Network Settings dialog opens.
h. Configure the proxy servers for all protocols. IMPORTANT: Do not

select 'Use the same proxy server for all protocols'.

Note: The default port for a SOCKS proxy (1080) is different from
HTTP proxy (3128).

4. If you are using standalone MPC, you must also do the following:

i. Open the start.bat file in MPC directory with a text editor.
j. Insert the following parameters to the command line. Add them

before "-classpath": -DsocksProxyHost=<socks proxy ip addr> ­DsocksProxyPort=<socks proxy port>

The parameters should look as follows:
start javaw -Xmn128M -Xmx512M -XX:MaxHeapFreeRatio=70 -

XX:MinHeapFreeRatio=50 -Dsun.java2d.noddraw=true ­DsocksProxyHost=192.168.99.99 -DsocksProxyPort=1080 ­classpath .\sdeploy.jar;.\sFoxtrot.jar;.\jaws.jar;.\sMpc.jar
com.raritan.rrc.ui.RRCApplication %1

Client Uses with Raritan Products

The following table lists Raritan products and the client applications with
which they work:

Chapter 1: Introduction

3

Product

Works with...

KX II G2

KX II 2.2 (or later)

KX II-101

KX II-101-V2

KX 101 G1

KSX G1

KSX II G2

LX 2.4.5 (or later)

SX

IP Reach G1

UST-IP G1

Legend:

G1

Generation 1

G2

Generation 2

Note: There are some differences in MPC when used with the Dominion
KX I, Dominion KX II, and Dominion KSX II devices; these differences
are noted in the respective device user guides.

Note: MPC and VKC are Java™ based. AKC is .NET based.

4

In This Chapter

About the Virtual KVM Client ..................................................................... 5

About the Active KVM Client ..................................................................... 5

Toolbar ....................................................................................................... 7

Connection Properties ............................................................................... 9

Connection Information ........................................................................... 11

Keyboard Options .................................................................................... 11

Video Properties ...................................................................................... 17

Mouse Options ........................................................................................ 22

Tool Options ............................................................................................ 27

View Options ........................................................................................... 31

Digital Audio ............................................................................................ 33

Smart Cards (VKC, AKC and MPC) ........................................................ 37

Help Options ............................................................................................ 42

Chapter 2

Virtual KVM Client (VKC) and Active
KVM Client (AKC)

The Virtual KVM Client (VKC) and Active KVM Client (AKC) are
interfaces used to access remote targets. AKC and VKC share similar
features with the exception of the following:

 Minimum system requirements
 Supported operating systems and browsers
 Keyboard macros created in AKC cannot be used in VKC.
 Direct port access configuration (see Enabling Direct Port Access

via URL)

 AKC server certification validation configuration (see Prerequisites

for Using AKC)

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

5

About the Virtual KVM Client

Whenever you access a target server using the Remote Console, a
Virtual KVM Client (VKC) window opens. There is one Virtual KVM Client
for each target server connected. These windows can be accessed via
the Windows® task bar.

Note: Some features, such as client launch settings and smart cards, are
not supported by the LX and, as such, are not supported by AKC or VKC
when used in conjunction with the LX.

Note: The KX II-101-V2 only supports a connection to one target at a
time.

Virtual KVM Client windows can be minimized, maximized, and moved
around your computer desktop.

Note: Refreshing your HTML browser closes the Virtual KVM Client
connection, so exercise caution.

Note: If you are using Firefox 3.0.3, you may experience problems
launching the application. If this occurs, clear the browser cache and
launch the application again.

About the Active KVM Client

The Microsoft Windows .NET-based Active KVM Client (AKC) is
available in the KX II 2.2 (and later) and LX 2.4.5 (and later). AKC can be
used with all KX II and LX models. The KX2-101 and KX II-101-V2 is not
supported.

AKC is based on Microsoft Windows .NET technology and allows you to
run the client in Windows environments without the use of the Java
Runtime Environment (JRE), which is required to run Raritan's Virtual
KVM Client (VKC) and Multi-Platform Client (MPC). AKC also works with
CC-SG.

Note: Some features, such as client launch settings and smart cards, are
not supported by the LX and, as such, are not supported by AKC or VKC
when used in conjunction with the LX.

Note: If you are using direct port access with AKC, you must open a new
browser window or browser tab for each target you want to access. If you
try to access another target by entering the DPA URL into the same
browser window or browser tab you are currently accessing a target
from, you will not be able to connect and may receive an error.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

6

AKC Supported .NET Framework, Operating Systems and Browsers

.NET Framework

AKC requires Windows .NET® version 3.5, and will work with both 3.5
and 4.0 installed but will not work with 4.0 alone.

Operating Systems

When launched from Internet Explorer®, AKC allows you to reach target
servers via the KX II 2.2 (and later) and the LX 2.4.5 (and later). AKC is
compatible with the following platforms running .NET Framework 3.5:

 Windows XP® operating system
 Windows Vista® operating system (up to 64 bit)
 Windows 7® operating system (up to 64 bit)

Note: You must be using Windows 7 if WINDOWS PC FIPs is turned
on and you are accessing a target using AKC and a smartcard.

Since .NET is required to run AKC, if you do not have .NET installed or
you have an unsupported version of .NET installed, you will receive a
message instructing you to check the .NET version.

Browser

 Internet Explorer 6 or later

If you attempt to open AKC from a browser other than IE 6 or later, you
will receive an error message instructing you to check your browser and
to switch to Internet Explorer.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

7

Toolbar

Button

Button
Name

Description

Connection
Properties

Opens the Modify Connection Properties dialog
from which you can manually adjust bandwidth
options (such as connection speed, color depth,
and so forth).

Video
Settings

Opens the Video Settings dialog, allowing you to
manually adjust video conversion parameters.

Color
Calibration

Adjusts color settings to reduce excess color
noise.

Same as choosing Video > Color Calibrate.

Note: Not available in KX II-101-V2.

Target
Screenshot

Click to take a screenshot of the target server
and save it to a file of your choosing.

Audio

Opens a dialog that allows you to select from a
list of audio devices connected to a client PC.

Once audio devices have been connected to the
target, select to disconnect the devices.

Prerequisites for Using AKC

In order to use AKC:

 Ensure the cookies from the IP address of the device that is being

accessed are not currently being blocked.

 Windows Vista, Windows 7 and Windows 2008 server users should

ensure that the IP address of the device being accessed is included
in their browser's Trusted Sites Zone and that Protected Mode is not
on when accessing the device.

Enable AKC Download Server Certificate Validation
If the device (or CC-SG) administrator has enabled the Enable AKC

Download Server Certificate Validation option:

 Administrators must upload a valid certificate to the device or

generate a self-signed certificate on the device. The certificate must
have a valid host designation.

 Each user must add the CA certificate (or a copy of self-signed

certificate) to the Trusted Root CA store in their browser.

When launching AKC from the CC-SG Admin Client, you must have
JRE™ 1.6.0_10 or above.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

8

Button

Button
Name

Description

Note: This feature is available with the KX II 2.4.0
(and later).

Note: This feature is not supported by the LX.

Synchronize
Mouse

Dual-mouse mode forces the realignment of the
target server mouse pointer with the mouse
pointer.

Note: Not available in KX II-101-V2.

Refresh
Screen

Forces a refresh of the video screen.

Auto-sense
Video
Settings

Forces a refresh of the video settings (resolution,
refresh rate).

Smart Card

Opens a dialog that allows you to select from a
list of smart card readers connected to a client
PC.

Note: This feature is available on the KSX II 2.3.0
(and later) and the KX II 2.1.10 (and later).

Note: This feature is not supported by the LX.

Send
Ctrl+Alt+Del

Sends a Ctrl+Alt+Del hot key combination to the
target server.

Single Cursor
Mode

Starts Single Cursor mode in which the local
mouse pointer no longer appears onscreen.

Press Ctrl+Alt+O to exit this mode.

Note: Not available in KX II-101-V2.

Full Screen
Mode

Maximizes the screen real estate to view the
target server desktop.

Scaling

Increases or reduces the target video size so you
can view the entire contents of the target server
window without using the scroll bar.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

9

Connection Properties

The dynamic video compression algorithms maintain KVM console
usability under varying bandwidth constraints. The devices optimize KVM
output not only for LAN use, but also for WAN use. These devices can
also control color depth and limit video output, offering an optimal
balance between video quality and system responsiveness for any
bandwidth.

The parameters in the Properties dialog can be optimized to suit your
needs for different operating environments. Connection properties are
saved across subsequent connections to generation 2 devices once they
are set and saved.

To set the connection properties:

1. Choose Connection > Properties or click the Connection Properties
button in the toolbar. The Properties dialog appears.

Note: KX II-101 does not support 1G Ethernet.

2. Choose the Connection Speed from the drop-down list. The device
can automatically detect available bandwidth and not limit bandwidth
use. However, you can also adjust this usage according to
bandwidth limitations.

 Auto
 1G Ethernet
 100 Mb Ethernet
 10 Mb Ethernet
 1.5 Mb (MAX DSL/T1)
 1 Mb (Fast DSL/T1)
 512 Kb (Medium DSL/T1)

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

10

 384 Kb (Slow DSL/T1)
 256 Kb (Cable)
 128 Kb (Dual ISDN)
 56 kb (ISP Modem)
 33 kb (Fast Modem)
 24 kb (Slow Modem)

Note that these settings are an optimization for specific conditions
rather than an exact speed. The client and server always attempt to
deliver video as quickly as possible on the network regardless of the
current network speed and encoding setting. But the system will be
most responsive when the settings match the real world environment.

3. Choose the Color Depth from the drop-down list. The device can
dynamically adapt the color depth transmitted to remote users in
order to maximize usability in all bandwidths.

 15-bit RGB Color
 8-bit RGB Color
 4-bit Color
 4-bit Gray
 3-bit Gray
 2-bit Gray
 Black and White

Important: For most administrative tasks (server monitoring,
reconfiguring, and so on), the full 24-bit or 32-bit color spectrum
made available by most modern video graphics cards is not
necessary. Attempting to transmit such high color depths wastes
network bandwidth.

4. Use the slider to select the desired level of Smoothing (15-bit color
mode only). The level of smoothing determines how aggressively to
blend screen regions with small color variation into a single smooth
color. Smoothing improves the appearance of target video by
reducing displayed video noise.

5. Click OK to set these properties.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

11

Connection Information

To obtain information about your Virtual KVM Client

connection:

 Choose Connection > Info... The Connection Info window opens.

The following information is displayed about the current connection:

 Device Name - The name of the device.
 IP Address - The IP address of the device.
 Port - The KVM communication TCP/IP port used to access the

target device.

 Data In/Second - Data rate in.
 Data Out/Second - Data rate out.
 Connect Time - The duration of the connect time.
 FPS - The frames per second transmitted for video.
 Horizontal Resolution - The screen resolution horizontally.
 Vertical Resolution - The screen resolution vertically.
 Refresh Rate - How often the screen is refreshed.
 Protocol Version - RFB protocol version.

Keyboard Options

To copy this information:

 Click Copy to Clipboard. The information is available to be pasted

into the program of your choice.

Keyboard Macros

Keyboard macros ensure that keystroke combinations intended for the
target server are sent to and interpreted only by the target server.
Otherwise, they might be interpreted by the computer on which the
Virtual KVM Client is running (your client PC).

Macros are stored on the client PC and are PC-specific. Therefore, if you
use another PC, you cannot see your macros. In addition, if another
person uses your PC and logs in under a different name, that user will
see your macros since they are computer-wide.

Keyboard macros created in the Virtual KVM Client are available in Multi­Platform Client (MPC) and vice versa. However, keyboard macros
created in Active KVM Client (AKC) cannot be used in VKC or MPC, and
vice versa.

Note: KX II-101 does not support AKC.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

12

Import/Export Keyboard Macros

Macros exported from Active KVM Client (AKC) cannot be imported into
Multi-Platform Client (MPC) or Virtual KVM Client (VKC). Macros
exported from MPC or VKC cannot be imported into AKC.

Note: KX II-101 does not support AKC.

To import macros:

1. Choose Keyboard > Import Keyboard Macros to open the Import
Macros dialog. Browse to the folder location of the macro file.

2. Click on the macro file and click Open to import the macro.
a. If too many macros are found in the file, an error message is

displayed and the import terminates once OK is selected.

b. If the import fails, an error dialog appears and a message

regarding why the import failed is displayed. Select OK to
continue the import without importing the macros that cannot be
imported.

3. Select the macros to be imported by checking their corresponding
checkbox or using the Select All or Deselect All options.

4. Click OK to begin the import.
a. If a duplicate macro is found, the Import Macros dialog appears.

Do one of the following:
 Click Yes to replace the existing macro with the imported

version.

 Click Yes to All to replace the currently selected and any

other duplicate macros that are found.

 Click No to keep the original macro and proceed to the next

macro

 Click No to All keep the original macro and proceed to the

next macro. Any other duplicates that are found are skipped
as well.

 Click Cancel to stop the import.
 Alternatively, click Rename to rename the macro and import

it. If Rename is selected, the Rename Macro dialog appears.
Enter a new name for the macro in the field and click OK.
The dialog closes and the process proceeds. If the name
that is entered is a duplicate of a macro, an alert appears
and you are required to enter another name for the macro.

b. If during the import process the number of allowed, imported

macros is exceeded, a dialog appears. Click OK to attempt to
continue importing macros or click Cancel to stop the import
process.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

13

The macros are then imported. If a macro is imported that contains a hot
key that already exists, the hot key for the imported macro is discarded.

To export macros:

1. Choose Tools > Export Macros to open the Select Keyboard Macros
to Export dialog.

2. Select the macros to be exported by checking their corresponding
checkbox or using the Select All or Deselect All options.

3. Click Ok. A dialog from which to locate and select the macro file
appears. By default, the macro exists on your desktop.

4. Select the folder to save the macro file to, enter a name for the file
and click Save. If the macro already exists, you receive an alert
message. Select Yes to overwrite the existing macro or No to close
the alert without overwriting the macro.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

14

Building a Keyboard Macro

To build a macro:

1. Click Keyboard > Keyboard Macros. The Keyboard Macros dialog
appears.

2. Click Add. The Add Keyboard Macro dialog appears.

3. Type a name for the macro in the Keyboard Macro Name field. This
name appears in the Keyboard menu after it is created.

4. From the Hot-Key Combination field, select a keyboard combination
from the drop-down list. This allows you to execute the macro with a
predefined keystroke. Optional

5. In the Keys to Press drop-down list, select each key you would like to
use to emulate the keystrokes that is used to perform the command.
Select the keys in the order by which they are to be pressed. After
each selection, select Add Key. As each key is selected, it appears
in the Macro Sequence field and a Release Key command is
automatically added after each selection.

6. To use the Send Text to Target function for the macro, click the
Construct Macro from Text button.

7. For example, create a macro to close a window by selecting Left Ctrl
+ Esc. This appears in the Macro Sequence box as follows:

Press Left Ctrl
Release Left Ctrl
Press Esc
Release Esc

8. Review the Macro Sequence field to be sure the macro sequence is
defined correctly.

a. To remove a step in the sequence, select it and click Remove.
b. To change the order of steps in the sequence, click the step and

then click the up or down arrow buttons to reorder them as
needed.

9. Click OK to save the macro. Click Clear to clear all field and start
over. When you click OK, the Keyboard Macros dialog appears and
lists the new keyboard macro.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

15

10. Click Close to close the Keyboard Macros dialog. The macro now
appears on the Keyboard menu in the application. Select the new
macro on the menu to run it or use the keystrokes you assigned to
the macro.

Running a Keyboard Macro

Once you have created a keyboard macro, execute it using the keyboard
macro you assigned to it or by choosing it from the Keyboard menu.

Run a Macro from the Menu Bar

When you create a macro, it appears under the Keyboard menu.
Execute the keyboard macro by clicking on it in the Keyboard menu.

Run a Macro Using a Keyboard Combination

If you assigned a keyboard combination to a macro when building it, you
can execute the macro by pressing its assigned keystrokes. For
example, press the keys Ctrl+Alt+0 simultaneously to minimize all
windows on a Windows target server.

Modifying and Removing Keyboard Macros

To modify a macro:

1. Choose Keyboard > Keyboard Macros. The Keyboard Macros dialog
appears.

2. Choose the macro from among those listed.

3. Click Modify. The Add/Edit Macro dialog appears.

4. Make your changes.

5. Click OK.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

16

To remove a macro:

1. Choose Keyboard > Keyboard Macros. The Keyboard Macros dialog
appears.

2. Choose the macro from among those listed.

3. Click Remove. The macro is deleted.

Ctrl+Alt+Del Macro

Due to its frequent use, a Ctrl+Alt+Delete macro is preprogrammed.
Clicking on the Ctrl+Alt+Delete button in the toolbar sends this key

sequence to the server or to the KVM switch to which you are currently
connected.

In contrast, if you were to physically press the Ctrl+Alt+Del keys, the
command would first be intercepted by your own PC due to the structure
of the Windows operating system, instead of sending the key sequence
to the target server as intended.

Note: VKC for the KX II-101 uses an icon set that differs from the icon
set used in VKC for other Dominion KX products. See VKC Toolbar for
the KX II-101 for additional information.

Setting CIM Keyboard/Mouse Options

To access the DCIM-USBG2 setup menu:

1. Put the mouse focus on a window such as Note Pad (Windows®
operating system) or an equivalent.

2. Select Set CIM Keyboard/Mouse options. This is the equivalent of
sending the Left-Control and Num Lock to the target. The CIM setup
menu options are then displayed.

3. Set the language and mouse settings.

4. Exit the menu to return to normal CIM functionality.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

17

Video Properties

Refreshing the Screen

The Refresh Screen command forces a refresh of the video screen.
Video settings can be refreshed automatically in several ways:

 The Refresh Screen command forces a refresh of the video screen.
 The Auto-sense Video Settings command automatically detects the

target server's video settings.

 The Calibrate Color command calibrates the video to enhance the

colors being displayed.

In addition, you can manually adjust the settings using the Video Settings
command.

To refresh the video settings, do one of the following:

 Choose Video > Refresh Screen or click the Refresh Screen button

in the toolbar.

Auto-Sense Video Settings

The Auto-sense Video Settings command forces a re-sensing of the
video settings (resolution, refresh rate) and redraws the video screen.

To automatically detect the video settings, do the following:

 Choose Video > Auto-sense Video Settings or click the Auto-Sense

Video Settings button in the toolbar. A message stating that the
auto adjustment is in progress appears.

Calibrating Color

Use the Calibrate Color command to optimize the color levels (hue,
brightness, saturation) of the transmitted video images. The color
settings are on a target server-basis.

Note: The Calibrate Color command applies to the current connection
only.

Note: The KX II-101 does support color calibration.

To calibrate the color, do the following:

 Choose Video > Calibrate Color or click the Calibrate Color button

in the toolbar. The target device screen updates its color

calibration.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

18

Adjusting Video Settings

Use the Video Settings command to manually adjust the video settings.

To change the video settings:

1. Choose Video > Video Settings or click the Video Settings button

in the toolbar to open the Video Settings dialog.

2. Adjust the following settings as required. As you adjust the settings
the effects are immediately visible:

a. Noise Filter

The device can filter out the electrical interference of video output
from graphics cards. This feature optimizes picture quality and
reduces bandwidth. Higher settings transmit variant pixels only if
a large color variation exists in comparison to the neighboring
pixels. However, setting the threshold too high can result in the
unintentional filtering of desired screen changes.
Lower settings transmit most pixel changes. Setting this
threshold too low can result in higher bandwidth use.

b. PLL Settings

Clock - Controls how quickly video pixels are displayed across
the video screen. Changes made to clock settings cause the
video image to stretch or shrink horizontally. Odd number
settings are recommended. Under most circumstances this
setting should not be changed because the autodetect is usually
quite accurate.

Phase - Phase values range from 0 to 31 and will wrap around.
Stop at the phase value that produces the best video image for
the active target server.

c. Brightness: Use this setting to adjust the brightness of the target

server display.

d. Brightness Red - Controls the brightness of the target server

display for the red signal.
e. Brightness Green - Controls the brightness of the green signal.
f. Brightness Blue - Controls the brightness of the blue signal.
g. Contrast Red - Controls the red signal contrast.
h. Contrast Green - Controls the green signal.
i. Contrast Blue - Controls the blue signal.

If the video image looks extremely blurry or unfocused, the
settings for clock and phase can be adjusted until a better image
appears on the active target server.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

19

Warning: Exercise caution when changing the Clock and Phase
settings. Doing so may result in lost or distorted video and you may
not be able to return to the previous state. Contact Raritan Technical
Support before making any changes.

j. Horizontal Offset - Controls the horizontal positioning of the

target server display on your monitor.
k. Vertical Offset - Controls the vertical positioning of the target

server display on your monitor.

3. Select Automatic Color Calibration to enable this feature.

4. Select the video sensing mode:
 Best possible video mode

The device will perform the full Auto Sense process when
switching targets or target resolutions. Selecting this option
calibrates the video for the best image quality.

 Quick sense video mode

With this option, the device will use a quick video Auto Sense in
order to show the target's video sooner. This option is especially
useful for entering a target server's BIOS configuration right after
a reboot.

5. Click OK to apply the settings and close the dialog. Click Apply to

apply the settings without closing the dialog.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

20

Note: Some Sun background screens, such as screens with very dark
borders, may not center precisely on certain Sun servers. Use a different
background or place a lighter colored icon in the upper left corner of the
screen.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

21

Using Screenshot from Target

You are able to take a screenshot of a target server using the
Screenshot from Target server command. If needed, save this
screenshot to a file location of your choosing as a bitmap, JPEG or PNG
file.

To take a screenshot of the target server:

1. Select Video > Screenshot from Target or click the Screenshot from

Target button on the toolbar.

2. In the Save dialog, choose the location to save the file, name the file,

and select a file format from the 'Files of type' drop-down.

3. Click Save to save the screenshot.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

22

Mouse Options

Changing the Maximum Refresh Rate

If the video card you are using on the target uses custom software and
you are accessing the target through MPC or VKC, you may need to
change the maximum refresh rate of the monitor in order for the refresh
rate to take effect on the target.

To adjust the monitor refresh rate:

1. In Windows®, select Display Properties > Settings > Advanced to

open the Plug and Play dialog.

2. Click on the Monitor tab.

3. Set the 'Screen refresh rate'.

4. Click OK and then OK again to apply the setting.

When controlling a target server, the Remote Console displays two
mouse cursors: one belonging to your client workstation and the other
belonging to the target server.

You can operate in either single mouse mode or dual mouse mode.
When in dual mouse mode, and provided the option is properly
configured, the mouse cursors align.

When there are two mouse cursors, the device offers several mouse
modes:

 Absolute (Mouse Synchronization)
 Intelligent (Mouse Mode)
 Standard (Mouse Mode)

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

23

Mouse Pointer Synchronization

When remotely viewing a target server that uses a mouse, two mouse
cursors are displayed: one belonging to your remote client workstation
and the other belonging to the target server. When the mouse pointer
lies within the Virtual KVM Client target server window, mouse
movements and clicks are directly transmitted to the connected target
server. While in motion, the client mouse pointer slightly leads the target
mouse pointer due to mouse acceleration settings.

On fast LAN connections, you can disable the Virtual KVM Client mouse
pointer and view only the target server's pointer. You can toggle between
these two modes (single mouse and dual mouse).

Mouse Synchronization Tips

Be sure to follow these steps when configuring mouse synchronization:

1. Verify that the selected video resolution and refresh rate are among

those supported by the device. The Virtual KVM Client Connection
Info dialog displays the actual values that the device is seeing.

2. For KX II and LX devices, verify that the cable length is within the

specified limits for the selected video resolution.

3. Verify that the mouse and video have been properly configured

during the installation process.

4. Force an auto-sense by clicking the Virtual KVM Client auto-sense

button.

5. If that does not improve the mouse synchronization (for Linux, UNIX,

and Solaris KVM target servers):
a. Open a terminal window.
b. Enter the xset mouse 1 1 command.
c. Close the terminal window.

6. Click the "Virtual KVM Client mouse synchronization" button .

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

24

Additional Notes for Intelligent Mouse Mode

 Be sure that there are no icons or applications in the upper left

section of the screen since that is where the synchronization routine
takes place.

 Do not use an animated mouse.
 Disable active desktop on KVM target servers.

Synchronize Mouse

In dual mouse mode, the Synchronize Mouse command forces
realignment of the target server mouse pointer with Virtual KVM Client
mouse pointer.

To synchronize the mouse, do one of the following:

 Choose Mouse > Synchronize Mouse or click the Synchronize

Mouse button in the toolbar.

Note: This option is available only in Standard and Intelligent mouse
modes.

Standard Mouse Mode

Standard Mouse mode uses a standard mouse synchronization
algorithm using relative mouse positions. Standard Mouse mode requires
that mouse acceleration is disabled and other mouse parameters are set
correctly in order for the client and server mouse to stay synchronized.

To enter Standard Mouse mode:

 Choose Mouse > Standard.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

25

Intelligent Mouse Mode

In Intelligent Mouse mode, the device can detect the target mouse
settings and synchronize the mouse cursors accordingly, allowing mouse
acceleration on the target. Intelligent mouse mode is the default for non­VM targets.

During synchronization, the mouse cursor does a “dance” in the top left
corner of the screen and calculates the acceleration. For this mode to
work properly, certain conditions must be met.

To enter intelligent mouse mode:

 Choose Mouse > Intelligent.

Intelligent Mouse Synchronization Conditions

The Intelligent Mouse Synchronization command, available on the
Mouse menu, automatically synchronizes mouse cursors during
moments of inactivity. For this to work properly, however, the following
conditions must be met:

 The active desktop should be disabled on the target.
 No windows should appear in the top left corner of the target page.
 There should not be an animated background in the top left corner of

the target page.

 The target mouse cursor shape should be normal and not animated.
 The target mouse speeds should not be set to very slow or very high

values.

 Advanced mouse properties such as “Enhanced pointer precision" or

“Snap mouse to default button in dialogs” should be disabled.

 Choose “Best Possible Video Mode” in the Video Settings window.
 The edges of the target video should be clearly visible (that is, a

black border should be visible between the target desktop and the
remote KVM console window when you scroll to an edge of the
target video image).

 When using the intelligent mouse synchronization function, having a

file icon or folder icon located in the upper left corner of your desktop
may cause the function not to work properly. To be sure to avoid any
problems with this function, Raritan recommends you do not have file
icons or folder icons in the upper left corner of your desktop.

After autosensing the target video, manually initiate mouse
synchronization by clicking the Synchronize Mouse button on the toolbar.
This also applies when the resolution of the target changes if the mouse
cursors start to desync from each other.

If intelligent mouse synchronization fails, this mode will revert to standard
mouse synchronization behavior.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

26

Please note that mouse configurations will vary on different target
operating systems. Consult your OS guidelines for further details. Also
note that intelligent mouse synchronization does not work with UNIX
targets.

Absolute Mouse Mode

In this mode, absolute coordinates are used to keep the client and target
cursors in sync, even when the target mouse is set to a different
acceleration or speed. This mode is supported on servers with USB ports
and is the default mode for VM and dual VM targets.

To enter absolute mouse mode:

 Choose Mouse > Absolute.

Note: The absolute mouse setting requires a USB target system and is
the recommended mouse setting for KX II-101.

Note: For KX II, Absolute Mouse Synchronization is available for use with
the virtual media-enabled USB CIM (D2CIM-VUSB and D2CIM-DVUSB)
only.

Single Mouse Mode

Single Mouse mode uses only the target server mouse cursor and the
local mouse pointer no longer appears onscreen. While in single mouse
mode, the Synchronize Mouse command is not available (there is no
need to synchronize a single mouse cursor).

Note: Single mouse mode does not work on Windows or Linux targets
when using VM as a client.

Note: VKC for the KX II-101 uses an icon set that differs from the icon
set used in VKC for other Dominion KX products. See VKC Toolbar for
the KX II-101 for additional information.

To enter single mouse mode, do the following:

1. Choose Mouse > Single Mouse Cursor.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

27

Tool Options

2. Click the Single/Double Mouse Cursor button in the toolbar.

To exit single mouse mode:

1. Press Ctrl+Alt+O on your keyboard to exit single mouse mode.

General Settings

To set the tools options:

1. Click Tools > Options. The Options dialog appears.

2. Select the Enable Logging checkbox only if directed to by Technical

Support. This option creates a log file in your home directory.

3. Choose the Keyboard Type from the drop-down list (if necessary).

The options include:

 US/International
 French (France)
 German (Germany)
 Japanese
 United Kingdom
 Korean (Korea)
 French (Belgium)
 Norwegian (Norway)
 Portuguese (Portugal)
 Danish (Denmark)
 Swedish (Sweden)

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

28

 German (Switzerland)
 Hungarian (Hungary)
 Spanish (Spain)
 Italian (Italy)
 Slovenian
 Translation: French - US
 Translation: French - US International

In AKC, the keyboard type defaults to the local client, so this option
does not apply. Additionally, the KX II-101 and KX II-101-V2 do not
support single cursor mode, so the Exit Single Cursor Mode function
does not apply for those devices.

4. Configure hotkeys:

 Exit Full Screen Mode - Hotkey. When you enter Full Screen

mode, the display of the target server becomes full screen and
acquires the same resolution as the target server. This is the hot
key used for exiting this mode.

 Exit Single Cursor Mode - Hotkey. When you enter single cursor

mode, only the target server mouse cursor is visible. This is the
hot key used to exit single cursor mode and bring back the client
mouse cursor.

 Disconnect from Target - Hotkey. Enable this hotkey to allow

users to quickly disconnect from the target.

For hotkey combinations, the application does not allow you to
assign the same hotkey combination to more than one function. For
example, if Q is already applied to the Disconnect from Target
function, it won't be available for the Exit Full Screen Mode function.
Further, if a hotkey is added to the application due to an upgrade and
the default value for the key is already in use, the next available
value is applied to the function instead.

5. Click OK.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

29

Keyboard Limitations

Language

Configuration method

US Intl

Default

French

Keyboard Indicator

German

System Settings (Control Center)

Japanese

System Settings (Control Center)

UK

System Settings (Control Center)

Korean

System Settings (Control Center)

Belgian

Keyboard Indicator

Norwegian

Keyboard Indicator

Danish

Keyboard Indicator

Swedish

Keyboard Indicator

Hungarian

System Settings (Control Center)

Spanish

System Settings (Control Center)

Italian

System Settings (Control Center)

Slovenian

System Settings (Control Center)

Portuguese

System Settings (Control Center)

Turkish Keyboards
If using a Turkish keyboard, you must connect to a target server through

the Active KVM Client (AKC). It is not supported by other Raritan clients.
Slovenian Keyboards
The < key does not work on Slovenian keyboards due to a JRE

limitation.

Language Configuration on Linux

Because the Sun JRE on Linux has problems generating the correct Key
Events for foreign-language keyboards configured using System
Preferences, Raritan recommends that you configure foreign keyboards
using the methods described in the following table.

Note: The Keyboard Indicator should be used on Linux systems using
Gnome as a desktop environment.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

30

Client Launch Settings

Configuring client launch settings allows you to define the screen
settings for a KVM session.

Note: LX devices support this feature in MPC. LX does not support client
launch setting in VKC and AKC.

To configure client launch settings:

1. Click Tools > Options. The Options dialog appears.

2. Click on the Client Launch Settings tab.

 To configure the target window settings:
a. Select 'Standard - sized to target Resolution' to open the window

using the target's current resolution. If the target resolution is
greater than the client resolution, the target window covers as
much screen area as possible and scroll bars are added (if
needed).

b. Select Full Screen to open the target window in full screen mode.
 To configure the monitor on which the target viewer is launched:
a. Select 'Monitor Client Was Launched from' if you want the target

viewer to be launched using the same display as the application
that is being used on the client (for example, a web browser or
applet).

b. Use Select From Detected Monitors to select from a list of

monitors that are currently detected by the application. If a
previously selected monitor is no longer detected, 'Currently
Selected Monitor Not Detected' is displayed.

 To configure additional launch settings:
a. Select Enable Single Cursor Mode to enable single mouse mode

as the default mouse mode when the server is accessed.

b. Select Enable Scale Video to automatically scale the display on

the target server when it is accessed.

c. Select Pin Menu Toolbar if you want the toolbar to remain visible

on the target when it is in Full Screen mode. By default, while the
target is in Full Screen mode, the menu is only visible when you
hover your mouse along the top of the screen.

3. Click OK.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

31

Scan Settings

The KX II and LX provide a port scanning feature that searches for
selected targets and displays them in a slide show view, allowing you to
monitor up to 32 targets at one time. You can connect to targets or focus
on a specific target as needed. Scans can include standard targets,
blade servers, tiered Dominion devices, and KVM switch ports. See
Scanning Ports. Use the Scan Settings tab to customize the scan interval
and default display options.

To set scan settings:

1. Click Tools > Options. The Options dialog appears.

2. Select the Scan Settings tab.

3. In the "Display Interval (10-255 sec):" field, specify the number of

seconds you want the target that is in focus to display in the center of
the Port Scan window.

4. In the "Interval Between Ports (10 - 255 sec):" field, specify the

interval at which the device should pause between ports.

5. In the Display section, change the default display options for the

thumbnail size and split orientation of the Port Scan window.

6. Click OK.

View Options

View Toolbar

You can use the Virtual KVM client with or without the toolbar display.

To toggle the display of the toolbar (on and off):

 Choose View > View Toolbar.

View Status Bar

By default, the status bar is displayed at the bottom of the target window.

To hide the status bar:

 Click View > Status Bar to deselect it.

To restore the status bar:

 Click View > Status Bar to select it.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

32

Scaling

Scaling your target window allows you to view the entire contents of the
target server window. This feature increases or reduces the size of the
target video to fit the Virtual KVM Client window size, and maintains the
aspect ratio so that you see the entire target server desktop without
using the scroll bar.

To toggle scaling (on and off):

 Choose View > Scaling.

Full Screen Mode

When you enter Full Screen mode, the target's full screen is displayed
and acquires the same resolution as the target server. The hot key used
for exiting this mode is specified in the Options dialog, see Tool Options
(on page 27).

While in Full Screen mode, moving your mouse to the top of the screen
will display the Full Screen mode menu bar. If you want the menu bar to
remain visible while in Full Screen mode, enable the Pin Menu Toolbar
option from the Tool Options dialog. See Tool Options (on page 27).

To enter full screen mode:

 Choose View > Full Screen.

To exit full screen mode:

 Press the hot key configured in the Tool's Options dialog. The default

is Ctrl+Alt+M.

If you want to access the target in full screen mode at all times, you can
make Full Screen mode the default.

To set Full Screen mode as the default mode:

1. Click Tools > Options to open the Options dialog.

2. Select Enable Launch in Full Screen Mode and click OK.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

33

Digital Audio

The KX II 2.4.0 (and later) supports end-to-end bidirectional digital audio
connections for digital audio playback and capture devices from a remote
client to a target server. The audio devices are accessed over a USB
connection. A D2CIM-DVUSB and the current device firmware are
required.

Windows®, Linux® and Mac® operating systems are supported. The
Virtual KVM Client (VKC), Active KVM Client (AKC) and Multi-Platform
Client (MPC) support connections to audio devices.

Note: Audio CDs are not supported by virtual media so will not work with
the audio feature.

Before you begin using the audio feature, Raritan recommends you
review the audio related information documented in the following
sections of Help:

 Supported Audio Device Formats (on page 33)
 Audio Recommendations and Requirements (on page 33)
 Informational Notes, Audio (on page 197)

Supported Audio Device Formats

The KX II 2.4.0 (and later) supports one playback device and one record
device on a target at a time. The following audio device formats are
supported:

 Stereo, 16 bit, 44.1K (Playback only)
 Mono, 16 bit, 44.1K (Playback only)
 Stereo, 16 bit, 22.05K (Playback only)
 Mono, 16 bit, 22.05K (Playback only)
 Stereo, 16 bit, 11.025K (Playback and Capture)
 Mono, 16 bit, 11.025K (Playback and Capture)

Audio Recommendations and Requirements

Set the target audio level to a mid-range setting. For example, on a
Windows® client, set the audio to 50 or lower. This setting must be
configured through the playback or capture audio device, not from the
client audio device control.

Note: This feature is available with the KX II 2.4.0 (and later).

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

34

Audio Bandwidth Requirements

Audio format

Network bandwidth requirement

44.1 KHz, 16bit stereo

176 KB/s

44.1 KHz, 16bit mono

88.2 KB/s

2.05 KHz, 16bit stereo

88.2 KB/s

22.05 KHz, 16bit mono

44.1 KB/s

11.025 KHz, 16bit stereo

44.1 KB/s

11.025 KHz, 16bit mono

Audio 22.05 KB/s

The table below details the bandwidth requirements to transport audio
under each of the selected formats.

In practice, the bandwidth used to connect audio to a target is higher due
to the keyboard and video data consumed in opening and using an audio
application on the target.

A general recommendation is to have a least 1.5MB of connection before
running Playback and Capture. However, high video content, full color
connections at high target screen resolutions consume much more
bandwidth and impact the quality of the audio considerably.

There are a number of recommended client settings that will reduce the
impact of the video on audio quality at lower bandwidths:

 Connect Audio playback at the lower quality formats. The impact of

video consuming bandwidth is much less notable at 11k connections
than at 44k

 Set the connection speed under Connection Properties to a value

that best matches the client to server connection.

 Set the color depth to as lowest value as possible. Reducing to 8 bit

color considerably reduces the bandwidth consumed.

 Set Smoothing, under Connection Properties, to High. This will

improve the appearance of the target video by reducing displayed
video noise.

 Set the Noise Filter, under Video settings to its highest setting, 7

(highest value). Less bandwidth will be used for target screen
changes.

Connecting to Digital Audio

To connect to an audio device from the Virtual KVM Client

(VKC) or Active KVM Client (AKC):

1. Connect the audio device to the remote client PC prior to launching

the browser connection to the KX II 2.4.0 (and later).

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

35

2. Connect to the target from the Port Access page.

3. Once connected, click the Audio icon in the toolbar. The

Connect Audio Device dialog appears. A list of available audio
device connected to the remote client PC is displayed.

Note: If there are no available audio devices connected to the remote
client PC, the Audio icon is grayed out. .

4. Check Connect Playback Device if you are connecting to a playback

device.

5. Select the device that you wish to connect from the drop-down list.

6. Select the audio format for the playback device from the Format:

drop-down.

Note: Select the format that you wish to use based on the available
network bandwidth. Formats with lower sampling rates consume less
bandwidth and may tolerate more network congestion.

7. Check Connect Recording Device if you are connecting a recording

device.

8. Select the device that you wish to connect from the drop-down list.

9. Select the audio format for the recording device from the Format:

drop-down.

10. Click OK. If the audio connection is established, a confirmation

message appears. Click OK.

If the connection was not established, an error message appears.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

36

Once an audio connection is established, that Audio menu is
changed to Disconnect Audio.

To disconnect from the audio device:

 Click the Audio icon in the toolbar and select OK when you are

prompted to confirm the disconnect. A confirmation message
appears. Click OK.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

37

Smart Cards (VKC, AKC and MPC)

Using the KX II 2.1.10 (and later) or KSX II 2.3.0 (and later), you are able
to mount a smart card reader onto a target server to support smart card
authentication and related applications. For a list of supported smart
cards, smart card readers, and additional system requirements, see

Supported and Unsupported Smart Card Readers (on page 39).

When accessing a server remotely, you will have the opportunity to
select an attached smart card reader and mount it onto the server. Smart
card authentication is used with the target server, it is not used to log into
the device. Therefore, changes to smart card PIN and credentials do not
require updates to device accounts. When mounted onto the target
server, the card reader and smart card will cause the server to behave
as if they had been directly attached. Removal of the smart card or smart
card reader will cause the user session to be locked or you will be logged
out depending on how the card removal policy has been setup on the
target server OS. When the KVM session is terminated, either because it
has been closed or because you switch to a new target, the smart card
reader will be automatically unmounted from the target server.

When PC-Share mode is enabled on the device, multiple users can
share access to a target server. However, when a smart card reader is
connected to a target, the device will enforce privacy regardless of the
PC-Share mode setting. In addition, if you join a shared session on a
target server, the smart card reader mounting will be disabled until
exclusive access to the target server becomes available.

After a KVM session is established to the target server, a Smart Card
menu and button are available in the Virtual KVM Client (VKC), Active
KVM Client (AKC) and Multi-Platform Client (MPC). Once the menu is
opened or the Smart Card button is selected, the smart card readers that
have been detected as attached to the remote client are displayed. From
this dialog you can attach additional smart card readers, refresh the list
of smart card readers attached to the target, and detach smart card
readers. You are also able to remove or reinsert a smart card. This
function can be used to provide notification to a target server OS that
requires a removal/reinsertion in order to display the appropriate login
dialog. Using this function allows the notification to be sent to a single
target without affecting other active KVM sessions.

To mount a smart card reader:

1. Click the Smart Card menu and then select Smart Card Reader.

Alternatively, click the Smart Card button in the toolbar.

2. Select the smart card reader from the Select Smart Card Reader

dialog.

3. Click Mount.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

38

4. A progress dialog will open. Check the 'Mount selected card reader

automatically on connection to targets' checkbox to mount the smart
card reader automatically the next time you connect to a target. Click
OK to begin the mounting process.

To update the smart card in the Select Smart Card Reader

dialog:

 Click Refresh List if a new smart card reader has been attached to

the client PC.

To send smart card remove and reinsert notifications to the

target:

 Select the smart card reader that is currently mounted and click the

Remove/Reinsert button.

To unmount a smart card reader:

 Select the smart card reader to be unmounted and click the Unmount

button.

Smart card reader mounting is also supported from the Local Console.
See Local Console Smart Card Access in your Dominion device help.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

39

Supported and Unsupported Smart Card Readers

Type

Vendor

Model

Verified

USB

SCM
Microsystems

SCR331

Verified on local
and remote

USB

ActivIdentity®

ActivIdentity USB
Reader v2.0

Verified on local
and remote

USB

ActivIdentity

ActivIdentity USB
Reader v3.0

Verified on local
and remote

USB

Gemalto®

GemPC USB-SW

Verified on local
and remote

USB
Keyboard/Card
reader Combo

Dell®

USB Smart Card
Reader Keyboard

Verified on local
and remote

USB
Keyboard/Card
reader Combo

Cherry GmbH

G83-6744
SmartBoard

Verified on local
and remote

USB reader for
SIM-sized cards

Omnikey

6121

Verified on local
and remote

Integrated (Dell
Latitude D620)

O2Micro

OZ776

Remote only

PCMCIA

ActivIdentity

ActivIdentity
PCMCIA Reader

Remote only

PCMCIA

SCM
Microsystems

SCR243

Remote only

Type

Vendor

Model

Notes

USB Keyboard/Card
reader Combo

HP®

ED707A

No interrupt endpoint
=> not compatible with

External, USB smart card readers are supported.

Supported Smart Card Readers

Note: SCM Microsystems SCR331 smart card readers must be using
SCM Microsystems firmware v5.25.

Unsupported Smart Card Readers

This table contains a list of readers that Raritan has tested and found not
to work with the Raritan device, therefore they are unsupported. If a
smart card reader does not appear in the supported smart card readers
table or in the unsupported smart card readers table, Raritan cannot
guarantee it will function with the device.

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

40

Type

Vendor

Model

Notes

Microsoft® driver

USB Keyboard/Card
reader Combo

SCM
Microsystems

SCR338

Proprietary card
reader implementation
(not CCID-compliant)

USB Token

Aladdin®

eToken
PRO™

Proprietary
implementation

Smart Card Minimum System Requirements

Local Port Requirements

The basic interoperability requirement for local port attachment to the is:

 All devices (smart card reader or token) that are locally attached

must be USB CCID-compliant.

Target Server Requirements

When using smart card readers, the basic requirements for
interoperability at the target server are:

 The IFD (smart card reader) Handler must be a standard USB CCID

device driver (comparable to the generic Microsoft® USB CCID
driver).

 A D2CIM-DVUSB (Dual-VM CIM) is required and must be using

firmware version 3A6E or later.

 Blade chassis server connections, where a CIM per blade is used,

are supported.

 Blade chassis server connections, where a CIM per chassis is used,

is only supported for IBM® BladeCenter® models H and E with auto­discovery enabled.

Windows XP Targets

Windows XP® operating system targets must be running Windows XP
SP3 in order to use smart cards with the . If you are working with .NET

3.5 in a Windows XP environment on the target server, you must be

using SP1.

Linux Targets

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

41

If you are using a Linux® target, the following requirements must be met

Operating system

CCID requirements

RHEL 5

ccid-1.3.8-1.el5

SuSE 11

pcsc-ccid-1.3.8-3.12

Fedora® Core 10

ccid-1.3.8-1.fc10.i386

Operating system

Required PC/SC

RHEL 5

pcsc-lite-1.4.4-0.1.el5
SuSE 11

pcsc-lite-1.4.102-1.24

Fedora® Core 10

pcsc-lite-1.4.102.3.fc10.i386

to use smart card readers with the Raritan device.

 CCID Requirements

If the Raritan D2CIM-DVUSB VM/CCID is not recognized as a smart
card reader by your Linux target, you may need to update the CCID
driver version to 1.3.8 or above and update the driver configuration
file (Info.plist).

Remote Client Requirements

The basic requirements for interoperability at the remote client are:

 The IFD (smart card reader) Handler must be a PC/SC compliant

device driver.

 The ICC (smart card) Resource Manager must be available and be

PC/SC compliant.

 The JRE™ 1.6.x with smart card API must be available for use by the

Raritan client application.

Linux Clients

If you are using a Linux® client, the following requirements must be met
to use smart card readers with the Raritan device.

Note: User login to client, on smart card insertion, may take longer when
1 or more KVM sessions are actively in place to targets. As the login
process to these targets is also under way.

 PC/SC Requirements

Chapter 2: Virtual KVM Client (VKC) and Active KVM Client (AKC)

42

Help Options

 Create a Java™ Library Link

A soft link must be created to the libpcsclite.so after upgrading RHEL
4, RHEL 5 and FC 10. For example, ln –s /usr/lib/libpcsclite.so.1
/usr/lib/libpcsclite.so, assuming installing the package places the
libraries in /usr/lib or /user/local/lib.

 PC/SC Daemon

When the pcsc daemon (resource manager in framework) is
restarted, restart the browser and MPC, too.

About Raritan Virtual KVM Client

This menu command provides version information about the Virtual KVM
Client, in case you require assistance from Raritan Technical Support.

To obtain version information:

1. Choose Help > About Raritan Virtual KVM Client.

2. Use the Copy to Clipboard button to copy the information contained

in the dialog to a clipboard file so it can be accessed later when
dealing with support (if needed).

43

In This Chapter

Overview .................................................................................................. 43

Requirements and Installation ................................................................. 43

Operation ................................................................................................. 61

Administrative Functions ....................................................................... 131

Chapter 3

Multi-Platform Client and Raritan
Remote Client

Overview

Raritan Multi-Platform Client (MPC) and Raritan Remote Console are
graphical user interfaces for the Raritan product lines, providing remote
access to target servers connected to Raritan KVM over IP devices. See

Client Uses with Raritan Products (on page 2) for information on the

clients that are compatible with specific Raritan devices.

Requirements and Installation

MPC Requirements and Installation Instructions

Note to CC-SG Users

If you are using Dominion KX II in a CC-SG configuration, do not use the
CC-SG proxy mode if you are also planning to use the Multi-Platform
Client (MPC).

MPC Minimum System Requirements

The minimum system requirements for the Multi-Platform Client are:

 CPU Speed: 1.0 GHz
 RAM: 512 Mbytes

Note: Running the client software on system configurations below either
of these specifications may impact performance and result in errors.

Chapter 3: Multi-Platform Client and Raritan Remote Client

44

MPC Supported Operating Systems and Browsers

Device
generation

Operation system

Browsers

Generation 1

 Windows XP® operating

system

 Windows 2000® operating

system SP4

 Windows Vista® operation

system (32 bit only)

 Red Hat Enterprise

Workstation 3.0 and 4.0

 SUSE Linux Professional

9.2 and 10

 Fedora Core 5 and above
 Mac OS 10.4.9 or later®*
 Solaris™

 Internet Explorer®

6 and above**

 Firefox® 1.0 or

later

 Safari® 2.0 or later
 Netscape® 7.2
 Mozilla® 1.7

Operating Systems

When launched as a web applet or as a standalone application, MPC
allows you to reach target servers via different Raritan Dominion devices
and IP Reach models.

Following are the operating systems and browsers supported for
Generation 1 and Generation 2 Raritan devices using MPC.

Chapter 3: Multi-Platform Client and Raritan Remote Client

45

Generation 2

 Windows 7® (32 and 64

bit)

 Windows XP operating

system

 Windows 2008
 Windows 2003

Windows 2000® operating
system SP4

 Windows Vista operation

system (32 and 64 bit)

 Red Hat Enterprise

Workstation 4.0 and 5.0

 Open SUSE Linux 10 and

11

 Fedora Core 8 -11
 Mac* OS 10.5 and above

Solaris™

 Internet Explorer 6

and above**

 Firefox 1.5, 2.0

and 3.0 (up to
build 3.0.10)

 Safari 3.0 or later

* Important: Only Mac 10.5 and 10.6 with an Intel® processor can run
JRE 1.6 and, therefore, be used as a client. Mac 10.5.8 does not
support MPC as a standalone client.

Chapter 3: Multi-Platform Client and Raritan Remote Client

46

** Note: If you are using Internet Explorer® 7, you may run into

Mode

Operating system

Browser

Windows x64
32-bit mode

Windows XP®

 Internet Explorer® 6.0

SP1+ or 7.0, IE 8

 Firefox® 1.06 - 3

Windows Server 2003®

 Internet Explorer 6.0

SP1++, IE 7, IE 8

 Firefox 1.06 - 3

Windows Vista®

 Internet Explorer 7.0 or

8.0

Windows 7®

 Internet Explorer 9.0
 Firefox 1.06 - 3

Windows x64
64-bit mode

Windows XP

64bit OS, 32bit browsers:

 Internet Explorer 6.0

SP1+, 7.0 or 8.0

 Firefox 1.06 - 3

64bit mode, 64bit browsers:

 Internet Explorer 7.0 or

Windows XP
Professional®

Windows XP Tablet®

Windows Vista

Windows Server 2003

permission issues when trying to connect to a target server. To avoid
this, do the following:

1. In Internet Explorer, click Tools > Internet Options to open the Internet

Options dialog.

2. In the "Temporary Internet files" section, click Settings. The Settings

dialog opens.

3. In the "Check for newer versions of stored pages" section, select

Automatically.

4. Click OK to apply the settings.

JRE

 Generation 1 devices support JRE™ 1.4.2_05 and above
 Generation 2 devices support JRE 1.6.x and higher with the

exception of 1.6.2

The JRE™ plug-in is available for the Windows® 32-bit and 64-bit
operating systems. MPC and VKC can be launched only from a 32-bit
browser, or 64-bit IE7 or IE8 browser.

Following are the Java™ 32-bit and 64-bit Windows operating system
requirements.

Chapter 3: Multi-Platform Client and Raritan Remote Client

47

Mode

Operating system

Browser

Windows Server 2008

8.0

Windows 7

Note: If you are using Internet Explorer 8 to access MPC and do not

Character

Description

Character

Description

!

Exclamation point

:

Colon

"

Double quote

;

Semi-colon

#

Pound sign

=

Equal sign

$

Dollar sign

>

Greater than sign

%

Percent sign

?

Question mark

&

Ampersand

@

At sign

'

Single quote

[

Left bracket

(

Left parenthesis

\

Backward slash

)

Right parenthesis

]

Right bracket

*

Asterisk

^

Caret

+

Plus sign

_

Underscore

have Java installed on your machine, an alert bar or a dialog opens
asking you to download the latest version of Java. However, in some
instances, only a blank window opens and you are prompted to perform
the download. If this occurs, set Internet Explorer 8 to use Compatibility
View. See Microsoft® Internet Explorer help for information on change IE
to this view.

Note to IPv6 Users

Due to a browser limitation, MPC cannot be downloaded via the KX IPv6
address from Firefox® if Pop-up Manager is enabled. Do one of the
following to avoid this issue:

 Use the hostname of the device for the MPC browser download.
 Set Firefox to not block Pop-up windows via edit\Preferences\Privacy

and Security.

 Use IPV4 address.
 Use standalone MPC.
 Use the latest version of Firefox.

Special Characters in MPC

The following table identifies the special characters that can be used in
MPC:

Chapter 3: Multi-Platform Client and Raritan Remote Client

48

Character

Description

Character

Description

,

Comma

`

Grave accent

-

Dash

{

Left brace

.

Period

|

Pipe sign

/

Forward slash

}

Right brace

<

Less than sign

~

Tilde

Character

Description

:

Colon

"

Double quote

&

Ampersand

'

Single quote

Invalid MPC Username Characters

The following characters cannot be used in usernames for MPC.

Installing and Opening Standalone MPC

Raritan recommends that you open only one standalone MPC session at
a time. Opening more than one standalone MPC session on the same
client at the same time may cause performance problems and system
errors.

Important: MPC modem connectivity is supported on the Windows®
operating system. When working in Windows, use Standalone MPC.

Important: Only Mac 10.5 and 10.6 with an Intel® processor can run
JRE 1.6 and, therefore, be used as a client. Mac 10.5.8 does not
support MPC as a standalone client.

You must have the MPC JAR file to install MPC for any of these
operating systems.

To check for the MPC JAR file:

1. Download the installation file, MPC-installer.jar from the Raritan

website (www.raritan.com) on the Support > Firmware and
Documentation page.

2. Locate the Dominion product you are working with and click the

Standalone Multi-Platform Client link.

Chapter 3: Multi-Platform Client and Raritan Remote Client

49

3. If copying MPC-installer.jar from a known location, double-click the

file to start installation.

Windows

To check the JRE version in Windows:

1. Do one of the following to check the JRE version in Windows:

 Determine your version of the JRE from the Java website:

http://www.java.com/en/download/help/testvm.xml.

 Click the Windows Start button at the bottom left of your page

and click Control Panel.

Tip: In the upper left corner of the page, you may see a panel named
Control Panel with the option Switch to Classic View or Switch to
Category View. For easier viewing, opt for Classic View.

a. Search the Control Panel files for a Java icon. When you locate

the Java icon, double-click it to open the Java Control panel.
Click the General tab and then click the About button to check
the current Java Runtime Environment (JRE).

b. If the JRE is version 1.6 or later, proceed with the MPC

Installation. If the Java icon does not exist in the Control Panel or
if the JRE version is prior to 1.6, go to the Sun Microsystems
website at http://java.sun.com/products/ to download the latest
version of JRE.

2. For future Java access and to automatically open it, set your path to

the Java executable.
a. Right-click the My Computer icon on your desktop and click

Properties.

b. Click the Advanced tab and then click "Environment variables".
c. Edit the Path address so that it contains the path to the Java

executable.
For example, if Java is installed on C:\j2re1.6 and your path is
currently set to C:\WINDOWS\SYSTEM32, then change the path
to read C:\WINDOWS\SYSTEM32;C:\j2re1.6

To install MPC for Windows:

1. Download the MPC-installer.jar installation file or copy the file from a

known location.

2. Double-click the jar file icon to open the installation dialog.

3. After the initial dialog appears, click Next.

4. Choose the directory where you want to install MPC and click Next.

Click Browse to locate a non-default directory.

Chapter 3: Multi-Platform Client and Raritan Remote Client

50

Note: If you are using Windows 7, when User Access Control is
turned on, you will need to manually create a folder to contain the
MPC files. You will also need to assign the Admin user, at a
minimum, Write permissions to the folder from Properties dialog >
Security tab. Alternatively, you can turn off User Access Control.

5. Click Next.

6. In the Shortcut dialog, choose a shortcut location, determine who

should have the shortcut, and determine whether you want the
shortcut on the desktop. When finished, click Next.

Once the installation is complete, the final dialog indicates where you
will find an uninstaller program and provides an option for generating
an automatic installation script. Click Done to close the Installation
dialog.

To open MPC in Windows:

1. Click the Windows Start menu and then choose All Programs >

Raritan Multi-Platform Client. Alternatively, double-click the MPC
desktop shortcut icon if you created one.

2. Double-click the desired device in the Navigator to establish a

connection.

3. Type your user name and password in the device dialog and then

click OK to log on.

To disable Java caching and clear the cache (use these steps

with Microsoft Windows XP and JRE 1.6.0):

1. From the Start menu, click Control Panel.

2. Double-click on the Java icon to launch it. The Java Control Panel

dialog appears.

3. To disable Java caching:

a. From the General tab, click the Settings button. The Temporary

Files Settings dialog appears.

b. Click the View Applets button. The Java Applet Cache Viewer

opens.

c. Deselect the Enable Caching checkbox if it is already checked.
d. Click OK.

4. To clear the Java cache:

a. From the Temporary Files Settings dialog, click the Delete Files

button. The Delete Temporary Files dialog appears.

b. Select the temporary files that you want to delete.
c. Click OK.

Chapter 3: Multi-Platform Client and Raritan Remote Client

51

Linux®

Determine your version of the JRE from the Java website:
http://www.java.com/en/download/help/testvm.xml.

You may need some configuration depending on your OS and browser.
Configuration instructions are provided with the JRE download.

Important: When launching MPC from a browser, it is highly
recommended that you disable the Java Applet caching.

Although no actual problems have occurred when Java caching is turned
on, some non-impacting Java exceptions have occurred. Generation of
these Java-exceptions can appear in the Java Applet Console window
and may degrade performance.

For Linux/UNIX environments, the Java Control Panel is located in the
JRE's bin directory; the location varies based on where JRE was
installed by your Linux/UNIX administrator.

Tip: It is also recommended that you clear the Java cache.

To check the JRE version in Linux:

1. In a graphical environment, open a terminal dialog.

2. Type java-version in the command line and press Enter on your

keyboard. The currently-installed version of Java Runtime
Environment (JRE) is displayed.

If your path variable is not set to where the java binaries have been
installed, you may not be able to see the JRE version.

3. Set your path:

a. To set your path and assuming JRE 1.6 is installed in

/usr/local/java: you must set your PATH variable.

b. To set the path for bash shell, export

PATH=$PATH:/usr/local/java/j2re1.6/bin.

c. To set the path for tcsh or csh, set PATH = ($PATH

/usr/local/java/j2re1.6/bin).

These commands can be typed at the terminal each time you login.
Alternatively, you can add it to your .bashrc for bash shell, .cshrc for
csh, or tcsh so that each time you login the PATH is already set.

See your shell documentation if you encounter problems.

4. If the JRE is version 1.6 or higher, proceed with the MPC installation.

If the version is prior to 1.6, go to the Java website at
http://java.sun.com/products/ to download the latest Runtime
Environment.

Chapter 3: Multi-Platform Client and Raritan Remote Client

52

To install MPC for Linux:

You must have Administrative privileges to install MPC.

1. Download the MPC-installer.jar file or copy it from a known location.

2. Open a terminal dialog and open the directory where the installer is

saved.

3. Type java -jar MPC-installer.jar and press Enter to run the installer.

4. After the initial page loads, click Next.

5. Use the Browse function to select a directory to install MPC if the

directory is different from the default path displayed in the "Select the
installation path" field.

6. Click Next to open the Shortcut dialog.

7. On the Shortcut dialog:

 Choose a shortcut location from the "Select a Program Group for

the Shortcuts:" field.

 Select either "current user" or "all users" to define who should

have access to the shortcut.

 Check the "Create shortcut on the desktop" checkbox if you want

the shortcut to appear on the desktop.

8. When finished, click Next.

Note: Once MPC is installed successfully, a shortcut will be available
on the desktop. However, for Linux users, you will need to log off of
and then back into your session before the shortcut will be visible on
the desktop.

Once the installation is complete, the final page indicates where you
will find an uninstaller program and provides you with the option to
generate an automatic installation script.

9. Click Done to close the Installation dialog.

To open MPC in Linux:

1. Open a terminal window and change directories to the directory

where you installed MPC (default location: /usr/local/Raritan/Raritan
MPC/version number).

2. Type ./start.sh and press Enter to open MPC.

3. Double-click the desired device to establish a connection, type your

user name and password, and click OK to log on.

Solaris™

To check the JRE version for Sun Solaris:

1. Launch a terminal window on the Sun Solaris desktop.

Chapter 3: Multi-Platform Client and Raritan Remote Client

53

2. Type java-version in the command line and press Enter. The

currently-installed version of Java Runtime Environment (JRE)
appears.

If your path variable is not set to where the java binaries have been
installed, you may not be able to see the JRE version.

a. To set your path and assuming JRE 1.6 is installed in

/usr/local/java, you must set your PATH variable.

b. To set path for bash shell, export

PATH=$PATH:/usr/local/java/j2re1.6/bin.

c. To set path for tcsh or csh, set PATH = ($PATH

/usr/local/java/j2re1.6/bin).

3. These commands can be typed at the terminal each time you login.

Alternatively, you can add it to your .bashrc for bash shell, .cshrc for
csh, or tcsh so that each time you login the PATH is already set. See
your shell documentation if you encounter problems.

4. If the JRE is version 1.6 or higher, proceed with the MPC installation.

If the version is prior to JRE 1.6, go to the Sun website at
http://java.sun.com/products/ to download the latest Runtime
Environment.

To install MPC for Sun Solaris:

You must have administrative privileges to install MPC.

1. Download the MPC-installer.jar file or copy it from a known location.

2. Open a terminal window and navigate to the directory where the

installer is saved.

3. Type java -jar MPC-installer.jar and press Enter to run the installer.

4. After the initial page loads, click Next.

5. Use the Browse function to navigate to the directory you want to

install MPC or select the default directory displayed in the "Select the
installation path" field.

6. Click Next.

7. When installation is complete, click Next.

8. Click Next again.

Once the installation is complete, the final dialog will indicate where
you will find an uninstaller program and provides the option to
generate an automatic installation script.

9. Click Done to close the Installation dialog.

Chapter 3: Multi-Platform Client and Raritan Remote Client

54

To open MPC in Sun Solaris:

1. Open a terminal window and navigate to the directory where you

installed MPC (the default location is /usr/local/Raritan/Raritan
MPC/version number).

2. Type ./start.sh and press Enter to open MPC.

3. Double-click the desired device to establish a connection, type your

user name and password, and click OK to log on.

Macintosh®

To check JRE on a Mac®:

1. Launch a terminal window on the Macintosh desktop.

2. Type java-version in the command line and press Enter. The

currently-installed version of the Java Runtime Environment (JRE) is
displayed.

3. If the JRE is version 1.6 or higher, proceed with the MPC installation.

If the version is prior to 1.6, go to the Apple website to download the
latest Runtime Environment.

To install MPC on a Mac:

You must have administrative privileges to install MPC.

1. Download the MPC-installer.jar file or copy it from a known location.

2. Open a Finder window and locate the installer.

3. Double click the MPC-installer.jar file to run the installer.

4. After the initial dialog appears, click Next.

5. Use the Browse function to select a directory to install MPC if the

directory is different from the default path displayed in the "Select the
installation path" field.

6. When installation is complete, click Next.

Once the installation is complete, the final dialog indicates where you
will find an uninstaller program and provides you with the option to
generate an automatic installation script.

7. Click Done to close the Installation dialog.

To open MPC on a Mac:

1. Open a Finder window and navigate to the directory where you

installed MPC (the default location is /Applications/Raritan/Raritan
MPC/version number).

2. Double-click the desired device to establish a connection, type your

user name and password, and click OK to log on.

Chapter 3: Multi-Platform Client and Raritan Remote Client

55

Connecting to a Server via MPC when Alternate RADIUS Authentication is
Enabled on the KX II-101

When Alternate RADIUS Authentication is enabled, you are
authenticated exclusively against a remote authentication database. If
the remote authentication database is inaccessible, you will be
authenticated against a local authentication database and will be
prompted to enter your local authentication username and password.

Remote authentication will be attempted again on the next login after you
have successfully logged on and then logged out, or after the third
unsuccessful attempt to log on with your local authentication database
credentials.

See User Authentication Process in the Dominion KX II-101 Help for
details about the Alternate RADIUS Authentication process and how it
works with MPC.

Launching MPC from a Web Browser

Important: Regardless of the browser you use, you must allow pop­ups from the Dominion device's IP address in order to open MPC.

Important: Only Mac 10.5 and 10.6 with an Intel® processor can run
JRE 1.6 and, therefore, be used as a client. Mac 10.5.8 does not
support MPC as a standalone client.

1. To open MPC from a client running any supported browser, type

http://IP-ADDRESS/mpc into the address line, where IP-ADDRESS
is the IP address of your Raritan device. MPC opens in a new
window.

Note: The Alt+Tab command toggles between windows only on the
local system.

When MPC opens, the Raritan devices that were automatically
detected and which are found on your subnet are displayed in the
Navigator in tree format.

2. If your device is not listed by name in the navigator, add it manually:

a. Choose Connection > New Profile. The Add Connection window

opens.

b. In the Add Connection window, type a device Description,

specify a Connection Type, add the device IP address, and click
OK. These specifications can be edited later.

3. In the Navigator panel on the left of the page, double-click the icon

that corresponds to your Raritan device to connect to it.

Chapter 3: Multi-Platform Client and Raritan Remote Client

56

Note: Depending on your browser and browser security settings, you
may see various security and certificate check and warning messages. It
is necessary to accept the options in order to open MPC.

Note: If you are using Firefox 3.0.3, you may experience problems
launching the application. If this occurs, clear the browser cache and
launch the application again.

RRC Requirements and Installation Instructions

Important: RRC works only with Microsoft® Internet Explorer®. If you
are using a different web browser, MPC loads automatically.

Most users access RRC via Internet Explorer, while other users,
particularly those operating over a modem connection, access RRC
standalone. Both options are detailed in this guide.

Note: Modem use is not supported with Raritan's Dominion KX101.

RRC Minimum System Requirements

The minimum system requirements for the Raritan Remote Client are:

 CPU Speed: 1.0 GHz
 RAM: 512 Mbytes

Note: Running the client software on system configurations below either
of these specifications may impact performance and result in errors.

Installing and Opening Standalone RRC

Note: This step is optional. Devices can be accessed from a remote PC
either by installing RRC software or by opening RRC via a web browser.
Accessing Devices via a web browser does not require any software
installation on a remote PC.

This section lists the steps required to invoke RRC using standalone
software, which may be useful for accessing devices via modem or if you
wish to close firewall access to ports 80 and/or 443.

1. Launch your web browser and go to Raritan's website

(http://www.raritan.com/).

2. Click Support in the top navigation bar and then click Firmware

Upgrades in the left navigation panel (or type the URL
http://www.raritan.com/support/firmwareupgrades).

3. Scroll down the page until you see the appropriate product name and

click on it.

Chapter 3: Multi-Platform Client and Raritan Remote Client

57

4. Locate the version of the standalone RRC client you are using. The

entry for the standalone RRC client is a .zip file which contains the
release notes and the installer for standalone RRC. Check the
release notes for the latest information.

5. Download the .zip file or simply click on the .zip file entry.

6. Double-click on the installer executable in the .zip file and follow the

instructions in the InstallShield Wizard to complete the RRC
installation. Be sure to check the release notes for the latest
information and any release specific instructions.

Depending upon the configuration of your PC, the RRC installation
program may also automatically install DirectX® and Microsoft®
Foundation Class libraries (if they are required). If they are installed,
you are asked to restart your PC after the installation.

7. A Raritan Remote Client icon appears on your desktop after the

installation is complete. Click on this icon to open the standalone
RRC application.

The standalone application can be uninstalled using the Add or
Remove Programs function in the Windows® Control Panel.

Note: You must uninstall the application before installing a new version
of standalone RRC.

Chapter 3: Multi-Platform Client and Raritan Remote Client

58

Opening RRC from a Web Browser

Your device features web browser-access capabilities and can provide a
connection from any Windows-based, remote PC running Microsoft®
Internet Explorer® 6.0/7.0.

Security Settings

To access a device via the web, your web browser must be configured
appropriately on the Internet Explorer security settings tab. Specifically:

 "Download Signed ActiveX controls" should be set to either Enable

or Prompt.

 "Run ActiveX controls and plug-ins" should be set to either Enable or

Prompt.

Consult your Microsoft Internet Explorer documentation for additional
information.

Note: Microsoft Windows 2000®, Windows XP®, and Windows 2003®
operating systems restrict certain types of users from downloading and
running ActiveX® controls and plug-ins regardless of the settings in
Internet Explorer. Consult your Microsoft Windows documentation for
more information.

To open RRC:

1. Ensure that your browser security settings are configured

appropriately and type the IP address assigned to your device in the
URL field of your web browser.

Note: Devices ship with the default IP address of 192.168.0.192.
Note that an IP address must be used. Host names are not currently
supported.

Chapter 3: Multi-Platform Client and Raritan Remote Client

59

You are redirected to an HTTPS (128-bit) secure web page so you
can open RRC.

2. Depending on your browser and its security configuration, you may

see any or all of the following dialogs asking you to confirm you want
to access and open an externally-provided application. Click Yes to
accept these prompts.

Chapter 3: Multi-Platform Client and Raritan Remote Client

60

Removing RRC from the Browser Cache

 To remove RRC from your browser cache for any reason, follow the

standard procedure for your web browser software.

To remove cached files in Internet Explorer v6.0:

1. If you have used RRC recently, exit all instances of Internet Explorer

and restart Internet Explorer.

2. On the Internet Explorer Tools menu, choose Internet Options.

3. When the Internet Options dialog appears, click on the General

Settings tab and then click Delete Files.

4. Click on the Settings tab and then click View Objects.

5. Internet Explorer displays a list of cached objects. Select any entries

named “TeleControl Class,” “Raritan Console,” or “Power Board” and

delete them.

Chapter 3: Multi-Platform Client and Raritan Remote Client

61

Operation

Navigator

The navigator provides a tree view of every known Raritan device. From
this panel, access all Raritan networked devices for which a connection
profile exists and/or all Raritan devices automatically identified on the
network.

Note: Automatic Raritan device identification uses the UDP protocol and
typically identifies all Raritan devices on your subnet. Network
administrators rarely allow UDP broadcasts to function outside of a
subnet. Automatic Raritan device identification finds only those Raritan
devices that are configured to use the default TCP Port (5000) or another
broadcast port, which is defined on the Advanced tab of the Options
dialog (choose Tools > Options to access the Options dialog).

Device Naming in the MPC Navigator

In MPC, devices are named according to the Manager Name field on the
Manager's Network Configuration page. Dominion devices are named
according to the Device Name field on the Dominion Console Network
Settings page.

Chapter 3: Multi-Platform Client and Raritan Remote Client

62

Devices in the RRC Navigator

Icon

Description

Profiled - A network connection profile exists for this
device.

Modem Profile - A modem connection profile exists for
this device.

Not Profiled - The device was found on the network but
a connection profile does not exist for it.

In RRC, profiled devices are listed in the Navigator according to the data
in the Description field of the device's profile. Automatically-identified
devices are identified according to the name assigned to them in that
device's network configuration setting.

Device Ports in the Navigator

For each device to which you are connected, you are able to expand the
tree associated with it to see each device port to which you have access.
Ports with a green icon indicate that you are connected to that port. The
port that is bolded in the Navigator indicates that it is the port currently
displayed (active) in the remote desktop area of the application.

If no name is assigned to a port, by default it is listed in the Navigator as
'Unnamed' for Generation 1 devices and, for the KX II, as
Dominion_KX2_PortN (N = port number).

Depending on the maximum number of KVM sessions the device can
handle at once, if all device ports to which you are connecting are
already occupied, an alert message appears and you must wait until one
of the ports is available in order to connect.

Navigator Icons

Each device in the Navigator is assigned two icons. One icon represents
the device's connection profile and the other icon represents its network
status. A connection profile is generally created by a user in order to
store personalized information about specific devices (see Connection

Profiles (on page 80) for additional information). The connection status

indicates the current status of the device.

Device Connection Profile Icons (Left Icon)

Device Network Status Icons (Right Icon)

Chapter 3: Multi-Platform Client and Raritan Remote Client

63

Icon

Description

Connected (green) - You are currently authenticated
and connected to this device.

Available (black) - This device is currently available on
the network but you are not currently connected to it.

Unavailable - A profile exists for this device but it is not
currently available on the network. (Note that all devices
to which you are not currently connected and that have
modem profiles use this icon.)

Port Connection Status Icons

Icon

Description

Connected

Available for connection.

Unavailable (either no device is connected or access is
blocked).

In use by another user (may be unavailable depending
on permissions).

Icon

Action

Description

Display/Hide
Navigator

Select Navigator in the View menu to
toggle between displaying and hiding
the Navigator.

Refresh Navigator

Updates the device status information
displayed in the Navigator.

Browse
Discovered
Devices

When enabled, Show Discovered

Devices displays devices that are “not
profiled” but have been found on the

network. This option can also be
enabled by choosing View > Show >
Discovered Devices.

Note: The Browse Discovered Devices

For each server port listed in the Navigator, the following icons can be
associated with it depending on its status:

Customizing the Navigator

Use specific tools in the toolbar to customize some Navigator attributes:

Chapter 3: Multi-Platform Client and Raritan Remote Client

64

Icon

Action

Description

option is the only method of connecting
to a Raritan device configured to use a
DHCP IP address.

MPC Navigator Tabs

MPC tabs at the base of its Navigator pane. These tabs allow you to
change how you display devices. Click the View By Name tab to sort the
list alphabetically by name, click the View By IP tab to sort the list
numerically by IP address, or click on the View by Host Name tab to sort
the list alphabetically by display name.

These tabs are available only in the MPC interface.

Chapter 3: Multi-Platform Client and Raritan Remote Client

65

Navigator Display and Sort Options

To better organize your view of all ports, use the Show and Sort options
in the View menu. Note that you do not need an open connection to a
target to show and sort targets in the Navigation panel.

Showing Ports

 Discovered Devices - Shows or hides discovered devices from the

Navigator view. You will not see broadcast messages when this
option is disabled (not selected).

 Unassigned Channels - Shows or hides channels with no assigned

targets. Note that the default for Generation 1 (G1) devices is to
show unassigned channels (option is enabled), whereas the default
is to hide unassigned channels (option is disabled) for Generation 2
(G2) devices.

 Tools - Shows or hides the Admin and Diagnostic ports.
 Groups - Shows all port groups.

Note: These settings are saved from session to session.

Sorting Ports

Use the Sort options on the View menu to organize port information. You
are able to sort ports by channel number, channel name, or channel
status.

 Channel Number - When sorted by channel (View > Sort > Channel),

ports are listed numerically.

Chapter 3: Multi-Platform Client and Raritan Remote Client

66

 Name - When sorted by name (View > Sort > Name), port names are

sorted alphanumerically within each group.

 Status - When sorted by status (View > Sort > Status), ports are

sorted in the following order:

 Active Channels
 Busy Channels
 Available Devices
 Unavailable Devices

Note: Sorting ports does not apply to KX II-101.

Chapter 3: Multi-Platform Client and Raritan Remote Client

67

Set Scan Group

a port scanning feature that searches for selected targets and displays
them in a slide show view, allowing you to monitor up to 32 targets at
one time. You can connect to targets or focus on a specific target as
needed. Scans can include standard targets, blade servers, tiered
Dominion devices, and KVM switch ports.

Note: Scanning for tiered devices is not supported by the Multi-Platform
Client (MPC).

When you start a scan, the Port Scan window opens. As each target is
found, it is displayed as a thumbnail in a slide show. The slide show
scrolls through the target thumbnails based on the default interval of 10
seconds or according to the interval you specify. As the scan scrolls
through the targets, the target that is the focus of the slide show displays
in the center of the page. See Scan Settings (on page 31)

You can change the time between the slide show thumbnail rotation, the
thumbnail focus interval, and the page display settings from the Scan
Settings tab of the Virtual KVM Client (VKC), Active KVM Client (AKC)
and Multi-Platform Client (MPC) Tools > Options dialog. See Scan

Settings (on page 31).

The name of the target is displayed below its thumbnail and in the task
bar at the bottom of the window. If a target is busy, a blank screen is
displayed instead of the target server access page.

The status of each target is indicated by green, yellow and red lights that
are displayed below the target thumbnail and, as the target is the focus
of the rotation, in the task bar. The status lights indicate the following:

 Green - the target is up/idle or up/connected
 Yellow - the target is down but connected
 Red - the target is down/idle, busy, or otherwise not accessible

Note: This feature is only supported by the KX II.

To begin a scan in MPC:

1. Click on Set Scan at the bottom of the Navigator.

2. From the list of targets in the Navigator, use Ctrl + click select each

target you want to include in the scan, or use Shift + click to select a
range of targets.

3. Once you've selected all the targets to include in the scan, right click

next to the selected targets and select Start Scan. The targets
detected in the scan are displayed.

Chapter 3: Multi-Platform Client and Raritan Remote Client

68

See Using Scan Options (on page 69) for information on the options
available to you while scanning targets.

Chapter 3: Multi-Platform Client and Raritan Remote Client

69

Using Scan Options

Following are options available to you while scanning targets. With the
exception of the Expand/Collapse icon, all of these options are selected
from the Options menu in the upper left of the Port Scan viewer. The
options will return to their defaults when you close the window.

Hide or View Thumbnails

 Use the Expand/Collapse icon at the upper left of the window to

hide or view thumbnails. Expanded is the default view.

Pause the Thumbnail Slide Show

 Pause thumbnails from rotating between one target and the next by

selecting Options > Pause. Rotating thumbnails is the default setting.

Resume the Thumbnail Slide Show

 Resume the thumbnail rotation by selecting Options > Resume.

Size the Thumbnails in the Port Scan Viewer

 Enlarge the size of the thumbnails by selecting Options > Size >

360x240.

 Minimize the size of the thumbnails by selection Options > Size >

160x120. This is the default thumbnail size.

Change the Orientation of the Port Scan Viewer

 View thumbnails along the bottom of the Port Scan viewer by

selecting Options > Split Orientation > Horizontal.

 View thumbnails along the right of the Port Scan viewer by selecting

Options > Split Orientation > Vertical. This is the default view.

Toolbars

Standard Toolbar

The Standard toolbar provides one-click access to the most frequently­used commands.

To display the Standard toolbar:

 Choose View > Standard Toolbar.

Following is a list of the buttons in the standard toolbar as well as a
description of the action performed once the buttons are selected.
Additionally, if there are menu options or shortcut menu options that
perform the same task, they are listed, too.

Chapter 3: Multi-Platform Client and Raritan Remote Client

70

Button

Button
name

Description

New Profile

Creates a new Navigator entry for a
Raritan device.

Same result as choosing Connection >
New Profile in the menu.

Connection
Properties

Opens the Modify Connection Properties
dialog to manually adjust bandwidth
options (such as connection speed, color
depth, and so forth).

Same as choosing Connection >
Properties or choosing Connection
Properties on the shortcut menu, which is
opened by pressing Ctrl+Left Alt+M.

Video
Settings

Opens the Video Settings dialog, allowing
you to manually adjust video conversion
parameters.

Same as choosing Video > Video Settings
or choosing Video Settings.

Color
Calibration

Adjusts color settings to reduce excess
color noise.

Same as choosing Video > Color Calibrate.

Target
Screenshot

Click to take a screenshot of the target
server and save it to a file of your
choosing.

Audio

Click to connect to a digital audio device.

Note: This feature is only available in KX II

2.4.0 or higher.

Synchronize
Mouse

In dual-mouse mode, forces realignment of
the target server mouse pointer with the
mouse pointer.

Same as choosing Mouse > Synchronize
Mouse or choosing Synchronize Mouse on
the shortcut menu, which is opened by
pressing Ctrl+Left Alt+M.

Refresh
Screen

Forces a refresh of the video screen.
Same as choosing Video > Refresh Screen

or choosing Refresh Screen on the
shortcut menu, which is opened by
pressing Ctrl+Left Alt+M.

Chapter 3: Multi-Platform Client and Raritan Remote Client

71

Button

Button
name

Description

Auto-sense
Video
Settings

Forces a refresh of the video settings
(resolution, refresh rate).

Same as choosing Video > Video Settings
or choosing Video Settings on the shortcut
menu, which is opened by pressing
Ctrl+Left Alt+M.

Enter On­Screen
Menu

Not applicable for the device. Used by the
application with other Raritan products.

Same as choosing Keyboard > Enter On­Screen Menu.

Note: This function is not available on the
KSX II.

Exit On­Screen
Menu

Not applicable for IP-Reach or Dominion.
Used by the application with other Raritan
products.

Alternatively, select Esc on the keyboard.
Same as choosing Keyboard > Exit On­Screen Menu.

Note: This function is not available on the
KSX II.

Smart Card

Opens a dialog that allows you to select
from a list of mounted smart card readers.

Send
Ctrl+Alt+Del

Sends a Ctrl+Alt+Del hot key combination
to the target server.

Same as choosing Keyboard > Send
Ctrl+Alt+Del.

Single
Cursor
Mode

Starts Single Cursor mode in which the
local mouse pointer no longer appears
onscreen.

Same as choosing Mouse > Single Cursor
Mode. Press Ctrl+Alt+X to exit this mode.
Alternatively, choose Single/Double Cursor
from the shortcut menu, which is opened
by pressing Ctrl+Left Alt+M.

Full Screen
Mode

Maximizes the screen real estate to view
the target server desktop.

Same as choosing View > Target Screen
Resolution (in MPC) or Full Screen (in
RRC). Alternatively, press Ctrl+Left Alt+M

Chapter 3: Multi-Platform Client and Raritan Remote Client

72

Button

Button
name

Description

to open the shortcut menu and then
choose Full/Normal Screen or press the F
key on your keyboard.

Scaling

Increases or reduces the target video size
so you can view the entire contents of the
target server window without using the
scroll bar.

Show/Hide
Navigator

Toggles the Navigator panel between
visible and hidden.

Same as choosing View > Navigator.

Refresh
Navigator

Forces a refresh of the data displayed in
the Navigator.

Show/Hide
Browse All
Devices

Toggles between displaying and not
displaying Raritan devices in the Navigator
that are automatically identified on the
network and that do not have
preconfigured profiles associated with
them.

About

Displays the application version
information.

Same as choosing Help in the menu bar.

Chapter 3: Multi-Platform Client and Raritan Remote Client

73

MPC Connected Server(s) Toolbar

The Connected Server(s) toolbar is comprised of a button for each
connected target server port, thus enabling quick access to connected
targets. When you connect to a port, a button corresponding to that port
is added to the toolbar and labeled with the name of the port.
Conversely, when you disconnect from a port, the corresponding button
is removed from the toolbar.

Note: In Single Mouse mode, the Connected Server(s) Toolbar appears
on the target but cannot be accessed.

By default, the Connected Server(s) toolbar is enabled (visible). To
disable it, deselect Connected Server(s) Toolbar in the View menu.
Buttons corresponding to windows that do not support Full Screen mode
are not shown in the toolbar. For example, serial ports, generation one
(G1) admin ports, and G1 diagnostic ports are not displayed in the
toolbar in Full Screen mode.

While in Full Screen mode, view the Connected Server(s) toolbar by
hovering your mouse over the top of the screen. To use this feature, the
Connected Servers Toolbar option must be selected in the View menu.

To display the Connected Server(s) toolbar (when not already

visible):

 Choose View > Connected Server(s) Toolbar.

To view the window for a target server:

 Click the button that corresponds to the appropriate connected target

server you want to view. The window for the corresponding target
server is displayed and the button for the selected port is highlighted.
In Full Screen mode, note that this action is window swapping, not
video switching.

When you click a button that is already highlighted, the corresponding
window is minimized. If you click that button again, the window is brought
forward and maximized.

Status Bars

MPC Status Bar

The status bar displays session information about your connection to a
Raritan device. This information includes:

Chapter 3: Multi-Platform Client and Raritan Remote Client

74

Icon

Session
information

Description

Concurrent
connections
indicator

Indicates that multiple remote users are
currently connected to the same target
server on the device.

One icon indicates a single user is
connected, and two icons indicates two or
more users are connected.

Concurrent connection ability can be set
globally under PC share mode on the
Manager Security Settings page or set
per individual user in the Concurrent
Access Mode setting on the Manager
User Account Settings page. For the
device, concurrent connection ability can
be set using the PC Share Mode option in
the Security Settings page: PC-Share
permits concurrent access and Private
limits server access to one user at a time.

CAP,
NUM,
SCRL

Lock key
indicators

Indicates the status of the current target
KVM Server, in respect to the activation of
the Caps-Lock, Num-Lock, and Scroll­Lock keys. If these keys are enabled on
the target server being viewed, this
affirmative status is reflected on the status
bar.

Note: If a light is used on your keyboard to indicate the Scroll Lock, Num
Lock, and Caps Lock key is active, it may or may not be in sync with the
lock key indicator status displayed on the status bar. See the status bar
as your guide if this occurs.

RRC Status Bar

The status bar displays session information about your connection to a
Raritan device. This information includes:

Chapter 3: Multi-Platform Client and Raritan Remote Client

75

Diagram
key

Session
information

Description

Video sensing
status/path
indicator

Indicates when video sensing occurs
during connections to target KVM server
ports.

Bandwidth
usage indicator

Indicates how much of your total
available bandwidth is currently being
used. The connection speed setting
determines total available bandwidth.

This setting is defined on the
Compression tab of the Connection
Properties dialog, which is accessed by
choosing Connection > Properties, or
pressing Ctrl+Left Alt+ M and then
choosing Connection Properties.

Security
indicator

Indicates whether the current remote
connection is protected by encryption.
Encryption requirements are set during
configuration of your Raritan device.

When a device is configured for no
encryption or SSL authentication, the
Security Indicator is represented on the
status bar by an open lock icon.

When SSL authentication, data
encryption, or SSL encryption is applied,
the security indicator is represented on
the status bar by a closed lock.

Concurrent
connections
indicator

Indicates that multiple remote users are
currently connected to the same target
server on the device.

One icon indicates a single user is
connected, and two icons indicates two
or more users are connected.

Concurrent connection ability can be set
globally under PC share mode on the
Manager Security Settings page or set
per individual user in the Concurrent
Access Mode setting on the Manager
User Account Settings page. For the
device, concurrent connection ability can
be set using the PC Share Mode option
in the Security Settings page: PC-Share
permits concurrent access and Private
limits server access to one user at a
time.

Chapter 3: Multi-Platform Client and Raritan Remote Client

76

Diagram
key

Session
information

Description

Lock key
indicators

Indicates the status of the current target
KVM Server, in respect to the activation
of the Caps-Lock, Num-Lock, and Scroll­Lock keys. If these keys are enabled on
the target server being viewed, this
affirmative status is reflected on the
status bar.

Note: If a light is used on your keyboard to indicate the Scroll Lock, Num
Lock, and Caps Lock key is active, it may or may not be in sync with the
lock key indicator status displayed on the status bar. See the status bar
as your guide if this occurs.

Screen Modes

Besides a standard view, full screen view and a scaling option are
available. These options increase the remote desktop area and make
viewing the target video easier.

Chapter 3: Multi-Platform Client and Raritan Remote Client

77

MPC Full Screen Mode

Full Screen mode provides you with the ability to view the target server
desktop in Full Screen mode, which removes all toolbars from view.

Activate Full Screen mode once you are connected to a target by doing
one of the following:

 Click the Full Screen button in the toolbar and then click OK in

the confirmation message that appears.

 Choose View > Full Screen and then click OK in the confirmation

message that appears.

 Press Ctrl+Left Alt+M to open the shortcut menu. Next, press the F

key on your keyboard or use your mouse to choose Full/Normal
Screen. Click OK in the confirmation message that appears.

Hover your mouse at the top of the screen while in full screen mode to
display the MPC menus. To exit Full Screen mode, use the shortcut

menu or click the Close icon that appears at the top right of the page
when you hover your mouse along the top of the screen.

While in Full Screen mode, you are able to view the Connect Server
toolbar by hovering your mouse over the top of the screen. To use this
feature, the Connected Servers Toolbar option must be selected in the
View menu.

Additionally, while in Full Screen mode, your monitor's resolution may be
adjusted to match the resolution of the target server (provided your
graphics system supports it). If your graphics system does not support
the resolution of the target system, you are not able to activate Full
Screen mode and a message appears requesting that you change your
video resolutions first.

Tip: To view the video resolutions your system supports in a Windows®
operating system environment, access your computer's Control Panel
from the Windows Start menu, double-click Display, and click the
Settings tab.

Chapter 3: Multi-Platform Client and Raritan Remote Client

78

RRC Full Screen Mode

Full screen mode removes the surrounding RRC graphical interface and
your local desktop area, filling your screen with the video from the target
server. Your screen's resolution is adjusted to match the resolution of the
target server (provided your graphics system supports it). If your
graphics system does not support the resolution of the target system,
you are unable to activate full screen mode and a message appears
requesting that you change your video resolutions first.

Note: To view the video resolutions your system supports in a Windows®
operating system environment, access your computer's Control Panel
from the Windows Start menu, double-click on Display, and click on the
Settings tab.

Activate full screen mode in one of the following ways once you are
connected to a target:

 Click the Full Screen icon in the toolbar and then click OK in the

confirmation message that appears.

 Choose View > Full Screen and then click OK in the confirmation

message that appears.

 Press Ctrl+Left Alt+M to open the shortcut menu. Next, press the F

key on your keyboard or use your mouse to choose Full/Normal
Screen. Click OK in the confirmation message that appears.

Chapter 3: Multi-Platform Client and Raritan Remote Client

79

MPC Scaling

Scaling your target window size allows you to view the entire contents of
the target server window. This feature increases or reduces the size of
the target video to fit the window size and maintains the aspect ratio.
This allows you to see the entire target server desktop while in standard
view.

To activate Scaling, do one of the following:

 Choose View > Scale Video.
 Click the Scaling button on the toolbar.

 To exit this mode and return the target window to its previous size,

deselect Scale Video on the View menu or click the Scaling button
once again.

Note: Enabling Scale Video scales the complete target video image to fit
the remote desktop area as it grows or shrinks. Combine this setting with
target screen resolution for a 'full page' effect on targets with a higher
resolution than your desktop.

RRC Scaling

Scaling your target window size allows you to view the entire contents of
the target server window. This feature increases or reduces the size of
the target video to fit the window size and maintains the aspect ratio.
This allows you to see the entire target server desktop while in standard
view.

To activate Scale Video mode, do one of the following:

 Choose View > Scale.
 Click the Scaling button on the toolbar.

To exit this mode and return the target window to its previous size,
choose Scale on the View menu or click the Scaling button once again.

Note: Enabling Scale Video scales the complete target video image to fit
the remote desktop area as it grows or shrinks. Combine this setting with
target screen resolution for a full page effect on targets with a higher
resolution than your desktop.

Chapter 3: Multi-Platform Client and Raritan Remote Client

80

Auto-Scroll

The auto-scroll feature automatically scrolls the video display in the
direction of the cursor as the cursor approaches the edge of the display.
A thin border appears around the perimeter of the remote desktop area
to indicate the function is on. When enabled, if you see scroll bars and
then move the cursor onto the border, the page automatically scrolls in
the appropriate direction.

The scroll border is activated by selecting Show Scroll Borders in the
Options dialog, which is accessed by choosing Tools > Options.

Connection Profiles

Connection profiles store important information about your Raritan
device such as the IP address, custom TCP ports, preferred
compression settings, and custom security keys. A profile is required to
access devices outside your subnet and to access devices using a dial­up connection.

Through profiles, you can set up personalized connections. These
profiles are not shared among other users.

The information collected when creating a new connection profile differs
based on Generation 1 and Generation 2 devices.

Tip: If your Raritan device is configured to use a custom TCP port or a
group security key, first create a connection profile to access the device.

Managing Profiles in KX, KSX and KX-101 G1 Devices

Creating, Modifying and Deleting Profiles in MPC

To create a profile:

1. There are two ways to create a profile:

 For automatically discovered devices, right-click the device name

in the Navigator and choose Add Profile from the shortcut menu.

 For other devices, choose Connection > New Profile.

The Add Connection dialog appears. Options are organized into
three tabs.

Note: The Compression and Security tabs are not available for
Generation 2 devices.

Connect Tab

2. On the Connect tab, type a meaningful description of the device in

the Description field. This description identifies the Raritan device in
the Navigator.

Chapter 3: Multi-Platform Client and Raritan Remote Client

81

3. From the Product drop-down, choose the Raritan product you are

using.

TCP/IP Connections

4. Select the type of connection from the Connection Type drop-down.

a. If TCP/IP Connection is selected for a LAN/WAN connection,

complete the information in the "Find Raritan device By" section:

 Type the IP address assigned to your Raritan device.
 Type the name assigned to your Raritan device during initial

setup.

 Type the Domain Name Server (DNS) name in the Host Name

field. Use this option if you use a DNS server to resolve a DNS
name to the IP address assigned to your Raritan device.

Dial-up Connections

a. Select Dial Up Connection from the Connection Type drop-down

for a direct analog modem connection to the Raritan device.
Type the parameters that should be used to establish a
connection.

 Enter the phone number for the dial-up connection. Remember to

include any additional codes that should be dialed to establish a
connection, such as country codes, area codes, or outside line
access codes.

 Select the modem (as configured in Windows) from the drop-

down list that will be used to dial and connect to your Raritan
device.

Chapter 3: Multi-Platform Client and Raritan Remote Client

82

Note: For security reasons, you must use the MPC standalone client
if you require modem access. Further, one modem on a client PC
can be used for only one device connection.

Note: Dial-up is not support in KX II-101.

5. Select the Use Default Port Number checkbox to use the default port

number (5000). For TCP Ports, devices are automatically configured
to use TCP Port 5000 when communicating with the client.

If you do not want to use the default port number, deselect the
checkbox and type the port number in the Port Number field.

Compression Tab

6. Set the Connection Speed.

Use this setting to manually adjust the connection speed to
accommodate bandwidth constraints. Devices can automatically
detect available bandwidth and not limit bandwidth use. However,
you can also adjust this usage according to your needs. Depending
on the Raritan device in use, different options may be available:

 Auto Detect
 1G Ethernet
 100mb Ethernet
 10mb Ethernet
 1.5mb (Max DSL/T1)
 1mb (Fast DSL/T1)
 512 kb (Medium DSL/T1)
 384 kb (Slow DSL/T1)

Chapter 3: Multi-Platform Client and Raritan Remote Client

83

 256 kb (Cable)
 128 kb (Dual ISDN)
 56 kb (ISP Modem)
 33 kb (Fast Modem)
 24 kb (Slow Modem)

Note: Raritan recommends that if you are connecting to the device
via modem, you set the connection speed to 33kb.

7. Set the Color Depth.

Devices can dynamically adapt the color depth transmitted to remote
users in order to maximize usability in all bandwidths. Select from
among the options in the drop-down list. Depending on the Raritan
device in use, different options may be available:

 15-bit RGB Color
 8-bit RGB Color
 4-bit Color
 4-bit Gray
 3-bit Gray
 2-bit Gray
 Black and White

Important: For most administrative tasks (server monitoring,
reconfiguring, and so forth), administrators do not require the full 24­bit or 32-bit color spectrum made available by most video graphics
cards. Attempting to transmit such high color depths wastes network
bandwidth.

Note: If you are connecting to the device via a modem, Raritan
recommends setting the color depth to 4-bit gray.

8. Select Progressive Update to increase the usability in constrained

bandwidth environments. When Progressive Update is enabled, the
device initially sends an image of the remote desktop at lower color
depths. Higher color depth images are provided as the bandwidth
allows.

Note: When Color Depth is set to Auto Select Color (default),
Progressive Update is automatic. The device will enable/disable
Progressive Update as required, disabling it for fast connections and
enabling it for slow connections.

Chapter 3: Multi-Platform Client and Raritan Remote Client

84

9. Selecting the Internet Flow Control checkbox ensures that packets

transmitted by the device are received and reconstructed by the
client application in the correct order. This is useful when using a
device over an unpredictable public WAN (particularly in international
scenarios).

10. Use the slider to select the desired level of video Smoothing (15-bit

mode only). The level determines how aggressively to blend page
regions with small color variation into a single, smooth color.
Smoothing improves the appearance of the target video by reducing
the video noise that is displayed.

11. Select "Frames per second". This setting instructs MPC on how often

to redraw the video display of the target. This only affects the client
display behavior and has no bearing on the data rate of the video
being sent to the client. Setting this option higher makes the video
appear smoother but also requires more processing power.

Security Tab

12. Enter the private security key in the Private Key field if your device is

configured to use a private security key. Entering a security key
allows you to gain the authorization required to initiate a connection
to that device.

13. Retype the private security key in the Confirm Private Key field to

ensure no typographical errors were made.

Chapter 3: Multi-Platform Client and Raritan Remote Client

85

14. Click OK to create the connection profile.

To modify a profile:

1. Select the device in the Navigator panel and right-click it.

2. Choose Modify Profile. The Modify Connection dialog appears.

3. Update the fields as appropriate.

4. Click OK.

To delete a profile:

1. Select the device with a profile in the Navigator and right-click it.

2. Choose Delete Profile.

3. When prompted to confirm the deletion, click Yes to delete the profile

for this device or click No to return to the application without deleting.

Note: The device only supports modem connections to the Administrative
functions in MPC. Port functions are not supported via modem.

Creating, Modifying and Deleting Profiles in RRC

To create a profile:

1. There are two ways to create a profile:

 For automatically discovered devices, right-click the device name

in the Navigator and choose Add Profile from the shortcut menu.

 For other devices, choose Connection > New Profile.

The Add Connection dialog appears. Options are organized into
three tabs.

Chapter 3: Multi-Platform Client and Raritan Remote Client

86

Note: The Compression and Security tabs are not available for
Generation 2 devices.

Connect Tab

2. On the Connect tab, type a meaningful description of the device in

the Description field. This description identifies the Raritan device in
the Navigator.

3. Select Dial Up Connection from the Connection Type drop-down for

a direct analog modem connection to the Raritan device. Type the
parameters that MPC or RRC should use to establish a connection.
Dial up connection does not apply to Generation 2 (G2) or KX101.

 Enter the phone number for the dial-up connection. Remember to

include any additional codes that should be dialed to establish a
connection, such as country codes, area codes, or outside line
access codes.

 Select the modem (as configured in Windows) from the drop-

down list that will be used to dial and connect to your Raritan
device.

Note: For security reasons, you must use the MPC standalone client
if you require modem access. Further, one modem on a client PC
can be used for only one device connection.

Chapter 3: Multi-Platform Client and Raritan Remote Client

87

4. Select the Use Default Port Number checkbox to use the default port

number (5000). For TCP Ports, devices are automatically configured
to use TCP Port 5000 when communicating with the client.

If you do not want to use the default port number, deselect the
checkbox and type the port number in the Port Number field.

Compression Tab

5. Set the Connection Speed.

Use this setting to manually adjust the connection speed to
accommodate bandwidth constraints. Devices can automatically
detect available bandwidth and not limit bandwidth use. However,
you can also adjust this usage according to your needs. Depending
on the Raritan device in use, different options may be available:

 Auto Detect
 1G Ethernet
 100mb Ethernet
 10mb Ethernet
 1.5mb (Max DSL/T1)
 1mb (Fast DSL/T1)
 512 kb (Medium DSL/T1)
 384 kb (Slow DSL/T1)
 256 kb (Cable)
 128 kb (Dual ISDN)
 56 kb (ISP Modem)
 33 kb (Fast Modem)
 24 kb (Slow Modem)

6. Set the Color Depth.

Devices can dynamically adapt the color depth transmitted to remote
users in order to maximize usability in all bandwidths. Select from
among the options in the drop-down list. Depending on the Raritan
device in use, different options may be available:

 15-bit RGB Color
 8-bit RGB Color
 4-bit Color
 4-bit Gray
 3-bit Gray
 2-bit Gray
 Black and White

Chapter 3: Multi-Platform Client and Raritan Remote Client

88

Important: For most administrative tasks (server monitoring,
reconfiguring, and so forth), administrators do not require the full 24­bit or 32-bit color spectrum made available by most video graphics
cards. Attempting to transmit such high color depths wastes network
bandwidth.

7. Select Progressive Update to increase the usability in constrained

bandwidth environments. When Progressive Update is enabled, the
device initially sends an image of the remote desktop at lower color
depths. Higher color depth images are provided as the bandwidth
allows.

Note: When Color Depth is set to Auto Select Color (default),
Progressive Update is automatic. The device will enable/disable
Progressive Update as required, disabling it for fast connections and
enabling it for slow connections.

8. Selecting the Internet Flow Control checkbox ensures that packets

transmitted by the device are received and reconstructed by the
client application in the correct order. This is useful when using a
device over an unpredictable public WAN (particularly in international
scenarios).

Chapter 3: Multi-Platform Client and Raritan Remote Client

89

9. Use the slider to select the desired level of video Smoothing (15-bit

mode only). The level determines how aggressively to blend page
regions with small color variation into a single, smooth color.
Smoothing improves the appearance of the target video by reducing
the video noise that is displayed.

Security Tab

10. Enter the private security key in the Private Key field if your device is

configured to use a private security key. Entering a security key
allows you to gain the authorization required to initiate a connection
to that device.

11. Retype the private security key in the Confirm Private Key field to

ensure no typographical errors were made.

Chapter 3: Multi-Platform Client and Raritan Remote Client

90

12. Click OK to create the connection profile.

Managing Profiles in KX, KSX and KX-101 G2 Devices

Creating, Modifying and Deleting Profiles in MPC - Generation 2 Devices

To create a profile:

1. There are two ways to create a profile:

 For automatically discovered devices, right-click the device name

in the Navigator and choose Add Profile from the shortcut menu.

 For other devices, choose Connection > New Profile.

The Add Connection dialog appears. Options are organized into
three tabs.

Note: The Compression and Security tabs are not available for
Generation 2 devices.

2. On the Connect tab, type a meaningful description of the device in

the Description field. This description identifies the Raritan device in
the Navigator.

3. From the Product drop-down, choose the Raritan product you are

using.

4. Select the type of connection from the Connection Type drop-down.

Chapter 3: Multi-Platform Client and Raritan Remote Client

91

TCP/IP Connections

a. If TCP/IP Connection is selected for a LAN/WAN connection,

complete the information in the "Find Raritan device By" section:

 Type the IP address assigned to your Raritan device.
 Type the name assigned to your Raritan device during initial

setup.

 Type the Domain Name Server (DNS) name in the Host Name

field. Use this option if you use a DNS server to resolve a DNS
name to the IP address assigned to your Raritan device.

a. To use the default port settings for the HTTPS port (port 443)

and the Discovery port (port 5000), leave their respective Use
Default checkboxes selected. As long as the Use Default
checkboxes are selected, the HTTPS Port and Discovery Port
fields are not active.

If you would like to change the default ports to other ports,
deselect the respective Use Default checkbox and enter the port
in the appropriate field. For example, to change the HTTPS port,
deselect its Use Default checkbox and enter the port number in
the HTTPS field.

Dial-up Connection

b. Select Dial Up Connection from the Connection Type drop-down

for a direct analog modem connection to the Raritan device.
Type the parameters that should be used to establish a
connection.

 Enter the phone number for the dial-up connection. Remember to

include any additional codes that should be dialed to establish a
connection, such as country codes, area codes, or outside line
access codes.

Chapter 3: Multi-Platform Client and Raritan Remote Client

92

 Select the modem (as configured in Windows) from the drop-

down list that will be used to dial and connect to your Raritan
device.

Note: For security reasons, you must use the MPC standalone client
if you require modem access. Further, one modem on a client PC
can be used for only one device connection.

a. To use the default port settings for the HTTPS port (port 443)

and the Discovery port (port 5000), leave their respective Use
Default checkboxes selected. As long as the Use Default
checkboxes are selected, the HTTPS Port and Discovery Port
fields are not active.

If you would like to change the default ports to other ports,
deselect the respective Use Default checkbox and enter the port
in the appropriate field. For example, to change the HTTPS port,
deselect its Use Default checkbox and enter the port number in
the HTTPS field.

To modify a profile:

1. Select the device in the Navigator panel and right-click it.

2. Choose Modify Profile. The Modify Connection dialog appears.

3. Update the fields as appropriate.

4. Click OK.

To delete a profile:

1. Select the device with a profile in the Navigator and right-click it.

2. Choose Delete Profile.

Chapter 3: Multi-Platform Client and Raritan Remote Client

93

3. When prompted to confirm the deletion, click Yes to delete the profile

for this device or click No to return to the application without deleting.

Establishing a New Connection

Note: Depending on your version of the JRE™, you might receive a
certificate message when using the standalone application to access a
Dominion device. You have to accept the certificate in order to establish
the connection.

To connect to a device, double-click the device's icon in the Navigator,
then type your user name and password to connect. Right-click the
device name in the Navigator and select New Connection.

Note: The default device login user name is admin and the default
password is raritan. You have administrative privileges using these login
credentials.

If you do not see an icon for your device in the Navigator, follow the
instructions on creating new profiles, which is available in this section.

If you are having problems connecting to a device, be sure to check the
following:

 User name - Raritan usernames are not case-sensitive.
 Password - Raritan passwords are case-sensitive.
 TCP Port - If you have configured your device to use a non-default

TCP Port, this information must be entered into its connection profile.

 Firewall Settings - If you are accessing a device through a firewall,

that firewall must be configured to allow two-way communication on
TCP Port 5000 (or the custom TCP Port to which your device has
been configured).

 Security Key - If you have configured your device to require a group

security key, that key must be entered into the device's connection
profile.

Note: If you are running MPC on Internet Explorer® with both a Microsoft®
firewall and a non-Microsoft firewall utility installed, IE displays a
message telling you that MPC is already running (even if it is not in fact
running). To avoid this, deactivate one of your firewalls, or use a browser
such as Firefox®.

Connection Information

To obtain information about your connection:

 Choose Connection > Connection Info. The Connection Info dialog

appears.

Chapter 3: Multi-Platform Client and Raritan Remote Client

94

Generation 1 Devices

Connection
information

Description

Device name

The name of your device.

IP address

The IP address of your device.

Port

The KVM Communication TCP/IP Port used to
access the target device.

Data in/second

Data rate in.

Data out/second

Data rate out.

FPS

The frames per second transmitted for video.

Connect time

The duration of the connect time.

Horizontal resolution

The page resolution horizontally.

Vertical resolution

The page resolution vertically.

Refresh rate

How often the page is refreshed.

Protocol version

The RFB Protocol version.

Oldest supported
version

The oldest supported version of the client
software.

Hardware version

0 - Obsolete

Software version

3 (Software version)

Post code

Power on self-test error code. 0 = no error.

Network flags

A list of the various network options that have
been enabled or disabled such as DHCP, dial­in, autodetection, and so on.

Security flags

A list of the various security options that have
been enabled or disabled such as SSL
encryption, SNMP, and so on.

Options

RFP and TR support enabled or disabled.

Frame grabber info

0 - not used

KME info

KME version number for systems that use the
KME.

Serial Info

Serial devices

Video devices count

Number of video devices detected.

The following information is displayed about a current connection to
Generation 1 devices: