User manual HP STORAGEWORKS 2000S NAS NAS 2000S ADMINISTRATION GUIDE

[. . . ] Administration Guide hp StorageWorks NAS 2000s First Edition(September 2003) Part Number: 345650-001 This guide provides information on performing the administrative tasks necessary to manage the HP StorageWorks NAS 2000s server. Overview information as well as procedural instructions are included in this guide. © Copyright 2003 Hewlett-Packard Development Company, L. P. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. [. . . ] The domain controller is a repository of accounts and account access for the NAS 2000s. Client machines are also members of the domain, and users log on to the domain through their Windows clients. The domain controller also administers user accounts and appropriate access levels to resources that are a part of the domain. In a CIFS/SMB environment, when mapping a network drive or a client machine, a user sends a logon credential to the server. This credential includes the username, password, and if appropriate, domain information. Using the credential, the server authenticates and provides the corresponding access to the user. When a NAS 2000s is deployed into a workgroup environment, all user and group account access permissions to file resources are stored locally on the server. By contrast, when a NAS 2000s is deployed into a domain environment it uses the account database from the domain controller, with user and group accounts stored outside the server. The server integrates with the domain controller infrastructure. Note: The NAS 2000s cannot act as a domain controller for other servers on the network. If user and group account information is stored locally, those accounts may be used only to authenticate logons to the NAS 2000s, resulting in a workgroup configuration. Administering users and groups in a domain environment is similar in a mechanical sense to administering them in a workgroup environment. If using an Active Directory domain controller, the Computer Management tool allows for adding, modifying, and removing users in the same context as in a workgroup environment. The concepts, however, are very different. Additional information about planning for domain environments can be found at: http://www. microsoft. com/windows2000/technologies/directory/ad/default. asp NAS 2000s Administration Guide 101 User and Group Management The configuration of the domain controller is reflected on the NAS 2000s because it obtains user account information from the domain controller when deployed in a domain environment. As mentioned previously, the server cannot act as a domain controller itself. User and Group Name Planning Effective user and group management is dependent upon how well the user and group names are organized. Administrators typically create a small number of groups on the network and then assign users to the appropriate group or groups. File system and share permissions can then be applied at the group level, rather than at the user level. If the number of groups is small, assigning the appropriate permissions to selected group, or groups, is more efficient than assigning permissions to each user. Although each organization has specific conventions, following general guidelines makes administration simpler and more efficient. Because CIFS/SMB is dependent on users and groups to grant appropriate access levels to file shares, CIFS/SMB administration benefits from a consistent user and group administration strategy. Managing User Names Usernames should reflect a logical relationship between the username and the person who uses the account. It is important that rules are established to ensure that usernames are: Systematic Easy to follow and implement Easy to remember Using a combination of the user's first name, middle initial, and last name results in systematic usernames for every member of a particular organization. Common examples include: First initial followed by last name (jdoe for John Doe) First initial followed by middle initial and last name (jqpublic for John Q. Public) First name followed by last name, separated by a period (john. smith for John Smith) Last name followed by first initial (doej for Jane Doe) Guidelines must be in place for instances when two users have the same initials or name. [. . . ] At the Integrated Lights-Out Account Login screen, supply the username and password for the iLO and click Login. The Remote Console Information screen is displayed. Click on the Remote Console choice in the menu on the left side of the screen. Press Ctrl-Alt-Del to login to the console. [. . . ]