Hi @Joney
When a deployment step fails, it's recommended to manually test the failed step on the target machine using the same account under which the deployment was executed.
This helps to replicate the exact environment and identify potential issues.
Follow these steps:
- Copy the Command: Retrieve the command from the Result field of the failed deployment package step.
- Update the Path: Replace {PackageShare} with the full UNC path defined under the Deployment\Security settings.
- Run the Command Manually: Open Command Prompt on a sample target machine, paste the command, and execute it.
This process helps determine whether the failure is related to command syntax, permissions, or network paths. A command must run successfully in Command Prompt to work correctly in Lansweeper.