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.
Novell eDirectory 8.8, Active Directory, or openldap
Novell iManager 2.7
Apache 2 Web Server (worker mode) with SSL configured
The iFolder client supports the following operating systems:
SUSE Linux Enterprise Desktop (SLED) 11 SP2 64-bit
NOTE:The iFolder Linux client requires the Mono framework for Linux and a GNOME desktop for iFolder Nautilus plug-in support.
Windows XP SP3 32-bit
Windows Vista SP1
Macintosh OS X 32-bit (Intel architecture) v10.6 and later (requires Mono 188.8.131.52). PowerPC architecture is not supported.
Novell iFolder supports the following Web browsers:
Internet Explorer 8
Mozilla Firefox 3.6.x and later
Apple Safari 4.x and later
The iFolder client is available for download on the OES 11 Welcome page of your iFolder enterprise server. For more information, see Novell iFolder 3.9.1 Administration Guide.
This section describes known issues for the iFolder enterprise server, Web Access server, and Web Admin server.
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.
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.
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to the Novell International Trade Services Web page for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 2007 - 2012 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.
For Novell trademarks, see the Novell Trademark and Service Mark list.
All third-party trademarks are the property of their respective owners.