Rack-Mount RDMS
TM
Telemetry Receiver
114
Quasonix, Inc.
Client 2 (HCD-L2) clicks on Yes. Immediately the message window closes, Client 2’s RDMS Client window closes,
and the Mission Control Active Clients windows for Client 1 and 2 now show Client 2 as “Not Assigned” to a rack.
Figure 207: Example
– Mission Control Window for Both Clients
A close-up view of the Active Clients window, Figure 208, shows Client 2 (HCD-L2) is no longer assigned to the
RDMS_DEV rack, though his client desktop is still open. If Client 2 closes his RDMS client desktop application, his
entry will drop off of the Active Clients list.
Figure 208: Example
– Mission Control Window for Both Clients
4.2.6.1.2 Client Master
The Client Master, simply put, is the person with the password – a mission operator, supervisor, team leader,
security officer, etc. – some designated person. A Client Master has the ability to take control of any rack without
the permission of the client who owns the rack.
This option should only be used in an emergency
when an RDMS™ rack client is open and unattended – the
Client Master needs the rack and can’t get a response from anyone to release control in spite of repeated requests.
This is important because the action may result in an active, assigned client being immediately shutdown with no
warning—as if someone pulled a plug.
In the following example, ERIC-LAPTOP needs control of the rack and can’t get it for some reason. No one with
access to HCD-L2 is responding to requests for control.
Client ERIC-LAPTOP (who happens to be the Mission Operator with the password) clicks on the Enable Master
screen button, shown in Figure 209.