Example 1: Diagnostics can Identify and Automatically Repair or Recommend a Solution
Updated: December 23, 2009
Applies To: Windows 7, Windows Server 2008 R2
This example demonstrates the phases through which NDF diagnostics progresses in a diagnostic session for a failed attempt to connect to a wireless network. Upon completion, the example demonstrates how a user can review the resulting Troubleshooting Report to obtain additional details about the diagnostic session.
Diagnostics automatically repairs a wireless network adapter problem
In this scenario, a Windows® 7 user is attempting to connect to a wireless network. Windows® 7 is unable to connect to the specified wireless network, and displays a message indicating the connection attempt was unsuccessful. An option is provided to launch diagnostics by clicking Troubleshoot problems. This is shown in the following figure.
The user clicks Troubleshoot problems, and Windows Network Diagnostics starts. This is shown in the following figure.
The status indicates that it is investigating for problems in connection management. This is shown in the following figure.
Status transitions to indicate that diagnostics is looking for network adapter problems. This is shown in the following figure.
The diagnostics status is updated to inform you that it is collecting configuration details. In this phase, NDF is collecting information about the system that will be stored with the logs, in case support is needed. This is shown in the following figure.
Because NDF detected a root cause for which a repair could be performed automatically, the repair is attempted without further user interaction. If the repair had required user consent or administrative privileges, the user would have been prompted before proceeding.
Status indicates that the wireless adapter is reset as part of the corrective steps. This is shown in the following figure.
NDF checks to make sure that the problem has been resolved by the fix. This is shown in the following figure.
If not, diagnostics would restart to look for new issues uncovered by fixing the first one. For example, resetting the adapter lets you see wireless networks, but now you don’t have a profile for any network that is visible.
Diagnostics does not detect any additional problems. The diagnostic results are collected as part of the NDF reporting feature. This is shown in the following figure.
Diagnostic status indicates troubleshooting has completed, and that a problem with the wireless adapter or access point was found and subsequently fixed. No additional problems were present – NDF confirms that the problem was fixed and that no new problems have appeared. This is shown in the following figure.
Summary of this example diagnostic session
The user launched diagnostics in the context of a failed attempt to connect to a wireless network.
Diagnostics determined that a problem with the wireless adapter existed and automatically fixed the problem.
The summary of the diagnostic session tells the user that the problem is fixed. Diagnostics presented options that the user could select to view the diagnostic details, explore additional options, or end the diagnostic session.
Conclusion: Diagnostics successfully identified and corrected the wireless connectivity problem. No additional user action is required.
Viewing additional details in the Troubleshooting Report
In this scenario, a user, support professional, or network admin wants to view the details of the diagnostic session to better understand the cause of the problem. The process to access and view the report occurs in the following phases.
Click Start, in Search programs and files, type Troubleshooting history, and then in the results, under Control Panel, click Troubleshooting History. This is shown in the following figure.
Troubleshooting History opens. Click the Troubleshooting Report that corresponds to the diagnostic session to investigate. The Windows Network Diagnostics DetailsTroubleshooting report opens. This is shown in the following figure.
In Issues found, diagnostics indicates there was a problem with the wireless adapter that has been fixed. Scroll down to Detection details to view additional details. This is shown in the following two figures.