I'm trying to troubleshoot a PowerShell script that uses `Invoke-Command` with `Start-Process`, but I'm having trouble retrieving the results from the script block. I have the following functions in my script to set up a server and client for network latency testing using ntttcp. Despite validating that the `ntttcp.exe` is running on the server, I can't seem to capture the output back to the client. Any guidance on how to enhance my script to get the expected results would be greatly appreciated!
3 Answers
It looks like your script block isn't set up to wait for the process to finish. You should add the `-Wait` parameter to the `Start-Process` command. This way, it will hold off on proceeding until the `ntttcp.exe` execution is complete, which might resolve the output issues you're facing.
Just a heads up, your pipeline inputs in the Begin block might lead to inconsistent behavior, depending on how you call those functions. It’s a good idea to rethink how you manage those sessions, either by closing them properly or keeping them alive for the duration you need to minimize overhead. Also, consider avoiding `Write-Host` and instead output PowerShell objects for better logging and handling later.
Thanks for the feedback! I'm aiming to automate a manual process and will definitely re-evaluate how I'm managing sessions and outputs in my script.
You're missing a return value from the `Invoke-Command`. When you run the `Invoke-Command`, try assigning it to a variable. This will allow you to capture any output data you might need later. You might want to check out some resources on collecting return values from `Invoke-Command` for better results.
That makes sense! I didn't think about assigning that output to a variable. I’ll give it a try and see if that helps.
Right, I see what you're saying. The `Start-ntttcpServer` function indeed needs the `-Wait` flag on the `Start-Process` for it to finish properly before moving to the client function. Thanks for the tip!