Vous êtes sur la page 1sur 2

8/5/12

Understanding the User Name Mapping component

Understanding the User Name Mapping component


Applies To: Windows Server 2003 R2 User Name Mapping acts as a single clearinghouse that provides centralized user mapping services for Client for NFS and Server for NFS. User Name Mapping lets you create maps between Windows and UNIX user and group accounts even though the user and group names in both environments may not be identical. Perhaps most importantly, User Name Mapping lets you maintain a single mapping database for the entire enterprise. This makes it easy to configure account mapping for multiple computers running Microsoft Services for Network File System (NFS). In addition to one-to-one mapping between Windows and UNIX user and group accounts, User Name Mapping permits one-to-many mapping. This lets you associate multiple Windows accounts with a single UNIX account. This can be useful, for example, when you do not need to maintain separate UNIX accounts for individuals and would rather use a few accounts to provide different classes of access permission. You can use simple maps, which map Windows and UNIX accounts with identical names. You can also create advanced maps to associate Windows and UNIX accounts with different names, which you can use in conjunction with simple maps. For information about simple and advanced maps, see Understanding user maps1. User Name Mapping can obtain UNIX user, password, and group information from one or more Network Information Service (NIS) servers or from password and group files located on a local hard drive. The password and group files can be copied from a UNIX host or from a NIS server. See Configuring User Name Mapping2 for more information about specifying the source for UNIX user information. User Name Mapping periodically refreshes its mapping database from the source databases, ensuring that it is always kept up-to-date as changes occur in the Windows and UNIX name spaces. You can also refresh the database anytime you know the source databases have changed. For information about how to refresh the database automatically and manually, see Configuring the refresh interval for maps3 and Refreshing maps4. You can back up and restore User Name Mapping data at any time. Because the database is backed up to a file, you can use that file to copy the mapping database to another server. This provides redundancy for the sake of fault tolerance. To learn how to back up and restore the mapping database, see Backing up and restoring maps5. Note If you obtain information from multiple NIS domains, it is assumed that each domain has unique users and user identifiers (UIDs). User Name Mapping does not perform any checks.

Links Table
1http://technet.microsoft.com/en-us/library/cc756929(v=ws.10) 2http://technet.microsoft.com/en-us/library/cc778466(v=ws.10) 3http://technet.microsoft.com/en-us/library/cc787366(v=ws.10)
technet.microsoft.com/en-us/library/cc739581(d=printer,v=ws.10) 1/2

8/5/12

Understanding the User Name Mapping component

4http://technet.microsoft.com/en-us/library/cc783500(v=ws.10) 5http://technet.microsoft.com/en-us/library/cc784926(v=ws.10)

Community Content
2012 Microsoft. All rights reserved.

technet.microsoft.com/en-us/library/cc739581(d=printer,v=ws.10)

2/2

Vous aimerez peut-être aussi