Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
Registry Flag fUseDefaultGina Does Not Work
Article ID: 214488 - View products that this article applies to.
This article was previously published under Q214488
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:
(http://support.microsoft.com/kb/256986/EN-US/ )Description of the Microsoft Windows Registry
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\ConsoleThis 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:
Windows NT Server 4.0, Terminal Server EditionTo 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:
(http://support.microsoft.com/kb/152734/EN-US/ )How to Obtain the Latest Windows NT 4.0 Service Pack
Windows 2000The 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
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.