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

Create a technical support case if you need further support.

Migrating Control Manager (TMCM) database via command line

    • Updated:
    • 8 Oct 2015
    • Product/Version:
    • Control Manager 6.0
    • Platform:
    • Windows 2003 Compute Cluster Server
    • Windows 2003 Datacenter Server
    • Windows 2003 Datacenter Server Edition 64-bit
    • Windows 2003 Enterprise Server
    • Windows 2003 Standard Server Edition
    • Windows 2003 Standard Server Edition 64-bit
    • Windows 2003 Storage Server
    • Windows 2003 Web Server Edition
    • Windows 2008 Enterprise
    • Windows 2008 Standard
Summary

Use this procedure to migrate a TMCM installation given the following environment:

  • TMCM 3.5 was upgraded to version 5.0/5.5/6.0.
  • The upgraded TMCM 5.0/5.5/6.0 is using the TMCM 3.5 MSDE/SQL 2000 database.
  • TMCM database is called db_ControlManager.
  • TMCM 5.0/5.5/6.0 is now installed in C:\Program Files\Trend Micro\Control Manager.
  • Windows 2003 SP2 with IIS 6.0 and ASP.NET v2.0.50727 is being used.
  • The SQL user is named "tmcm", or some other name aside from the default 'sa' account.
  • SQL 2005 is installed in Mixed Mode.
  • SQL 2005 is accepting Local and Remote Connections, with TCP/IP and Named Pipes enabled.
Details
Public

To migrate the TMCM database via command line:

Refer to Microsoft article Move a Database Using Detach and Attach (Transact-SQL) for additional information on how to attach/detach/move a Database.

These steps should be done with the assistance of a SQL Database Administrator, if available:

  1. Log off from the TMCM console and then shut down these TMCM services:
    • Trend Micro Control Manager
    • Trend Micro Management Infrastructure
    • Trend Micro Common CGI

    It may take a while (5-10 minutes) to terminate all connections. If you do not want to wait that long, you can restart the SQL server service instance.

  2. On the SQL server where the original TMCM service is installed, execute the following via command line:

    hese commands may also be executed via SQL Query Analyzer.

    1. Type “c:\osql” –E then press ENTER.
    2. Type “exec sp_detach_db 'db_controlmanager', 'true';” then press ENTER.
    3. Type “go” then press ENTER.

    If a message similar to the one below appears, then some processes may still be using the TMCM database when you terminated the connection:

    Cannot detach the database 'db_controlmanager' because it is currently in use.

    Make sure that all services are stopped, or you can restart the SQL Server service/instance.

  3. Run the command again. You will get the following message once the database has been detached:

    The database 'db_controlmanager' does not exist. Use sp_helpdb to show available databases.

  4. Copy the db_controlmanager.mdf and db_controlmanager_log.ldf files of the SQL 2005 server to the directory of your choice.

    For example:

    C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data

    The default installation for the database if you have MSDE installed is C:\Program Files\TrendMicro\MSDE2000\DataMSSQL\Data. If you were running SQL 2000 Server, then it would be where your data directories are.

  5. Execute the following command on the SQL 2005 server: 

    These commands can also be executed via an SQL Query Analyzer.

    1. c:\ osql –E
    2. USE master;
    3. GO
    4. CREATE DATABASE db_controlmanager ON (FILENAME = 'C:\path\to\db_controlmanager.mdf'), (FILENAME = 'C:\path\to\db_controlmanager_Log.ldf') FOR ATTACH;
    5. GO

    The SQL Server engine will automatically upgrade the database from 2000 to 2005. Attaching database from a lower to a higher version is fine, but attaching database from a higher to a lower version is not possible.

  6. Launch the Microsoft SQL Server Management Studio. The db_controlmanager database should be visible. This is with the assumption that you have the 'tmcm' SQL username login already created. Otherwise, create one at this point.
  7. When you expand the Databases > db_controlmanager > Tables node, you will notice that all the schema of the tables are [dbo]. If not, take note of the schema and then make the appropriate value adjustment for step 4 (on the assignment of the default schema).
  8. Go to Databases > db_controlmanager > Security > Users and then do the following:
    1. Add 'tmcm' user and map it to the 'tmcm' log in.  If the you wanted  to use another username, then use that name

      Use the same user name in both SQL servers.

    2. Set the default schema to [dbo].
    3. Set the database role membership to db_owner.
  9. As an option, you can go to Security > Logins > tmcm and set the Default Database option to db_controlmanager under the General page.
  1. On the TMCM server, go to Administrative Tools > Data Sources (ODBC) > System DSN
  2. Modify the ControlManager_Database DSN and change the SQL server location to the appropriate settings of the following:
    • If you are using an instance:
      [hostname/IP address of the server]\instance
    • If you are not using an instance:
      [hostname/IP address of the server]

    Use SQL server authentication and on the Test Data Source the following should occur:

    Test Completed Successfully.

    Note the following changes:

    1. Make sure that you selected the SQL server location, indicating the instance name if needed.
    2. After selecting the SQL server location, click Next. There will be a Client Configuration button.
    3. Click on the Client Configuration button, and change the Network Libraries option from TCP/IP to Other.
    4. Server Alias must be equal to [hostname/ipaddress of the server ]\instance name, if you are using an instance or [hostname/ipaddress of the server] if you are not.
    5. File name must be uqual to dbmssocn, parameters = [hostname/ipaddress of the server]\instance name, if you are using an instance, or [hostname/ipaddress of the server] if you are not.
  3. On the TMCM server, run DBConfig tool. Open the Command Prompt  and go to this directory:

    <drive:>\Program Files\Trend Micro\Control Manager\DBConfig

    Refer to KB article Changing the Control Manager (TMCM) 5.0/5.5 database configuration settings about the details on how to use the DBConfig tool.

  4. Execute this sample command:

    DBConfig -DBName="db" -DBAccount="sqlAct" -DBPassword="sqlPwd" -Mode="SQL" -DBHost="10.10.1.5"

    Notes:

    • Default Mode is the SQL authentication mode used. Mode="WA" is necessary when configuring Windows authentication.
    • The Windows account must belong to the Administrators group.
Premium
Internal
Rating:
Category:
Upgrade; Migrate
Solution Id:
1055310
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.