Home
  •  

ConfigMgr 2007 Consolidated Status: WSUS Configuration Manager detected that a WSUS Server can not sync from the parent WSUS Server as there is no parent WSUS Server

SMSv4_Consolidated_Status__WSUS_Configuration_Manager_detected_that_a_WSUS_Server_can_not_sync_from_the_parent_WSUS_Server_as_there_is_no_parent_WSUS_Server_1_Rule (Rule)

Knowledge Base article:

Summary

The Windows Server Update Services (WSUS) server has to have the parent WSUS server property (also known as the upstream WSUS server) set correctly before it can synchronize updates. For the central Configuration Manager site, the parent WSUS server should be set to “Microsoft Update” and for the software update point on the child Configuration Manager site, the upstream WSUS server is set to the name of the software update point role that is configured on the parent site. If the parent site does not have a software update point role configured, then the child site WSUS server can have the parent WSUS server set to “Microsoft Update”.

For more information about this error, see the SMS\Logs\WCM.log.

Causes

This condition could occur because:

Element properties:

TargetMicrosoft.SystemCenter.ConfigurationManager.2007.Microsoft_SMSv4_Site_Database_Servers_Installation
CategoryEventCollection
EnabledFalse
Alert GenerateFalse
RemotableTrue
CommentMom2005ID='{14056B50-C1E6-40A5-9DC2-672B548EE8A6}';MOM2005ComputerGroupID={15348338-2E39-4B34-9DFF-4719AE7F1CCE}

Member Modules:

ID Module Type TypeId RunAs 
_F320DA51_13BF_11D3_B2CD_00A0C92A28B4_ DataSource System.Mom.BackwardCompatibility.FilteredEvent.DataProvider Default
ConsolidatedEventWriteAction WriteAction System.Mom.BackwardCompatibility.ConsolidatedEventResponse Default

Source Code:

<Rule ID="SMSv4_Consolidated_Status__WSUS_Configuration_Manager_detected_that_a_WSUS_Server_can_not_sync_from_the_parent_WSUS_Server_as_there_is_no_parent_WSUS_Server_1_Rule" Target="Microsoft.SystemCenter.ConfigurationManager.2007.Microsoft_SMSv4_Site_Database_Servers_Installation" Enabled="false" ConfirmDelivery="false" Comment="Mom2005ID='{14056B50-C1E6-40A5-9DC2-672B548EE8A6}';MOM2005ComputerGroupID={15348338-2E39-4B34-9DFF-4719AE7F1CCE}">

  <Category>EventCollection</Category>

  <DataSources>

    <DataSource ID="_F320DA51_13BF_11D3_B2CD_00A0C92A28B4_" Comment="{F320DA51-13BF-11D3-B2CD-00A0C92A28B4}" TypeID="MomBackwardCompatibility!System.Mom.BackwardCompatibility.FilteredEvent.DataProvider">

      <Expression>

        <And>

          <Expression>

            <SimpleExpression>

              <ValueExpression>

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

              </ValueExpression>

              <Operator>Equal</Operator>

              <ValueExpression>

                <Value>6610</Value>

              </ValueExpression>

            </SimpleExpression>

          </Expression>

          <Expression>

            <SimpleExpression>

              <ValueExpression>

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

              </ValueExpression>

              <Operator>Equal</Operator>

              <ValueExpression>

                <Value>ConfigMgr 2007 Monitor SMS Status Messages</Value>

              </ValueExpression>

            </SimpleExpression>

          </Expression>

        </And>

      </Expression>

    </DataSource>

  </DataSources>

  <WriteActions>

    <WriteAction ID="ConsolidatedEventWriteAction" TypeID="MomBackwardCompatibility!System.Mom.BackwardCompatibility.ConsolidatedEventResponse">

      <ConsolidationProperties>

        <PropertyXPathQuery>EventDisplayNumber</PropertyXPathQuery>

        <PropertyXPathQuery>PublisherName</PropertyXPathQuery>

        <PropertyXPathQuery>EventDescription</PropertyXPathQuery>

      </ConsolidationProperties>

      <Interval>3600</Interval>

    </WriteAction>

  </WriteActions>

</Rule>