How to Upgrade

If your machine already has a version of EP on it, you do not need to uninstall before installing EP 4. Although it's not required to stop IIS at the beginning of the EP 4 install/upgrade, doing so makes it unnecessary to reboot Windows at the end of the installation process.

When reinstalling or upgrading, EP does not overwrite the existing eep.ini file. But you might want to make a backup copy of eep.ini before upgrade/reinstall. This file is located in the Program Files/Enfold Proxy directory.

Rolling back to a previous version. If you want to retain the ability to rollback to the previous EP version, stop IIS and copy the entire Program Files/Enfold Proxy directory to a safe place. (If IIS is not stopped, you won't be able to copy all the files). If you configured EP to store cache and log files elsewhere, you may wish to back these up as well.

There are two basic approaches to handling the upgrade.

First Method: Test on a Separate Machine (Safest)

• install EP 4 into a test environment on a different machine (with Enfold Server or Plone).
• Copy your original eep.ini file into the EP 4 directory or manually input each proxy definition by using the configuration utility.
• After verifying that EP 4 works, uninstall EP 3 (or earlier versions).
• Install EP 4 into the same machine as the live server (that will uninstall the previous EP version).
• Restart IIS. (If adding proxy definitions one at a time, you may need to restart each time).

Second Method: Install on the production machine (Saves Time, Useful for Simple configurations)

• Copy your original eep.ini file into a safe place.
• Install EP 4.

The first method is safest and recommended. But if you are already sure your proxy definitions worked before and not doing any special out-of-the-ordinary customizations (see reasons for editing the configuration file manually ), then the second method will usually suffice.

Previous versions of EP used different terminology and sometimes asked users to configure EP by editing the eep.ini file. For Version 4 Enfold recommends that users configure EP by using the configuration utility instead of hand-editing the eep.ini file. This prevents editing errors and ensures that changes are propagated successfully to Microsoft's Internet Information Services (IIS).

Importing eep.ini files from EP 3 to EP 4 should generally be safe (especially if you generated the file completely from the configuration utility instead of hand-editing it). If for some reason, the settings from your existing eep.ini do not work, the Enfold Proxy configuration utility will start (even though some of the proxy definitions won't be active). To see which of your proxy definitions is not functioning, run the check utility .

Another idea is to delete the eep.ini file causing problems (it will be autogenerated after the configuration tool is restarted) and start again from scratch (adding one proxy definition at a time).

Deleting Orphaned Content

Earlier versions of EP had a bug that prevented cached content from being deleted. For users who were using a previous EP version, it may be necessary to run a one-time script to recognize and delete orphaned content. This command line utility ep_cache_check lets you count and remove orphaned content. You only need to run this once.

C:\Program Files\Enfold Proxy>ep_cache_check.exe
Opening cache
Cache has 257 entries, but 540 files exist
Computing missing files
Computing orphans
We have 283 orphans (use --fix to correct this)

As the prompt says, you could run the same command with the --fix switch. Doing that will remove these 283 orphans. This is a way to reduce the amount of space on your machine.

People installing EP 4 for the first time will never need to run this script. Normally, to empty a cache directory, you should issue a command to purge all content, either using a caching product in Plone, or the purging button in the EP configuration utility.