Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've got the following setup:

  • Windows 2008 R2 server: Remote Desktop Services (RemoteApp, Session Host, Services Manager)
  • Windows 2008 R2 server: AD + AD Certificate services + DNS
  • Windows 7 client PC, in the domain, logged on as local admin (which is also a domain admin)

Whenever I try to launch RemoteApps from the client PC, I get a password popup. The password authenticates fine, and the app starts, but launching another one will show another password popup. Why doesn't it automatically authenticate, seeing as I'm in the domain?

share|improve this question
up vote 2 down vote accepted

You can absololutely use SSO, but it requires some fiddling. I don't know if you're using a connection broker or a gateway in your environment, but from your description it sounds like you're running tests in a small lab. So, in order for Web SSO to work, you have to digitally sign every remoteapp "program" you publish, and the client must trust the certificate you are using to sign the programs. This blog entry paints the big picture, hope it's enough for you to get going:

share|improve this answer

SSO is not working out of the box in AD. If you want true SSO you need to implement some kind of ticket system like Kerberos. If you just want it for terminal server you can delegate your credentials (this can be set through GPO and is described here)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.