Migrate Intranet v13.0 to a new server

Introduction

While running version 13.0, if you decide to migrate the intranet to a new server (cloud hosted provider, newer server), the following steps can be used. 

Note: this is only for migrating version 13.0 to a new server, this does not include upgrade instructions from previous versions.

 

Migrating version 13.0 to a new server

  1. Verify the web server meets the server requirements shown here.
  2. Verify the web server has the correct server roles installed shown here (You may or may not need Windows Authentication, refer to your existing server to see whether or not this will be required on your new server.
  3. Install the Corporate installer found here. Note: This installer will require you to run as a local administrator on the web server. To be safe, we recommend right-clicking on the installer and clicking 'run as administrator' as well.
  4. You should see the notification that the software was installed successfully once you have completed the installation wizard.
  5. Restore and overwrite the fresh 13.0 database with your current production server's database.
    When restoring, under options, ensure Overwrite the existing database is selected.

    databaseoverwrite.png

  6. Run the following SQL against the restored database, to ensure database login is connected to server login:

    exec sp_change_users_login 'auto_fix','intranetconnections';

  7. Stop the IIS Server and Railo Server service
  8. Rename the Intranet folder on your new server (typically located in C:\inetpub\wwwroot\Intranet). Eg. 'Intranet_old'
  9. Copy the Intranet folder from your existing production server into the wwwroot folder (to replace the Intranet folder you renamed in step 8).
  10. If step 9 has been done correctly, there should be only one Intranet folder:
    e.g. C:\inetpub\wwwroot\Intranet<files and folders> NOT C:\inetpub\wwwroot\Intranet\Intranet\<files and folders>
  11. Start the Railo Server service and the IIS server

Now that your site has been configured, there are some additional considerations to make.

 

Update the Intranet's URL (Web Location)

The intranet using the Web Location setting to determine how to create relative URLs. If you have a custom URL for the intranet, or have moved the intranet to a new server (and are not updating the DNS entries), follow these instructions to update the Web Location.

Update Web Location

  1. Update the binding for the site in IIS to use the new URL if not already done.
    Note: This step is not necessary if you are just removing "/Intranet' for the URL as detailed above.
  2. Log into the intranet using the new URL as an administrator (e.g. kellybristow / password)
  3. Click the Admin link near the top right ( or go directly to this page http://<new URL>/admin/sitesettings/site_settings.cfm?tabidx=1)
  4. It should show the admin screen, with the Setup tab displayed by default.
  5. Scroll to the bottom of the page you you should see a Web Location option under System Information, Intranet Application.
  6. If the new URL is different from the current Web Location, you will see warning text in red, display the new and old URL.
  7. Click the "Update Web Location" button to update the intranet to use the new URL.

Update Scheduled Task

In addition to updating the web location, you must also update the scheduled task in either the Railo or ColdFusion administrator.

  1. Login to the Railo Administrator ( http://<server name>railo-context/admin/web.cfm
    OR
    Login to the CF Administrator ( http://<server name>/cfide/administrator/index.cfm
  2. Default password is usually "connections"
  3. Find the Schedule (or Scheduler) menu item.
  4. Change the URL to match the server's new URL.

 

Final configuration steps

  • Re-index the site data: This can be done by going to admin > Site Search > click 're-index my site data'. 
  • The intranet is now ready for use while the search index is running
Have more questions? Submit a request

0 Comments

Article is closed for comments.