Novell iFolder 3.8 Readme

November 2009

2.1 Client
3.1 Server
3.2 Client

1.0 Overview

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 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. It also lists the known issues and limitations with this release.

2.0 What’s New

The new features for iFolder are as follows:

2.1 Client

The new features for iFolder clients are as follows:

Password change

The password change feature enables you to change the password of your iFolder account using the web access console or any of the iFolder clients on Linux, Windows, and Mac.

Passphrase recovery wizard

The passphrase recovery wizard enables you to reset the passphrase and recover an encrypted iFolder. This wizard is available with iFolder clients on Linux, Windows, and Mac.

Enhanced User interface

The user interface of iFolder thick clients, web admin console, and web access console is enhanced to improve the usability of iFolder.

iFolder client for openSUSE 11.1, openSUSE 11.2, and SLED 11

The iFolder enterprise server for 3.8 supports iFolder clients for openSUSE 11.1, openSUSE 11.2, and SLED11.

64 bit version of iFolder client for Vista and Windows 7

The 64 bit version of iFolder client is available for Vista and Windows 7. This includes:

  • New 64 bit install

  • New 64 bit Flaim database

  • New iFolder binaries in 64 bit

Revert iFolder, from shell extension, uses the same Dialog that is used by the iFolder main window

Revert iFolder, from shell extension, now uses the same Dialog that is used by the iFolder main window. This has the Delete from server option.

iFolder client startup performance enhanced

The iFolder client startup performance is enhanced.

2.2 iFolder server

The new features for iFolder server are as follows:

Support for mono 2.4 runtime environment

iFolder now supports mono 2.4 runtime environment.This change in mono runtime addresses several issues related to thread synchronization and daily crashes.

Multi-level administration

Multi-level administration feature enables you to create primary as well as secondary administrators.

Active Directory integration for iFolder

The iFolder server is integrated with active directory so that the process of admin and proxy user creation is automated.

3.0 System Requirements

3.1 Server

Your server must satisfy the following system requirements.

  • Openldap

  • Apache 2 Web Server (worker mode) with SSL configured

3.2 Client

The iFolder client supports the following operating systems:

  • SUSE Linux Enterprise Desktop (SLED) 11

  • openSUSE 11.1

    The iFolder Linux client requires the Mono framework for Linux and a GNOME* desktop foriFolder Nautilus plug-in support.

  • openSUSE 11.2

  • Windows XP SP2 and above

  • Windows Vista SP1 and above

  • Macintosh OS X (Intel architecture) v10.4.11 and later (requires Mono 1.2.5 ). PowerPc architecture is not supported.

3.3 Browser

Novell iFolder supports the following Web browsers:

  • Internet Explorer*

  • Mozilla* Firefox* 2.x and later

  • Safari* 3.0

4.0 Known Issues for Novell iFolder

This section describes known issues for the iFolder enterprise server, Web Access server, and Web Admin server.

4.1 Unable to Rename Large-Sized Files

Renaming of large-sized files (size above 10 GB) may cause sync issues and the file rename will not be synced.

4.2 The iFolder setup throws an exception if LDAP proxy user already exists in Active Directory

The iFolder setup will throw an exception when you specify LDAP proxy user DN in Yast if LDAP proxy user already exists 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.

4.3 Re provisioning users from one server to another results in creation of duplicate entries of iFolders for the reprovisioned user

If you re-provision users from one server to another, then sometimes, duplicate entries of iFolders are displayed for the re-provisioned user in the Web console and iFolder clients. As a workaround, after you re-provison the users, you must login to the Web Admin console to verify if duplicate entries of iFolders are displayed for re-provisioned users. If duplicate entries are getting displayed, you must restart the iFolder server to resolve the issue.

4.4 iFolder deletion leaves an empty directory on the server

For every iFolder, a directory with iFolder's unique ID as name is created on the server. All the iFolder data is stored under this directory. On deleting an iFolder, the contents of the directory where iFolder data is stored is deleted. However, the directory itself not deleted.

4.5 Upload of files is possible only if secondary administrator sets disk quota

After you create a secondary administrator and assign a group to the secondary administrator, the secondary administrator must assign some disk quota to the users of the group. Otherwise, the users will not be able to upload any files using the Web Access console or the iFolder client. This is applicable only if the Administrator console option is selected for managing 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.

4.6 The iFolder configuration through Yast hangs when Active Directory on windows 2003 is configured as an ldap source

On configuring iFolder through Yast, if active directory 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:

  1. First, you must export the AD server certificate on Windows 2003 using the steps given below:

    1. Click Start > Administrative Tools > Certification Authority to launch the Certification Authority application.

    2. Select a certification authority, then right-click and select Properties.

    3. In the Properties window, click the View Certificate button.

    4. In the Certificate window, click the Details tab and click the Copy to File button.

    5. Click Next in the Certificate Export Wizard window.

    6. Select Base-64 encoded X.509 and click Next.

    7. Specify the path and file name of the certificate and click Next.

    8. Click Finish to export the certificate.

  2. Finally, copy the exported certificate file to 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, then this step must be executed for all the nodes.

