Parallel Processing with version 2.0

Question

Say I wanted to loop through a collection of servers, and copy a bunch of files to them, this part is simple, but how would I go about doing it, so that it copies the files to each server in parallel rather than serial? I know version 3.0 has Start-Job,
but version 2.0 doesn't.
I cannot use Invoke-Command because PSRemoting is not setup and most likely isn't allowed (I know dumb, but I don't make the rules).
If you find that my post has answered your question, please mark it as the answer. If you find my post to be helpful in anyway, please click vote as helpful.
Don't Retire Technet

Answer 1

Workflows require PowerShell 3.0.  Jobs should do the trick, so long as they're used smartly.  There's quite a bit of overhead involved with starting up a new job, so I wouldn't use them for really small individual tasks, but for a long file transfer
like you're describing, you probably won't notice the difference.
Do keep in mind that each job has a new process of powershell.exe running, which eats up 50MB or more of RAM until it's finished.  You don't want too many of them going at once.
An alternative would be to use runspaces.  They're faster, but quite a bit more complicated to use properly.  There are a few functions available on the internet which try to wrap this concept up and make it easier to call from a
script; try searching for "Invoke-Parallel" and "ForEach-Parallel", if you're interested in that.