Microsoft KB Archive/816513

= Poor Program Performance Occurs in a Remote Terminal Services Session =

Article ID: 816513

Article Last Modified on 5/9/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)

-





SYMPTOMS
When you run a program in a remote Terminal Services session, you may experience any of the following symptoms:
 * Poor performance
 * Excessive CPU usage
 * Reduced animations (flat text instead of bitmaps)



CAUSE
This issue may occur if you are using a program such as Microsoft Office and the SPI_GETUIEFFECTS setting is turned on. This setting is turned on by default during a Windows Server 2003 Terminal Services session. However, this setting is not turned on by default during a Windows 2000 Terminal Services session. Programs may be optimized or may rely on this setting to reduce the effect that a Terminal Services session has on bandwidth. This setting provides details about animation in the program.



RESOLUTION
To resolve this issue, use Compatibility Administrator Tool. Compatibility Administrator Tool is included in Application Compatibility Toolkit 3.0.

Note For information about how to obtain and install Application Compatibility Toolkit, visit the following Microsoft Web site:

http://msdn2.microsoft.com/en-us/library/aa286552.aspx

To obtain the toolkit, visit the following Microsoft Web site:

http://go.microsoft.com/fwlink/?linkid=9513&clcid=0x409

You can use Compatibility Administrator to supply a command-line value to change the EmulateGetUiEffects setting to FALSE for programs that run remotely. To do this, follow these steps:  Click Start, point to All Programs, point to Microsoft Windows Application Compatibility Toolkit, and then click Compatibility Administrator Tool 3.0. Create a new custom database. To do this, follow these steps:  In Compatibility Administrator Tool, click New on the File menu. On the Edit menu, click Rename. Type a name for the database, and then press ENTER. On the File menu, click Save.</li> Type a name for the file, and then click Save.</li></ol> </li> Create a new application fix. To do this, follow these steps: <ol style="list-style-type: lower-alpha;"> On the Database menu, point to Create New and then click Application Fix.</li> In the Name of the program to be fixed box, type the name of the program.</li> In the Name of the vendor for this program box, type the name of the vendor for the program.</li> Click Browse to select the program file location for the program, and then click Open</li> Click Next, and then click Next again.</li> In the Compatibility fixes box, click to select EmulateGetUiEffects, and then click Next.</li> If you want to test the program after the fix is applied and you want to supply a command-line value, click Test Run.</li> Click Finish.</li> On the File menu, click Save.</li></ol> </li></ol>

After you create the new custom database and the new application fix, you must copy the database file to each computer where the program runs. You must then register the information that is contained in the file on each computer. You can use the Sdbinst.exe command-line utility to register the fix. To use Sdbinst.exe, from a command prompt, type sdbinst followed by the full path and name of the custom .sdb file. For example, type the following command:

sdbinst &quot; &quot;

After the file is registered on a computer, its compatibility information is used every time the program starts on that computer.

For additional information about Sdbinst.exe, click the following article number to view the article in the Microsoft Knowledge Base:

308235 How to Use the Compatibility Database Installer Tool in Windows XP

Additional query words: terminal, remote, performance

Keywords: kbwinservperf kbtermserv kbprb KB816513

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.