Novell IFOLDER 3.7 - SECURITY ADMINISTRATION, Administration Manual

Page: 31 / 216

Planning iFolder Services 31
no
vd
ocx
(e
n)
13
Ma
y 20
09
If the LDAPGroup is moved to a different container that is not specified as a Search DN before
the LDAPGroup is moved, the LDAPGroup is removed from the iFolder LDAPGroup list. The
LDAPGroup’s iFolders are orphaned and the LDAPGroup is removed as a member of iFolders
owned by others. If the new container is later added as a Search DN, the LDAPGroup is treated
as a new LDAPGroup, with no association with previous iFolders and memberships.
Š
If the LDAPGroup appears in multiple defined Search DNs, if one or more DNs are removed
from the LDAP settings, the LDAPGroup remains in the iFolder LDAPGroup list if at least one
DN containing the LDAPGroup remains.
Š
If the LDAPGroup is deleted from LDAP or moved from all defined Search DNs, the
LDAPGroup is removed as an iFolder LDAPGroup. The LDAPGroup’s iFolders are orphaned
and the LDAPGroup is removed as a member of iFolders owned by others.
Š
The iFolder Admin LDAPGroup and iFolder Proxy LDAPGroup are tracked by their GUIDs,
whether their LDAPGroup objects are in a context in the Search DN or not.
2.5.4 Setting Account Quotas
You can restrict the amount of space each user account is allowed to store on the server by setting an
account quota. The account quota applies to the total space consumed by the iFolders the user owns.
If the user participates in other iFolders, the space consumed on the server is billed to the owner of
that iFolder. You can set quotas at the system or user level. Within a give account quota, you can also
set a quota for any iFolder.
2.6 iFolders Data and Synchronization
Considerations
Consider the following when setting policies for iFolders data and synchronization:
Š
“Naming Conventions for an iFolder and Its Folders and Files” on page 31
Š “Guidelines for File Types and Sizes to Be Synchronized” on page 32
2.6.1 Naming Conventions for an iFolder and Its Folders and
Files
The iFolder client imposes naming conventions that consider the collective restrictions of the Linux,
Macintosh and Windows file systems. An iFolder, folder, or file must have a valid name that
complies with the naming conventions before it can be synchronized.
Use the following naming conventions for your iFolders and the folders and files in them:
Š iFolder supports the Unicode* (http://www.unicode.org) character set with UTF-8 encoding.
Š
Do not use the following invalid characters in the names of iFolders or in the names of folders
and files in them:
\/:*?"<>|;
iFolder creates a name conflict if you use the invalid characters in a file or folder name. The
conflict must be resolved before the file or folder can be synchronized.
Š
The maximum name length for a single path component is 255 bytes. For filenames, the
maximum length includes the dot (
.
) and file extension.