I have a strange problem that I can't seem to get fixed. I'm running Server 2008 R2 SP1 and hosting RD Web Access on one server (RDWA-Host) and RDSH on two other servers (RDSH-Host1 and RDSH-Host2). I have RDWA set to connect directly to the RDSH servers as RemoteApp sources. The RemoteApp sources are hosting four applications, two on each server, called Host1-AppA, Host1-AppB, Host2-AppA, and Host2-AppB. My connection list on the Configuration tab looks like "RDSH-Host1.domain.local;RDSH-Host2.domain.local". The RDSH servers are configured identically, everything is signed, and the certificates are from a trusted internal CA.
Here's the problem:
When I click on Host1-AppA or Host1-AppB, they launch and SSO works great; I don't have to enter my username or password again. When I click on Host2-AppA or Host2-AppB, I'm asked for my username and password. Seems like an issue with RDSH-Host2,
right?
Here's the oddity:
If I switch the server names around in my configuration so that it reads "RDSH-Host2.domain.local;RDSH-Host1.domain.local", sign out, and sign back in, Host2-AppA and Host2-AppB start to work with SSO while Host1-AppA and Host1-AppB stop working. I can
do this all day long having only apps from the first server listed in the configuration working with single sign on. Apps from any server other than the first one listed all prompt me to login.
Anybody know why this is? I can't seem to find any information about this even happening to anyone else. We're really liking RemoteApp as our Term Server replacement, but this issue (coupled with one I posted yesterday about external names screwing SSO up as well) is slowing us way down.
Thanks!