Adaptec 5325301507 Administration Guide - Page 123

Windows ACLs, Home directories are supported for SMB, NFS, AFP, HTTP/HTTPS, and FTP/FTPS.

Page 123 highlights

Windows ACLs Home directories are supported for SMB, NFS, AFP, HTTP/HTTPS, and FTP/FTPS. They are accessed by clients in the following manner: • For SMB, AFP, and HTTP/HTTPS, users are presented with a virtual share named after the username. The virtual share is visible and accessible only to the user. Users are not limited only to their virtual shares; all other shares on the server continue to be accessible in the usual fashion. • For NFS, the home directory is exported. When a user mounts the home directory root, all home directories will be visible inside the root, but the user's home directory will be accessible only by the user and the administrator. Note If desired, UNIX clients can be configured to use a Snap Home Directory as the local user's system home directory. Configure the client to mount the home directory root for all users, and then configure each user account on the client to use the user-specific directory on the SnapServer as the user's home directory. • For FTP/FTPS, local users will automatically be placed in their private home directory when they log in. Access to the home directory is facilitated through a share pointing to a parent directory of the home directory, so users can still change to the top-level directory to access other shares. If ID Mapping is enabled, domain users and local users mapped to the same user will be directed to the domain user's home directory. In some cases, data in the local user's home directory will be copied to the domain user's home directory: • If a local user home directory accumulates files before the local and domain users are mapped, and if the domain user's home directory is empty, the local user's files will be copied to the domain user's home directory the first time the local user connects after the users are mapped. • If both the local and domain user home directories accumulate files before the local and domain users are mapped, the files in the local user's home directory will not be copied to the domain user's home directory. Windows ACLs Introduced in v5.0, GuardianOS now fully supports Windows NTFS-style file system ACLs, including configuration, enforcement, and inheritance models. Inside Windows/Mixed SnapTrees, files created and managed by Windows clients have the Windows security personality and behave just as they would on a Windows server. Clients can use the standard Windows NT, 2000, 2003, XP, Vista or Windows 7 interface to set directory and file permissions for local and Windows domain users and groups on the SnapServer. Permissions are enforced for the specified users in the same manner for all client protocols, including non-SMB clients that normally have the UNIX security personality. However, if a non-SMB client changes permissions or ownership on a Chapter 6 Share and File Access 107

  • 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
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250

Windows ACLs
Chapter 6
Share and File Access
107
Home directories are supported for SMB, NFS, AFP, HTTP/HTTPS, and FTP/FTPS.
They are accessed by clients in the following manner:
For SMB, AFP, and HTTP/HTTPS, users are presented with a virtual share
named after the username. The virtual share is visible and accessible only to the
user. Users are not limited only to their virtual shares; all other shares on the
server continue to be accessible in the usual fashion.
For NFS, the home directory is exported. When a user mounts the home directory
root, all home directories will be visible inside the root, but the user’s home
directory will be accessible only by the user and the administrator.
Note
If desired, UNIX clients can be configured to use a Snap Home Directory as
the local user’s system home directory. Configure the client to mount the home
directory root for all users, and then configure each user account on the client to
use the user-specific directory on the SnapServer as the user’s home directory.
For FTP/FTPS, local users will automatically be placed in their private home
directory when they log in. Access to the home directory is facilitated through a
share pointing to a parent directory of the home directory, so users can still
change to the top-level directory to access other shares.
If ID Mapping is enabled, domain users and local users mapped to the same user
will be directed to the domain user’s home directory.
In some cases, data in the
local user's home directory will be copied to the domain user's home directory:
If a local user home directory accumulates files before the local and domain users
are mapped, and if the domain user's home directory is empty, the local user's
files will be copied to the domain user's home directory the first time the local
user connects after the users are mapped.
If both the local and domain user home directories accumulate files before the
local and domain users are mapped, the files in the local user's home directory
will not be copied to the domain user's home directory.
Windows ACLs
Introduced in v5.0, GuardianOS now fully supports Windows NTFS-style file
system ACLs, including configuration, enforcement, and inheritance models. Inside
Windows/Mixed SnapTrees, files created and managed by Windows clients have
the Windows security personality and behave just as they would on a Windows
server. Clients can use the standard Windows NT, 2000, 2003, XP, Vista or Windows
7 interface to set directory and file permissions for local and Windows domain users
and groups on the SnapServer.
Permissions are enforced for the specified users in the same manner for all client
protocols, including non-SMB clients that normally have the UNIX security
personality. However, if a non-SMB client changes permissions or ownership on a