There are often times you need to execute a cmd within PowerShell that creates output in the cmd's output, but not PowerShell.
I came across a similar issue on the technet forums.
http://social.technet.microsoft.com/Forums/en-US/scogeneral/thread/a9511617-c174-4a5b-a531-3110471c9222
For example....
Running w/ PowerShell in the Run .NET Script activity cannot catch the output of the winrs cmd. Even w/ adding the $Output = ... and adding the Output variable to published data.
$Output = winrs -r:server_name -u:server_name\administrator -p password net localgroup Administrators Domain\User /ADD
This will result in the Output variable in the published data being empty.
The trick is simply adding "2>&1" (without quotes) at the end of the cmd. So the complete command would look like this.
$Output = winrs -r:server_name -u:server_name\administrator -p password net localgroup Administrators Domain\User /ADD 2>&1
This will result in the $Output variable catching the result from winrs into the published data. Also note, you may have to Flatten the data since the result may end up in multiple lines.
Here is a link that explains different methods for catching output in PowerShell.
http://mctexpert.blogspot.com/2010/11/what-does-2-mean-in-powershell.html
