‎03-19-2018 09:45 AM
Solved! Go to Solution.
‎03-19-2018 12:12 PM
‎03-21-2018 07:54 AM
‎03-20-2018 03:46 PM
‎03-19-2018 01:55 PM
‎03-20-2018 05:27 AM
Charles.X wrote:
To test the logonscript, you can open CommandPrompt on a client machine you want to scan with the command below. Again, make sure that you replace the LansweeperServer with the name of your Lansweeper scanning server, or the IP address of that scannig server. The command will trigger a local scan and will send the scan results directly to your Lansweeper server for import. The /showresult parameter will also provide you with visual feedback.
"%logonserver%\netlogon\LsPush.exe"LansweeperServer /showresult
As tbal mentioned, you can also run the vbs script locally to test it.
‎03-19-2018 12:12 PM
‎03-20-2018 05:31 AM
tbal wrote:
Personally we aren't using this I have setup a scheduled task instead because VPN won't be connected when they logon.
But I would use %logonserver% instead of main-dc01 as it goes towards the DC you login to.
I would check event viewer for any errors, do you have any other logon scripts running? Does the computers have connection to the DC when logging in?
Check gpresult /r as admin to see so the GPO is applied.
What happens if you run the vb script manually?
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now