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.8.4. It also lists the known issues and limitations with this release.
The new features for iFolder are as follows:
The iFolder data recovery tool is a CLI-based utility that enables you to restore backed-up files, folders, or iFolders for any user. For more information, see Novell iFolder 3.8.4 Administration Guide.
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
Mono 2.4 (novell-ifolder-mono-2.4)
The iFolder client supports the following operating systems:
SUSE Linux Enterprise Desktop (SLED) 10 SP3
SUSE Linux Enterprise Desktop (SLED) 11 SP1 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.5 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 2 SP3 Welcome page of your iFolder enterprise server. For more information, see Novell iFolder 3.8.4 Administration Guide.
This section describes known issues for the iFolder enterprise server, Web Access server, and Web Admin server.
If you have password policies that support non-ASCII passwords or that require passwords to be 4 characters or shorter, or 12 characters or longer, make sure you select theoption (the default setting) on the OES proxy install screen.
Selecting this option prevents the password-compliance issues with the proxy user after the installation.
If you are installing, then abort the installation and reinstall OES. In the common proxy page, you must provide a password for the common proxy user that complies with your password policy.
The auto-generated iFolder specific proxy user password is compliant with the default settings of the password policy. If you modify the proxy user password or the password policy, make sure that they are compliant with each other. otherwise the iFolder configuration fails.
During the OES2 SP3 server installation, the iFolder server configuration might fail. This is a rare occurrence. If this issue occurs, run yast2 novell-ifolder3 to reconfigure the iFolder server.
When you are configuring iFolder in a cluster, iFolder should not use the common proxy user. The service level proxy should be used instead.
You must ensure that the Web Admin alias name specified during iFolder configuration has no space. Otherwise, the Apache restart after iFolder configuration fails.
If namcd services are down, you cannot change the common proxy user password by using common proxy script. This is because the Apache wwwrun user cannot be retrieved from the eDirectory if the namcd services are down.
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.
If you reprovision users from one server to another, duplicate entries of iFolders are sometimes displayed for the reprovisioned user in the Web console and iFolder clients. As a workaround, after you reprovison the users, you must log in to the Web Admin console to verify if duplicate entries of iFolders are displayed for reprovisioned users. If duplicate entries are displayed, you must restart the iFolder server to resolve the issue.
For every iFolder, a directory with iFolder's unique ID as its name is created on the server. All the iFolder data is stored in this directory. When you delete an iFolder, the content of the directory is deleted. However, the directory itself is not deleted.
After you create a secondary administrator and assign a group to the secondary administrator, the secondary administrator must assign a disk quota to the users of the group. Otherwise, the users cannot upload any files by using the Web Access console or the iFolder client. This is applicable only if the Administrator console option was selected for managing the group quota while creating the secondary administrator. However, users can create empty iFolders even if the secondary administrator has not set any disk quota for users.
When you configure iFolder through YaST, if Active Directory (AD) is given as the ldap source, the iFolder configuration hangs indefinitely. This occurs only for Active Directory configured on Windows 2003. As a workaround for this issue, follow the steps given below:
First, you must export the AD server certificate on Windows 2003:
Clickto launch the Certification Authority application.
Select a certification authority, then right-click and select.
In the Properties window, click thebutton.
In the certificate window, click thetab and click the button.
Clickin the Certification Export Wizard window.
Selectencoded and click .
Specify the path and filename of the certificate and click.
Clickto export the certificate.
Finally, copy the exported certificate file to the Linux server, and run the following command from the command terminal:
certmgr -add -c -m Trust win2k3-vin.ifolder.ad_win2k3-vin.crt
NOTE: If iFolder is configured in a cluster environment, this step must be executed for all the nodes.
iFolder does not support spaces or dots in the admin DN and user container DN. If the Admin DN or user container DN has a space or dot in it, iFolder configuration fails. This is applicable for all directory services.
Modifying any file in an encrypted iFolder performs a full sync to the iFolder server, instead of synchronizing only the changes.
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.
While you set the passphrase, the iFolder client on Linux might hang. This is a rare occurrence. As a workaround, if the client hangs for a long time, you must kill the client and restart it.
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.
The iFolder client on Linux client might freeze. This is a rare occurrence. If this occurs, you must kill the client and restart it.
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.
For iFolder clients on SLED 11 and openSUSE 11.3, if you leave iFolder running and log out of the system, iFolder does not start as expected during system reboot.
As a workaround, you must add iFolder to the list of startup programs:
In the Sessions dialog box, click thetab.
You can also open the Sessions dialog box from the command terminal by typing the command gnome-session-properties.
To add iFolder to the list of startup programs, clickand browse to the location where the iFolder executable is available.
IMPORTANT:The iFolder client executable is present in /opt/novell/ifolder3/bin .
Clickand then click to close the Sessions dialog box.
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 iFolder clients on openSUSE 11.3 and SLES and SLED 11, if you convert a folder to an iFolder or revert an iFolder to a regular folder, the icon on iFolder is not updated automatically.
As a workaround for this issue, you must do a manual refresh. For instance, you can manually refresh by pressing the F5 key.
This section describes known issues for the iFolder client for Windows.
If you have installed the 3.8 version of the Windows 64-bit iFolder client, any attempt to automatically upgrade to a new version of the client fails. You must manually install the new version of the client. After you install the client manually and replace the 3.8 version of the client, the auto upgrade feature works for subsequent client versions.
When you connect an iFolder 3.6 client to an iFolder 3.7 and later server, the system throws a System.Web.Services.Protocols.SoapException error instead of prompting the user to log in to the new client.
This is because the iFolder 3.6 Windows client cannot communicate with an SSL 3.7 or later server. During the connection attempt, the server responds that the preferred communication is HTTPS; however, the 3.6 client does not support HTTPS. When the client attempts to connect via HTTPS, the connection fails because the certificate validation and acceptance fail.
The workaround for this issue is to perform a manual upgrade or set the iFolder 3.7 and later server to communicate via only HTTP.
This section describes known issues for the iFolder client for Macintosh.
If you delete a previously configured account and create any new account by using the account creation wizard, you might receive an error. This is a rare occurrence.
If you receive this error, you must stop the iFolder client, delete the local simias directory ( $HOME/.local/share/simias), then create a new account.
There is an inconsistency in menus for clients on Mac in comparison to the clients on Windows and Linux. For instance, for the iFolder client in Mac, bothand options are enabled for both local and remote iFolders.
The iFolder client for Macintosh doesn’t provide the auto upgrade feature. When a new version of the client is available, iFolder prompts you about the availability of the client for downloading, and when you click, it downloads the client to a location on your workstation. You need to go to that location and manually install the new client.
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 © 2010 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.