Migrating XMPro from one Windows server to another

1. Install IIS and/or enable IIS features on new server.  Refer to KB article Setting up IIS 8 for XMPro on Windows 2012 server
2. Register msscript.ocx

• Open the command prompt (CMD Shell). If UAC (User Access Control) is enabled, run the CMD Shell with elevated privileges (right-click, Run as administrator).
• Run the following command from the command prompt:

For 32-bit:

Windows Vista/7:

%windir%system32regsvr32.exe msscript.ocx

Windows Server 2008:

%systemroot%system32regsvr32.exe msscript.ocx

For 64-bit:

Windows Vista/7:

%windir%system32regsvr32.exe %windir%SysWOW64msscript.ocx

Windows Server 2008:

%systemroot%system32regsvr32.exe %systemroot%SysWOW64msscript.ocx

3. After the new server is prepared, copy the XMPro folder across from the old server to the new server.
4. Open IIS Manager and create a new application pool.
5. Under Default Web Site, add new application using:
   • Same Alias as on the old server
   • Select the new Application Pool
   • Specify the Physical Path to location where XMPro folder is copied to on the new server
   • Ensure required authentication (windows or xmpro) is enabled for the website that the site is meant to be running under. If windows, ensure the windows authentication option is enabled.
6. Leave XMPro on new server still connected to the old database.
7. Ensure that XMPro on new server can access the old sql server (and the IP address is not blocked) – a simple ping from command prompt can generally get this done.
8. Setup the security for the site.config and “upload” folder (and any custom folders that needs this access).
9. Login to XMPro application on the new server to ensure application is up and running.
10. Backup SQL databases (XMPro core and any Master DBs) on the old server, copy and restore them on the new SQL server.
11. Ensure that the SQL logins (used in the SQL connection strings) are recreated on the new SQL server. Check this by using SQL management studio that you can login to the new server and access those databases.
12. On the new XMPro server, update the connection strings to the new SQL server.
13. Reset IIS on new server as the connection strings have now changed.
14. Login to the new XMPro application and verify that the application is running and can connect to databases on new SQL server.
15. Final checks: ensure the IIS is setup as configured on the oldserver i.e., check the app pool and website and how it was configured (using InProc, ASP_State, etc).