Novell iFolder is a simple and secure storage solution that increases your productivity by enabling you to back up, access, and manage your personal files from anywhere, at any time. Novell iFolder has clients on Linux, Macintosh, and Windows platforms.
You can share files in multiple iFolders, each with a different group of users. You control who can participate in an iFolder and the access level for each member. You can also participate in iFolders that others share with you. iFolder also provides higher security for your confidential iFolder files, to protect them from intentional or unintentional access by unauthorized people.
This Readme provides a brief overview of new features, and installation and configuration instructions for Novell iFolder 3.9.x. It also lists the known issues and limitations with this release.
Novell iFolder supports a system built with the following components of Novell Open Enterprise Server:
Your server must satisfy the following system requirements.
NetIQ eDirectory 8.8.8, Active Directory, or openldap
Novell iManager 2.7.7
Apache 2 Web Server (worker mode) with SSL configured
The iFolder client supports the following operating systems:
SUSE Linux Enterprise Desktop (SLED) 11 SP3
NOTE:The iFolder Linux client requires the Mono framework for Linux and a GNOME desktop for iFolder Nautilus plug-in support.
SUSE Linux Enterprise Desktop (SLED) 10 SP3
Windows XP SP3 (32-bit)
Macintosh OS X 32-bit (Intel architecture) v10.6 and later (requires Mono 220.127.116.11). PowerPC architecture is not supported.
Novell iFolder supports the following Web browsers:
This section describes known issues for the iFolder enterprise server, Web Access server, and Web Admin server.
If you attempt to install the Mono framework package for Mac 10.9 and 10.10 clients, installation fails if the Gatekeeper feature is enabled on the Mac clients.
On the OES 11 server, iFolder common proxy password update fails when changing password with the change_proxy_pwd.sh script.
When you are configuring iFolder in a cluster, iFolder should not use the common proxy user. The service level proxy should be used instead.
The iFolder setup throws an exception when you specify the LDAP proxy user DN in YaST and if the LDAP proxy user is already existing in Active Directory. As a workaround, you must either use a new user's DN or delete the existing user for AD and then use the same DN again.
On the OES 11 SP2 and OES 2015 servers, iFolder service fails when iFolder servers and preferred servers are configured with SHA-2 signed certificates.
This section describes known issues for iFolder client for Linux.
For iFolder clients on SLED 10, if you make any modifications to a file or folder that is beyond the second level in the directory structure, the corresponding changes are not reflected on the iFolder server. However, modifications to files or folders in the first or the second level of the directory structure synchronized on the server for files or folders beyond the second level.
For iFolder clients on Linux, when iFolders are added or deleted, the changes are not instantly reflected. It takes some time for the changes to appear. To view the changes immediately, in the client > open panel, change the Client view to Thumbnail view or List view.
If encryption is enabled and you are configuring an account using the iFolder client, then you might receive an Operation timeout error when you are prompted to enter the passphrase on the Encryption page of the iFolder Account Assistant. This might occur when the server is busy serving iFolder client sync requests and LDAP sync and if the number of users in the system is high.
This is a rare occurrence and you cannot set the passphrase when this issue occurs. As a workaround, you must clickin the Encryption page of the iFolder Account Assistant to continue with the account creation. After an account is created, when you attempt to create an encrypted iFolder, you are prompted to specify the passphrase. You must then specify the passphrase to create an encrypted iFolder.
When you upload multiple files with the same name to the same iFolder by using two different clients, the synchronization is successful. However, a name conflict occurs that you must resolve.
When you download a shared iFolder, the first synchronization cycle fails with an error message “1 item not synchronized”. However, during subsequent synchronization cycles, the synchronization is successful.
For information about legal notices, trademarks, disclaimers, warranties, export and other use restrictions, U.S. Government rights, patent policy, and FIPS compliance, see https://www.novell.com/company/legal/.