This is a known issue. Engineering is currently working on a fix.
This is on Vista systems, correct?
I have seen this on XP boxes also.
Windows XP (I don't have any Vista PC's as of yet.)
There was a spearate issue with Vista. This Vista issue was fixed in this build:
LDISCN32.EXE version 188.8.131.52
This current issue we are discussing did not occur with this version:
LDISCN32.EXE version 184.108.40.206
So it looks like the current issue was caused by the supposed fix for the Vista issue.
To understand this problem, we need to understand how this feature works. There is a configuration to determine how many of the last logins to monitor in Configure | Services | Inventory.
On the client, that number of logins will be stored in this registry key:
Who ever has the most logins wins and is the Primary owner. If they are all unique then it is the last one to log in.
When LDISCN32.EXE is launched and no one is logged in, this Registry key should not be updated at all.
Starting with build 220.127.116.11 this issue is occuring. It is also occuring in build 18.104.22.168 (our latest build).
So it looks like we need to work with engineering.
1 of 1 people found this helpful
Looks like a bug has been submitted with LANDesk already.
Any news on this fix?
we have a few XP clients reporting the system as the Owner.
ldiscn32.exe is 22.214.171.124
This is a new Deployment so we all have the same version, but not all users have this problem.