Home deployment troubleshooting wds windows server

Troubleshooting Deployment? Enable Logging in Windows Deployment Services (WDS) for Insights

Updated: • 0 • min read
Table of Contents

This article details the process of enabling logging within Windows Deployment Services (WDS) on Windows Server environments. Logging is a critical tool for diagnosing and resolving issues that may arise during the deployment process. By activating and analyzing logs, administrators can gain valuable insights into the inner workings of WDS, pinpointing the root causes of deployment failures and ensuring smoother, more reliable system deployments. This guide provides a comprehensive walkthrough of how to enable and utilize logging across various WDS components.

Introduction

This document serves as a guide to enabling logging within Windows Deployment Services (WDS) on Windows Server. It is essential to understand how to activate and collect log data to effectively troubleshoot deployment problems. This information is invaluable for diagnosing issues within WDS, from server health to client interactions, and management components. By following the steps outlined in this article, administrators can proactively identify and address potential deployment bottlenecks, leading to a more robust and efficient deployment infrastructure.

Overview

Warning: Incorrect modifications to the Windows Registry can lead to severe system instability, potentially requiring a complete operating system reinstallation. Always exercise extreme caution and back up your registry before making any changes. Microsoft does not guarantee the resolution of problems resulting from improper registry modifications. Modify the registry at your own risk and only when necessary for troubleshooting purposes.

Windows Deployment Services incorporates logging and tracing mechanisms within each of its components. These features, when enabled, generate detailed records of operations and events, which can be crucial for troubleshooting. Analyzing these logs allows administrators to understand the sequence of events leading to an issue and identify the specific component that is malfunctioning. The following sections provide step-by-step instructions to enable logging and tracing for different parts of WDS, ensuring comprehensive diagnostic coverage.

General WDS Server Health

For a quick overview of the general health of your WDS server, you can use a simple command to generate a health report. This report is then logged in both the Application and System event logs, providing a centralized location for monitoring server status. This is a useful first step in diagnosing general server issues or verifying the basic operational status of WDS.

To generate general server health information, execute the following command in an elevated command prompt:

WDSUTIL /get-server /show:all /detailed

This command triggers the generation of comprehensive server health information. This information is automatically recorded in the Application log and the System log within Event Viewer. Reviewing these logs after running the command provides a snapshot of the server’s overall health and can highlight any immediate issues requiring attention.

WDS Server Component

To delve deeper into the health of the core WDS server component itself, a similar command can be utilized. This command focuses specifically on the WDS server component and generates detailed health information related to its operations. Like the general server health command, the output is directed to the Application and System logs for convenient review.

To generate health information specifically for the WDS server component, use the same command as for general server health:

WDSUTIL /get-server /show:all /detailed

Executing this command again will populate the Application log and System log with information specific to the WDS server component. This allows for a focused examination of the WDS server’s operational status, separate from the broader system health, aiding in pinpointing component-specific problems.

Obtain Trace Logs for Windows Server

For more granular troubleshooting, trace logs provide a detailed sequence of events. To access trace logs for Windows Server WDS components, you need to utilize Event Viewer and enable specific log channels. This involves navigating to the Deployment-Services-Diagnostics section within the Applications and Services Logs to activate logging for detailed tracing information.

To access trace logs for Windows Server, follow these steps:

  1. Open Event Viewer. You can do this by searching for “Event Viewer” in the Start Menu or running eventvwr in a command prompt.
  2. In the Event Viewer window, navigate to Windows Logs -> Applications and Services Logs -> Microsoft -> Windows -> Deployment-Services-Diagnostics.
  3. Right-click on the Deployment-Services-Diagnostics channel.
  4. Select Enable Log from the context menu.

Event Viewer

After enabling the log channel, you can configure specific WDS components for tracing by modifying registry settings. These settings allow you to control which aspects of WDS are logged in detail, focusing on areas relevant to your troubleshooting efforts. By setting specific registry keys to a value of 0, you enable tracing for components like WDS Multicasting, PXE, and TFTP.

