Lansweeper Network / GP Deployment.

[Tigger]

Forgive me if this is already detailed in another thread but could the developer of this product please provide a list that includes all of the following detail:

Two lists answering the below questions. One specific to the lansweeper Server and One specific to the Client.

1. Exact Service Dependancys that Lansweeper needs for full funtionality. (ie. We know it requires the Remote Registry but what else?)
2. Exact Ports / Firewall rules to allow it to function.
3. Permissions & file shares that need to be accessed.

4. Anything else that is required to deploy this in a large network environment.

Background:
We are looking to deploy this software on multiple customer sites. With a view to encouraging some of these clients to purchase the full package once they become dependant. However currently our in house trials have hit issues configuring access through GP and found in-consistant behavior in relation to auding different machines. We assume some dependancys on some machines arent there. But I've been unable to find one place that puts all this information together. The machines that dont work provide a perfect test using the test utility but fail on registry connection after confirming DNS is perfect both in DNS management and on the lansweeper server and client. We assume their are dependancys that we are unaware of or the product is faulty. Hence any help to rule this product in / out for our customers would be appriciated.

Cheers & thanks in advance for any assistnace.

[Tigger]

Just another note: The actual vista machine mentioned above tests fine using the connection tester.

Cheers,

[Tigger]

Thanks for taking the time to reply. Can you please be really specific on which ports etc need to be open and which services need to be running. If your able to give me the info I'm happy to write a guide on how to deploy it for the rest of your user base once we confirm it ourselves.

Specificly with one vista machine we have rulled out: Any firewall / blocked ports. Remote Registry, WMI Working & Dcom enabled. And of course DNS. We tested dns lookups from the lansweeper server and the client as well as checking the records on the dns server.

Cheers,

[Tigger]

Tigger wrote:
We tested dns lookups from the lansweeper server and the client as well as checking the records on the dns server.

[Hemoco]

Tigger wrote:
We tested dns lookups from the lansweeper server and the client as well as checking the records on the dns server.

Did you also check the reverse dns lookups (ptr records)

[Hemoco]

We assume their are dependancys that we are unaware of or the product is faulty

99% of the problems are caused by reverse ptr records not pointing to the correct hostname. (the reverse dns)
I haven't found one single computer scan issue that could not be solved so far.

1. Exact Service Dependancys that Lansweeper needs for full funtionality. (ie. We know it requires the Remote Registry but what else?)

Remote registry, wmi working (dcom enabled), remote administration ports open.

2. Exact Ports / Firewall rules to allow it to function.

In group policies you can configure "remote administration"

3. Permissions & file shares that need to be accessed.

This depends on which extra files you want to scan.
The default administrative shares needs to be enabled (C$, D$, ...)