Exchange 2010: HelpUri property from commandInfo object type

In Exchange 2010, by default, PowerShell has 7 Cmdlets loaded in remote session for "import-session *" scenario which leads to about 30 MB of memory spike. Any additional Exchange help files that’re loaded will cause additional spike, which’s seem when users would call get-help on Cmdlets, PowerShell’s just preempting spike. In order to correct and prevent these spikes there’s a […]

In Exchange 2010, by default, PowerShell has 7 Cmdlets loaded in remote session for "import-session *" scenario which leads to about 30 MB of memory spike. Any additional Exchange help files that’re loaded will cause additional spike, which’s seem when users would call get-help on Cmdlets, PowerShell’s just preempting spike. In order to correct and prevent these spikes there’s a manual configuration that can be done as part of steps during an Exchange Server deployment. This configuration’s not part of Exchange setup because file belongs to PowerShell. In this case change can be made using a simple script that’ll go into PowerShell directory and make necessary change to ComandInfo object type removing HelpUri property from it.