Services left behind

thilde

We have a vendor who uses LogMeIn Rescue to connect to and support an application on our network. Each time they use it it creates a new service entry on the server. It cause aggravatio because our monitoring system sees this new services. Is there anyway to have the services be removed after they disconnect or have it not create new service entries every time they connect.

 

Below is an example of the service names. Only  the second and last services run but all are set to automatic start.

 

LogMeInRescue (04e57c7e-bfe7-46b4-bb35-4e5142ca46f6

LogMeInRescue (1253959)

LogMeInRescue (2e3d2ca2-9029-4624-b724-17d5d417bd14)

LogMeInRescue (4930a63d-0489-4b3c-98cd-b21bcf57ff0b)

LogMeInRescue (72c3bd69-9c2e-4bff-9d38-9c1ba0af683d)

 

paleRider67

Hello Thilde,

 

These services are removed automatically when the Rescue client applet is closed. In some cases they get stuck there when the service isn't closed properly (e.g. killed from task manager for example).

 

In order to remove them, a useful command is:

 

sc delete servicename

 

This works better if command prompt is run as administrator

 

To get the full name of the service, run services.msc, right click on the service / properties, copy the name.

 

This can also be done via script so you can flush the services from time to time. There's an example from Mian here: http://stackoverflow.com/questions/9291915/remove-install-windows-services-using-batch

 

Hope it helps!