Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17


Remote Desktop Web Access

Posted on 2010-08-19
Medium Priority
Last Modified: 2013-11-21
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?
Question by:DMayo
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
LVL 74

Accepted Solution

Glen Knight earned 1000 total points
ID: 33478332
Single Sign on is an option with Windows 2008 R2 which is detailed here:

This is not available in non-R2 Windows 2008
LVL 31

Assisted Solution

by:Cláudio Rodrigues
Cláudio Rodrigues earned 1000 total points
ID: 33478625
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

Expert Comment

ID: 33478756
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:

Author Closing Comment

ID: 33496668
Thank you very much.

Featured Post

Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

You might have come across a situation when you have Exchange 2013 server in two different sites (Production and DR). After adding the Database copy in ECP console it displays Database copy status unknown for the DR exchange server. Issue is strange…
Resolving an irritating Remote Desktop connection that stops your saved credentials from being used.
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…

704 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question