Appreciate that Roland. I started moving in that direction once I found the KB Article.
I've got the lspush agent delivered via GPO and built out a Powershell script with some logging features commented out for long term management.
<#
General Information
The Lspush.exe must be updated when the Lansweeper application is updated.
Knowledge Base Article on implementing lspush through Group Policy.
https://community.lansweeper.com/t5/scanning-your-network/scan-windows-computers-with-lspush-in-a-group-policy/ta-p/64434
Knowledge Base Article on the different switches for lspush and an explaination of how they function.
https://community.lansweeper.com/t5/scanning-your-network/introduction-to-the-lspush-scanning-agent-for-windows/ta-p/64277
#>
# Server is listed out with the FQDN for consistency. Update as needed.
$Server = "Lansweeper"
$lsPushPath = "C:\Temp\lspush.exe"
# Begins the lspush scan and sends the information to the Lansweeper server.
Start-Process $lsPushPath -ArgumentList $Server
# Text file for debugging and logging.
New-Item -Path C:\Temp\Lansweeperscan.txt -Value "Lansweeper script ran to completion. Last good run time was $(Get-Date)" -Force
This is functioning correctly for now. I'm going to go back and add some more later to check if a user is on VPN.