Tandberg Data Viking FS-412 User & Group Name Planning, Managing User Names, rectory/default.mspx

Tandberg DataUser & Group Management

__________________________________________________________________________________________________

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 Microsoft® using the following URL:

http://www.microsoft.com/windowsserver2003/technologies/directory/activedi

rectory/default.mspx

The configuration of the domain controller is reflected on the NAS appliance 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.

5.3.User & 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.

5.3.1.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)

5-2 Tandberg Viking Series Storage Server Administration Manual