The problem is most likely caused by an incorrect argument that was applied to the deployment. When a deployment just sort of hangs after the copy process there is most likely a window (it may be hidden) that is waiting for input on the target machine. You need to find the appropriate arguments to supply in order to have a "silent" deployment.
For many applications that you wish to deploy you can find out the available deployment arguments by running the setup file with a '/?' argument.
e.g. setup.exe /?
A good way is to run the setup.exe /? from the Run command in the start menu.
This should give you a usage window showing the accepted arguments.
Please sign in to leave a comment.