Remote Desktop Web Access

Hi Everyone,

I am running Remote Desktop Services on Window Server 2008 using Web Acces and RemoteApp. Once the users sign on and get there Remote Applications, when they launch the programs they are then prompted to sign on again. Is there a way to disable this second logon?
Who is Participating?

Improve company productivity with a Business Account.Sign Up

Glen KnightConnect With a Mentor Commented:
Single Sign on is an option with Windows 2008 R2 which is detailed here:

This is not available in non-R2 Windows 2008
Cláudio RodriguesConnect With a Mentor Founder and CEOCommented:
Even on 2008 R2 note this does NOT work out of the box.
You must use policies to make sure the certificate thumbprints is set on all machines connection otherwise SSO will fail.
The requirements for that are:
- Windows XP Service Pack 3.
- .NET Framework 3.5 SP1.
- Remote Desktop Connection 7.0 Client Update.
- Single Sign-on Hotfix for Windows XP SP3 clients.
- The registry files SSO.reg, Thumbprints.reg and CredSSP.reg. These are mandatory in order to guarantee the Single Sign-on (SSO) functionality.

Windows Registry Editor Version 5.00

"Security Packages"=hex(7):6b,00,65,00,72,00,62,00,65,00,72,00,6f,00,73,00,00,\

"SecurityProviders"="msapsspc.dll, schannel.dll, digest.dll, msnsspc.dll, credssp.dll"

Windows Registry Editor Version 5.00




Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services]

Cláudio Rodrigues
Microsoft MVP - Remote Desktop Services
Citrix CTP
do you have domain
you should deploy SSO or Single Sign on
it's the ability in 2008 & 2008 R2

What is single sign-on for Terminal Services?
Single sign-on is an authentication method that allows a user with a domain account to log on once by using a password, and then gain access to remote servers without being asked for their credentials again.

Key scenarios for single sign-on
The key scenarios for single sign-on are:

Line-of-business (LOB) applications deployment

Centralized application deployment

Due to lower maintenance costs, many companies prefer to install their LOB applications on a terminal server and make these applications available through RemoteApps or Remote Desktop. Single sign-on makes it possible to give users a better experience by eliminating the need for users to enter credentials every time they initiate a remote session.

Prerequisites for deploying single sign-on
To implement single sign-on functionality in Terminal Services, ensure that you meet the following requirements:

You can only use single sign-on for remote connections from a Windows Vista®-based computer to a Windows Server® 2008-based terminal server. You can also use single sign-on for remote connections from a Windows Server 2008-based server to a Windows Server 2008-based server.

Make sure that the user accounts that are used for logging on have appropriate rights to log on to both the terminal server and the Windows Vista client.

Your client computer and terminal server must be joined to a domain.

You must use password-based authentication. Smart cards are not supported.

Recommended configuration of a terminal server when using single sign-on
To configure the recommended settings for your terminal server, complete the following steps:

Configure authentication on the terminal server.

Configure the Windows Vista-based computer to allow default credentials to be used for logging on to the specified terminal servers.

To configure authentication on the server
1.Open Terminal Services Configuration. To open Terminal Services Configuration, click Start, click Run, type tsconfig.msc and then click OK.

2.Under Connections, right-click RDP-Tcp, and then click Properties.

3.In the Properties dialog box, on the General tab, verify that the Security Layer value is either Negotiate or SSL (TLS 1.0), and then click OK.

To allow default credential usage for single sign-on
1.On the Windows Vista-based computer, open the Local Group Policy Editor. To open Local Group Policy Editor, click Start, and in the Start Search box, type gpedit.msc and then press ENTER.

2.In the left pane, expand the following: Computer Configuration, Administrative Templates, System, and then click Credentials Delegation.

3.Double-click Allow Delegating Default Credentials.

4.In the Properties dialog box, on the Setting tab, click Enabled, and then click Show.

5.In the Show Contents dialog box, click Add to add servers to the list.

6.In the Add Item dialog box, in the Enter the item to be added box, type the prefix termsrv/ followed by the name of the terminal server; for example, termsrv/Server1, and then click OK.

fore more info go to:
DMayoAuthor Commented:
Thank you very much.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.