[Tutorials] [Remote Desktop Session Host] – Published Jan 2012

Thus far, I have only focused on Windows Server 2008 R2 Remote Desktop Services features and concepts from an administrator’s point of view, but without really looking at applications.  It is more than obvious, however, that successfully establishing RD Session Host servers relies on user acceptance and efficient delivery of applications.  This makes clear that application installation and compatibility are key success factor.

Ideally, no problems should arise when installing and running any program on a RD Session Host server without special configuration.  Unfortunately, this is the exception rather than the rule.  Many older applications or their installation routines might already behave badly on standard Windows 7 or Windows XP workstations.  Even more applications were designed in a way that does not allow their default settings to deal with multiple users simultaneously.  Consequently, such applications often make assumptions about the operating system that do not apply to a multi-user environment.

Basically, the Microsoft programming principles for Windows applications should ensure proper functioning of programs that are used in multiple instances by multiple users.  In the past, however, many application developers did not strictly follow these principles, making subsequent system improvements necessary to run their applications within a remote desktop environment.  The adjustments include registry handling as well as directory structures and file access permissions.

In an environment based on Remote Desktop Services, Windows applications run on remote servers or workstation only.  The clients do not execute any type of local application logic.  Client devices display only the user interface and accept input.  Of course, applications running on the remote platform must be able to deal properly with such a scenario.

When evaluating applications for Remote Desktop Services compatibility, you need to look at several application categories based on different fundamental technologies.

1. Conventional 32-bit or 64-bit Windows applications using the public Application Programming Interface (Windows API) of the operating system.  Such a conventional Windows application is based on unmanaged code, thus it is not using an underlying runtime system.
2. Applications developed as Microsoft .NET Windows Forms seem to behave like conventional Windows applications, but they are based on managed code.  It is important to note that compatibility statements made in the context of conventional Windows applications may not apply to Windows applications that are built on the .NET Framework
3. Web Applications are based on the Microsoft ASP.NET Web Forms concept or any other Web technology.  Web servers such as the Microsoft Internet Information Server control their processing logic.

[Tutorials] [Remote Desktop Session Host]