Prerequisites for the RDP User Scenario Performance Test (Windows Embedded CE 6.0)
1/6/2010
The following tables show the hardware requirement for the RDP User Scenario Performance Test.
Requirement | Description |
---|---|
RDP server |
A Windows XP-based desktop computer that can function as an RDP server. This desktop computer should be a different computer than the development workstation that runs Microsoft Platform Builder and the Windows Embedded CE 6.0 Test Kit (CETK). For information about configuring the RDP server, see Running the RDP User Scenario Performance Test. |
The following table shows the software requirements for the RDP User Scenario Performance Test.
Requirement | Description |
---|---|
Tux.exe |
Test harness, required to execute test. |
Kato.dll |
Logging engine, required to log test data. |
Startrdp.exe |
Executable file for the test. |
RDPPerfConfig.exe |
Executable file that creates a test account, with a user name that you specify, on an RDP server. RDPPerfConfig.exe also verifies that the WinBench 99 application is installed and completes other tasks required to configure the RDP server to run the RDP User Scenario Performance Test. |
ClientVC.dll |
Module that Remote Desktop loads on a Windows Embedded CE–based device. This module communicates with an RDP server over a virtual channel to track the time spent in each test. |
Perflog.dll |
Module that contains functions that are used to monitor and log performance. |
WinBench 99 |
Benchmarking software from VeriTest that runs on an RDP server. You must license WinBench 99 from VeriTest. |
WB_Time.dll |
Server-side module that captures the test finished message and notifies ClientVC.dll after each test is done. |
RDPServer.exe |
Server-side executable file that starts when the test RDP session opens. This application starts the RDP User Scenario Performance Test and establishes the virtual channel with ClientVC.dll. |
To run the RDP User Scenario Performance Test, you must include the Remote Desktop Protocol Catalog item in your operating system design before you build your run-time image.