Premium Tools Integration

[mgprichard]

Hello Lansweeper,

How are all the premium tools, E.G. LSREMOTE integrated? We just implemented Lansweeper latest version with the premium service and active scanning running correctly. When I logon to the web console and tried to used the actions such as Trigger Scan, Remote Control, first issue was getting Javascript errors due to the executables not being found. So to fix that, I have placed all of the premium executables into a single directory, and added it as a system path so Javascript finds them.

With the path set, the executables are found, and Javascript is hard coded to call for example Javascript RUNAPP:('LSTRIGGER.exe myserver NAME DOMAIN') I need it to call ('LSTRIGGER %myserver%') and be customisable.

Also what is the recommended method to have these tools available from client workstations that have admin priv, so the tools still run?

It would be nice for all this to be setup with a Premium tools setup utility.

Final question - what interval does the active scanning occur?

thanks

[desmi]

Hi Cobra7

Is it possible for you to make a screengrab of LS GUI | Configuration | Costum actions settings og paste then in a mail? mailto: erik.kronborg@tdcadsl.dk

I appreciate all your help.

Regards Erik

[Cobra7]

It can be a little confusing. Here is step by step.

1. Create a new share on the LS server, mine will be called LSTools.
2. Set up security on the share
3. Unzip the tools to this share (I added more, so I can not tell you how many come with it anymore)

At this point, you should be able to see all of the tools if you go to \\yourserver\LSTools
If you can not, need to start troubleshooting here, this is not an LS problem, it's something with your server.

Open the LS GUI program and log in. On the very top is the "Configuration" tab, when you click on that "Custom Actions" should be selected automatically, if it is not, then select it.

You should see the rows labeled "Description" "Action" "Icon" "Sort" "Enabled" "Confirm":

Description: This is what you will see in the LS Web page.
Action: This is the line we will be messing with, it tells your web browser where to go to find the tool and gives the tool it's parameters. I will get back to this.
Icon: This is the pretty icon next to the Description.
Sort: This arranges the actions, the lower the number the higher on the page it is.
Enabled: Make sure this is checked if you want to use it on the web page, if it is unchecked, that action will not work.
Confirm: This means that when you click on it in the web page, it will ask you if you are sure you want to run this tool.

Simple so far, right?

These examples will involve lstrigger.exe. What you do for this one should be repeated for all of them.
Now to get the tools to work, you need to change the action line. If I remember correctly the default is myserver. so the action line should be something like this:

lstrigger.exe myserver {computer} {domain}

Remember that share I told you to set up earlier, now we are going to use it. You will need to edit the action line. For my example, the server where Lansweeper is installed, and where the Lansweeper tools are located is "LSserver".

First thing you will need to do is tell the action line where the tool is, change the line to:

\\LSserver\lstools\lstrigger.exe myserver {computer} {domain}

All you did so far is tell the web browser where to find the tool, now we need to get the tool to work. You will need to change off of the "myserver" entries to the server where Lansweeper is installed.

\\LSserver\lstools\lstrigger.exe LSserver {computer} {domain}

If you have the Lansweeper tools installed on a server that is different from where the Lansweeper service is running, the names will not be the same, please change accordingly.

Now go to the LS web page and try the LStrigger on a computer. Give it a few moments then click Refresh on your web browser. On the lower right side you should see a lot of red squares that shows Lansweeper is updating the information.

When this works, update the rest of the tools. Test them to make sure they are working. Now your done.

Please note, I can not take screen shots of my server due to company policies, but if any of you have any I can add them in. I could use one of a fresh Custom Action screen before modification and one after. If you take others while going threw this I will add them in if applicable.

Best of luck!

[desmi]

Hi,

I have exactly the same experience - so an exsample would be nice.

Regards Erik

[Hemoco]

Hi,

The only thing that requires special attention is the premium service (the instructions are attached in the zip file)
There is no special setup for the other tools because they are all standalone tools and don't require any setup, you can just start the executables.

Most administrators change the action links to a shared drive, some point to their own pc, some copy the files to the system32 folder.

Without any setup you can place the tools where you want and configure lansweeper the way you like it.

But since you are the second person with this remark it's probably better for us to add some basic guidelines to the download files.

If you have any specific issue with a tool please let us know.

[jepit]

Hi,

I was very impressed by the free version, almost foolproof installation etc, works very nicely.

After just having bought the premium version, I'm quite surprised that I can't seem to find any documentation at all for the intergration of the extra tools in the interface, let alone a setup utility.... (visually they 'seem' to be integrated in the webinterface yes, but the download pack is just a bunch of loose files with hardly any documentation at all)

pages and pages of forum topics yes, but the idea I had buying the premium pack was to save time... This seems to be the opposite...

thank you,

[Hemoco]

I recommend placing all the tools in a shared folder where only the admins have access too. (\\server\sharename)
This way you can set up your actions to point to the share so your admins can access it from everywhere.

Active scanning scans the domain controllers every 15 minutes from new discovered computers. All computers are scanned once at minimum every 8 hours (except if you also use lsclient)

What is scanned is then based on the waittime.