Administrator Guide

● Adding Group Account Maps: Creating a group-class object in the CN=Users container to map the gidNumber and

sAMAccountName attributes.

Connecting to the distinguished name or naming context

To connect to the distinguished naming context:

Steps

1. In Server Manager, click Tools > ADSI Edit.

The ADSI Edit console is displayed.

2. In the console, right-click ADSI Edit and click Connect to.

Alternatively, in the ADSI Edit console, you can navigate to Actions > More Actions > Connect to.

The Connection Settings dialog box is displayed.

3. Under Connection Point, select the Select a well known Naming Context option.

By default, Default naming context option is selected from the drop-down menu.

4. Under Computer, select the Select or type a domain or server option, and enter the server name and port number in the

text box, separated by a colon (for example, localhost:389).

5. Click OK.

ADSI Edit refreshes to display the new connection.

6. In the resulting tree, under the Default naming context node, right-click the partition name, click New, and then click

Object.

NOTE:

For this example, under the Default naming context localhost:389, select the following properties:

CN=nfsadldsinstance, DC=server1.

7. In the Create Object dialog box, select the Container class, and then click Next.

8. In the Value box, type Users, and then click Next.

This value specifies the name of the container object that is used to hold your user account mappings.

9. Click Finish.

Adding user account maps

To add user account maps:

Steps

1. In ADSI Edit, expand the Default naming context node, and then expand the partition name.

2. Right-click CN=Users, click New, and then click Object.

3. In the Create Object dialog box, select the User class, and then click Next.

4. In the Value text box, type the user name, and then click Next.

NOTE: The user name is not associated with the Windows-or UNIX user, and can be a random entry.

5. Click the More Attributes button to edit the uidNumber, gidNumber, and sAMAccountName attributes of this user account.

NOTE:

The uidNumber and gidNumber represent the UID and GID of the UNIX user who is being mapped, and

sAMAccountName must match the name of a local Windows user on the computer that is running Server for NFS. If,

after selecting the More Attributes button, the uidNumber and gidNumber do not appear, exit and start the ADSI

Edit MMC.

6. Click OK.

Using your NAS system