The following items listed in this section apply to all server operating systems.
If an Admin object resides on multiple LDAP servers, do not enable this object as an iFolder user. If you have only one LDAP server and one corresponding Admin user, you can enable this object; however, enabling Admin users for iFolder accounts is not recommended.
The Admin context cannot exceed 38 characters in length (including spaces).
An iFolder user ID cannot exceed 64 characters in length. If the user ID is greater than 64 characters, the user will not be able to access his iFolder account.
WARNING: Do not try to synchronize your GroupWise® archive by setting a GroupWise archive path to the location of your iFolder directory. If you do this, the iFolder client will corrupt the GroupWise archive. This happens because iFolder does not synchronize files as a set and GroupWise needs the files in the archive to be maintained as a set of files.
This problem has been identified for GroupWise; however, similar problems might arise with any database that is implemented as a collection of linked files.
If a user logs in to his local iFolder account in a disconnected state (without a live Internet connection), any policy changes that are made from the iFolder Management Console will not take effect until that user logs in again with an active Internet connection.
The numbers displayed in the Totals field in the Reporting section of the iFolder Management Console are incorrect. These numbers reflect only the totals of the server that the Admin is logged in to.
Rapidly toggling back and forth between the Reporting and System Monitoring screens in a browser might cause iFolder to hang. If iFolder hangs, stop and restart the iFolder software.
If two administrators are simultaneously making system monitoring requests from two different browsers to two different iFolder servers, iFolder might hang. If iFolder hangs, stop and restart the iFolder software.
We require that you use the version of Apache that ships with iFolder. If you use another version of Apache, iFolder will not work as designed.
If you have a large number of users that have extended characters in their pass phrases, uninstall iFolder and install the new iFolder 2.0 version instead of upgrading.
In iFolder 2.0, the iFolder client stores the pass phrases differently than it did in iFolder 1.0. (Storage was in ANSI hash previously; it is now Unicode based). If you upgrade iFolder, the iFolder 2.0 client will not recognize the iFolder 1.0 pass phrases, and if a user tries to access his account through the Java* applet, the login will fail and return a message prompting the user to contact the administrator to change his pass phrase.
To avoid this, uninstall iFolder 1.0 and remove the user accounts from the iFolder 1.0 server. Then install iFolder 2.0 on your server and have your users log in to the iFolder server. The initial iFolder client login will prompt the users to enter a new pass phrase. They can enter the old pass phrase if they want to, because iFolder doesn't need a new pass phrase; it just needs to store the pass phrase in a format that it can recognize.
By doing this, you won't have to manually remove each user account when users report that they can't log in.
The iFolder 1.0 client cannot access an iFolder 2.0 server. If you have multiple iFolder accounts located on different servers, make sure that you are accessing the iFolder server with the correct version of the iFolder client.
The iFolder startup might hang if you have ZENworks® for Desktops and iFolder running on the same server. If you encounter this problem, go to the AUTOEXEC.NCF and move the iFolder STARTIFOLDER.NCF command line before the ZENworks ZFDSTART.NCF command line.
Make sure the client for Microsoft networks is installed on your Windows 98SE workstations before installing the iFolder client. Otherwise, your workstation might crash.
The iFolder Management Console and the Java applet can be accessed from Internet Explorer 5 or later. Netscape* 4.7 is the recommended Netscape browser version.
If your server is running NetWare or Windows NT/2000, you must use IE to access your files via a browser.
The iFolder Management Console and default iFolder Web site cannot be accessed from a Netscape browser on an IIS server. If you are using an IIS server, use IE; or, if you need to use Netscape, use a workstation to access these sites.
If you are using an iChain server or a BorderManager® proxy server to redirect requests to your iFolder server, be advised that uploads to the iFolder server are very slow.
Additionally, if your proxy server requires a username and password for authentication, the iFolder client will fail to log in to the iFolder server.
If your browser caches its pages, the next time you return to the iFolder Management console, after having logged out of the console and closed your browser, you might not have to log in again.