Lansweeper

Posted by slocs1@reddit | sysadmin | View on Reddit | 6 comments

We are currently implementing lansweeper. Company size is roughly 8000 employees in production, so there will be a lot of assets.

We chose 1 installation scanner mysql per site and connect all to cloud. We wanted now to install ITagent (new scanagent by lansweeper) but they dont seem confident that it will work and suggested LSagent (old and well known client).

Does anyone have expirience here?

We wanted to install ITagent on all Windows/Linux assets and do the rest via scanning. Also an own instance per plant for OT.

I would be happy if anyone has a similar scenario.

I have the feeling Lansweeper pushed cloud but their technicians seem to be hestitant when it comes to cloud and ITagent.

Thanks

[-]

modder9@reddit

LSAgent with cloud relay works perfectly fine.

post4u@reddit

Yep. We scan everything on-prem from a VM and sync to cloud. Works great.

healVoidCraft3520@reddit

The part where they "dont seem confident that it will work" from their own vendor is a bit of a red flag tbh. Did they give you any specifics on what breaks with ITagent at scale, or was it more of a vague "we suggest the older one" kind of answer?

slocs1@reddit (OP)

They are generally not so sure, but I think the deduplication of scanned assets which already have an agent is the major concern

dhardyuk@reddit

I’ve had much more success using scanning to create targets for lsagent push install than for anything else.

Once you get lsagent installed as part of your build scanning will only really find anomalies that don’t have lsagent installed.

It’s pretty cool once you name your IP ranges to have the names show in your reports - on last scan these machines were here, those were working from home and these are on the conference room WiFi.

cwk9@reddit

LSagent can relay to an on prem server via the lansweeper cloud. Great for laptops or devices that might not have line of site to the lansweeper server. At 6000 employee I've had one VM in Azure handle everything. You may want to consider scaling up before scaling out.