Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

SCOM alert when the Test-PowerShellConnectivity cmdlet is executed in an Exchange Server 2010 organization


View products that this article applies to.

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: DisplayName
MonitoringObjectFullName: FullName
Management 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.

↑ Back to the top


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.

↑ Back to the top


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

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More Information

For more information about the Test-PowerShellConnectivity cmdlet, go to the following Microsoft website:For more information about the failure to execute the Test-PowerShellConnectivity cmdlet by the monitoring rule, go to the following Microsoft website:For more information about the Windows PowerShell remote commands, go to the following Microsoft website:

↑ Back to the top


Keywords: kbqfe, kbfix, kbsurveynew, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 2779351
Revision : 1
Created on : 1/7/2017
Published on : 2/12/2013
Exists online : False
Views : 313