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]

There is no patch at the moment.
We could just ignore user "__vmware_user__" but the same problem can happen again with another user.

[dffe]

Is there an solution to this issue or will it come in a future patch/Release?

We have the same issue and also '%USERNAME%' is reported as the last user on terminal servers.

[admin3]

Just tested it with active scanning, lstrigger and lsclient. It happens with active scanning and lstrigger but not with lsclient.

Best regards

[taschen_dan]

I confirm the issue.

[kpeterson]

I'm having the same issue using Active Directory scanning. Is there any way to get Lansweeper to disregard the vmware_user account altogether?

[admin3]

Okay, it's only happening if a workstation has a VMWare Server installed. On this machines there is a user called __vmware_user__. But this user isn't currently logged on when i trigger the scan. Lstrigger works if there is no VMWare Server installed on the target machine.

The VMWare services are not started with the __vmware_user__ credentials.

Best regards

[Hemoco]

Most likely there is a local account on that computer called __vmware_user__ which is logged on according to WMI Maybe a vmware service running?

[admin3]

Here is the screenshot.

In the field "Domain" is the computername and not the domain name and in the field "Username" is an user that is not logged on and this user doesnt exist in our domain.

Best regards

[Hemoco]

Could you post a screenshot where exactly that you see this please.