PowerShell Remote Processes Execution and Monitoring - Runspaces vs Workflows

i trying fire off automated update provided our electronic medical record(emr) system vendor against list of devices(about 70).  the update can take while run , need check registry key after install finished verify has updated.  the issue running want remotely start installs via powershell using runspaces , monitor completion.  i prefer not use psexec security reasons.  unless missing method, leaves using win32_process via wmi start process.  the issue having monitor process termination in way provides low overhead.  i have looked monitoring system.diagnostics.process.exited event, generated if enableraisingevents property set true.  since, starting process via win32_process don't know of way specify property.  i have looked monitoring event id 4689, don't have enabled in environment @ time.  is there way better doing wait?

do have remoting enabled on machines?

edit:  

from description of problem, i'd use runspaces start process on each target computer , return computer name , process id of update started.   save information disk .csv file  and use script periodically read in , check each machine see if process still running.  

---

[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

Windows Server  >  Windows PowerShell