revisiting- scanning non domain machines

[david_chang]

Looking for some assistance in setting up my lansweeper server to scan non-domain machines.

Can I setup my Lansweeper server in the DMZ with a public IP address?

Can I then have the non-domain clients run the LSClient.exe and have it communicate back to the Lansweeper server?

We want to avoid setting up a new lansweeper server at each location (we have over 300).

This is being done becuase we want to inventory these locations prior to bringing them into our domain so at that point, we won't need extra servers laying around.

What is your recommended process to scan these non domain/AD machines?

thanks!
Dave

[danielm]

SEE ,
http://www.lansweeper.com/forum/yaf_postst5771_lspush-smtp-direct-send.aspx
,
I made a batch to run the lspush and just email it. this will work from anywhere 🙂

[EB]

possible VPN option? or maybe a dropbox and pickup using internet connections?

I do believe this software was for local lan use...external may be a pain...but you can make it work...believe and achieve...:)

[Hemoco]

1) Run lspush on the machines and send the all to a single shared folder.
2) Create a scheduled job to copy the files in the shared folder to the lansweeper\service\import folder.

[david_chang]

Lansweeper wrote:
1) Run lspush on the machines and send the all to a single shared folder.
2) Create a scheduled job to copy the files in the shared folder to the lansweeper\service\import folder.

#2 isn't going to work.

They don't have access back into our network. I need the inventories of their local machines in preparation for the project that will bring them into our network and onto our domain.


So this takes me back to the original idea.

Can I setup the lansweeper server in the DMZ with a public IP address?

Can I run LSpush or Lsclient on each machine that send the report to the public IP address?

thanks!
Dave

[Hemoco]

david.chang wrote:

Lansweeper wrote:
1) Run lspush on the machines and send the all to a single shared folder.
2) Create a scheduled job to copy the files in the shared folder to the lansweeper\service\import folder.

#2 isn't going to work.

They don't have access back into our network. I need the inventories of their local machines in preparation for the project that will bring them into our network and onto our domain.


So this takes me back to the original idea.

Can I setup the lansweeper server in the DMZ with a public IP address?

Can I run LSpush or Lsclient on each machine that send the report to the public IP address?

thanks!
Dave

That would work but I wouldn't recommend exposing the lansweeper port to internet for security reasons.
(Although there are no known problems with it)

[david_chang]

Lansweeper wrote:

david.chang wrote:

Lansweeper wrote:
1) Run lspush on the machines and send the all to a single shared folder.
2) Create a scheduled job to copy the files in the shared folder to the lansweeper\service\import folder.

#2 isn't going to work.

They don't have access back into our network. I need the inventories of their local machines in preparation for the project that will bring them into our network and onto our domain.


So this takes me back to the original idea.

Can I setup the lansweeper server in the DMZ with a public IP address?

Can I run LSpush or Lsclient on each machine that send the report to the public IP address?

thanks!
Dave

That would work but I wouldn't recommend exposing the lansweeper port to internet for security reasons.
(Although there are no known problems with it)

Ok. so how would this work? The machines as I stated, don't have access to our domain as they need to be inventoried BEFORE we join them to our domain.

thx
Dave

[Hemoco]

david.chang wrote:
Ok. so how would this work? The machines as I stated, don't have access to our domain as they need to be inventoried BEFORE we join them to our domain.

Before you try implementing this, be aware that you will manually have to update the machines' domain names when they're joined to your domain, as Lansweeper does not currently detect computer or domain name changes.