Jump to content

Recommended Posts

Posted (edited)

Since deploying Impero 5.2.10 we have seen the attached problems on a hand full of machines. I've tried redeploying the MSI to the machines however this hasn't fixed the problems. The next step is to uninstall the software and properly reinstall it.

 

I was wondering if anyone else has had this problem?

 

Here is an extract from the event viewer of one of the machines:

 

23.03.16 14:08:56 - SideBySide

 

Activation context generation failed for "c:\Program Files\Impero Solutions Ltd\Impero Client\64_ImperoShell.exe".Error in manifest or policy file "c:\Program Files\Impero Solutions Ltd\Impero Client\Microsoft.VC90.CRT.MANIFEST" on line 4. Component identity found in manifest does not match the identity of the component requested. Reference is Microsoft.VC90.CRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8". Definition is Microsoft.VC90.CRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8". Please use sxstrace.exe for detailed diagnosis.

 

 

 

23.03.16 14:14:55 - user32

 

The attempt by user DOMAIN\USER to restart/shutdown computer COMPUTER NAME failed

Impero.png

Impero04.png

impero004.jpg

Impero03.png

Impero02.png

Edited by timbo343
Posted

We are having the same problem with that Impero process and it's currently with their QA and developers. Our symptoms are that when users log out it either gets stuck logging out or prompts that imperowinlogon end now task which still doesn't actually log them out. The only way to get them to log out is to send a logout command with impero which resolves the issue but then the machines no longer show as being online on the impero console until you restart the service for the server.

 

It is a bit of a pain but all I know is as above which is that it's with QA and the developers are currently implementing a fix for the problem.

  • Thanks 1
Posted
Cool, at least im not the only one with the problem. We found that a force log off or restart sorted out too but its haopening on the same machines which is why im thinking we uninstall or push out a new image.
Posted

I have only built about 15 laptops since upgrading to 5.2.10. We use SCCM to built our workstations. It seems to me that either the Impero deployment does not occur or fails during deployment. I have had to install Impero manually for each of the laptops mentioned earlier [despite waiting more than 24 hours in some cases]

 

With the break coming up I am planning to look into this a bit more closely.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...