Single Sign-On works only when connecting from an XP SP3, Vista or a Windows Server 2008 machine to a Vista or Windows Server 2008 machine. What are the limitations when using Single Sign-on? Once the policy is enabled you will not be asked for credentials when connecting to the specified servers. For Single Sign-On this default list is empty, so the checkbox has no effect.)Ĭonfirm the changes by clicking on the "OK" button until you return back to the main Group Policy Object Editor dialog.Īt a command prompt, run "gpupdate" to force the policy to be refreshed immediately on the local machine. When this checkbox is selected your servers are added to the list of servers enabled by OS by default. (Notice the "Concatenate OS defaults with input above" checkbox on the picture above.
For example to enable Single Sign-On to all servers in "" you can type "TERMSRV/*.".
Using one wildcard (*) in a name is allowed. Navigate to "Computer ConfigurationAdministrative TemplatesSystemCredentials Delegation".ĭouble-click the "Allow Delegating Default Credentials" policy.Įnable the policy and then click on the "Show" button to get to the server list.Īdd "TERMSRV/" to the server list. Start Group Policy Editor - "gpedit.msc". Log on to your local machine as an administrator. Single sign-On can be enabled using domain or local group policy. Thus you will need to enable the Group Policy settings described below in order to use locally logged on credentials for TS or TS Gateway connections. Locally logged on credentials are used for connecting to TS Web Access, however, they cannot be shared across TS Web Access and TS or TS Gateway. If you use the same user name and password logging on to your local computer and connecting to a Terminal Server, enabling Single Sign-On will allow you to do it seamlessly, without having to type in your password again. When applied to Terminal Services, Single Sign-On means using the credentials of the currently logged on user (also called default credentials) to log on to a remote computer.
Note: This post was updated on March 12, 2009, to include the latest information. First published on CloudBlogs on Apr, 19 2007
0 kommentar(er)
