Mike Pfeiffer has a great post on implicit remoting of Exchange modules across the Internet via ISA/TMG publishing.
From the start of his post:
This post is inspired by a question asked during my presentation at the last Arizona PowerShell User Group (AZPOSH) meeting. After I demonstrated Exchange management via PowerShell implicit remoting, one of our members said, “Ok, so how do I do that over the internet?”. Due to time constraints, I didn’t go into it the process in great detail, so I’ve decided to do that here, in this post. To demonstrate this configuration, I’ll use a basic topology with a single Exchange 2010 server running the core roles (hub, cas, mailbox). I will be publishing the PowerShell virtual directory to the internet via HTTPS using Forefront Threat Management Gateway (TMG), as shown in the diagram below.
The key to this is configuring /powershell/ publishing via TMG…
I have mostly written scripts that leverage the Active Directory commandlets by importing the ActiveDirectory powershell module. My customer requirements now have me branching out into Exchange territory which requires the use of the Exchange Powershell module and associated commandlets. I have learned that there is no simple way to “install” the Exchange Powershell module on a system without installing the Exchange Management Tools
There is no simple “import-module” method to get the Exchange commandlets from a Powershell remote session. The following describes a method to discover an Exchange server and use that for Exchange Powershell commandlets in a script. First the script discovers all Exchange CAS Servers by finding servers that registered the “exchangeRFR” SPN and then attempts a Powershell connection to any Exchange server running Windows Server 2008. This ensures that the script connects to an Exchange 2007 or 2010 server.
NOTE: This may attempt a remote Exchange Powershell connection to Exchange servers that are not running Exchange 2007/2010.
UPDATED CODE:
Write-Verbose “Find Exchange servers `r ”
$SessionSuccess = $False
[array] $ExchangeCASServers = Get-ADComputer -filter { (operatingsystem -like “*Server*”) -and (ServicePrincipalNames -like “*exchangeRFR*”) } -properties *
$ExchangeCASServersCount = $ExchangeCASServers.Count
Write-Verbose “Found $ExchangeCASServersCount Exchange servers `r”
[array] $ExchangeServerList = @()ForEach ($Server in $ExchangeCASServers)
{ ## OPEN ForEach Server in ExchangeCASServers
[array] $ExchangeServerList += $Server.Name
} ## OPEN ForEach Server in ExchangeCASServersForEach ($Server in $ExchangeServerList)
{ ## OPEN ForEach Server in ExchangeCASServers
$ServerInfo = Get-ADComputer -Identity $Server -Properties *
IF ( $ServerInfo.OperatingSystem -like “*2008*”)
{ ## OPEN IF Server OS is 2008
Write-Verbose “$Server is running 2008. Now checking for Exchange Powershell Remoting… `r ”
TRY
{ ## OPEN TRY Powershell Remote Session
Write-Verbose “Create a Powershell remote session to a server with the commandlets installed. `r ”
$ExchangeSession = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://$Server/PowerShell/ -Authentication Kerberos
Write-Verbose “Use the newly created remote Powershell session to send a command to that session `r ”
Import-PSSession $ExchangeSession
IF ($ExchangeSession.Availability -eq “Available”) {Write-Host “Exchange connection to $Server successful. `r ” ; $SessionSuccess = $True ; break }
} ## CLOSE TRY Powershell Remote SessionCATCH
{ Write-Verbose “The Exchange server $ServerHostName does not accept a remote Powershell session with currrent credentials. `r “ }
} ## CLOSE IF Server OS is 2008
ELSE { Write-Output “$Server is Not running Windows Server 2008. Skipping… `r ” }
} ## CLOSE ForEach Server in ExchangeCASServers
Here is the isolated script block code that pulls in the Exchange commandlets remotely.
Write-Verbose “Create a Powershell remote session to a server with the commandlets installed. `r “
$ExchangeSession = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://$ExchangeCASServers[0]/PowerShell/ -Authentication Kerberos
Write-Verbose “Use the newly created remote Powershell session to send a command to that session `r “
Import-PSSession $ExchangeSession
This pulls in Exchange Powershell modules from a CAS server and makes them available to the local machine.
Microsoft includes a Powershell script on machines that the Exchange Management Tools are installed on. This script is automaticaly run when clicking on “Exchange Management Shell” since this is only a shortcut to the command:
“C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -noexit -command “. ‘C:\Program Files\Microsoft\Exchange Server\V14\bin\RemoteExchange.ps1‘; Connect-ExchangeServer -auto”
Note in the command above the script name I bolded named “RemoteExchange.ps1″. This script discovers an appropriate Exchange server, connects to it, and “imports” the Exchange powershell commandlets. It may be possible to copy this Powershell script to another machine and use it as part of a pseudo-Exchange Management Shell (though I haven’t tested this yet).
That was easy!
Isn’t Powershell fun?
Written by 
