Novell IFOLDER 3 - ADMINISTRATION, Manual

Page: 142 / 148

142 Novell iFolder 3.x Administration Guide
no
vd
ocx (
E
NU)
01
F
ebr
ua
ry
200
6
E.1.2 Managing an iFolder Enterprise Server
The following change was made to this section:
E.1.3 Managing iFolders
The following change was made to this section:
E.1.4 Clustering iFolder 3.x Servers with Novell Cluster
Services for Linux
The following changes were made to this section:
Section 6.7, “Distributing the
iFolder Client to Users,” on
page 62
NOTE: iFolder 3. x does not support a silent install (that is, a scriptable
non-interactive install) on any platform. A silent install is possible the Linux
client using its
.rpm
files, but it is not supported.
Location Change
Configuring the iFolder
Nightly Restart
It is no longer necessary to run scripts for a nightly restart of iFolder
services.
Location Change
Section 11.1, “Creating an
iFolder for a User’s
Account,” on page 109 You cannot specify where on the individual computers that the iFolder is to
be stored. Each user decides where to set up the iFolder on his or her own
computer. If you want users to each store iFolders in the same relative
location on their computers, you must coordinate that behavior outside of
iFolder. There is no way to enforce it using iFolder tools, of course.
Section 11.5, “Sharing an
iFolder,” on page 112 In iFolder 3.2 and earlier, when an owner adds a user to an iFolder, the
user does not become a member until he or she accepts the iFolder on at
least one machine. After the user accepts the invitation and sets up the
iFolder, the user shows up in the member list. However, if you add the user
as a member of an iFolder from the iManager pages, then the user is
automatically a member. The user and the iFolder will show up in the Web
access interface without the user setting up a local iFolder on his or her
computer.
Location Change
Section B.3, “Configuring
iFolder 3.x Services on an
NCS for Linux Cluster,” on
page 126 Corrections were made in Step 4.
Section B.7.3,
“Troubleshooting,” on
page 132 This section is new. It explains how to tune the cluster unload script to
allow enough time to gracefully break connections with users.
Location Change