Upgrading IPF with the IPF Installer

In the event that you cannot upgrade IPF with your existing Farm Manager, you can use the newest IPF Installer. Follow these steps:

  1. Download the new release files.
  2. Start the IPF.Installer file. If you are updating the IPF Control Service on the same machine where you are running the Installer, you must right-click and run as administrator. Otherwise, do not run as administrator.
  3. Select Upgrade IPF Control Service.
  4. On the right side of the form, specify the same user type, user, password, and server names that were given for the existing installation.
  5. Click Apply Changes.
  6. When prompted to confirm the upgrade, click Yes.
  7. When the upgrade is complete, add the new IPF instance to the necessary portals.
    1. Launch the Farm Manager using the desktop shortcut or system tray launcher. The new version from the upgrade is downloaded and launched.
    2. Follow the instructions in the Launcher Status window until the new Farm Manager is opened.
    3. Determine which of these applies to your installation:
      • If a default IPF instance was specified on the Farms tab before portals were created, you can assign the new instance to all portals by updating that Default IPF Instance field.
      • If a default IPF instance was not specified, then you must assign the new instance by using the Force IPF Instance field on the Portals tab. First, click Refresh on that tab to add the new instance, so it will be included in the Force IPF Instance list. Then select a portal, click Edit, update the Force IPF Instance field, and click Save. All other portals on the same port and host name combination are also set to the new instance.
        Note: If you force the IPF instance on the portals, then after you are sure the new version is working as expected, you should update the Default IPF Instance field on the Farms tab, so future portals are automatically created with the latest instance.
  8. Update any new content versions. This is necessary only if new IPF or portal content versions were included with the architecture upgrade.

    See steps 5 – 9 in Updating a content version.