User Manual

DRAFT COPY
NOMAD MXU Administration Manual
3:33 PM 02/12/99
DRAFT COPY
31
4.2.1 Operator Security
Problem: it is desirable to have different Nomad administration operators control separate groups of
NOMAD MXUs and it is required that each operator be restricted to just the assigned NOMAD MXUs.
Solution: After the initial configuration (.NOMAD MXU) file has been saved and named, set the NT file
permissions
of the configuration (.NOMAD MXU) file and the subdirectory that has the same name as the configuration
file.
Set the permissions to allow read/write access to only the assigned operator/logon and the NT
Administrator. Refer to the Files and Directories section for more information. Also check the NT help
facility on the NT Start Menu for "files:permissions".
4.2.2 Air Time Recharge Control
If the Auto Recharge On box is checked, the NOMAD MXU will automatically credit the amount of time
displayed under the "Recharge" heading for the group or phone to the "Nomad Time" account at the start
of each month. If the administrator removes the check from this box and sends the configuration, the
recharge will still be applied for one more month. If the Auto Recharge is turned on again, monthly
recharge will resume until the expiration of the Nomad program.
4.2.3 Maintaining Consistency with the NOMAD MXU
It is important to realize that the local configuration file and the actual airtime values on the remote
NOMAD MXU are only in agreement after the configuration has been read from the NOMAD MXU and
saved to the file by using the
Connect…Get Configuration from Unit and the File…Save menu commands.
The correct procedure for changing the NOMAD MXU configuration is to first upload the current values
from the NOMAD MXU, make the desired changes and then send the updated configuration to the
NOMAD MXU.
4.2.4 Creating a Field Unit
The .NOMAD MXU file must be present in order to communicate with a specific NOMAD MXU
installation. If more than one PC must be able to communicate with an NOMAD MXU, use the following
procedure AFTER initializing the NOMAD MXU by sending a first configuration:
1. Install the MCM software on the second PC (either the ADMIN or MONITOR versions, depending on
whether the second PC is allowed to change the configuration at the NOMAD MXU or only read it).
Refer to the
2. Copy the .NOMAD MXU file for the site to be administered from the original PC to the MCM
directory on the second PC.
3. Run the MCM program on the second PC and use the File..Open menu command to open the NOMAD
MXU file, and then save it. This will create the directories associated with the configuration file.
4. Make any connection changes that are required. For example, if the second PC is a laptop that will be
directly connected to the NOMAD MXU, change the NOMAD MXU Connection Data selection
from Modem to Cable.
The PC is now ready to make connections to the NOMAD MXU. Repeat the above process for each
NOMAD MXU that the new PC will need to administer.
4.3 Files and Directories