2. Note which versions the portal is currently on so you may install at the same versions on the new server. This information can be found by going to Reports > Portal Framework > System Summary > Blue section. The blue section will denote what versions of the portal framework and all modules are currently on.

3. Contact Passageways Technical Support Team by emailing support@passageways.com or calling 765-535-1880 and have them clear out your entitlement. This step will allow you to install a new portal on a different server than the portal was previously installed or updated on.

10. On the User Mapping tab, for each database you restored, click the checkbox in the Map column to map the user to the database and then click db_owner at the bottom to make the user the owner. Click OK when complete.

--End SQL Server Section

11. Copy the Passageways folder from the old server. (Usually located at c:\inetpub\wwwroot\[Passageways/Name of Entitlement])

12. Paste the Passageways folder to the new server. (In the folder c:\inetpub\wwwroot\)

13. Change the SQL server and database names in the connection strings in all of the following locations:

a. Web.config (c:\inetpub\wwwroot\[Passageways/Name of Entitlement])

i. Portal Connection String

ii. Documents Connection String

b. Module configs (some modules may not apply to customers) (c:\inetpub\wwwroot\[Passageways/Name of Entitlement]\Modules\[Module]\)

14. If the Copy and Paste locations are not the same exact path on the server, you will need to change the folder paths in the module config files. For example, older portals would be installed using ‘Passageways’ while portals installed using Expressway would be installed with ‘Production Portal’, ‘Test Portal’, or ‘Board Portal’.

16. In the Sites section, locate the portal that was just installed and click it.

17. Click the Basic Settings... link that appears on the right side under Actions.

18. Change the Physical Path to the location you pasted to in step 12 and click OK.

19. If a binding is in use, the DNS entry will need to be updated to reflect the new server IP. A DNS flush may be necessary.

20. Stop the website in IIS on the old server.

21. Make sure the new portal site is up and running.

22. On the old server, uninstall the Passageways Programs from Add Remove Programs or from Programs and Features.

23. Delete the old databases from the old SQL server.

24. Delete the old Passageways folder from the old SQL server.

25. Change the folder in the RAP settings file if the website folder is called Passageways. The newly installed folder will be named 'Production Portal' and when applying updates after install, this folder will be updated instead of the 'Passageways' folder where the website is pointing. The RAP settings location varies depending on server version. Below are the possible paths to follow:

26. Also check that mapped or document list folder paths have not been moved and use this article to change the paths from the old server to the new. This should also be done if performing a Sandbox data refresh with Production data so that the URLs point to the correct portal.

Comments

Thanks for posting these instructions. Using them I was able to migrate our Portal to a new server, albeit with help from the excellent Passageways support team. We moved from Windows Server 2008 / IIS 6.0 to Windows Server 2012 / IIS 8.0. We also use Windows authentication and portal documents exclusively. Some of our issues are probably specifically tied to change in IIS versions. Here are a few things that caused me problems.
1) Had to remove these 3 lines from Web.config file "<authentication>
<anonymousAuthentication enabled="true" />
</authentication>"

3) Island images were not appearing. FIX > had to fix the drive letter in path for "fileCabinetContentPath=" entry in web.config file (STEP 13).

4) Unable to access portal documents. FIX > there's a web.config file in C:\inetpub\wwwroot\Passageways\WebDAV that was "messed up". Meredith fixed this for me so I don't know all the changes that were made. I believe the "<authentication mode="Windows" />" tag was removed and " <authorization>
<allow users="*" verbs="OPTIONS" />
</authorization>" was added.