Overview of Remote Desktop Services (RDS)
This is a landing page for information about publishing applications, including but not limited to the following topics:
Please add links to the sections below, and feel free to add more links if appropriate.
The Remote Desktop Services (RDS) Application Compatibility Analyzer can be used to determine the compatibility of an application with a Remote Desktop Session Host (RD Session Host). You can start using the Analyzer by following the step-by-step guide below.
Publishing in Windows Server 2008 R2
1) How to resolve the issue: “A website wants to start a remote connection. The publisher of this remote connection cannot be identified.”
2) How to troubleshoot Logon Attempt Failed messages when connecting through RD Gateway
3) The case of invisible RemoteApp programs (a.k.a. No RemoteApp programs listed on RD Web Access site)
More info on the option "Optimize my experience for a LAN network when connecting to the computer or application." in RD WebAccess
In Windows Server 2008 R2, the Web Single Sign-On (Web SSO) feature provides users with the ability to enter their credentials only once during logon to Remote Desktop Web Access (RD Web Access). After logon, users can launch RemoteApp programs that are part of the same connection in RemoteApp and Desktop Connections without any further credential prompts, even if the RemoteApp programs are configured to use RD Gateway.
If the RemoteApp programs are signed using a certificate from a public CA that participates in the Microsoft Root Certificate Program Members program (http://go.microsoft.com/fwlink/?LinkID=59547), then Web SSO should just work.
If the certificate is not issued by a trusted public CA, the certificate must be imported into the Trusted Root Certification Authorities certification store on the client computer to be trusted by the client operating system. Members of the local Administrators group, or equivalent, on the client computer can import the certificate or it can be done by using Group Policy
Web SSO also works when RemoteApp programs are set to use RD Gateway regardless of whether RD Web Access accesses RemoteApp programs in RD Session Host mode or RD Connection Broker mode.
For more detailed information configuring Remote Desktop Services Web SSO see this blog post:
The RD Web Access Portal can be customized to put in the company/department name. The following are some resources to get stated with:
- Simple change instructions: http://blogs.technet.com/b/askperf/archive/2011/01/21/modifying-the-default-rdwebaccess-web-page-for-fun-and-profit.aspx
- More in depth customization on this Wiki: http://social.technet.microsoft.com/wiki/contents/articles/7263.customizing-rd-webaccess.aspx
- Windows Server 2008 prototype customization at http://archive.msdn.microsoft.com/tswebsilverlight Video demo at http://technet.microsoft.com/en-us/edge/Video/ff710338
No longer a stub. Great job!