
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-01-2009 12:25 AM
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
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
Labels:
- Labels:
-
Archive
7 REPLIES 7

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-06-2009 06:09 PM
Please contact us by e-mail to receive a test build.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-06-2009 10:22 AM
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?
I recognized this issue in version 3.5.1 and was hoping it will be fixed with new version.
Any ideas?

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-05-2009 10:44 AM
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
Just to be sure:
-You are using lansweeperservice.exe 3.5.2.x
-You are using active scanning

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-05-2009 01:30 AM
Some machines having 5.0, some have 5.5, some 6.0 and some 6.5.
All with same behaviour.
Sascha
All with same behaviour.
Sascha

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-02-2009 08:28 PM
Which version of vmware workstation is installed on the client?

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-02-2009 01:24 AM
That's exactly the name.
Thanks
Sascha
Thanks
Sascha

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-01-2009 01:08 PM
just took a look at the source code.
'__vmware_user__' is still there.
Is this the exact correct name?
'__vmware_user__' is still there.
Is this the exact correct name?
