I wrote a script that will be used to upgrade the monitoring agents on
our servers, and the one challenge that I have not been able to
resolve is how to incorporate asynchronous processing into the
solution. Since this is a production script, I am using PS V1. The
script is written to take in a list of server, but the issue is that
the script will not begin upgrading ServerB unless ServerA is complete
AND no terminating errors were encountered while upgrading ServerA. I
have read the SDK regarding Runspaces, and i found the new-job.ps1,
PSThreading, and AsyncLib.ps1 scripts, but I have not been able to put
this together to create an asynchronous solution..



At this time, we are opening multiple PowerShell consoles, and running
the script against a single server, but I would like to automate this
process. We must be able to pass parameters and switches to the
script, and have multiple runspaces executing at the same time. So in
short, I would like to do something like this:

Pseudo Code:
Import-Csv "inputlist.csv" | foreach-object {
open a new runspace
execute the script with the correct parameters and switches
if ($?){Start another runspace and move to the next server}
if $numberofrunspace -eq 5 {loop until $numberofrunspace -le 4}
}

As soon as the runspace starts successfully, I would like to start
upgrading the next server in the input file. This is where I keep
running into the issue. If I can't get the second runspace to start
until the first loop is complete, I still do not have asynchronous
processing. Also, I would like to limit the number of runspaces to 5
so we don't have a runspace open for every server in the input file.

So in short, if anyone has figured out how to use runspaces and/or a
PS1 library to create an asynchronous processing solution, please let
me know...

Any help with this issue will be greatly appreciated.
Ozone

Running an external process asynchronously


---
Shay Levi
$cript Fanatic
http://scriptolog.blogspot.com

> I wrote a script that will be used to upgrade the monitoring agents on
> our servers, and the one challenge that I have not been able to
> resolve is how to incorporate asynchronous processing into the
> solution. Since this is a production script, I am using PS V1. The
> script is written to take in a list of server, but the issue is that
> the script will not begin upgrading ServerB unless ServerA is complete
> AND no terminating errors were encountered while upgrading ServerA. I
> have read the SDK regarding Runspaces, and i found the new-job.ps1,
> PSThreading, and AsyncLib.ps1 scripts, but I have not been able to put
> this together to create an asynchronous solution..
>
> At this time, we are opening multiple PowerShell consoles, and running
> the script against a single server, but I would like to automate this
> process. We must be able to pass parameters and switches to the
> script, and have multiple runspaces executing at the same time. So in
> short, I would like to do something like this:
>
> Pseudo Code:
> Import-Csv "inputlist.csv" | foreach-object {
> open a new runspace
> execute the script with the correct parameters and switches
> if ($?){Start another runspace and move to the next server}
> if $numberofrunspace -eq 5 {loop until $numberofrunspace -le 4}
> }
> As soon as the runspace starts successfully, I would like to start
> upgrading the next server in the input file. This is where I keep
> running into the issue. If I can't get the second runspace to start
> until the first loop is complete, I still do not have asynchronous
> processing. Also, I would like to limit the number of runspaces to 5
> so we don't have a runspace open for every server in the input file.
>
> So in short, if anyone has figured out how to use runspaces and/or a
> PS1 library to create an asynchronous processing solution, please let
> me know...
>
> Any help with this issue will be greatly appreciated. Ozone
>

For a manual version:

1..5 | foreach {
$psi = new-object system.diagnostics.processStartInfo
$psi.fileName = "notepad.exe"
$psi.arguments= $profile
$psi.loadUserProfile = $false
$psi.useShellExecute = $false
$proc = [system.diagnostics.process]::start($psi)
write-host "Process #$_ launched"
}





---
Shay Levi
$cript Fanatic
http://scriptolog.blogspot.com

> http://www.vistax64.com/powershell/1...al-process-asy
> nchronously.html#post726296
>
> ---
> Shay Levi
> $cript Fanatic
> http://scriptolog.blogspot.com

