Share via

Troubleshooting Terminal Server PNP Redirection Testing

  • Article

Note  This content applies to the Windows Logo Kit (WLK). For the latest information using the new Windows Hardware Certification Kit (HCK), see Windows HCK User's Guide on the Windows Hardware Dev Center.

This topic describes how to troubleshoot the TS client-side and TS server-side runs.

Troubleshooting the TS Client side test run - TS_PNPRedirection-WDK

After running the TS_PnpRedirection-WDK job on TS client machine, if the redirected Cellular phone device does not show up in the DTM Device Console UI on the TS server, make sure:

  1. Your device is directly connected to the TS Client machine and installed under "Portable Devices". If not, check that your driver INF file is correctly installed on the TS Client machine.

  2. From the TS Session running on the TS Client machine, you should be able to see the device enumerated in Device Manager under "Portable Devices", and driver details should show it as a TS redirected device. The device hardware ID should begin with the prefix "TS_".

  3. If the device fails to install under "Portable Devices" on the TS Server, check that your TS-redirection driver INF file is correctly installed on the TS Server machine.

  4. Verify that the TS-redirection driver INF file contains the correct TS redirection sections as specified: Device Driver INF Changes for Plug and Play Device Redirection on Terminal Server

  5. Looking at the SetupAPI device installation logs on the TS server will also suggest what went wrong.

  6. Go to the TS client machine and verify that the client machine has launched an active TS session to the TS server. You should notice that the workstation on the TS server is locked and this session is consumed by the TS client machine.

  7. Make sure WTT\FullMachineName constraint having Client Machine Name is added to LMS_Client.

Troubleshooting the TS Server-side test run for Cellular Handset Logo Tests

If the tests do not run after you schedule them, the tests require the "WPD\PortableDeviceType =Exists" constraint before you can run them.

To enable this constraint, you need to apply the "Wdk\ConfigureCellularHandsetsPortableDevice" dimension on your test machine pool. (For more information about how to apply this dimension, see the "Test system configuration" section of Preparing for Portable Media Device Testing.)

If many tests start to fail after some time, especially when you are running the Stress test, do the following to check that the device has not gone into a bad state:

  • Verify that the device is still connected to the test machine and is turned on.

  • Verify that the device node is still visible in Device Manager.

  • Browse the device's contents in My Computer by viewing objects or files in the device storage. If the device stops responding (that is, hangs), the driver or device might have gone into a bad state.

  • If the device has gone into a persistent bad state, reset the device or remove and insert the batteries.

 

 

Build date: 9/14/2012