The steps below are for converting the collaboration database using Microsoft's Migration Utility. The IMail Utilities package now contains a Migration tool that is the preferred utility for systems running 11.03 and higher. You can find instructions on how to use the new utility here: IMail Collaboration Migration Utility
To use the Microsoft Migration Utility, follow the steps below:
NOTE: IMail uses the WorkgroupShare.mdb file to store personal contacts, which uses Access by default. Below are the instructions for converting this database from Access to SQL or SQLExpress.
This article is for IMail running on Server 2003 or 2008. If you are running Server 2000, please see Converting Web Mail Personal Contacts from Access to SQL or SQLExpress on a 2000 Server.
1. If IMail 11 was installed before April 18th, 2009, redownload the installer from MyIpswitch and run it in repair mode.
2. Download and install SQLExpress and the SQL Management Studio. (If you already have SQL, this can be used).
a. Once done open Computer management. Make sure SQL protocols are running:
b. Make sure all of the SQL protocols are enabled:
NOTE: You will have to restart the SQL services before they take effect.
c. Create the SQL aliases so the DSN can connect to it (use your IP and computer name):
3. Once installed, open the SQL Server Configuration Manager.
4. Expand SQL Server Network.
5. Highlight Protocols for SQLExpress.
6. Right-click TCP/IP and choose Properties.
7. On the IP Address tab, under the IPALL section, set the TCP Dynamic Ports to 2874, and the TCP Port to 1433.
8. Once set, save and close the SQL Server Configuration Manager console.
9. Open the SQL Management Express Studio and create a new database named WorkgroupShare. (When prompted for login information, make sure to use machine_name\SQLEXPRESS for the 'Server name' section and not an IP address.)
10. Close the console.
11. Download and install SQL Server Migration Assistant for Access.
12. Once installed, follow the registration process (Required) for SSMA for Access.
13. Once registered, open SSMA for Access and add the old WorkgroupShare.mdb file.
14. Next, point to the newly created WorkgroupShare SQL database created in step 8.
15. Once the conversion completes, exit the console. Use defaults on all pop-up screens.
16. Open SQLExpress, Expand 'Security' and highlight 'Logins'. Right-click and create 'New Login'.
17. Add the user NT AUTHORITY\NETWORK SERVICE. Leave Windows Authentication checked.
18. Next add the IIS_WPG account and the IIS Anonymous User set up for your Web Mail web sites. This is usually IUSR_machinename.
a. Make sure you have Groups selected when adding the Following user group: IIS_WPG user group
19. Now expand 'Databases\WorkgroupShare\Security'.
20. Highlight 'Users', Right-click and add 'New User'.
21. Add the 'NT AUTHORITY\NETWORK SERVICE' user.
22. In the 'DB Role Membership' section, grant this user the db_datareader, db_datawriter, and db_owner permissions.
23. Repeat steps 20 and 21 for IIS_WPG and the 'IUSR_machinename' user.
24. Once this has been saved, exit the SQLExpress console and reboot the server.
25. Once the server has rebooted, open the Data Source (ODBC) console from Administrative Tools.
26. Click the 'System DSN' tab.
27. Select the current WorkgroupShare DSN, click the 'Configuration' button and rename it to 'WorkgroupShareOld'
28. Back on the 'System DSN' tab, select 'Add', and select SQL Server.
29. Next click the 'Client Configuration' button, uncheck the 'Dynamically determine Port' check box, and make sure the Port is set to 1433.
30. Finish the setup.
31. Edit HKEYLM\Software\Softalk\WorkgroupShare\Setup\DBType (Dword) to 1 (this may have to be created)
32. Remove unnecessary constraints added by the convertion utility.
33. Restart IIS.
NOTE: If you are running IMail v11.03 or higher, you will need to do the next step to prevent a repair or upgrade form overwritting the DSN to the old configuration. If you are running IMail v11.02 or older, you can skip the next step.
34. Run the MSI install that was used to install the current version, and select Modify. Do not change any of the values and allow the install to complete. (You can also do this from the AddRemove Ptrograms). this will allow the install to detect the change and update the internal ODBC configuration so it will be kept in an upgrade or repair in the future.