The following registry keys control tracing for specific WDS components. Setting these keys to a value of 0 enables tracing:

  • WDS Multicasting:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WDSServer\Providers\WDSMC\TraceDisabled
  • WDS PXE:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WDSServer\Providers\WDSPXE\TraceDisabled
  • WDS TFTP:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WDSServer\Providers\WDSTFTP\TraceDisabled

Registry Editor

In addition to enabling tracing, WDS servers support further customization through the following registry keys, which control the level of detail in tracing:

  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WDSServer\Providers\WDSTFTP\TraceFlags
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WDSServer\Providers\WDSMC\TraceFlags

These TraceFlags keys can be set to specific hexadecimal values to fine-tune the tracing level:

  • 7F0000: Includes packet tracing and protocol tracing for maximum detail.
  • 3F0000: Excludes packet tracing but includes protocol tracing.
  • 3E0000: Excludes both packet tracing and protocol tracing (default value).

Note: Enabling tracing can impact server performance due to the overhead of logging detailed information. It is recommended to disable tracing once troubleshooting is complete and logs are no longer required to minimize performance impact on the WDS server.

After configuring these registry settings, the trace information for the WDS server component is logged to the following file: %windir%\Tracing\wdsserver.log. This log file contains detailed trace information based on the enabled components and tracing levels configured in the registry.

WDS Management Components

Similar to the WDS server component, you can generate health information for WDS management components. This is useful for diagnosing issues related to the administrative aspects of WDS, such as the WDS console or management tools. This command provides insights into the operational status of the management infrastructure of WDS.

To generate health information for WDS management components, use the same WDSUTIL command:

WDSUTIL /get-server /show:all /detailed

This command, when executed, logs management component health information to the Application log and System log. Reviewing these logs helps in identifying problems within the WDS management layer, ensuring smooth administrative operations.

Enable Tracing

For in-depth analysis of WDS management operations, tracing can be enabled for both the WDS management component and the WDS Microsoft Management Console (MMC) component. This is crucial for troubleshooting issues related to administrative tasks performed through the WDS console or management tools. Enabling tracing for these components provides detailed logs of management actions and potential errors.

To enable tracing for WDS management components, you need to modify specific registry entries. These entries control file tracing for both the management component itself and the MMC interface used to manage WDS.

For the Management Component

To enable tracing for the WDS management component, configure the following registry entry:

  • Path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tracing\WDSMGMT
  • Name: EnableFileTracing
  • Value Type: REG_DWORD
  • Value Data: 1

For the MMC Component

To enable tracing for the WDS MMC component, configure the following registry entry:

  • Path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tracing\WDSMMC
  • Name: EnableFileTracing
  • Value Type: REG_DWORD
  • Value Data: 1

After setting these registry entries, trace information is logged to the following files:

  • WDS Management Component: %windir%\Tracing\wdsmgmt.log
  • WDS MMC Component: %windir%\Tracing\wdsmmc.log

These log files capture detailed trace information for the respective components, providing valuable data for troubleshooting management-related issues within WDS.

WDS Legacy Components

For environments still utilizing legacy management functions, tracing can be enabled for the RISetup component. This is important for troubleshooting issues related to older deployment methods or configurations that rely on RISetup functionalities. Enabling tracing for RISetup provides insights into the operations of these legacy components.

To enable tracing for the RISetup component, set the following registry entry:

  • Path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tracing\RISetup
  • Name: EnableFileTracing
  • Value Type: REG_DWORD
  • Value Data: 1

For capturing trace logs during the WDSCapture operation, a slightly different procedure is required due to the nature of the capture environment. This involves accessing a command prompt within the Capture Windows PE environment and enabling tracing for the WDSCapture component directly within that environment.

To obtain trace logs in the WDSCapture operation, follow these steps:

  1. Start the Capture Windows PE boot image.
  2. When the Capture Wizard starts, press SHIFT+F10 to open a command prompt.
  3. Enable tracing for the WDSCapture component within the command prompt environment:
    a. Start Registry Editor by typing regedit and pressing Enter.
    b. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tracing\WDSCapture.
    c. Set the EnableFileTracing registry entry to 1 as a REG_DWORD value.
  4. Start a second instance of the WDSCapture component. This is crucial for isolating the tracing process.
  5. Reproduce the problem using the second instance of WDSCapture.

