This appendix explains how to use the controller management software to manage controllers that are installed in other computers. This is referred to as remote management.

Installing the Remote Management Software

The controller management software (including FAST and the CLI) is installed when you use the controller installation software to perform a Full Install, Controller Hardware on Local System.

To remotely manage controllers from a system that does not have a local controller, use the installation software supplied with the controller to perform a Remote Management Software Install, No Controller Hardware.

The controller remote management software requires Windows NT 4.0 or above or Windows 2000.

Note: To remotely manage a controller that is installed on a NetWare^TM server, the NetWare server must have its network up and running, and the spxs.nlm module must be loaded. For more information, see the installation guide for your controller and the NetWare system documentation.

Security Requirements

The remote management software provides stringent security measures to prevent unauthorized management of controllers from the network. These security measures stipulate the following requirements for users who want to remotely manage controllers:

• The user's computer must be in the same domain as, or in a domain trusted by, the computer containing the controller. If this requirement is not met, the user receives the following error message:

   Remote access was denied. The domain is not trusted or 
  the user is not allowed to login to this domain.
  

• The user must log in using a Windows NT or Windows 2000 account that is recognized by the computer with the controller. If this requirement is not met, the user receives the following error message:

   Remote access was denied. The domain is not trusted or 
  the user is not allowed to login to this domain.
  

• The user must have permission to access the controller. When FAST is installed, the default access control list (ACL) for the controller allows access only to members of the Administrators group. A user must be in the Administrators group on the remote computer to access the controller over the network. Alternatively, the default ACL can be modified to grant access privilege to a particular user or group of users (see Modifying the ACL for a Controller). If a user who is not a member of the Administrators group or who has not been explicitly added to the controller's ACL attempts to access the controller, the user receives the following error message:

   Remote access was denied. The user has no permission to 
  access the specified device.
  

Limiting Access to a Controller

The controller management software supports two methods for protecting controllers from unauthorized access by users:

• Network-wide access protection
• Access control list (ACL) protection

Network-wide Access Protection

You can set read-write or read-only access to all controllers in the network by using the FAST Management Interfaces dialog box described in FAST Management Interfaces. The access level you specify is granted only to members of the Administrators group.

To allow individual users to access a particular controller, you must modify the access control list (ACL) for that controller.

Modifying the ACL for a Controller

You can restrict or extend access to a controller through its access control list (ACL), which is associated with the UserPermissions subkey in the Windows NT registry.

When the controller is installed, the UserPermissions subkey is created with a default ACL that includes the Administrators group. This should be a suitable default for using the controller. However, by modifying the controller's ACL, you can extend access privileges to individual users or users in groups other than Administrators.

The location of the UserPermissions key in the registry is as follows:

 HKEY_LOCAL_MACHINE
 \SOFTWARE
 \Adaptec
 \RAIDController
 \AFA
 \UserPermissions

You must use the Windows NT Registry Editor (regedt32) to modify the ACL for a controller, as follows:

1. At the command prompt, run regedt32.
2. In the Registry Editor, locate the UserPermissions subkey and double-click it.
3. Select Permissions from the Security menu.
4. In the Registry Key Permissions dialog box, select a user or group from the Name list to change the permissions for that user or group. Select an access type from the Type of Access list, and click OK.
5. To remove a user or group from the ACL, select the user or group from the Name list and click Remove.
6. To add a user or group to the ACL, click Add. In the Add Users and Groups dialog box, click Show Users to include individual user names in the Name list. Select one or more names from the list and click Add. Select an access type from the Type of Access list, and click OK.

Manuals
Back to Contents Page Remote Management: Dell™ Flexible Array Storage Tool User's Guide	Installing the Remote Management Software	Security Requirements	Limiting Access to a Controller