>> I wrote a script that will be used to upgrade the monitoring agents
>> on our servers, and the one challenge that I have not been able to
>> resolve is how to incorporate asynchronous processing into the
>> solution. Since this is a production script, I am using PS V1. The
>> script is written to take in a list of server, but the issue is that
>> the script will not begin upgrading ServerB unless ServerA is
>> complete AND no terminating errors were encountered while upgrading
>> ServerA. I have read the SDK regarding Runspaces, and i found the
>> new-job.ps1, PSThreading, and AsyncLib.ps1 scripts, but I have not
>> been able to put this together to create an asynchronous solution..
>>
>> At this time, we are opening multiple PowerShell consoles, and
>> running the script against a single server, but I would like to
>> automate this process. We must be able to pass parameters and
>> switches to the script, and have multiple runspaces executing at the
>> same time. So in short, I would like to do something like this:
>>
>> Pseudo Code:
>> Import-Csv "inputlist.csv" | foreach-object {
>> open a new runspace
>> execute the script with the correct parameters and switches
>> if ($?){Start another runspace and move to the next server}
>> if $numberofrunspace -eq 5 {loop until $numberofrunspace -le 4}
>> }
>> As soon as the runspace starts successfully, I would like to start
>> upgrading the next server in the input file. This is where I keep
>> running into the issue. If I can't get the second runspace to start
>> until the first loop is complete, I still do not have asynchronous
>> processing. Also, I would like to limit the number of runspaces to 5
>> so we don't have a runspace open for every server in the input file.
>> So in short, if anyone has figured out how to use runspaces and/or a
>> PS1 library to create an asynchronous processing solution, please let
>> me know...
>>
>> Any help with this issue will be greatly appreciated. Ozone
>>

On Jun 4, 10:30*am, Ozone <rs_dov...@xxxxxx> wrote:

> I wrote a script that will be used to upgrade the monitoring agents on
> our servers, and the one challenge that I have not been able to
> resolve is how to incorporate asynchronous processing into the
> solution. *Since this is a production script, I am using PS V1. *The
> script is written to take in a list of server, but the issue is that
> the script will not begin upgrading ServerB unless ServerA is complete
> AND no terminating errors were encountered while upgrading ServerA. *I
> have read the SDK regarding Runspaces, and i found the new-job.ps1,
> PSThreading, and AsyncLib.ps1 scripts, but I have not been able to put
> this together to create an asynchronous solution..
>
> At this time, we are opening multiple PowerShell consoles, and running
> the script against a single server, but I would like to automate this
> process. *We must be able to pass parameters and switches to the
> script, and have multiple runspaces executing at the same time. *So in
> short, I would like to do something like this:
>
> Pseudo Code:
> Import-Csv "inputlist.csv" | foreach-object {
> open a new runspace
> execute the script with the correct parameters and switches
> if ($?){Start another runspace and move to the next server}
> if $numberofrunspace -eq 5 {loop until $numberofrunspace -le 4}
>
> }
>
> As soon as the runspace starts successfully, I would like to start
> upgrading the next server in the input file. *This is where I keep
> running into the issue. *If I can't get the second runspace to start
> until the first loop is complete, I still do not have asynchronous
> processing. *Also, I would like to limit the number of runspaces to 5
> so we don't have a runspace open for every server in the input file.
>
> So in short, if anyone has figured out how to use runspaces *and/or a
> PS1 library to create an asynchronous processing solution, please let
> me know...
>
> Any help with this issue will be greatly appreciated.
> Ozone

Hi Ozone,

"Background jobs and PowerShell"
http://jtruher.spaces.live.com/blog/...628D!130.entry

(powershell 1.0)

- Oisin

Hi Ozone, you may want to take a look at my Split-Job script; it should do
what you need and even collects the output (if any) from each asynchronous
pipeline. In your case, you could run something like

Import-Csv "inputlist.csv" | Split-Job { Upgrade-Agent $_} -MaxPipelines 5 |
Out-File Upgrade-Agent.log

The blog post with the script is here:
http://www.jansveld.net/powershell/2...b-version-0-9/

Hope this helps,
Arnoud
--
http://www.jansveld.net/powershell


"Shay Levi" wrote:

