Hi Bullman,
Are you seeing any errors when trying to deploy this package?
If you are then the feedback that is returned is in most cases the direct result of the command being executed in CMD on the target computer.
Lansweeper simply executes the commands you provide on the specified computers using the specified credentials.
• Uses your scanning credentials to write the deployment executable on the target computer
• Uses your scanning credentials to write the deployment package details into the registry
• Uses your scanning credentials to create a scheduled task that executes the deployment command in CMD
• The scheduled task runs with your "Run Mode" user (Local System, current user or scanning credentials)
Since the deployment module allows you to execute any non-Lansweeper-specific command towards a non-Lansweeper-specific environment, we, unfortunately, cannot provide in-depth support for creating or troubleshooting custom deployment packages. In general, when troubleshooting deployment packages, we recommend the following:
• Run CMD on the computer you're getting the error on, run it with the same user as your Run Mode user.
• Copy/paste your deployment command and check the output.
• Make sure the command works in local CMD first, without producing any dialogs (must run silently), before trying to send it via Lansweeper.
More information on our deployment module can be found in this section of our knowledge base: https://www.lansweeper.com/kb-category/deploying-software-and-other-changes/
