A new feature of UAG 2010 is the publishing of a RemoteApp application on a single RDS server or by using an RDS connection broker. You can find the necessary steps to publish RemoteApps in the TechNet library at http://technet.microsoft.com/en-us/library/ee441339.aspx.
Although this step-by-step guide covers all basic configuration points, you have to consider some more important configuration settings in a real-world deployment with external and unmanaged clients.
As soon as external and unmanaged clients access your portal and RemoteApps, you have to carefully examine the RDS server certificate. By default, a self-issued (self-signed) certificate is used. The recommendation from the RDS team is to use a public certificate (which means a certificate issued by one of the trusted public certification authorities). Please see http://technet.microsoft.com/en-us/library/cc770833.aspx for more information.
However, if you plan to use a certificate from your internal PKI, you have to ensure that:
If you still have a problem getting the RemoteApps working because of problems with the CRL, you can ignore revocation errors by modifying the appropriate registry key on a Windows 7 client:
Another good idea is the digital signing of your RemoteApp applications, for example to help protect against manipulated .rdp files or to reduce the number of displayed confirmation dialogs (also called Web SSO). The digital signing process is described at http://technet.microsoft.com/en-us/library/cc754499.aspx. Digitally signed apps can be exported and imported in UAG like unsigned RemoteApps.
Author: Dominik Zemp, Tech Solution Prof, Microsoft Switzerland
Reviewer: Meir Feinberg, Technical Writer, Forefront Edge
Do you have any solution for revocation error message in Windows7?