>
> For a manual version:
>
> 1..5 | foreach {
> $psi = new-object system.diagnostics.processStartInfo
> $psi.fileName = "notepad.exe"
> $psi.arguments= $profile
> $psi.loadUserProfile = $false
> $psi.useShellExecute = $false
> $proc = [system.diagnostics.process]::start($psi)
> write-host "Process #$_ launched"
> }
>
>
>
>
>
> ---
> Shay Levi
> $cript Fanatic
> http://scriptolog.blogspot.com
>

> > http://www.vistax64.com/powershell/1...al-process-asy
> > nchronously.html#post726296
> >
> > ---
> > Shay Levi
> > $cript Fanatic
> > http://scriptolog.blogspot.com

> >> I wrote a script that will be used to upgrade the monitoring agents
> >> on our servers, and the one challenge that I have not been able to
> >> resolve is how to incorporate asynchronous processing into the
> >> solution. Since this is a production script, I am using PS V1. The
> >> script is written to take in a list of server, but the issue is that
> >> the script will not begin upgrading ServerB unless ServerA is
> >> complete AND no terminating errors were encountered while upgrading
> >> ServerA. I have read the SDK regarding Runspaces, and i found the
> >> new-job.ps1, PSThreading, and AsyncLib.ps1 scripts, but I have not
> >> been able to put this together to create an asynchronous solution..
> >>
> >> At this time, we are opening multiple PowerShell consoles, and
> >> running the script against a single server, but I would like to
> >> automate this process. We must be able to pass parameters and
> >> switches to the script, and have multiple runspaces executing at the
> >> same time. So in short, I would like to do something like this:
> >>
> >> Pseudo Code:
> >> Import-Csv "inputlist.csv" | foreach-object {
> >> open a new runspace
> >> execute the script with the correct parameters and switches
> >> if ($?){Start another runspace and move to the next server}
> >> if $numberofrunspace -eq 5 {loop until $numberofrunspace -le 4}
> >> }
> >> As soon as the runspace starts successfully, I would like to start
> >> upgrading the next server in the input file. This is where I keep
> >> running into the issue. If I can't get the second runspace to start
> >> until the first loop is complete, I still do not have asynchronous
> >> processing. Also, I would like to limit the number of runspaces to 5
> >> so we don't have a runspace open for every server in the input file.
> >> So in short, if anyone has figured out how to use runspaces and/or a
> >> PS1 library to create an asynchronous processing solution, please let
> >> me know...
> >>
> >> Any help with this issue will be greatly appreciated. Ozone
> >>

>
>
>

I've done very similar things arnoud, but i LOVE the design of this.. we
don't have to come back and check status of jobs being run async etc. it
just fits into the same workflow as your orginal script... I love it, at
first sight. I hope to get the chance to look at it in depth sometime.

Arnoud Jansveld wrote:

> Hi Ozone, you may want to take a look at my Split-Job script; it should do
> what you need and even collects the output (if any) from each asynchronous
> pipeline. In your case, you could run something like
>
> Import-Csv "inputlist.csv" | Split-Job { Upgrade-Agent $_} -MaxPipelines 5 |
> Out-File Upgrade-Agent.log
>
> The blog post with the script is here:
> http://www.jansveld.net/powershell/2...b-version-0-9/
>
> Hope this helps,
> Arnoud

I've done very similar things arnoud, but i LOVE the design of this.. we
don't have to come back and check status of jobs being run async etc. it
just fits into the same workflow as your orginal script... I love it, at
first sight. I hope to get the chance to look at it in depth sometime.

Arnoud Jansveld wrote:

> Hi Ozone, you may want to take a look at my Split-Job script; it should do
> what you need and even collects the output (if any) from each asynchronous
> pipeline. In your case, you could run something like
>
> Import-Csv "inputlist.csv" | Split-Job { Upgrade-Agent $_} -MaxPipelines 5 |
> Out-File Upgrade-Agent.log
>
> The blog post with the script is here:
> http://www.jansveld.net/powershell/2...b-version-0-9/
>
> Hope this helps,
> Arnoud

I want to thank everyone for the suggestions... They have given me
new ideas on how to finally incorporate asynchronous processing into
the script. Thanks for everyone's time, I really appreciate it...

Thanks
Ozone