Adaptec 5325301638 Administration Guide - Page 38

Local Users and Groups, Guidelines for Local Authentication

Page 38 highlights

Local Users and Groups guidelines: (1) the Snap Server does not recognize users or groups whose identification numbers are less than 100 or greater than 17999; and (2) each UID or GID must be unique. Local Users and Groups Local users or groups are created using the Security > Users and Security > Groups screens in the Administration Tool. Local users and groups are used for administrative and guest access to the server. Windows Workgroup, Macintosh, and FTP clients initially access the server using the guest account. If you require a higher degree of control over individual access to the file system for these clients, you must create local accounts. Guidelines for Local Authentication Consider the following technical information when configuring access for your Windows clients. Duplicating Client Login Credentials for Local Users and Groups To simplify user access for Windows Workgroup or Macintosh clients, duplicate their login credentials on the Snap Server. That is, create local accounts on the Snap Server that match those used to log into client workstations. This strategy allows users to bypass the login procedure when accessing the Snap Server. Caution This strategy applies only to local users. Do not use duplicate domain user login credentials. Default Local Users and Groups The default local users and groups (see "Default User and Group Settings" on page 23) cannot be modified or deleted. For this reason, they do not appear on the list of users or groups on the User or Group Management screens. As you would expect, the default local users and groups do appear on the Share Access and Quotas screens. Changing Local UIDs or GIDs The Snap Server automatically assigns and manages UIDs and GIDs. Because you may need to assign a specific ID to a local user or group in order to match your existing UID/GID assignments, the Snap Server makes these fields editable. 24 Snap Server Administrator Guide

  • 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

Local Users and Groups
24
Snap Server Administrator Guide
guidelines: (1) the Snap Server does not recognize users or groups whose
identification numbers are less than 100 or greater than 17999; and (2) each UID or
GID must be unique.
Local Users and Groups
Local users or groups are created using the
Security > Users
and
Security > Groups
screens in the Administration Tool. Local users and groups are used for
administrative and guest access to the server. Windows Workgroup, Macintosh,
and FTP clients initially access the server using the guest account. If you require a
higher degree of control over individual access to the file system for these clients,
you must create local accounts.
Guidelines for Local Authentication
Consider the following technical information when configuring access for your
Windows clients.
Duplicating Client Login Credentials for Local Users and Groups
To simplify user access for Windows Workgroup or Macintosh clients, duplicate
their login credentials on the Snap Server. That is, create local accounts on the Snap
Server that match those used to log into client workstations. This strategy allows
users to bypass the login procedure when accessing the Snap Server.
Caution
This strategy applies only to local users. Do not use duplicate domain user
login credentials.
Default Local Users and Groups
The default local users and groups (see “Default User and Group Settings” on page
23) cannot be modified or deleted. For this reason, they do not appear on the list of
users or groups on the User or Group Management screens. As you would expect,
the default local users and groups do appear on the Share Access and Quotas
screens.
Changing Local UIDs or GIDs
The Snap Server automatically assigns and manages UIDs and GIDs. Because you
may need to assign a specific ID to a local user or group in order to match your
existing UID/GID assignments, the Snap Server makes these fields editable.