
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-19-2009 06:45 PM
I just installed Lansweeper for the first time and doing some testing. Everything seems to work as a charm, even on a SQL2008 Express install. Though when I launch the LsClient on the server were Lansweeper is installed (need this server in the inventory as well) it errors with cannot access file or no permissions, etc.
Is this as designed or am I doing something wrong. It works on the other servers though.
Cheers
Dennis
- Labels:
-
Archive

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-23-2009 01:57 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-20-2009 10:30 PM
Could you try disabling the virusscanner (if you use one)

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-21-2009 01:12 PM
Lansweeper wrote:
Is it possible that a virusscanner is somehow blocking the executable?
Could you try disabling the virusscanner (if you use one)
I qoute from an earlier post that I was able to run it via c:\windows\sysvol\.... so a virusscanner can't be the issue.
Cheers Dennis

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-20-2009 07:09 PM
I have the same problem. Try to check if DEP (Data Execution Prevention) is on :
My Computer --> Properties --> Advanced --> (Performance) Settings --> (Tab) Data Execution Prevention --> (Check) Turn on DEP for essential Windows programs and services only
and REBOOT !!
-- nicogab --
french system admin

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-20-2009 09:12 PM
nicogab wrote:
Hi,
I have the same problem. Try to check if DEP (Data Execution Prevention) is on :
My Computer --> Properties --> Advanced --> (Performance) Settings --> (Tab) Data Execution Prevention --> (Check) Turn on DEP for essential Windows programs and services only
and REBOOT !!
-- nicogab --
french system admin
Thanks for the tip, but it wasn't the solution.
Dennis.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-20-2009 07:06 PM
You could create a new share somewhere, copy lsclient there and in your loginscript use \\servername\newshare\lsclient.exe

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-20-2009 09:12 PM
Lansweeper wrote:
I'm pretty sure it's an nfts problem with the file or share.
You could create a new share somewhere, copy lsclient there and in your loginscript use \\servername\newshare\lsclient.exe
Share and rightsare all correct. Checked effective permissions and full control is in place.
Thanks,
Dennis.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-20-2009 04:29 PM
The database is now updated with the server info. Still I'm open for suggestions why it won't run via the share. So it won't error while running the logonscript.
Thanks for the help so far.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-20-2009 03:59 PM