4.7 iFolder Does Not Support Spaces or Dots in the Admin DN (Distinguished Name) and User container DN

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 in case of all directory services.

4.8 Delta Sync Is Not Supported for Encrypted iFolders

Modifying any file in an encrypted iFolder performs a full sync to the iFolder server, instead of synchronizing only the changes.

4.9 iFolder Does Not Support Multibyte Characters in Username

The iFolder user account cannot have multibyte characters in the username. Authentication fails if the user name contains multibyte characters.

4.10 All strings in Web admin and Web access console are displayed only in English

When you login to Web admin and Web access console, irrespective of the language you select from the Language list, all strings in the console will be visible in english only.

5.0 Known Issues for the iFolder Client For Linux

This section describes known issues for iFolder client for Linux.

5.1 No Auto Upgrade Support for Linux Clients

If you install iFolder linux client 3.8.0.0 and then upgrade your iFolder server to 3.8.0.1, the iFolder client does not automatically prompt for an upgrade. You can download the client from the Welcome page (http://<OES 2 SP2 server ip> ) and install the clients manually.

5.2 Confirmation dialog is not displayed on removing an iFolder account

If you remove an account from the Accounts tab of the iFolder Preferences Window of the iFolder client, the account might get removed without displaying a confirmation dialog. This is a rare occurrence.

5.3 The iFolder client on Linux might hang while setting the passphrase

While setting the passphrase, the iFolder client on Linux might hang. This is a rare occurrence and as a workaround, if the client hangs for a long time, you must kill the client and restart it.

5.4 When iFolders are added or deleted, the changes do not get reflected on Linux clients immediately

For iFolder clients on Linux, when iFolders are added or deleted, the changes do not get reflected instantly. It takes some time for the changes to come into effect.

5.5 The iFolder client on Linux might freeze sometimes

The iFolder client on Linux client might freeze sometimes. This is a rare occurrence. If this occurs, then as a workaround, you must kill the client and restart it.

5.6 On SLED 11 and openSUSE 11.1, any modifications to files or folders beyond the second level is not getting synchronized

For iFolder clients on SLED 11 and openSUSE 11.1, if you make any modifications to a file or folder that is beyond the second level in the directory structure, then the corresponding changes are not getting reflected on the iFolder server. However, modifications to files or folders in the first or the second level of the directory structure will lead to synchronization of changes on the server for files or folders beyond second level also.

5.7 While configuring an account using iFolder client, an error is received on specifying the passphrase on the Encryption page

If encryption is enabled and you are configuring an account using the iFolder client, then you may receive an Operation timeout error when you are prompted to enter the passphrase on the Encryption page of the iFolder Account Assistant. This may 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 will not be able to set the passphrase when this issue occurs. As a workaround, you must click Cancel in 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 will be prompted to specify the passphrase. You must then specify the passphrase to create an encrypted iFolder.

5.8 No notification of name conflicts on uploading multiple files with the same name using two different clients

When you upload multiple files with the same name to the same iFolder using two different clients, the synchronization is successful. However, in such a scenario a name conflict must occur which enables you to resolve the name conflict.

5.9 Option to start iFolder during system login does not work in iFolder client for SLED 11 and openSUSE 11.1

For iFolder clients on SLED 11 and openSUSE 11.1, 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. To do this, follow the steps given below:

  1. Click the Gnome Control Center.

  2. Click Systems->Sessions.

  3. In the Sessions dialog box, click the Startup Programs tab.

    NOTE:You can also open the Sessions dialog box from the command terminal by typing the command gnome-session-properties.

  4. To add iFolder to the list of startup programs, click Add and browse to the location where the iFolder executable is available.

    IMPORTANT:The iFolder client executable is present at the location /opt/novell/ifolder3/bin .

  5. Click OK and then click Close to close the Sessions dialog box.

5.10 The first synchronization cycle after downloading a shared iFolder generates an error

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.

5.11 iFolder emblem does not get updated automatically on openSUSE 11.1 and SLE 11

For iFolder clients on openSUSE 11.1 and SLE 11, if you convert a folder to an iFolder or revert an iFolder to a regular folder, the emblem on the iFolder does not get updated automatically.

As a workaround for this issue, you must do a manual refresh. For instance, you can manually refresh by pressing the F5 button.

6.0 Known Issues for the iFolder Client For Macintosh

This section describes known issues for the iFolder client for Macintosh.

6.1 Menus for iFolder client on Mac are inconsistent with those on Windows and Linux

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, both Delete and Revert to Normal iFolder options get enabled for both local and remote ifolders.

6.2 No Auto-Upgrade For iFolder Mac Client

iFolder client for Macintosh doesn’t provide the auto-upgrade feature. When a new version of the client is available for upgrade, iFolder prompts you about the availability of the client for download, and when you click OK, it downloads the client to a location on your workstation. You need to go to that location and manually install the new client.

7.0 Documentation Conventions

In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.

A trademark symbol (®, ™, etc.) denotes a Novell trademark; an asterisk (*) denotes a third-party trademark