Upgrade to 13.0 on a new server


Preparing for the Upgrade

1. Check Server Requirements

Please ensure the new server meets the server requirements for Super Search.  

The upgrade will install 700MBs of new files under your web root directory (typically located on the C: drive), as well as requiring space for the new search index, depending on the number of entries and files in your installation. We recommend having at least 2GB of free hard drive space before upgrading.

Browser Compatibility

This version is compatible with Chrome, Firefox, and Internet Explorer (IE) 9+.

IE 8 can still be used by end users (same level of compatibility as Version 12.5) but with limited functionality. Due to the Javascript limitations of IE 8, and Microsoft dropping support of this browser, it is recommended to upgrade users to IE 9 or later.

2. Update to Latest 12.5 Patch

Always start by updating your 12.5 Mega version to the latest patch (currently Patch 17).

3. Backup Current Intranet

This upgrade will modify both your database and intranet files.

It is very important to backup both your database and files.

  • Take a backup of the Intranet folder from the web root as .zip file
  • Backup the database using Management Studio as a .bak file. 

If you have a virtual environment, it would be recommended to take a snapshot ahead of upgrading.


Upgrade Instructions

1. Prepare the New Server

If you are upgrading to a new server. Please see Preparing a New Server for instructions on how to prepare the new server and move the files and database.

2. Export current installation details

To upgrade your intranet, certain configuration information must be provided to the upgrade installer (database and mail server settings, intranet location, etc). This information needs to be exported from your current intranet installation to the setup details file before the upgrade installer is run.

 The Create Setup Details File article explains how to export your intranet configuration file.


3. Run the Upgrade Installer

a. Download the Upgrade Installer

When prompted for credentials, the Username is the email address of the primary contact we have on file. The Password is your IC serial number

b. Run the Upgrade Installer on the server as an administrator.

NOTE: You must be logged into the server as Administrator. Logging as a non-administrator and right clicking to "Run as Administrator" will not allow the installation to complete successfully because the installer must call several other executables during the installation process. 

The upgrade install now updates to version 13.0.7. 

Screen 1 - Select setup details file exported in Step 2  "Export current installation details" above.


Click Browse and select the setup details file (IC_12.5._InstallDetails.xml).

Screen 2 - Choose the Intranet folder location


If you are upgrading an existing server, click Next.

If you are upgrading to a new server, please click "Change" and select the location of your Intranet folder if this is different.

Screen 3 - Select the location of your IntranetConnections database


Click Browse to verify that the IntranetConnections database exists, and click Next.

If you have restored a copy of your database on a new SQL server, enter the new connection information. The connection information will be used during the upgrade process, as well as by the intranet to access the database after upgrade (used in Railo datasource).

In some cases, the password for the IntranetConnections SQL login can not be read from the setup details file, and you will receive an error message "Login failed for user 'IntranetConnections'. Try the default password "ICu$er&7ogin@20". If this fails, please contact your database administrator.

Screen 4 - Installation


Once you click "Install" the installation will begin and take up to 15 minutes. Note that during this time IIS (Intranet Information Server) will be stopped and all websites on the server, including the intranet, will be unresponsive.

Once the installer is complete, click "Finish" to close it.

Please ensure you continue on to the next step before accessing the intranet. 

4. Clean-Up Old Files (Mandatory)

If you access your site at this time, you will see something similar to the following screen:

A number of older files must be deleted for the upgraded intranet to work properly. To clean up these files:

  • Confirm that the _CleanFiles folder exists under the /Intranet folder on your web server. If this does not exist, you can download it from the links available at the bottom of this article (_CleanFiles.zip). The path to the files inside should look like: /Intranet/_CleanFiles/run.cfm
  • Browse to the downloaded cleanup script under your Intranet site
    • Eg. http://localhost/Intranet/_CleanFiles/run.cfm
      OR http://localhost/_CleanFiles/run.cfm (if website path points directly to the intranet folder)


 You should see the above message and a list of any files that were found and deleted.  It will delete files no longer in use, CF Encoded files, and hot fix files now part of the latest release.

Once this is completed you can delete this folder from your Intranet directory (_CleanFiles). 

Post Upgrade Steps

Once the upgrade is complete, you can immediately start using the intranet. Note that the initial indexing of your intranet content will be done in the background, and can take between 10 to 30 mins depending on the amount of content. During this time, not all items may be returned in search.

The loading of the first intranet request can take up to a minute, as the intranet application loads. Subsequent pages will load much more quickly.

See the Super Search (V13.0) Troubleshooting Guide if there are any errors after upgrading.

Note the application will be rebuilding the search index in the background after the upgrade, and it may take several minutes before all site content is searchable.

Once the upgrade has completed successfully, please do the following:

  1. Launch the intranet site and browse to the Admin Setup screen.
  2. If you migrated from ColdFusion the scheduled task will be missing.  Click the [create] button to configure this in the Railo Web Administrator.
  3. Verify web services are working and your maintenance expiry is up to date by running the scheduled task.
  4. Check to see if any patches are available for 13.0 (It is recommended you apply these once the search indexing is complete)
  5. If you migrated to a new server: Navigate to the intranet on the new server using the URL you will be directing users to going forward. Go to Admin > Setup > look at the Web Location. If you see any messages about the web location not matching, click 'update locations' to update all link references to the old server and point them to the new one.


Referenced by:

Have more questions? Submit a request


Article is closed for comments.