HP StorageWorks NAS 1000s, Administration Manual, Page: 65 / 172

User and Group Management
65 NAS 1000s Administration Guide
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. For
example, a number can be added to the end of the username (jdoe1 and jdoe2).
Other conventions can be applied. Just ensure that conventions are both systematic and
consistent.
Managing Group Names
Group management follows many of the same principles as user management.
It is recommended that group naming conventions be systematic and easy to understand. Make
the group name convey some logical information about the function or purpose of the group.
Table 3 provides examples of group names.
Using tags is a helpful convention that indicates the specific access that a particular user has to
a network resource. For example, if there is a data share on the device, the network
administrator can create a "Data Users ROnly" group and a "Data Users RWrite" group to
contain users that have read only or read write access on the share, respectively.
Table 3: Group Name Examples
Group Name Description
Administrators All designated administrators on the server
Users All standard server users
Power users All standard server users requiring advanced access levels