DeployNRun Issue

nk_sc

Hi!!

We are using OD 5.0.1. for our deployment purposes:
We are using the DeployNRun option to invoke a batch script on the target machine (which is a Windows NT m/c).
We have noticed that if the batch script contains the DOS command "start /separate" then when the script runs we do NOT get a separate window appearing which ideally should happen. The process does start as it shows up in the TaskManager as "cmd.exe" , but we are unable to visually see another console wondow.
Furthermore the deployment does not end with the status being stuck at "setup transferred committing".

For example, a simple script contains the line
"start /separate date"
and if this is invoked manually, then we are able to see a new window with the current system date. However this is not the case when it is invoked via OpenDeploy.
Is this expected??

Please let us know of possible reasons / solutions...

Thanks!!!

nk_sc

Will someone look into this please, the script that we're using presently invokes a Java application. This appl in turn invokes certain services that have to be called with the "/separate" switch ..... and its failing at this point.
So its not as trivial as the script containing the "start /separate date"!!!

Any ideas???