cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
FethS
Engaged Sweeper
Hi,

I found the following discussion covering the above mentioned issue:
http://www.lansweeper.com/forum/yaf_postst1355_Lstrigger-problem.aspx

We recently upgraded to version 3.5.2 and still have the same behaviour.
According to the 'old' discussion this issue should be fixed with verson 3.5.1 already.
Any ideas?

Cheers
Sascha
7 REPLIES 7
Hemoco
Lansweeper Alumni
Please contact us by e-mail to receive a test build.
FethS
Engaged Sweeper
Yes, we are using Lansweeper.exe version 3.5.2.4 and we are using active scanning.
I recognized this issue in version 3.5.1 and was hoping it will be fixed with new version.
Any ideas?
Hemoco
Lansweeper Alumni
Can't reproduce it at the moment.

Just to be sure:

-You are using lansweeperservice.exe 3.5.2.x
-You are using active scanning
FethS
Engaged Sweeper
Some machines having 5.0, some have 5.5, some 6.0 and some 6.5.
All with same behaviour.

Sascha
Hemoco
Lansweeper Alumni
Which version of vmware workstation is installed on the client?
FethS
Engaged Sweeper
That's exactly the name.
Thanks
Sascha
Hemoco
Lansweeper Alumni
just took a look at the source code.
'__vmware_user__' is still there.

Is this the exact correct name?

New to Lansweeper?

Try Lansweeper For Free

Experience Lansweeper with your own data.
Sign up now for a 14-day free trial.

Try Now