Run Program activity not exiting

Question

I'm running SCOrch 2012 R2 and am having trouble with a runbook hanging. Here are the facts
My runbook executes a script (the code for which, I have included below) that gets a list of AD users and exports that list to a .csv file. 
When run manually, from a Powershell window, the script executes and returns the expected file, before returning to the prompt.
When run through the SCOrch, the script runs fine, with the output file created and the Powershell process exiting.
The commands I'm using to execute the script manually and through the runbook, are the same (see below) and the run-as accounts are the same.
The runbook never gets past the step that runs the Powershell script.
The activity looks like this: 
Command execution
Command: cmd.exe /c | C:\Windows\system32\WindowsPowerShell\v1.0\powershell.exe –c "C:\it\getADUserProperties-Parameterized.ps1 -SearchPath 'ou=customer,dc=domain,dc=tld' -DomainName domain.tld | Export-Csv C:\it\userList.csv -NoTypeInformation"
Run as account credentials specified
The rest of the options are set to the default values
The question is, why doesn't the Run Program activity close when powershell.exe exits? I know it won't matter, but here is the script anyway:
<#
.Synopsis
Get Active Directory user list with a user-specified set of properties
.DESCRIPTION
Get a list of Active Directory users from a user-specified list of containers (or the root of the domain) and return a user-specified set of attributes.
This script can connect to non-native domains (domains that the executing computer is not a member of) if DNS is configured properly. If accessing a
non-native domain, the script will prompt for credentials.
.NOTES
Author: Mike Hashemi
V1 date: 15 August 14
.LINK
.PARAMETER DomainName
Defines which DNS domain to connect to.
.PARAMETER SearchPath
Default value = cn=users,dc=domain,dc=tld. This parameter represents the AD to search and can contain multiple values.
.PARAMETER OutputProperties
Default value = Name,Enabled. This parameter represents a comma-spearated list of AD attributes to return.
.EXAMPLE
.\getADUserProperties-Parameterized.ps1 -DomainName domain.tld
This example will output the name and enabled status of all users in "cn=users,DC=domain,DC=tld" and below.
.EXAMPLE
.\getADUserProperties-Parameterized.ps1 -OutputProperties name,telephoneNumber | Export-Csv C:\userList.csv -NoTypeInformation
This example will output the name and telephone number of all users in "cn=users,DC=domain,DC=tld" and below. Output will be sent to c:\userList.csv.
#>
[CmdletBinding()]
param(
[Parameter(Mandatory=$True)]
[string]$DomainName,
[string[]]$SearchPath = 'cn=users,DC=domain,DC=tld',
[string]$OutputProperties = 'Name,Enabled'
Import-Module ActiveDirectory
If ((Get-Module ActiveDirectory -ErrorAction SilentlyContinue) –eq $null) {
Write-Error "This script requires the Powershell Module: 'ActiveDirectory'. Please make sure you've got the correct tools installed."
Exit
Else {
Foreach ($ou in $SearchPath) {
Try {
Write-Verbose ("Getting users from {0}." -f $ou)
Get-ADUser -Filter * -SearchBase $ou -Properties $OutputProperties.Split(",") -Server $DomainName | Select $OutputProperties.Split(",")
Catch [System.Security.Authentication.AuthenticationException] {
Write-Output ("Connection failed. Prompting for credentials to {0}" -f $DomainName)
$cred = Get-Credential -Message "Enter credentials for $DomainName."
Write-Verbose ("Getting users from {0}. with user: {1}" -f $ou, $cred.Username)
Get-ADUser -Filter * -SearchBase $ou -Properties $OutputProperties.Split(",") -Server $DomainName -Credential $cred | Select $OutputProperties.Split(",")
Thanks.

Answer 1

mhashemi,
I had a simliar issue as you did where my runbook would run until it got to the "Run .Net Script" Activity and then the Runbook would just stop. What I found was you can not have the command "Exit" in your script. The command "Exit"
will force the Activity to close and will not output any variables.
I am not the only one to find this issue.
Check out the article labeled
"Run .Net Script (powershell), "exit" and published data" on technet under
System Center Orchestrator > System Center Orchestrator - General
(not able to post the link, I am restricted)
Doesn't sound like there is going to be a fix anytime soon
Hope this helps
-Ozarkclay