LSAgent update on locked down servers

[MDammer]

Hi,

Recently, we deployed Lansweeper in our network. Because we have a very segmented network, we decided for most of our VLANs to implement the LSagent as only option. This saves us creating security loopholes by opening ports, creating non-MFA accounts etc.

Our network is locked down, with no internet access unless explicitly specified. For allowing the LSAgent to communicate to the relay, I instructed the network team to specifically grant access to lsagentrelay.lansweeper.com for said VLANs.

This has been running fine for a few months now, but it came to my attention that machines in locked down-VLANs don't perform auto-updates of the LSAgent, as opposed to machines that aren't on locked down networks. I suspect this is because they need access to specific auto-update URLs or IP addresses. I guess this is the same URL as used in auto-install scripts: content.lansweeper.com, however I can't seem to find any documentation on this.

I don't want to redeploy the agent again for every update, and I'm willing to add other URL's to the firewall, but our security team wants to scope this as narrow as possible, so no *.lansweeper.com allowed.

Can anybody tell me which URLs I have to use? 

[MDammer]

Thanks for your answer.

Currently seeing LSAgent 11.4.1.2 on the devices that have unrestricted access to internet and 11.1.10.0 on devices that only have access to lsagentrelay.lansweeper.com.

If this is 'works as designed', and the agentrelay trails a little behind the general updates, that's fine too. However, if certain devices don't update their agent due to a missing networkconfig, I need to take action 🙂

[FrankSc]

Hello MDammer, 

Which version of LsAgent do you currently have on your agents? To which version did they update? 

It could be that the very last version of LsAgent is currently not being served by the relay server. We'll have to double-check that.