Registry Flag fUseDefaultGina Does Not Work

Article translations Article translations
Article ID: 214488 - View products that this article applies to.
This article was previously published under Q214488
This article has been archived. It is offered "as is" and will no longer be updated.
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
Expand all | Collapse all

On This Page

SYMPTOMS

If a third-party Gina.dll file is installed and the fUseDefaultGina value in the following registry key is set to 0x1, the third-party Gina.dll file is still used for the main console on the server:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\Console
This setting should force the Msgina.dll file to be used.

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.


To use the default Gina for Terminal Server clients, use the following steps:
  1. Start Registry Editor (Regedt32.exe).
  2. Locate the fUseDefaultGina value under the following key in the registry:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
    NOTE: The above registry key is one path; it has been wrapped for readability.
  3. On the Edit menu, click REG_DWORD, type 0x1, and then click OK.
  4. Quit Registry Editor.

RESOLUTION

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

Windows 2000

The English version of this fix should have the following file attributes or later:
   Date        Time   Version        Size    File name
   ------------------------------------------------------
   06/23/2000  03:53p 5.0:2195.2097  177,936 Winlogon.exe
				

STATUS

Microsoft has confirmed that this is a problem in Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT Server 4.0, Terminal Server Edition Service Pack 4.

Properties

Article ID: 214488 - Last Review: October 14, 2013 - Revision: 3.3
APPLIES TO
  • Microsoft Windows NT Server 4.0, Terminal Server Edition
  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix KB214488

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com