Users Guide

228 Using GUI Virtual Console
Why can't I use a keyboard or mouse
while installing a Microsoft operating
system remotely by using iDRAC6
Virtual Console?
When you remotely install a supported
Microsoft operating system on a system with
Virtual Console enabled in the BIOS, you
receive an EMS Connection Message that
requires that you select OK before you can
continue. You cannot use the mouse to
select OK remotely. You must either select
OK on the local system or restart the
remotely managed server, reinstall, and then
turn Virtual Console off in the BIOS.
This message is generated by Microsoft to
alert the user that Virtual Console is
enabled. To ensure that this message does
not appear, always turn off Virtual Console
in the BIOS before installing an operating
system remotely.
Why doesn’t the Num Lock indicator
on my management station reflect the
status of the Num Lock on the remote
server?
When accessed through iDRAC6, the Num
Lock indicator on the management station
does not necessarily coincide with the state
of the Num Lock on the remote server. The
state of the Num Lock is dependent on the
setting on the remote server when the
remote session is connected, regardless of
the state of the Num Lock on the
management station.
Why do multiple Session Viewer
windows appear when I establish a
Virtual Console session from the local
host?
You are configuring a Virtual Console
session from the local system. This is not
supported.
If I am running a Virtual Console
session and a local user accesses the
managed server, do I receive a warning
message?
No. If a local user accesses the system, you
both have control of the system.
How much bandwidth do I need to run
a Virtual Console session?
It is recommended that you use a 5 MB/sec
connection for good performance. A
1 MB/sec connection is required for minimal
performance.
Table 10-9. Using Virtual Console: Frequently Asked Questions
(continued)
Question Answer