5.4 Upgrading iFolder to OES

5.4.1 About iFolder on OES

NetWare runs only iFolder 2.x while OES runs iFolder 3.9, and as the version numbers imply, iFolder 3.9 is much more robust and flexible.

Figure 5-3 How Novell iFolder 3.9 Works

The following table explains the information illustrated in Figure 5-3.

Access Methods

Authentication/File Encryption

Novell iFolder 3.9 Services

Linux, Macintosh, and Windows workstation users who have the Novell iFolder Client installed can access and modify their files in one or more workstation folders. Changes are automatically synchronized with the iFolder 3.9 Enterprise servers.

A Web interface lets users access their files from any computer with an active network or Internet connection.

All file service access is controlled by LDAP- based authentication through the eDirectory LDAP server.

Although it is shown separately, eDirectory could be installed on the OES server.

Files can be encrypted for transport using SSL connections (HTTPS).

Slave servers can be added as needed, providing the ability to dynamically grow iFolder services without disrupting users.

Local and network copies of each file are automatically synchronized by the Novell iFolder Client and Server pieces.

Additional overview information is available in Overview of Novell iFolder in the Novell iFolder 3.9.2 Administration Guide.

5.4.2 Platform Differences in iFolder File Services

There are numerous significant differences between iFolder 2.x and iFolder 3.9, including:

  • Automatic Service Provisioning: Multiple servers participate in a single iFolder domain, and iFolder user assignments are automatically balanced across the domain.

  • Multiple iFolders: Users can use a virtually unlimited number of iFolders.

  • Sharing iFolders: Users can share their iFolders with other iFolder users, granting them full, read/write, or read only access.

  • File-type Synchronization: If desired, you can limit which file types are synchronized.

For a complete list of differences, see Comparing Novell iFolder 2.x with 3.9 in the Novell iFolder 3.9.2 Administration Guide.

5.4.3 Planning


Table 5-6 iFolder Source and Target Server Requirements

Source Server

Target Server

NetWare server with iFolder 2.x installed

One or more OES servers installed.


The iFolder 3.9 service pattern is installed on each server but not configured.


All iFolder 3.9 servers, the iFolder 3.9 Web Access server, and eDirectory are up and running.


Data must be moved before the iFolder service is transferred.

If multiple servers are targeted, data migration is balanced by default. Users are then assigned to the appropriate iFolder. However, other provisioning options are available.

For more information, see Multi-Server Migration in the OES 2015 SP1: Migration Tool Administration Guide.


Moving Encrypted iFolders

The Migration Tool doesn’t move encrypted iFolders because user passphrases are needed. Each user with an encrypted iFolder needs to perform a client-side migration if they want their iFolder 2.x data moved to iFolder 3.9. For more information, see Migrating from iFolder 2.x to iFolder 3.9.2 in the Novell iFolder 3.9.2 Cross-Platform User Guide.

iFolder 2.x User Policies Not Transferred

iFolder 2.x configuration settings, such as user policies, are not compatible with iFolder 3.9 and are therefore not transferred. You must set the policies for each user after the migration is complete.

5.4.4 Upgrading iFolder

You can use either of the two migration types offered by the Migration Tool to upgrade iFolder file services from NetWare to OES:

To upgrade Novell iFolder on NetWare to OES, follow the instructions in Migrating iFolder 2.x in the OES 2015 SP1: Migration Tool Administration Guide.

5.4.5 Post-Upgrade Checks

As mentioned in iFolder 2.x User Policies Not Transferred, you must set a policy for each user after the upgrade is finished.