How to Ensure your application is TS aware
Thursday, 29 May 2008 by Michel Roth
Wilco van Bragt has written an insightful article about how you can make sure (or check) that your applications will work in a Terminal Server environment. By the way, the mere fact that these articles exist points out one of the strengts in VDI.

So even though more and more manufactures are aware of the Server Based Computing concept and which impact this can have on the usage of the application there are still lots of applications which are not compatible with Server Based Computing. In this article Wilco describes which tests you need to go through to ensure that the application is ready for your SBC infrastructure.

This article should be used in conjunction with a tool by Microsoft that has been specifically written to check for Terminal Server compatibility: Terminal Services Application Analyzer. The tool is currently in beta but provides a truckload of valuable information. It provides a summary of an application’s TS-incompatible behavior. The classes of application compatibility issues targeted for detection are:
1. Shared resources – files/registries
2. Access/privilege issues
3. Windows API calls with special cases for TS

Read Wilco's article here and download the Terminal Services Application Analyzer beta here.


Related Items:

New Version of RDS Application Analyzer (17 August 2009)
Using SoftGrid In A Terminal Service Environment (16 February 2007)
The Microsoft Application Compatibility Tools (17 January 2007)
Microsoft Standard User Analyzer Updated (27 September 2006)
The Microsoft Application Compatibility Tools (Part 2) (21 February 2007)
Microsoft Standard User Analyzer (5 June 2006)
Using the RDS Application Compatibility Analyzer (25 January 2010)
Using SoftGrid To Support The Use Of Conflicting Applications In A Terminal Service Environment - Pa (10 April 2007)
PMicrosoft Windows Vista Application Compatibility Toolkit 5.0 RC for Download (8 November 2006)
CPU Management In Terminal Server Environments (11 January 2006)
Comments (0)