Using PowerShell Remote Sessions in a large SCOM environment

I have previously blogged using SCOM PowerShell snap-in and SDK client in a PowerShell remote session to avoid maintain a consistent SDK connection to RMS server. I just found out there might be a potential issue when using this technique to run scripts against a reasonably large SCOM management group. By default, the maximum amount of memory a PowerShell remote session can use is limited to 150MB. You can check this setting on your computer by using Depending on how much data the remote session has to process, you might running into problems. For example, compare these 2 scripts: Sample

%d bloggers like this: