Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Manual migration of local ScanMail for Exchange (SMEX) 12.0 database to a remote SQL server

    • Updated:
    • 22 Apr 2016
    • Product/Version:
    • ScanMail for Exchange 12.0
    • Platform:
    • Windows 2008 Standard 64-bit
    • Windows 2012 Standard
Summary
When migrating local database to remote databse, SQL account authentication is used and not Windows authentication. This follows SMEX 11.0.

Learn how you can manually migrate the SMEX 12.0 database to a remote SQL server.

Details
Public

Scenario 1: For SMEX 12.0 which is upgraded from SMEX 11.0, Please refer to KB 1095817.

Scenario 2: For SMEX 12.0 fresh installation:

  1. Click the Start button and type "services.msc" in search program and files field. The Services window will appear.
  2. Stop the following services:
     
    On a cluster environment, the ScanMail resource in the cluster administrator also needs to be offline.
    • ScanMail for Microsoft Exchange Master Service
    • ScanMail for Microsoft Exchange System Watcher
  3. Go to the ScanMail for Microsoft Exchange Master Service properties and see if it has dependencies on the SQL Server (ScanMail).

    ”XXX”

  4. Remove the dependency to the SQL server:
    1. Open cmd.exe and type:

      sc config ScanMail_Master depend= ""

    2. Verify if SMEX still depends on the SQL server after the command was entered. The Dependencies window should look like this:

      ”XXX”

  5. Detach the ScanMail database use SQLManagementStudio:

    ”XXX”

  6. Stop the SQL server (ScanMail) service.
    1. Go to the %SCANMAIL_INSTALL_PATH%\data folder, wherein “%SCANMAIL_INSTALL_PATH%\data” is the actual SMEX installation path.
    2. For cluster servers, use the following path:

      \%SCANMAIL_INSTALL_PATH%\ data

    3. Repeat the step for each virtual server instance.
  7. Copy the 2 database files under the folder %smex install root%\Trend Micro\Smex\data to their respective folders on the remote SQL server.
  8. Login the remote database server and use SQL admin account (for example, SA account) that matches with dbcfg_SQLUserId.txt in step 11 to login the SQL management studio.
  9. On SQL Server Management Studio, right-click Databases and select Attach.

    ”XXX”

    ”XXX”

  10. Go back to the ScanMail server and modify the SMEX database profiles by using the path: \%SCANMAIL_INSTALL_PATH%\config.

    For clusters, use the path:\%SCANMAIL_INSTALL_PATH%\config\.

  11. Modify the following files to reflect the new remote SQL.
     
    Always back up the files before making any modifications.
    • dbcfg_DatabaseInstance.txt

      This should match the remote SQL instance where you attached the ScanMail databases.
      For example : dbcfg_DatabaseInstance.txt is set to 192.168.141.91\SQLINSTANCE

    • dbcfg_IsSeperateSQLServer.txt

      The value should be 1.

    • dbcfg_SQLUserId.txt

      This should include the UserID you created for the ScanMail databases.
      For example: SA

    • dbcfg_ServerName.txt

      This should match the ScanMail server name.

    • dbcfg_SecurityString.txt

      This should include the following: Persist Security Info=True;

    • dbcfg_InstallPath.txt

      This should include the correct path where the .mdf file is located on the remote SQL server.
      For example : C:\SMEX

    • dbcfg_SQLPassword.txt

      To generate the encrypted password:

      1. Go to the \%SCANMAIL_INSTALL_PATH%\SMEX folder.
      2. Remove the content for dbcfg_SQLPassword.txt.
      3. Type the command:

        toolChangeRemoteDBPWD.exe -p < sharedisk>\%SCANMAIL_INSTALL_PATH%\config\ -c Current SQL Password

      4. Type toolChangeRemoteDBPWD.exe /? to view the usage info.
    • dbcfg_SQLServerAuthenticationMethod.txt

      Local database always uses Windows authentication. If the remote database is changed to SQL account, change this file from “1” to “0”.

    • The following config files should be blank and not contain any information:
      • Dbcfg_ReportInitFileName.txt
      • Dbcfg_LogInitFileName.txt
      • Dbcfg_ConfInitFileName.txt
  12. Start the following services:
    • ScanMail for Microsoft Exchange Master Service
    • ScanMail for Microsoft Exchange System Watcher
  13. Open the ScanMail console and verify if all the configurations are there and no errors on the console. The console should look like the following screenshots:

    ”XXX”

    ”XXX”

    ”XXX”

  14. Uninstall the SQL Express when necessary.
Premium
Internal
Rating:
Category:
Configure; Troubleshoot; Migrate
Solution Id:
1114008
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.