Performance Difference between InvokeCommand and ImportSession

kumar — Wed, 10 Nov 2010 06:00:00 GMT

I have a C# application that issues commands and scripts (1 or 2 liners) to an Exchange 2010 through remote powershell (Configuration "Microsoft.Exchange"). I found two ways to do this - create a remote session and then (a) using InvokeCommand on that session with my scriptblock or (b) ImportSession and then running the commands/scripts on that shell. I understand the way the two options work, but my question is regarding the performance difference between these two options. I see that when I have a script with pipes (obviously) followed by select or foreach or similar, the network traffic is much higher in the ImportSession option. Is this expected? I would go for InvokeCommand, but my problem is that many of the basic script constructs (like where, foreach etc.) are not accepted in the script block. It reports 'command not found error'. Any suggestions, advices?

thanks,

Kumar

Search results for 'app:forums' matching tags 'Remoting' and 'performance'

Performance Difference between InvokeCommand and ImportSession