Impero vs Senso vs NetSupport vs Others?

[OLPTech]

We haven't had any issues on 24H2. Although we did used to have issues with the Impero service not starting, we now rarely have this issue at all since we've done the following ( I wrote this before on a different forum) :

 

 

We did have the problem of machines showing offline on Impero and unable to communicate with the Impero Server, it was down to the ImperoClientSVC service failing to start.

Since we've rolled out what seems now a permanent 'hotfix' I don't think this issue occurs much at all anymore, now I only see about 1 device every 5/6 months with this issue instead of multiple devices not working daily.

We created a GPO that disables the ImperoGuardianSvc service, we had ImperoServiceStarter originally disabled too so if there are still devices experiencing the issue disabling both should help.

 

 

[Warwick_Tech]

On 25/04/2025 at 14:04, liamread2000 said:

We haven't had any issues on 24H2. Although we did used to have issues with the Impero service not starting, we now rarely have this issue at all since we've done the following ( I wrote this before on a different forum) :

 

 

We did have the problem of machines showing offline on Impero and unable to communicate with the Impero Server, it was down to the ImperoClientSVC service failing to start.

Since we've rolled out what seems now a permanent 'hotfix' I don't think this issue occurs much at all anymore, now I only see about 1 device every 5/6 months with this issue instead of multiple devices not working daily.

We created a GPO that disables the ImperoGuardianSvc service, we had ImperoServiceStarter originally disabled too so if there are still devices experiencing the issue disabling both should help.

 

 

 

Why disable the guardian service and rely on the service starter? It was my (admittedly possibly wrong) assumption all the service starter did was restart the Guardian if it failed it's 3 base attempts (?)

[OLPTech]

My interpretation of it when spent months helping Impero support is that Impero Service Starter checks that ImperoClientSVC and ImperoGuardianSVC are started, if they are not then it will start them.

 

However those 3 services all running at the same time sometimes caused the ImperoClientSVC service to fail to start, we and Impero found that across our 4 environments that disabling the Guardian service solved the problem in pretty much all instances.