HP AiO400r HP StorageWorks All-in-One Storage System User Guide (440583-006, J - Page 180

User Name Mapping, Use naming conventions to identify shares with EUC encoding

Page 180 highlights

• Use naming conventions to identify shares with EUC encoding • Protect configuration files For further details, see the online help for Microsoft Services for Network File System. User Name Mapping The User Name Mapping component provides centralized user mapping services for Server for NFS and Client 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. User Name Mapping lets you maintain a single mapping database making it easier to configure account mapping for multiple computers running MSNFS. 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. 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. 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. 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. 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. User Name Mapping associates Windows and UNIX user names for Client for NFS and Server for NFS. This allows users to connect to Network File System (NFS) resources without having to log on to UNIX and Windows systems separately. NOTE: Most of the functionality of User Name Mapping has been replaced by Active Directory Lookup. Active Directory Lookup enables Client for NFS and Server for NFS to obtain user identifier (UID) and group identifier (GID) information directly from Active Directory. For information about storing UNIX user data in Active Directory, see documentation for Identity Management for UNIX. For information about enabling Active Directory Lookup, see "Specifying how Server for NFS obtains Windows user and group information" available in online help. 180 Microsoft Services for Network File System (MSNFS)

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216

Use naming conventions to identify shares with EUC encoding
Protect configuration files
For further details, see the online help for Microsoft Services for Network File System.
User Name Mapping
The User Name Mapping component provides centralized user mapping services for Server for NFS
and Client 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.
User Name Mapping lets you maintain a single mapping database making it easier to configure
account mapping for multiple computers running MSNFS.
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.
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.
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.
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.
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.
User Name Mapping associates Windows and UNIX user names for Client for NFS and Server for
NFS. This allows users to connect to Network File System (NFS) resources without having to log on
to UNIX and Windows systems separately.
NOTE:
Most of the functionality of User Name Mapping has been replaced by Active Directory Lookup. Active
Directory Lookup enables Client for NFS and Server for NFS to obtain user identifier (UID) and group
identifier (GID) information directly from Active Directory. For information about storing UNIX user data
in Active Directory, see documentation for Identity Management for UNIX. For information about enabling
Active Directory Lookup, see “Specifying how Server for NFS obtains Windows user and group information”
available in online help.
Microsoft Services for Network File System (MSNFS)
180