The problem is that Lansweeper provides an exe installer instead of an MSI package which is required by Group Policy. It’s less effort than manual install, will run the next time a computer turns on unlike a Lansweeper deployment, and is arguably less effort than writing a script. In our case, we prefer to use Active Directory Group Policy to deploy software. You can manually run the installer on each machine, you could deploy it using the included Lansweeper deployment package, or you could write a script to run the exe silently. There are a few ways you can deploy the agent. It also helps if computers are turned off during your normal scan time or if a laptop is connected to your guest network and unable to talk directly to your local Lansweeper server due to a network security ACL or Firewall. However, installing the Lansweeper Agent allows you to scan laptops that are not on your local network, doesn’t require a highly privileged domain account to be added to Lansweeper, and can usually bypass the Windows firewall on a client.

Out of the box, Lansweeper can scan Windows computers without installing the agent program on the computer.

Lansweeper lspush install location