I have a strange issue it seems that the policy.client.invoker process is preventing my Windows 7 machine from logging off / shutting down. All the users get is the logging off screen and the pc will stay like this for hours or until a hard reset is performed. If I manually end the process the machine will log off / shutdown normally. Is there a fix for this or a work around. it seems that more and more of my windows 7 machine are getting this issue.
Landesk Version 220.127.116.11
can you tell us what is the version of the file that is preventing the normal shutdown?
Have you installed the SP3 already on your environment?
I think you can install SP3 on TVT but it is better to open a support case to ask confirmation of this before to proceed.
The SIZE of the file is a bit weird! Zero bytes???
Please compare the file (you can use FC or MD5Summer ) with the one that you have in the \\CORENAME\ldlogon
Is the file really zero sized?!
If I browse to \\corename\ldlogon on the server or program files\landesk\ldclient on the client the file size is the same 201KB. The screen shot above was taken from the process tab. Something interesting if I look at the policy.client.invoker log file there used to be shutdown events.
Thu, 29 Mar 2012 18:21:58 2272: Service shutdown has been requested, setting shutdown event
Thu, 29 Mar 2012 18:21:58 2272: Shutdown event set, sockets closed
Thu, 29 Mar 2012 18:21:58 2272: Service is shutting down
Thu, 29 Mar 2012 18:21:58 2272: Exiting the service
Thu, 29 Mar 2012 18:21:58 2272: Service stopped
These don't seem to happen anymore
Anyway even if the size is the same I suggest to compare them with the FC command.
The syntax is FC /B File1.exe File2.exe
May you check using the STREAMS.EXE utility (you can find it here http://technet.microsoft.com/en-us/sysinternals/bb897440.aspx ) that you do not have streams on your C:\Program Files (x86)\LANDesk (or C:\Program Files\LANDesk on 32bit systems) ?
The syntax is
STREAMS -s -d "C:\Program Files (x86)\LANDesk\*.*" This will show if you have streams and if yes will remove them.
Another test may be to download SP3 and install, only as a test, the client part of it on an affected client to see if this fixes the issue.
Both policy.invoker files are the same no differences between them. There are also no streams at all. How do I install only the client part of SP3?
the procedure is simple: