Cool Solutions

Virtualizing iFolder using Novell ZENworks Application Virtualization


May 7, 2010 10:22 am





Authors: Bhavani S.T and Raghu Kota


iFolder is known to many people as a share and sync data application. Visit for more details about it. Though it provides a facility to access the iFolder information via a browser, there are few limitations when compared to a standalone client. It is simple to create a Virtual application that makes iFolder even easier for end-users.

A virtual application is a virtual machine image pre-configured with all of the files, registry data, settings,components, runtimes, and other dependencies required for a specific application to execute immediately. Novell ZENworks Application Virtualization supports the creation of Virtual applications with specific runtime environments.

Problem Statement:

Sometimes the following error might occur while launching the iFolder Virtual Application, which is created using Snapshot method. As shown in figure 1.1.

Figure 1.1

Click to view.

There could be multiple reasons for failure as follows:

  • Restart required to build the Virtual Application.
  • ZAV prefers to use the infrastructure components from its own repository like an iFolder utilizing .Net framework.

Probable Solution:

  1. Use the ZAV provided infrastructure components (like JRE, .Net, etc.,)
  2. Save the configuration before rebooting the system, i.e., after installation of the physical application and before capturing the delta changes.

Virtual iFolder:

iFolder 3.8 requires .Net 2.0 framework, and it checks for .Net 2.0 during the installation.

Creating a Virtual application (iFolder 3.8) follow the steps below:

  1. Create “Before Snapshot”: to take the initial Snapshot.

  2. Save the Configuration (recommended).
  3. Select the .Net 2.0 framework from the “Runtimes” tab (select the appropriate .Net framework that iFolder uses).

  4. Install the Physical Application, i.e., IFolder 3.8.
    Note: It requires a reboot. So, save the configuration in ZAV before rebooting the system as shown in the figure below.

  5. Open the configuration file which is created in the previous step (step 4).
  6. Capture and Diff: Snapshot after installation of the application. It computes the delta changes after installation of the physical application.

  7. Build the application using the snapshot(s).

  8. Test the virtual application (iFolder) on a different machine.


You will need to add .Net runtime framework and save the configuration before reboot, while installing the physical application for getting a working iFolder virtual application.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.

Categories: Uncategorized


Disclaimer: This content is not supported by Micro Focus. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.