Home
  •  

MECM Failed to configure proxy setting on WSUS server

MECM.WsusConfigurationManager.FailedToConfigProxy.Event.Rule (Rule)

This rule generates alert if the WSUS control manager fails to configure proxy setting on WSUS server

Knowledge Base article:

Summary

Configuring a Windows Server Update Services (WSUS) server to be used with the Configuration Manager site involves two components, the WSUS_Configuration_Manager and WSUS_Control_Manager. WSUS_Configuration_Manager sets the Configuration Manager site-specific properties that are common to all software update point role computers. WSUS_Control_Manager configures the properties that are specific to a software update point role, such as the proxy server to use or the proxy credentials to be used with the proxy server.

Causes

This condition could occur because:

Resolutions

Check the [ConfigMgrInstallationFolder]\Logs\WSUSCtrl.log on the specific computer that is raising this alert.

Element properties:

TargetMECM.WsusConfigurationManager
CategoryEventCollection
EnabledTrue
Event_ID7000
Event SourceSMS Server
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
RemotableTrue
Alert Message
MECM Failed to configure proxy setting on WSUS server alert
The WSUS control manager failed to configure the proxy setting on WSUS server {0}
Event Description: {1}
Event LogApplication

Member Modules:

ID Module Type TypeId RunAs 
DS DataSource Microsoft.Windows.EventProvider Default
Alert WriteAction System.Health.GenerateAlert Default

Source Code:

<Rule ID="MECM.WsusConfigurationManager.FailedToConfigProxy.Event.Rule" Enabled="true" Target="MECM.WsusConfigurationManager" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">

  <Category>EventCollection</Category>

  <DataSources>

    <DataSource ID="DS" TypeID="Windows!Microsoft.Windows.EventProvider">

      <ComputerName>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>

      <LogName>Application</LogName>

      <Expression>

        <And>

          <Expression>

            <SimpleExpression>

              <ValueExpression>

                <XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>

              </ValueExpression>

              <Operator>Equal</Operator>

              <ValueExpression>

                <Value Type="UnsignedInteger">7000</Value>

              </ValueExpression>

            </SimpleExpression>

          </Expression>

          <Expression>

            <SimpleExpression>

              <ValueExpression>

                <XPathQuery Type="String">PublisherName</XPathQuery>

              </ValueExpression>

              <Operator>Equal</Operator>

              <ValueExpression>

                <Value Type="String">SMS Server</Value>

              </ValueExpression>

            </SimpleExpression>

          </Expression>

        </And>

      </Expression>

    </DataSource>

  </DataSources>

  <WriteActions>

    <WriteAction ID="Alert" TypeID="Health!System.Health.GenerateAlert">

      <Priority>1</Priority>

      <Severity>2</Severity>

      <AlertName/>

      <AlertDescription/>

      <AlertOwner/>

      <AlertMessageId>$MPElement[Name="MECM.WsusConfigurationManager.FailedToConfigProxy.Event.Rule.AlertMessage"]$</AlertMessageId>

      <AlertParameters>

        <AlertParameter1>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/PrincipalName$</AlertParameter1>

        <AlertParameter2>$Data/EventDescription$</AlertParameter2>

      </AlertParameters>

      <Suppression>

        <SuppressionValue/>

      </Suppression>

      <Custom1/>

      <Custom2/>

      <Custom3/>

      <Custom4/>

      <Custom5/>

      <Custom6/>

      <Custom7/>

      <Custom8/>

      <Custom9/>

      <Custom10/>

    </WriteAction>

  </WriteActions>

</Rule>