What testing do I have to do for an application that is installed on Terminal Server? Or, can you give me the checkpoints that I have to go through to make sure the application maintains its integrity on Terminal Server?
- Applications that identify users by name, not by machine name or machine IP address
- Applications that don't overtax system resources such as processor time or memory. Memory leaks or constant CPU polling are very bad in an application running on a shared system
- On Windows 2000 Terminal Services without MetaFrame, applications that work well with a maximum color depth of 256 colors and
- 32-bit applications, rather than 16-bit applications. All else being equal -- and it usually isn't -- 32-bit applications will use less memory than 16-bit applications because 16-bit applications must all run within a private virtual machine that does not allow them to share code.
This was first published in June 2003