You can find a list of the services used in the deployment requirements article: https://www.lansweeper.com/kb/107/deployment-requirements.html
By default, you won't be able to see any logs regarding deployment. Our support team has specific instructions to turn on debug logs in cases where it is needed.
Personally, I've never seen a case where the deployment ends successfully without the software actually installing. If you are willing to you can export your package, add it to a .zip file and add it as an attachment to your post. I can take a look at the package itself to see if that clears anything up.
The most efficient way to troubleshoot this issue would be to send an email to our support team at support@lansweeper.com and include the following information:
- Program Files (x86)\Lansweeper\Service\Errorlog.txt, as present on your Lansweeper server.
- An .xml export of your deployment package. Select the package under Deployment\Packages and hit the Export button on the right side of the page, right below the package name.
- Screenshot of a testconnection.exe test performed to one target machine with a failed deployment. Connect to the client machine's name (and not its IP address), as this is what Lansweeper connects to for deployments as well. Testconnection.exe can be found in Program Files (x86)\Lansweeper\Actions on your Lansweeper server. Perform the test from your Lansweeper server to the client machine, submit the machine's Windows credential and show us the entire test window.
- An Excel export of the entire Deployment\Logs page. There is an Export To Excel button on the left side of the page.