How to stop Trend Micro Solution Platform service

Since renewing I received an updated version.

This version will not let me stop the 'Trend Micro Solution Platform' service or flag it for a manual start.

Do I need to remind Trend Micro that this IS MY COMPUTER.  It's my hardware and you're invited into the system.  Do not assume to take control of my environment.

How do I stop this from running.  I do not need it running all the time.  Some of us have knowledge far advanced than others and are more capable of operating in a safe manner than 99.99% of the dumb arses out there.

It slows down operation of my equipment.

Don't make me hack it out.

Gartner Peer Insights reviews constitute the subjective opinions of individual end users based on their own experiences, and do not represent the views of Gartner or its affiliates.

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open

bakiba opened this issue

· 1 comment

Comments

Expected Behavior

Current Behavior

When I RDP using mRemoteNG (v1.76/v1.77) from my Windows 10 PC to Windows 2016 Jump box that has Trend Micro Deep Security installed and I try to RDP (using native mstsc) from that box to another Windows server, the RDP session hangs at the credential window. If I stop the Trend Micro Solution Platform Service (Amsp), issue stops.
Another strange thing I noticed is that if I close the RDP session in mRemoteNG while the session from Jump box to Target Windows server is hanging, and I re-connect to Jump server via mRemoteNG again, the hanging session comes back to life and then all works fine until I properly sign out from Jump server.

Possible Solution

The two workarounds I figured for now:

1. Stop the Trend Micro Solution Platform Service (Amsp) service on Jump server
2. Close the session to Jump server (mRemoteNG) while the session from Jump server to target server is hanging and re-connect session to Jump server (mRemoteNG).

Steps to Reproduce (for bugs)

1. use mRemoteNG to RDP (all default setting) to Windows 2016 server (Jump server) with Trend Micro Deep Security installed
2. from Jump server open RDP (mstsc) session to another Windows 2016 server (Target server) - session to Target server will hang after entering credentials
3. close mRemoteNG session to Jump server
4. re-connect mRemoteNG session to Jump server - session to Target server will continue

Context

Your Environment

• Version used: Tried mRemoteNG-Portable-1.76.20.24669 and mRemoteNG-Portable-1.77.0.41307
• Operating System and version (e.g. Windows 10 1709 x64): my workstation Windows 10 build 1909 (no Trend Micro), Jump server and Target server Windows 2016 both running Trend Micro Deep Security (can't figure how to determine version of that crap).

Hi Bakiba

Does this issue happen as well when you use mstsc to connect to the Jump System or not? To me it looks like as if TMDS just tries to block an outgoing RDP session which was generated when a user is connected through RDP, and as soon as the initial connection is supended TMDS let's the connection happen.

This might be solely Trend Micro's fault and I expect it to have nothing to do that you use mRemoteNG to connect to the Jump System (prove me wrong). I suggest you contact your server/security admin and try to resolve this issue with Trend Micro directly (you don't pay a large sum of maintenance fee only to use it without support by the vendor). In my experience with Trend Micro in general they did their best to get such things resolved.

Regards
Simon

2.5.9.2. Turning off the Function¶

If necessary, please restart the function and stop one.

2.5.9.2.1. Turning off the Processing upon the OS¶

It may be possible for you to invalid a function at the Operation scree, while if doing so, it may take longer since shutting off the function won't execute until the next heartbeat.

If you would like to immediately stop the function, you can stop the one just by directly stopping the target process.

2.5.9.2.1.1. Malware Protection¶

To stop the anti-malware function You can temporarily stop the function by stopping the following services.

● Windows

Start "Server Maanger" , then shut off Trend Micro Solution Platform.

Execute the following commands.

2.5.9.2.1.2. Firewall & Intrusion Prevention Functions¶

To stop the firewall and intrusion prevention function You can temporarily stop the function by stopping the following services.

● Windows

Open the property of the NIC, whose traffic will correctly communicate. Next, untick either box of Trend Micro DSA Filter Driver (Windows 2003) or Trend Micro LightWeight Filter Driver (Windows 2008).

Execute the following commands.

2.5.9.2.1.3. Main Functions¶

If desired to access to the Management Server, stop this service.

● Windows

First, boot "Server Manager, next shut off "Trend Micro Deep Security Agent".

Execute the following commands.