title: using cmd's Start command to run exe. Works locally, but not remotely
body: <p>Some background: We are trying to automate installation of an agent on servers. The automated workflow will check for servers that need this install. If so, the workflow copies the necessary install files as well as a .cmd batch file.</p>
  
  <p>When calling this .cmd script locally, the install works fine. But when trying to call this script remotely from the workflow server, it hangs on a certain line in the batch. Snippet from the script se_install.cmd:</p>
  
  <pre><code>echo Installing SE 9.4 Agent
  start "" /wait "Installcimextensions.exe" -i silent
  echo Install completed
  </code></pre>
  
  <p>We are using psexec to remotely call the above-mentioned script, using admin-level account that we use to execute many other scripts for other processes. Here is what the workflow server will run:</p>
  
  <pre><code>c:\scripts\psexec.exe -accepteula \\targetserver -u domain\username -p password \\targetserver\c$\temp\se\se_install.cmd
  </code></pre>
  
  <p>When running this remotely, the last output I see is "Installing SE 9.4 Agent". After that, it seemingly hangs indefinitely. At the same time, I'm on the local server viewing the list of running processes, and installcimextensions.exe never shows up on this list like it should be. I couldn't find any sort of known issues with running the "start" command remotely, but I assume that it might be part of the problem. Or could it possibly be an issue with the way I have the quotes set up, or the "-i silent" flag? I also tried replacing this "start" line in the batch with a call to another batch file that contains this line, but no dice.</p>
  
  <p>Any advice? Thanks.</p>