Home
  •  

Image Server Configuration

Microsoft.Windows.Server.6.3.WDSRole.Service.DeploymentServer.ImageServerConfiguration (UnitMonitor)

For the boot and install images to be available, the Windows Deployment Services image server must be configured and initialized correctly. The image server stores configuration information in the registry and in Active Directory Domain Services.

Knowledge Base article:

Summary

For the boot and install images to be available, the Windows Deployment Services image server must be configured and initialized correctly. The image server stores configuration information in the registry and in Active Directory Domain Services.

Event ID 264 -- Examine the code or contact the provider of the custom client

Custom clients must meet the requirements defined in the software development kit (SDK). The Windows Deployment Services server received a logging message from the custom deployment client that it does not understand. For example, the server may be configured to log only errors and warnings, and the custom client may have sent an informational event.

Event IDs 258, 259, 260, 261, 262, 263, 265, 266: Ensure that the Image Server can read settings from Active Directory.

The Windows Deployment Services image server must be able to read configuration settings from the registry and from Active Directory. To resolve this issue, ensure that the registry is not corrupt and that the image server has the required permissions to read data from the registry and from Active Directory Domain Services.

Resolutions

Event ID 264 -- Examine the code or contact the provider of the custom client

To resolve this issue, examine the code of the custom client to ensure that it meets these requirements, or contact the vendor for further support. To download the Microsoft Windows SDK for Windows Server 2012 R2, see http://go.microsoft.com/fwlink/?LinkID=104661.

Event IDs 258, 259, 260, 261, 262, 263, 265, 266: Ensure that the Image Server can read settings from Active Directory.

To resolve this problem, do the following in the specified order:

Ensure that the registry data is not corrupt

Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.

To perform these procedures, you must either be a member of the local Administrators group or have been delegated the appropriate authority.

To ensure that the registry data and permissions are correct:

If this data is correct, use the procedure in the following section to ensure that the domain controller is reachable.

Ensure that the domain controller is reachable

To perform these procedures, you must either be a member of the local Administrators group or have been delegated the appropriate authority.

To ensure that the domain controller is reachable:

Ensure that the Windows Deployment Services server has network connectivity

Note: The following procedures include steps for using the ping command to perform troubleshooting. Therefore, before performing these steps, determine whether the firewall settings or the Internet Protocol security (IPsec) settings on your network allow Internet Control Message Protocol (ICMP) traffic. ICMP is the TCP/IP protocol that the ping command uses.

To perform these procedures, you must either be a member of the local Administrators group or have been delegated the appropriate authority.

To determine whether there is a network connectivity problem:

If necessary, you can perform the following additional steps to help identify the root cause of the problem:

If the preceding steps do not fix your issue, use the procedure in the following section to ensure that the machine account has sufficient permissions.

Ensure that the machine account has sufficient permissions

On the computer that containsActive Directory Domain Services, grant the machine account for the Windows Deployment Services server permissions to read its service control point (SCP).

To perform this procedure, you must either be a member of the local Domain Admins group or have been delegated the appropriate authority.

To grant permissions to the SCP object:

Element properties:

TargetMicrosoft.Windows.Server.6.3.WDSRole.Service.DeploymentServer
Parent MonitorSystem.Health.ConfigurationState
CategoryConfigurationHealth
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.Windows.2SingleEventLog2StateMonitorType
RemotableTrue
AccessibilityPublic
Alert Message
Image Server Configuration
Event ID: {0} -- {1}
RunAsDefault

Source Code:

<UnitMonitor ID="Microsoft.Windows.Server.6.3.WDSRole.Service.DeploymentServer.ImageServerConfiguration" Accessibility="Public" Enabled="onEssentialMonitoring" Target="Microsoft.Windows.Server.6.3.WDSRole.Service.DeploymentServer" ParentMonitorID="SystemHealth!System.Health.ConfigurationState" Remotable="true" Priority="Normal" TypeID="Windows!Microsoft.Windows.2SingleEventLog2StateMonitorType" ConfirmDelivery="true">

  <Category>ConfigurationHealth</Category>

  <AlertSettings AlertMessage="Microsoft.Windows.Server.6.3.WDSRole.Service.DeploymentServer.ImageServerConfiguration_AlertMessageResourceID">

    <AlertOnState>Error</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>Error</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Data/Context/EventDisplayNumber$</AlertParameter1>

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

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

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

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

  </OperationalStates>

  <Configuration>

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

    <FirstLogName>Application</FirstLogName>

    <FirstExpression>

      <And>

        <Expression>

          <RegExExpression>

            <ValueExpression>

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

            </ValueExpression>

            <Operator>MatchesRegularExpression</Operator>

            <Pattern>^(258|259|260|261|262|263|265|266)$</Pattern>

          </RegExExpression>

        </Expression>

        <Expression>

          <SimpleExpression>

            <ValueExpression>

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

            </ValueExpression>

            <Operator>Equal</Operator>

            <ValueExpression>

              <Value Type="String">WdsImgSrv</Value>

            </ValueExpression>

          </SimpleExpression>

        </Expression>

      </And>

    </FirstExpression>

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

    <SecondLogName>Application</SecondLogName>

    <SecondExpression>

      <And>

        <Expression>

          <RegExExpression>

            <ValueExpression>

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

            </ValueExpression>

            <Operator>MatchesRegularExpression</Operator>

            <Pattern>^(256|267)$</Pattern>

          </RegExExpression>

        </Expression>

        <Expression>

          <SimpleExpression>

            <ValueExpression>

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

            </ValueExpression>

            <Operator>Equal</Operator>

            <ValueExpression>

              <Value Type="String">WdsImgSrv</Value>

            </ValueExpression>

          </SimpleExpression>

        </Expression>

      </And>

    </SecondExpression>

  </Configuration>

</UnitMonitor>