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

Create a technical support case if you need further support.

Using the OfficeScan Policy Export Tool and the Control Manager Policy Setting Import Tool

    • Updated:
    • 17 Oct 2016
    • Product/Version:
    • Control Manager 6.0
    • OfficeScan 10.6
    • OfficeScan 11.0
    • OfficeScan XG.All
    • Platform:
    • Windows 2003 Enterprise
    • Windows 2003 Enterprise 64-bit
    • Windows 2003 Server R2
    • Windows 2003 Standard
    • Windows 2003 Standard 64-bit
    • Windows 2008 Enterprise
    • Windows 2008 Server R2
    • Windows 2008 Standard
    • Windows 2008 Standard 64-bit
    • Windows 2012 Standard
    • Windows 2012 Standard R2
Summary

This article contains the steps in exporting OfficeScan Policy settings and importing these settings into TMCM.

Details
Public

The OfficeScan Server Policy Export Tool helps administrators export OfficeScan policy settings supported by Control Manager 6.0. However, the Policy Export Tool cannot export customized data identifiers or customized DLP templates because these should be manually exported from the OfficeScan console.

The Policy Export Tool only supports OfficeScan 10.6 Service Pack 1 Server. For version 10.6 SP2 and later, the tool is already included in the ..\PCCSRV\Admin\Utility folder. Check the Officescan Policy Export Tool Readme file for more details.

The following settings can be exported for first and second level domains of OfficeScan 10.6:

  • Scan configurations for all scan types (Manual, Real-time, Scheduled, Scan now)
  • Update Agent Settings
  • Web reputation configurations
  • Approved URL list
  • Behavior Monitoring Settings
  • Device Control Settings
  • Data Loss Prevention Settings (previously Digital Asset Control)
  • Privileges and Other Settings
  • Additional Service Settings
  • Spyware/grayware approved list

The Control Manager (TMCM) Policy Import Tool allows administrators to import the OfficeScan settings into Control Manager 6.0 and save the settings as draft policies on the Policy Management screen. This tool is included in Control Manager 6.0 Patch 1 which is available in the Download Center. The package contains the following files:

  • config.php: This configures the Control Manager serverprotocol, port number, and IP address. If TMCM is installed on an IPv6 server, enclose the IP address in brackets. For example, [2001:1:2:3:4:5::6].
  • ImportPolicy.php: Use the Windows command line interface (CLI).
  • Policy: This contains example for the OfficeScan Anti-virus settings.

To export OfficeScan Policy settings:

  1. Download the OfficeScan Policy Export Tool. For 10.6 SP2, the Policy Export Tool is already available under ..\PCCSRV\Admin\Utility\PolicyExportTool folder.
  2. Copy PolicyExportTool.zip and extract the contents to any folder on the OfficeScan 10.6 Service Pack 1 server.
  3. Open a command line prompt, point to the PolicyExportTool directory.
  4. Type "PolicyExportTool.exe". The two subfolders, PolicyClient and PolicyDLP, will exist under the PolicyExportTool folder after a successful policy export.

To import the policy settings in TMCM:

  1. On the OfficeScan server, export the OfficeScan Anti-virus and DLP settings using the OfficeScan setting export tool.
  2. Place the PolicyClient and PolicyDLP folders created from the export tool in the Control Manager\WebUI\WebApp\widget\common\tool\PolicyImport folder.
  3. Modify the config.php file with the information of the Control Manager server you are currently using.
  4. Execute the ImportPolicy.php file using the Windows CLI. Use the following command:

    php.exe ImportPolicy.php --path="Foldername"

    • If Administrators want to import the Officescan antivirus settings for all domains, use the command:
      • 32-bit environment:

        C:\Program Files\Trend Micro\Control Manager\WebUI\WebApp\widget\common\tool\PolicyImport>”c:\Program Files\PHP\PHP.exe” ImportPolicy.php --path="<Path to Control Manager>\Control Manager\WebUI\WebApp\widget\common\tool\PolicyImport\PolicyClient"

      • 64-bit environment:

        C:\Program Files (x86)\Trend Micro\Control Manager\WebUI\WebApp\widget\common\tool\PolicyImport>”c:\Program Files (x86)\PHP\PHP.exe” ImportPolicy.php --path="<Path to Control Manager>\Control Manager\WebUI\WebApp\widget\common\tool\PolicyImport\PolicyClient"

    • If Administrators want to import the Officescan DLP settings for all domains, use the command:
      • 32-bit environment:

        C:\Program Files\Trend Micro\Control Manager\WebUI\WebApp\widget\common\tool\PolicyImport>”c:\Program Files\PHP\PHP.exe” ImportPolicy.php --path="<Path to Control Manager>\Control Manager\WebUI\WebApp\widget\common\tool\PolicyImport\PolicyDLP"

      • 64-bit environment:

        C:\Program Files (x86)\Trend Micro\Control Manager\WebUI\WebApp\widget\common\tool\PolicyImport>”c:\Program Files (x86)\PHP\PHP.exe” ImportPolicy.php --path="<Path to Control Manager>\Control Manager\WebUI\WebApp\widget\common\tool\PolicyImport\PolicyDLP"

     
    The creator for the imported draft policies will be the account created during the Control Manager installation (for example the root account).

    Import Policy Tool Screen

    Click image to enlarge.

    After the upload is complete, it will appear in the Control Manager Policy Management console:

    TMCM Policy Window

    Click image to enlarge.

    The generated policies are policies from each of the domains of the Officescan server. By default, the targets of created policies are set to None to prevent deployment of the policies. Once administrators have reviewed the policies, they can modify the policy and target to other machines.

Premium
Internal
Rating:
Category:
Configure
Solution Id:
1061126
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.