Using a 3rd Party GINA with the Novell Client

  • 2950350
  • 23-Apr-1999
  • 27-Apr-2001
  • 4

Archived Content: This information is no longer maintained and is provided 'as is' for your convenience.

Issue

PRIMUS

The Novell Client for Windows NT will default to replacing the Windows NT GINA (Graphical Identification and Authentication) with NWGINA.DLL. The registry key that controls this is:

Key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon
Value:
GinaDLL : REG_SZ : NWGINA.DLL

NOTE: The value prior to the installation of a Novell Client is MSGINA.DLL.

Novell's GINA is required for much of the advanced functionality of the Novell Client for Windows NT. This includes most of the ZENworks Policies, Storage of Roaming Profiles, Location Profiles, and more.

GINA Chaining:

The Microsoft standard allows for the use of multiple GINAs if they are "chained" together. This means that the first GINA executing (the one listed int he GinaDLL Winlogon registry key) must be configured with the filename of the second GINA executing. It will then have to have been written to be able to pass the username credentials (typically the name, password, and NT Domain/Workstation name) to the next GINA. Theoretically there can be many different GINAs called and executed in a single login. Currently the Novell GINA does not allow chaining behind it, but other GINAs can be chained in front of it (such as PCAnywhere32).

Novell Recommendation:

In nearly all cases, a workstation will be configured to only use the NWGINA.DLL GINA. Administrators must determine if there is an additional product that requires a GINA to be fully functional. If so, then administrators should check with that product's vendor to see if it supports GINA chaining. If so, the administrator should request configuration instructions from the vendor on how to chain to NWGINA.DLL (they will most likely be proprietary registry keys). If the product does not support GINA chaining, then the administrator must decide which GINAs functionality they need more on the workstation. The Novell Client for Windows NT can still login to the network, run scripts, access files, print, and other basic functionality without NWGINA being executed. The login can be called manually (possibly placed in the Startup folder) after the desktop is built (LOGINW32.EXE in the WINNT\SYSTEM32 directory). The Network and Print Providers will still load even if the NWGINA.DLL is never executed, which will provide the basic file and print services for NetWare servers.

Disclaimer: THIS CONFIGURATION IS NOT SUPPORTED BY NOVELL. It is only provided as a possible workaround.