Best Practices for Logo Testing and Avoiding Test Failures

The Microsoft Logo and Customer Service and Support (CSS) teams recommend the following guidelines to avoid logo test failures.

To avoid test failures

• Do not change the client hardware during setup unless advised by Microsoft.
• Make sure you complete all submissions for a client before you try to submit a different submission on the same client. Mark the client as unsafe in DTM Studio, and then uninstall the client.
• Launch all tests that you intend to submit for a logo through the Device Console submission view.
• From the Device Console in DTM Studio, make sure that you select your device, that the driver is loaded on the client, and that you have loaded the INF file for your submission.
• After your tests and submissions are completed, make sure that you review the DTM submission status window or the DTM log viewer to confirm submission and test status.
• Avoid generic VGA drivers for video and other outdated drivers. Load only the system BIOS and drivers that are recommended.
• Do not change the AutoLogon settings on the client.
• Do not use the Job Monitor rerun option.
• Do not alter or change jobs in the database.
• Do not place errata numbers in the Readme file before you obtain the errata from the Windows Hardware and Driver Central (WHDC) Web site.
• Run Storage > Adapter and LAN (Ethernet) test submissions for Windows Server 2008 on systems with a minimum of 4 processor cores and 6 gigabytes of memory. These requirements are in addition to those related to the Dynamic Partitioning (DP) Simulator and Test that all Windows Server 2008 device driver submissions must meet.
• Except for Para-Virtualization drivers (as defined by Logo Requirement Policy-0020), physical devices and their associated drivers being tested for Server Logo or Signature may not be tested in virtual machines using any form of virtualization. This is because not all virtualization products support the underlying functionality needed to pass the tests relating to Multiple Processor Groups, Device Power Management, Device PCI functionality, etc.

Take these proactive steps after setup to avoid unnecessary delays with your submission

• Download the latest errata update for your controller from the Windows Quality Online Services (Winqual) Web site.

• Clear the default Startup/Shutdown OS option on the DTM Client to reboot if there is a system failure.

  Important If you are running the Crashdump test for storage testing, ignore this guideline.

• Review the best practices for DTM maintenance on the Windows Hardware and Driver Central (WHDC) Web site.

Tracing down the exact reason for a test failure

When reviewing test logs for the source of failures, the Complete filter view of the Log viewer is acceptable for most testing. However, for tests which log context, the ContextTree filter view will show you the name of the test and the location of the functionality tested that failed and may results in a faster diagnosis of the failure.

To successfully test drivers with multiple INFs

• Run a complete logo test against each INF. The test should be run against every INF that is included in the driver package.
• Submit multiple CPK files (one for each INF file).

To uninstall a currently installed logo kit

If you uninstall a currently installed logo kit, the dimension(s) associated with the test client are removed. This happens because when the same logo kit is reinstalled, and the same MCU policy is deployed to the machine pool, the client machine won’t return the previously returned dimension data to the controller.

To work around this issue, try one of these steps:

1. Deploy an MCU policy that has never been deployed to the client before.
2. Uninstall, then re-install the DTM client, and rerun the config job associated with the MCU policy that was deployed.

Send feedback on this topic
Built on December 10, 2009