Note
Use the Restore button on any tab where you want to reset options to default values.
Bitmap Cache tab
The bitmap cache stores bitmaps client side so they do not have to be resent over the wire.
Bitmap caching places commonly used bitmaps, like the one used to display the Start button, in a file on the client computer. This improves performance by minimizing the amount of display information that must be passed over a connection.
Bitmap caching is enabled on a per-session basis from the client software and requires 10 megabytes (MB) of free hard-drive space on the client computer.
Persistent bitmap caching allows the client to store bitmaps sent from the server on a persistent media like a disk or flash RAM. On connection, the client informs the server of the bitmaps it has so the server doesn't have to send them over again. The bitmap cache uses a simple virtual memory scheme to increase the size of the cache, without taking up more physical memory. This allows the client to advertise more bitmap cache entries than it has in RAM, and use the disk or file system as the swap space. This helps to reduce the number of cache evictions and improves the bandwidth utilization. Virtual memory bitmap caching is especially useful for bitmaps larger than 4 kilobytes (KB).
The RDP protocol supports a maximum of five bitmap caches. The cell sizes for cache 0 to 4 are 256 bytes (16X16 bitmaps), 1024 bytes (32X32 bitmaps), up to 64 KB (256X256 bitmaps). The number of cell entries depends on the client's configuration. Persistent bitmaps are stored under the directory where the client is installed. Within that directory, a "cache/" directory is created, and within that are numbered directories, one for each cache.
These values are set in the following registry key: HKEY_CURRENT_USER \Software\Microsoft\Terminal Server Client\.| Bitmap cache | |
|---|---|
| Total Cache Size | Size in KB of RAM-based bitmap cache. |
| Distribution Proportion | |
| 1st item | Percentage of bitmap cache used for small cache entries. |
| 2nd item | Percentage of bitmap cache used for medium cache entries. |
| 3rd item | Percentage of bitmap cache used for large cache entries. |
| Persistent Caches | |
| Cache 1 | If "Cache bitmaps to disk" setting is enabled, setting this entry to 1 will cache small cache entries. |
| Cache 2 | If "Cache bitmaps to disk" setting is enabled, setting this entry to 1 will cache medium cache entries. |
| Cache 3 | If "Cache bitmaps to disk" setting is enabled, setting this entry to 1 will cache large cache entries. |
| Cache 4 | unused |
| Cache 5 | unused |
| Number of bitmap caches | Controls the number of active bitmap caches. Activates the number (1-5) of persistent caches you can configure. |
| Restore button | Restore default settings on this tab. |
Glyph Cache tab
The glyph cache stores glyphs client side so they do not have to be resent over the wire. The glyph cache contains the outline, vector, or raster font information.
A glyph is any character, such as a letter or number, along with the font information required to calculate how that character will be displayed. The first time a glyph is requested, its appearance is calculated, then stored in a glyph cache. Anytime after that the glyph is needed, it is transferred out of the cache to the screen or page buffer. For example, if you are typing in a document with particular font, chances are that 99.9 percent of the time the font is used on the screen as it is being transferred from the cache.
These values are set in the following registry key: HKEY_CURRENT_USER \Software\Microsoft\Terminal Server Client\.
| Glyph cache | |
|---|---|
| Glyph cell settings | |
| Cell 1 Size | Size of cells in glyph cache 1. |
| Cell 2 Size | Size of cells in glyph cache 2. |
| Cell 3 Size | Size of cells in glyph cache 3. |
| Cell 4 Size | Size of cells in glyph cache 4. |
| Cell 5 Size | Size of cells in glyph cache 5. |
| Cell 6 Size | Size of cells in glyph cache 6. |
| Cell 7 Size | Size of cells in glyph cache 7. |
| Cell 8 Size | Size of cells in glyph cache 8. |
| Cell 9 Size | Size of cells in glyph cache 9. |
| Cell 10 Size | Size of cells in glyph cache 10. |
| Glyph support level | 0 û none, 1 û partial, 2 û full glyph support. None turns glyph cache off. Partial and Full turn on glyph caching. They are treated the same. |
| Text Fragment Cell Size | Size of cells in the fragment cache. |
| Restore button | Restore default settings on this tab. |
Miscellaneous tab
These values are set in the following registry keys: HKEY_CURRENT_USER \Software\Microsoft\Terminal Server Client\ HKEY_CURRENT_USER\Control Panel\Desktop\| Miscellaneous | |
|---|---|
| Shadow Bitmap Enabled | Controls use of backup bitmap. A shadow bitmap is a copy of the screen memory maintained on the client to allow faster response to delta operations, like minimizing a window. |
| Dedicated Terminal | 0 - not a dedicated terminal, 1 - dedicated terminal. Dedicated terminal tells us that the Terminal Server client will always have a particular application window, and it won't get overlaid. For example, as would happen when it is used to serve up a particular application, rather then a desktop. Knowing this allows us to optimize other, such as turning off the shadow bitmap. |
| Order Draw Threshold | Number of orders to draw into the shadow bitmap before transferring. |
| ForegroundLockTimeout | |
| Restore button | Restore default settings on this tab. |
Client Profiles tab
Use this tab to save and load custom setting profiles. These are useful for quickly assessing the impact of different configuration setting combinations on your Terminal Services client.
Profiles are saved in the registry under HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\.
| Client Profiles | |
|---|---|
| Saved profiles | Select a profile containing settings for all other tabs.
Note Use the Restore button on any tab where you want to reset options to default values. |
| Load button | Load an existing profile. |
| Delete button | Delete a profile. |
| Save As button | Save existing settings in a new profile. |