Symptoms
When the Test-PowerShellConnectivity cmdlet is executed in a Microsoft Exchange Server 2010 organization that is monitored by a System Center Operations Manager (SCOM) server, you receive a SCOM alert that resembles the following:
MonitoringRuleID: RuleID MonitoringObjectDisplayName: DisplayNameMonitoringObjectFullName: FullNameManagement Group: Group ModifiedBy: User TimeRaised(SCOM): Date&Time CreateDatetime(RADAR): Date&Time ModifiedDatetime(SCOM): Date&Time Description: The test couldn't test the internal URL of this virtual directory, because the InternalURL property isn't set. Virtual directory: PowerShell-Proxy (Default Web Site) Diagnostic command: "Test-PowerShellConnectivity -TestType:Internal -MonitoringContext:$true -TrustAnySSLCertificate:$true"EventSourceName: MSExchange Monitoring PowerShellConnectivity Internal.
Cause
This issue occurs because a monitoring rule on the SCOM server executes the Test-PowerShellConnectivity cmdlet against a Client Access server that handles proxy requests. Additionally, because the internal URL of the PowerShell virtual directory is not set on the Client Access server, the execution of the Test-PowerShellConnectivity cmdlet fails.
Resolution
To resolve this issue, install Exchange Server 2010 Service Pack 3 (SP3) on the Exchange Server 2010 servers. For more information about Exchange Server 2010 SP3, click the following article number to view the article in the Microsoft Knowledge Base:
2808208 Description of Exchange Server 2010 Service Pack 3
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
For more information about the Test-PowerShellConnectivity cmdlet, go to the following Microsoft website:
General information about the Test-PowerShellConnectivity cmdletFor more information about the failure to execute the Test-PowerShellConnectivity cmdlet by the monitoring rule, go to the following Microsoft website:
Failed to execute the Test-PowerShellConnectivity (Internal) diagnostic cmdletFor more information about the Windows PowerShell remote commands, go to the following Microsoft website:
