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

Create a technical support case if you need further support.

Collecting the User-Mode Hooking (UMH) module's service and driver logs in OfficeScan (OSCE)

    • Updated:
    • 28 Dec 2016
    • Product/Version:
    • OfficeScan 10.6
    • OfficeScan 11.0
    • OfficeScan XG.All
    • Platform:
    • Windows 10
    • Windows 2008 32-Bit
    • Windows 2008 64-Bit
    • Windows 2012
    • Windows 7 32-Bit
    • Windows 7 64-Bit
    • Windows 8 32-Bit
    • Windows 8 64-Bit
    • Windows 8.1 32-Bit
    • Windows 8.1 64-Bit
Summary

This article introduces how to collect the UMH service and driver logs if required.

UMH is an engine in OSCE that supports the enhanced ransomware solution. It is installed in the Common Client Solution Framework (CCSF) service as a module. It provides API events for other modules, such as Behavior Monitoring, Predictive Machine Learning, etc. Those modules will make decisions according to the provided API events from UMH.

Below is the installation path for UMH in OSCE:

<OfficeScan Agent Installation Path>\CCSF\MODULE\20019\

UMH has been involved since OfficeScan 11.0 Service Pack 1 Critical Patch 6054 (Ransomware CP) and OfficeScan XG.

Details
Public

To collect the logs:

  1. Copy\PCCSRV\Private\LogServer\ofcdebugEx.ini from the OSCE server to C:\ in the OSCE agent.
  2. Rename ofcdebugEx.ini to ofcdebug.ini.
  3. Unload the OSCE agent.
  4. Open a command line. Run as administrator.
  5. Run the following prompt: net stop tmumh (Stop UMH driver).
  6. Download DebugView from the following link: DebugView v4.81.
  7. Open Dbgview.exe (Run as administrator), and check Capture Win32, Capture Global Win32, Caputer Kernel, Enable Verbose Kernel Output, Pass-Through, and Capture Events from the Caputer dropdown list.

    Caputer dropdown list

  8. Reload the OfficeScan Agent, and make sure that the tmccsf.exe, tmbmsrv.exe, ntrtscan.exe and tmlisten.exe processes are running. Also make sure that tmumh is running (sc query tmumh).
  9. Reproduce the problem.
  10. Collect the following logs:
    • C:\CCSF_DebugLog.log
    • C:\osceDB.log
    • Driver log from Dbgview.exe

    Collect logs for UMH

  11. Get the following UMH-related binary files:
    • \CCSF\module\20019
    • %windir%\system32\tmumh
    • %windir%\syswow64\tmumh
    • %windir%\system32\drivers\tmumh.sys
  12. Get the following UMH-related registry keys:
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tmumh
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\GlobalFlag
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options
    • HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows
Premium
Internal
Rating:
Category:
Troubleshoot
Solution Id:
1115440
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.