Registry Settings

 <  Day Day Up  >  

Before discussing Registry settings, note that if you use Registry Editor incorrectly, you can cause serious problems that might require you to reinstall your OS. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use the Registry Editor at your own risk.

Advertising as Terminal Server (281307)

Computers running Windows XP Professional or Windows Server 2003 that are not configured as a Terminal Services server, but have Remote Desktop enabled, can advertise as Terminal Services servers by modifying this Registry key:

 HKLM\System\CurrentControlSet\Control\Terminal Server 

Change the value of the TSAdvertise DWORD value from to 1 .

Windows Server 2003-based computers that are configured as Terminal Services servers, and Windows 2000 Server-based servers or Windows 2000 Advanced Server-based servers with Terminal Services installed in either Application Server mode or in Remote Administration mode, will advertise as Terminal Services servers because they already have the TSAdvertise Registry value set to 1 .

Application Behavior (186499)

Several compatibility bits can be set for an application, Registry path , or .ini file to change how a Terminal Server computer handles the merging of application initialization data when a session is in execute mode. These compatibility bits are set in the Registry under the following subkey :

 HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\Terminal Server\Compatibility 

There are three separate keys for applications, .ini files, and Registry entries under this Registry path. The default settings work for most applications, but they can be further tuned by using the compatibility bits.

Automatic Logon Fails (260711)

Security settings on the Terminal Services-based server can prevent automatic logon from working properly. The DontDisplayLastUserName Registry setting prevents this functionality from working correctly. To remove this setting on the server, modify

 HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\Winlogon 

Click the DontDisplayLastUserName value, and then choose String on the Edit menu. Type in the String Editor dialog box, and then click OK.

Automatic Reconnection Feature (323258)

Windows Server 2003 includes the Automatic Reconnection feature for Terminal Services. You can use this feature to automatically reconnect to the same session without retyping logon credentials if the session is disconnected because of dropped packets on the network or a network error. You can turn on the Automatic Reconnection feature in Windows Server 2003 either in the RDC tool or through a Group Policy.

By default, the Automatic Reconnection feature is turned on in Windows XP SP1. You can turn the Automatic Reconnection feature off by editing the Registry key

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

Add a new DWORD value that is named fDisableAutoReconnect to this Registry key. Set the fDisableAutoReconnect value data to either 1 or . A value of 1 means that Automatic Reconnection is turned off. A value of means that Automatic Reconnection is turned on.

Browse List Prevention (262852)

Terminal Services servers can be prevented from announcing the service to the browser list by modifying

 HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server 

Then, add the following:

  • Registry value : TSAdvertise

  • Data type : REG_DWORD

  • Radix : Decimal

  • Value :

Do not use this setting if you want the server to be accessible through the Terminal Services Manager snap-in.

Client License Removal (248430)

If you want to physically remove the TS CAL from the original client device, delete the local Registry key containing the license. This ensures that the client cannot connect to a Terminal Server in the future without being issued a new license.

Microsoft recommends that only system Administrators who are knowledgeable about the Windows 2000 Registry make this change. Note that deleting this key only removes the license from the client; it does not remove the issuance history contained in the Terminal Services license server.

All licenses under MSLicensing, TS CALs. LICENSE000, LICENSE001, LICENSE002, and so on, are used in succession until an empty slot is found. There is no particular mapping of license numbers to license types.

The key to be deleted is LICENSE000 or LICENSE00x is

 HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing\Store\LICENSE00x 

File Association Feature (257592)

On computers running Windows 2000 Terminal Services in Application Server mode, the UI can be locked down so that no one, not even Administrators, can change file type associations. This is done so that you can edit the entries only programmatically or by using Microsoft Installer (MSI)-based applications. This prevents an inadvertent change in the UI from affecting the global file type associations across the computer running Terminal Services and all its users. When this policy is enabled, the New, Delete, Change, and Advanced buttons are unavailable on the File Types tab of the Folder Options tool in the Control Panel.

You can enable this functionality by changing the following Registry entry:

 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion \Policies\Explorer] "NoFileAssociate"=dword:00000000 

Changing this key from its default value of 00000001 enables the File Types dialog box to function just as it does for other Windows 2000 configurations. Administrators and Power Users can change the global file type settings for the computer and all of its users.

Overriding the License Server Discovery Process (279561)

The Registry can be modified to select a specific license server for use in a domain or site. This is for Windows Server 2003 only.

 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ TermService\Parameters 

Add a new key called LicenseServers :

 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ TermService\Parameters\LicenseServers 

Add a new key ServerName , where ServerName is the NetBIOS name of the license server that you want to use, and then press Enter. The ServerName can be the NetBIOS name, the FQDN, or the IP address of the server. Restart the computer for the new settings to take effect.

 <  Day Day Up  >  


Windows Server 2003 on Proliants. Deployment Techniques and Management Tools for System Administrators
Windows Server 2003 on Proliants. Deployment Techniques and Management Tools for System Administrators
ISBN: B004C77T6A
EAN: N/A
Year: 2004
Pages: 214

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net