Impero service stops randomly

[Griff]

Weird one and thought I would post here before I start trawling through event viewer logs. This happens maybe couple of times in a day one, machines will just drop off Impero completely. I have to run a remote script that restarts the Impero services then they pop back up. Things I have noted;

 

- Randomly happens to all machines

- Always when user is logged in

- Happens more frequently if they are being broadcast to so we get lots of machines stuck in broadcast

- We are running version 8.5.73

 

Any help would be awesome. I have asked Impero about it before but they were kind of stumped as well.

[Steve21]

Yep raised the same issue with them last year and have got nowhere with it since

 

Only suggestion from then has been to disable the impero guardian service to test it, seems less issues occurring but certainly not “right” in any means

 

Super annoying as even the restart of services doesn’t always fix it and requires machines restart, which is controlled my Impero for us normally.: evil cycle of pain!

 

Steve

[GizmoIT]

Interested in this. We are running 8.5.61 an experience similar issues

[mavhc]

Same problem, it just gives up retrying to connect for some reason

[Oaktech]

Happens all the time - I just have a scheduled script to check and restart the service every 10 minutes.

[mavhc]

What does the script check?

[Griff]

Mine just does this

 

net stop ImperoServiceStarter

net start ImperoServiceStarter

net stop ImperoClientSVC

net start ImperoClientSVC

net stop ImperoGuardianSVC

net start ImperoGuardianSVC

[Oaktech]

What does the script check?

 

I'm not on the site that runs the code today, but I've just done what I did in the first place and nicked the code off Stack Overflow and subbed in the Impero Service names. I can't remember off the top of my head if there was anything else I needed to do... Source

 

for /F "tokens=3 delims=: " %%H in ('sc query ImperoServiceStarter  ^| findstr "        STATE"') do (
 if /I "%%H" NEQ "RUNNING" ( net start ImperoServiceStarter
)
)

for /F "tokens=3 delims=: " %%H in ('sc query ImperoClientSVC  ^| findstr "        STATE"') do (
 if /I "%%H" NEQ "RUNNING" ( net start ImperoClientSVC
)
)

for /F "tokens=3 delims=: " %%H in ('sc query ImperoGuardianSVC  ^| findstr "        STATE"') do (
 if /I "%%H" NEQ "RUNNING" ( net start ImperoGuardianSVC
)
)

 

Runs silently as a scheduled task every 10 minutes.

[Steve21]

We had a look at a script like that but found that sometimes it’d break where the client service won’t restart until other services have been restarted to, so the script just keeps trying to restart it constantly without actually fixing it l. Service just says failed to start etc

 

Curious to see if anyone else had similar with their scripts too?

 

I did wonder if it’s linked to something stupid like when .NET updates via windows update (if machine hasn’t been restarted to finalise updates) but not really had time to investigate over the basics

 

Steve

[Boredguy]

The Guardian service automatically tries to restart the main ImperoClient service anyway if it's not running, and most times it gets stuck in a startup loop when it doesn't respond.

 

Sometimes stopping all the Impero services on the station for a couple of minutes is enough to make it behave, but it's often easier to just reboot the workstation.

[CHiLL]

We've used Impero for years and this has been a constant across that time. Sometimes the service can be restarted manually, sometimes it can't and throws an error, where it requires a full uninstall of the Impero client, restart and reinstall. We are still on 8.5.17 as it's been relatively stable for us and Impero have a knack of introducing a lot of instability/bugs in new releases, so we took the approach of if it's not broken, don't fix it.

[mavhc]

I have a script that remotely restarts the ImperoClientSVC, not actually checked if the service is stopped though, could just make it auto restart if it is.

[Griff]

Just logged it as a ticket with Impero and linked this thread. Hopefully they will see its multiple people because I was told before they hadn't seen it before..

[Steve21]

Just logged it as a ticket with Impero and linked this thread. Hopefully they will see its multiple people because I was told before they hadn't seen it before..

 

Thought I'd do the same, as had the same response last time

 

My previous ticket IDs related to this - #44212 and #45635

 

Steve

Edited March 9, 2022 by Steve21

[mavhc]

That's why bugs need to be public unless they're security bugs, need to insist on that if you're paying a subscription to something

[Steve21]

Just as a note, first thing been asked again is to update to the last version, which we did try last time but had no luck, but having a quick look through the change logs there is one bit which I guess may be related in a newer version - "WINDOWS CLIENT 8007 Intermittent Client Connectivity issues" - So will upgrade server tonight and see if it helps at all.

 

Steve

[Griff]

Got a reply. They are aware of the issue and engineers will fix this in a future release..

[Boredguy]

Got a reply. They are aware of the issue and engineers will fix this in a future release..

 

Oh like it was meant to be fixed in previous releases before, but still occurs from time to time

[Steve21]

Got a reply. They are aware of the issue and engineers will fix this in a future release..

 

Interesting! Care to share the response/ticket? As would be interesting to raise it with my engineer

 

Steve

[Griff]

Interesting! Care to share the response/ticket? As would be interesting to raise it with my engineer

 

Steve

 

Yeah bud ticket is #82272

 

"Thank you for contacting Impero support.

 

This is an issue that we are aware of and our engineers are working on fixing it in future releases. "

[mavhc]

What's the version you're on that has the problem? 8.0.64 here

[Griff]

What's the version you're on that has the problem? 8.0.64 here

 

I am on 8.5.73

[Steve21]

Was on 8.5.61, same issue occurred on at least one client I've found today since upgrading to the latest version 8.5.82

 

Steve

[GizmoIT]

We are on 8.5.61

[Griff]

I updated our machines to 8.5.85 on Thursday so far no disconnects...