No SSO on windows 2008 terminal Services with Session Broker activated


I have installed three terminal server under Windows 2008.
On a server I have installed the Session Broker services.
The load balancing is working well but If I reach a server which has more user, I have no SSO (Single sign On) i.e. I need to write the password again in order to connect to another Terminal server.
I have installed everything as describ in the Ms KB.
To finish, I have modified the securityof the RDP protocol into "RDP compatibility" in order to let TS session Broker work


Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

We had a similar problem 
This applies only to SP3.

The other fix was to edit the registry for NTLMOnly Single Sign On:


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MarcFRANKHAUSERAuthor Commented:
It has been solved by itself by changing  the RDP connection properties two times ??
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.