AD DS Printer Publishing: Troubleshoot connectivity with a domain controller

Microsoft.Windows.Server.10.0.PrintServer.PrintQueue.ADDSPrinterPublishing.System.Troubleshootconnectivitywithadomaincontroller.EventBased.UnitMonitor (UnitMonitor)

Troubleshoot connectivity with a domain controller.

Knowledge Base article:

Summary

Troubleshoot connectivity with a domain controller.

Configuration

The monitor takes a single configuration parameter that controls whether the “Print Spooler” should be monitored when enable the “Microsoft-Windows-PrintService/Admin and Microsoft-Windows-PrintService/Operational” Event logs and restart event log service. By default, the “Print Spooler” Monitor will be monitored only If the “Microsoft-Windows-PrintService/Admin and Microsoft-Windows-PrintService/Operational" Event logs are Enabled.

Resolutions

To troubleshoot connectivity with a domain controller:

On the print server, open the Command Prompt window, and then type ipconfig /all at the command prompt.
Make sure that the print server has an IP address in the correct IP address range, and that it does not have an Automatic Private IP Addressing (APIPA) address (an IP address in the 169.254.x.x range).
Ping the loopback address of 127.0.0.1 to verify that TCP/IP is installed and correctly configured on the local computer. If the ping is unsuccessful, this may indicate a corrupt TCP/IP stack or a problem with the network adapter.
Test whether you can ping the local IP address. If you can ping the loopback address but not the local IP address, there may be an issue with either the routing table or the network adapter driver.
Ping the DNS servers. If you cannot ping the DNS servers, this indicates a potential problem with the DNS servers, or possibly a network problem between the print server and the DNS servers. It can also mean that the DNS servers are not configured to respond to ping requests. To determine if this is the case, ping the DNS servers from a computer that you know is functioning properly on the network.
print_server_name

print_server_name

If the nslookup command fails but you can ping or otherwise access the DNS server, restart the DNS Server service on the DNS server. To do this, open the Services snap-in from the Administrative Tools folder, select the DNS Server service, and then click the Restart Service toolbar button.
http://go.microsoft.com/fwlink/?LinkID=57927
Retry publishing the printer.

Element properties:

Target

Microsoft.Windows.Server.10.0.PrintServerRole

Parent Monitor

System.Health.AvailabilityState

Category

StateCollection

Enabled

False

Alert Generate

True

Alert Severity

MatchMonitorHealth

Alert Priority

Normal

Alert Auto Resolve

True

Monitor Type

Microsoft.Windows.2SingleEventLog2StateMonitorType

Remotable

True

Accessibility

Public

Alert Message

AD DS Printer Publishing Alert By Troubleshoot connectivity with adomai ncontroller

{0}

RunAs

Default

Source Code:

<UnitMonitor ID="Microsoft.Windows.Server.10.0.PrintServer.PrintQueue.ADDSPrinterPublishing.System.Troubleshootconnectivitywithadomaincontroller.EventBased.UnitMonitor" Accessibility="Public" Enabled="false" Target="Microsoft.Windows.Server.10.0.PrintServerRole" ParentMonitorID="SystemHealth!System.Health.AvailabilityState" Remotable="true" Priority="Normal" TypeID="Windows!Microsoft.Windows.2SingleEventLog2StateMonitorType" ConfirmDelivery="true">

  <Category>StateCollection</Category>

  <AlertSettings AlertMessage="Microsoft.Windows.Server.10.0.PrintServer.PrintQueue.ADDSPrinterPublishing.System.Troubleshootconnectivitywithadomaincontroller.EventBased.UnitMonitor.AlertMessage">

    <AlertOnState>Error</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>MatchMonitorHealth</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Data/Context/EventDescription$</AlertParameter1>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="Negative" MonitorTypeStateID="FirstEventRaised" HealthState="Error"/>

    <OperationalState ID="Success" MonitorTypeStateID="SecondEventRaised" HealthState="Success"/>

  </OperationalStates>

  <Configuration>

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

    <FirstLogName>Microsoft-Windows-PrintService/Admin</FirstLogName>

    <FirstExpression>

      <And>

        <Expression>

          <SimpleExpression>

            <ValueExpression>

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

            </ValueExpression>

            <Operator>Equal</Operator>

            <ValueExpression>

              <Value Type="String">Microsoft-Windows-PrintService</Value>

            </ValueExpression>

          </SimpleExpression>

        </Expression>

        <Expression>

          <RegExExpression>

            <ValueExpression>

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

            </ValueExpression>

            <Operator>MatchesRegularExpression</Operator>

            <Pattern>^(328|329)$</Pattern>

          </RegExExpression>

        </Expression>

      </And>

    </FirstExpression>

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

    <SecondLogName>Microsoft-Windows-PrintService/Operational</SecondLogName>

    <SecondExpression>

      <And>

        <Expression>

          <SimpleExpression>

            <ValueExpression>

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

            </ValueExpression>

            <Operator>Equal</Operator>

            <ValueExpression>

              <Value Type="String">Microsoft-Windows-PrintService</Value>

            </ValueExpression>

          </SimpleExpression>

        </Expression>

        <Expression>

          <RegExExpression>

            <ValueExpression>

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

            </ValueExpression>

            <Operator>MatchesRegularExpression</Operator>

            <Pattern>^(332|334|336|338|342|343|344|345|346)$</Pattern>

          </RegExExpression>

        </Expression>

      </And>

    </SecondExpression>

  </Configuration>

</UnitMonitor>