ODMHE - How to validate the PowerShell endpoint is configured correctly (4381610)

This article goes through the steps needed to check the PowerShell endpoint and that it is correctly configured for an on-premise Exchange.

The PowerShell endpoint address is derived from the EWS URL which is entered in the ODMHE (On Demand Migration Hybrid Exchange) configuration
http(s)://server-name/EWS/Exchange.asmx -> http(s)://server-name/powershell

The following steps will verify whether the PowerShell endpoint is correctly configured in the on-premise Exchange.

1. Check with web browser that PowerShell endpoint is available from outside
   
   In the case that the IPs had to be whitelisted, this test must be done from an IP which is whitelisted.
   
   Response when available: 
   
    
   Response when not available: 
   
    
   
   
2. Check if PowerShell endpoint is configured on Exchange on-prem IIS
   
   Open IIS Manager
   Expand the server
   Expand Sites
   Expand the Default Web Site
   Click PowerShell in the list
   On the right Actions pane click Basic Settings
   Verify the Application pool value is present
   
    
   
    
3. Check if Application pool configured for PowerShell endpoint is not stopped.
   
   Open IIS Manager
   Expand the server
   Click Application Pools
   Locate MSExchangePowerShellFrontEndAppPool 
   If the Application above is not started, right click on the name and choose start
   
    
4. If EWS endpoint works but Powershell does not try to compare EWS and PowerShell applications on IIS
   Try to compare some app settings like SSL settings, …
   
   Open IIS Manager
   Expand the server
   Expand the Sites
   Expand the Default Web Site
   Click PowerShell
   In the center window click on SSL Settings
   Compare the settings here to other sites in the list
   
   
5.  Compare ExternalUrl for EWS endpoint and PowerShell endpoint 
   
   1. Get-WebServicesVirtualDirectory | select internalUrl, ExternalUrl
   2. Get-PowerShellVirtualDirectory | select internalUrl, ExternalUrl
      
       
      
      
6. Check if Basic authentication is enabled
   1. Get-PowerShellVirtualDirectory | select *
      
       
      
      
7. Check if Admin account configured in ODM has required permissions needed for PowerShell operations
   1. User Guide - https://support.quest.com/technical-documents/on-demand-migration/current/hybrid-exchange-user-guide/3
      
8.  If PowerShell endpoint is correctly configured it should be possible to connect via PowerShell 
   
   $UserCredential = Get-Credential
   $SessionOpt = New-PSSessionOption -SkipCACheck:$true -SkipCNCheck:$true -SkipRevocationCheck:$true $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://[TODO]/PowerShell/ -Authentication Basic -Credential $UserCredential -SessionOption $SessionOpt Import-PSSession $Session -DisableNameChecking
   #test if we can get an mailbox
   Get-Mailbox