Lstrigger problem

[admin3]

Hi,

i just tested the lstrigger tool but with some strange results.

If i run lstrigger server computer domain the client will be scanned. But in domain field there will be the computername and in the username field there is always __vmware_user__. There is no __vmware_user__ logged on on the clients i scanned.

Any ideas?

Best regards

[Hemoco]

It seems that the "__vmware_user__" user is the only one reporting problems so we will just ignore this logged on user in the next update.

[admin3]

Yes, i see both users. First my user is written to the database, and a few minutes after this the vmware user is written into the database.

Best regards

[Hemoco]

When you go into the details of this computer/last logged on users. Do you also see the correct user logged on at this time?

[admin3]

Well, in the task manager of our machines there are no processes running under this user.

Best regards

[Hemoco]

admin@oepag wrote:
Well, in the task manager of our machines there are no processes running under this user.

Were there any running processes when the scan was running?

[admin3]

Lansweeper wrote:

admin@oepag wrote:
Well, in the task manager of our machines there are no processes running under this user.

Were there any running processes when the scan was running?

No, there are never processes running under this user. I just took a look at the task manager when the scan was triggered.

Best regards

[kpeterson]

admin@oepag wrote:
Well, in the task manager of our machines there are no processes running under this user.

Best regards

Agreed on one of the machines (one is running some processes under this user but the other definately is not)

[Hemoco]

We are working on it but it's not really a bug.
WMI reports that this user is logged on.
If you take a look at the processes running on that machine you will see that there are processes running under this user.

[kpeterson]

Is this something you're working on? Is there an easy way to ignore __vmware_user__ as a temporary measure?