Instructions for upgrading and moving the MessageStats Product to a Windows 2003 Server:
1. Confirm that the Windows 2003 Server has all the required software installed prior to installing MessageStats (SQL, IIS with ASP's and Outlook with the latest service packs, configured with a Mapi profile and logged on to at least once).
2. Download MessageStats from SupportLink (http://questsupportlink.quest.com/prod_upgrade_alert.asp) and upgrade the original installation on the Windows 2000 Server.
3. Install the newest version of MessageStats on the Windows 2003 Server after all the software requirements have been met.
4. Now there should be two instances the database: the original install on a Windows 2000 Server and the newly installed on a Windows 2003 Server.
5. The SQL 2000 Server's Client Tools are required to move the original MessageStats Database from Windows 2000 Server to the Windows 2003 Server. They can be installed on the Windows 2003 Server from the SQL 2000 Server CD setup by selecting to only install the Client Tools (if using MSDE).
6. Once the SQL 2000 Client Tools have been installed on the Windows 2003 Server, select Start | Programs | Microsoft SQL Server | Enterprise Manager.
7. Using Enterprise Manager running on the Windows 2003 Server, expand Microsoft SQL Server | SQL Server Group | (local) (Windows NT). Now expand the Database Folder and there should be a MessageStats Database. Right Click the MessageStats Database, select All Tasks | Detach Database and click OK. This will detach the newly created empty database.
8. Keep Enterprise Manager open, right click on SQL Server Group, select New SQL Server Registration, click Next, now find the original MessageStats Windows 2000 Server Name in the list, highlight it, click Add, click Next 3 times to use default settings and then Finish. This should add the original MessageStats Windows 2000 Server MSDE.
9. Now expand Microsoft SQL Server | SQL Server Group | 'ServerName' (Windows NT). Now expand the Database Folder and there should be a MessageStats Database. Right click the original MessageStats Database, select Properties, select the Data Files tab, note the Location and name of the .mdf file and do the same under the Transaction Log Tab. This way the .mdf and .ldf files can be copied to the Windows 2003 Server for reattachment.
10. Right Click the MessageStats Database, select All Tasks | Detach Database and click OK. This will detach the original database so .mdf and .ldf files can be copied over from the noted location to the Windows 2003 Server.
11. Once these files have been copied over and saved to a location of choice on the Windows 2003 Server, Enterprise Manager will need to be opened again in order to reattach.
12. With Enterprise Manager running on the Windows 2003 Server, expand Microsoft SQL Server | SQL Server Group | (local) (Windows NT). Right Click on the Database Folder, select All Tasks | Attach Database, click the Ellipses Button (...) and now locate the copied original MessageStats Database .mdf and .ldf files and select only the .mdf file and click OK.
13. Now see that both .mdf and .ldf files are listed in the window so click OK to attach the original MessageStats Database.
14. Once attached, confirm that the Console and Reports can connect successfully.
