I can't say anything about how the premium version works, but I had no problems executing the lsclient remotely using a couple of two-liner batch files and psexec with a domain admin account.
This command triggers the lansweeper client on all the workstations listed in C:\pcs.txt <file://wcul12c:/pcs.txt> which you create and drop somewhere (c:\ in this example): psexec @c:\pcs.txt -u domain\domainadminaccount " \\fileserver\share\lansweeper.bat <file://fileserver/share/lansweeper.bat>" Lansweeper.bat has to be put on a share and basically points to the lsclient.exe for all the workstations to find and directs them to your lansweeper server netbios name. Mine has just this line: "\\server\share\lsclient.exe <file://server/share/lsclient.exe>" mylansweeperserver What is more trouble is figuring out how to get it to rescan things after it has built the database once. Finally found that in the Lansweeper configuration utility. -Bill On Thu, Nov 19, 2009 at 7:31 AM, Kennedy, Jim <[email protected]>wrote: > Ok, I have seen this mentioned many times here so I am looking at it real > hard. I like it a lot, using the free version I have to have the client > execute an exe as they log on to ‘phone home’. Having a heck of a time > getting that to run under a user account (non-admin). The pay version uses AD > to look up computers and poll them, no client side software needed. > > > > I have no desire to fight this for testing when we plan to just do the > premium version if it passes testing. So the question is those of you using > the premium AD feature is it pretty trouble free…it finds your machines and > reports on them ok. > > > > JK > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
