re: Gain Remote Access to the Get-ExCommand Exchange Command

Doug — Wed, 15 Feb 2012 00:43:22 GMT

Ben is correct. The function as written seems to work since if you've got a manual Exchange session most of the commands that are functions are Exchange commands.

If you run get-excommand | ? {$_.Name -match "clear"} with a manual Exchange session, you'll see Clear-Host as a result which is not an Exchange command. If you run it from a proper Exchange Management Shell, that won't be there.

Additionally, the actual Get-ExCommand returns too many results as well. If for instance, you import the Active Directory module from an Exchange Management Shell, Get-ExCommand will return those commands as too. Try get-excommand | ? {$_ -match "get-adc"} for instance.

re: Gain Remote Access to the Get-ExCommand Exchange Command

Ben — Mon, 13 Feb 2012 15:34:41 GMT

This is helpless, the $global:importResults is set in the Exchange's CommonConnectFunctions.ps1 script, which is obviously not needed to make a manual remoting to the Exchange's Remote PowerShell. Hence, during a manual remoting this variable will not be defined, and will not be mapped to the Exchange's imported module, and would be $null (or something else wrong which would break your pseudo-function).