Note: Do not close the original instance of WDSCapture. Closing it will restart Windows PE. Use ALT+TAB to switch between instances. The trace log file for WDSCapture will be generated at X:\Windows\Tracing\WDSCapture.log within the Windows PE environment.

WDS Client Components

Client-side logging can be activated to monitor the interactions between WDS clients and the server. This is particularly useful for troubleshooting client-specific deployment issues. Client logging can be enabled and configured directly on the WDS server, controlling the level of detail captured in the logs.

To enable client logging functionality, run the following command on the WDS server in an elevated command prompt:

WDSUTIL /Set-Server /WDSClientLogging /Enabled:Yes

After enabling client logging, you can adjust the logging level to control the types of events that are recorded. Different logging levels offer varying degrees of detail, allowing you to focus on specific types of issues, from errors to informational events.

To change the logging level for WDS clients, use the following command on the WDS server, choosing from None, Errors, Warnings, or Info for the LoggingLevel:

WDSUTIL /Set-Server /WDSClientLogging /LoggingLevel:{None|Errors|Warnings|Info}

Note: Each logging level includes all events from the preceding levels. For example, Warnings level includes both warnings and errors.

The logging levels are defined as follows:

  • NONE: Disables client logging completely (default).
  • ERRORS: Logs only error events.
  • WARNINGS: Logs warning and error events.
  • INFO: Logs informational events, warnings, and errors (highest detail).

To view the client event logs, access Event Viewer on the WDS server and navigate to the Deployment-Services-Diagnostics logs. These logs are categorized into Admin and Operational logs, providing a structured view of client-related events.

To view client event logs, follow these steps on the WDS Server:

  1. Open Server Manager.
  2. Click Diagnostics in the left pane.
  3. Click Event Viewer.
  4. Navigate to Applications and Services Logs -> Microsoft -> Windows -> Deployment-Services-Diagnostics.

Within the Deployment-Services-Diagnostics logs:

  • The Admin log contains error events.
  • The Operational log contains informational messages.

Some errors in these logs may reference architecture codes. These codes indicate the processor architecture of the client experiencing the issue:

  • Architecture 0: x86 processor architecture.
  • Architecture 6: IA-64 processor architecture.
  • Architecture 9: x64 processor architecture.

Setup Logs from the Client Computer

Setup logs from the client machine are invaluable for diagnosing issues that occur during the operating system installation phase of deployment. The location of these logs varies depending on the stage of the deployment process at which the failure occurs. Understanding these locations allows for efficient retrieval of setup logs for troubleshooting.

The location of setup logs depends on when the failure occurs during the deployment process:

  • Failure in Windows PE before disk configuration: Logs can be found at X:\Windows\Panther. Access this location by pressing Shift+F10 in Windows PE to open a command prompt and then navigating to the directory.
  • Failure in Windows PE after disk configuration: Logs are located on the local disk volume (usually drive C:) at $Windows.~BT\Sources\Panther. Access this location via Shift+F10 and navigating to the directory.
  • Failure on the first boot after image application: Logs are located in the \Windows\Panther folder on the local disk volume (usually drive C:).

These Panther logs provide detailed information about the Windows setup process, including any errors encountered, making them essential for diagnosing installation-related problems.

Data Collection

Effective troubleshooting often requires collecting relevant log data from various sources. This article has outlined methods for enabling and accessing logs from different WDS components and client machines. Gathering these logs systematically and analyzing them in conjunction with error messages and observed behavior is crucial for identifying and resolving deployment issues efficiently. Remember to disable unnecessary logging after troubleshooting to maintain optimal system performance.

We encourage you to utilize these logging techniques to effectively troubleshoot your Windows Deployment Services environment. Do you have any experiences with WDS logging that you’d like to share or any further questions? Please leave a comment below!

Post a Comment