I'm having a major issue with some XP computers (8 out of 15 so far) after upgrading to the new 5.3.47927 client. When the computer is rebooted, I get an lsass.exe error message and the machine will NOT boot into Windows or safe-mode. These clients are XP SP3, fully patched computers (patched using the K1000 for the past 2 years). The KBOX (and new Dell/KACE) program folders are excluded from real-time virus scan. I've had NO issues with our Windows 7 x64 client upgrades.

Is anyone else having this issue? I had the same problem when testing the beta 5.2 agent several months ago.




0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Have you opened a ticket with support? I saw this recently at one location and have not found the cause of it. If you are able to reproduce this then please contact support. I would love a reproducible example of this. For example, if you have the steps to reproduce it consistently OR if you have a machine that could be virtualized that we could test with
Answered 10/31/2011 by: GillySpy
Seventh Degree Black Belt

Please log in to comment
0
P.S. did you feedback that information during the 5.2 beta cycle somehow? if so I would appreciate the information you might have.
Answered 10/31/2011 by: GillySpy
Seventh Degree Black Belt

Please log in to comment
0
Yes, I had a ticket open during the Beta test. I spent a lot of time with support at that time, even mounted the failed drive to a virtual machine for them to access, but they were unable to determine the cause. I also have a ticket open for the issue with 5.3.

The issue with the 5.3 agent just surfaced on Friday at 4:00pm. I will be comparing the machines that failed to the ones that seemed to have no problem and will updated if I have any additional information.
Answered 10/31/2011 by: cdeal
Yellow Belt

Please log in to comment
0
FWIW, my other customer applied a backup of their registry on to a machine they were certain would exhibit this behaviour and after doing that and then rebooting it did not give the LSASS error.
Answered 10/31/2011 by: GillySpy
Seventh Degree Black Belt

Please log in to comment
0
If a customer hits this and is able to identify a machine that is still on 5.1 (has not upgraded yet) but they are very certain that it will exhibit this behaviour when upgraded I would love to see it. Then I can virtualize it.

A VM image that can be rolled back or a machine from a template that can be retemplated would be just as good.
Answered 11/03/2011 by: GillySpy
Seventh Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity