There are several reasons why you might need several GINA’s using View. Problem is it’s not well documented on how to actually chain them together and make it work. So here is a quick post on how to do that.

Note* You will need to create the VdmGinaChainDll string value as it does not exist.

Under the following regkey create vdmGinaChainDLL and place the secondary GINA dll name in it.

HKey_Local_Machine\Software\Microsoft\WindowsNT\CurrentVersion\VdmGinaChainDLL: yourotherGINA.dll

Verify the View GINA is the Winlogon GINA.

HKey_Local_Machine\Software\Microsoft\WindowsNT\CurrentVersion\WinlogonGinaDLL: “C:\Program Files\VMware\VMware View\Agent\bin\wsgina.dll”

Now look for you secondary GINA location and set it to msgina

HKey_Local_Machine\Software\Novell or Sentillion or whatever\I put my GINA here key\SomethinglikeLoadGinaDLL = msgina

Now ignore the no longer used key HKey_Local_Machine\Software\Microsoft\WindowsNT\CurrentVersion\Winlogon\Notify\WSGINA

There you go, you are now GINA chaining, enjoy. Thank you to Andrew and his customer for the heavy lifting on this one!

Similar Posts:

• How to use Novell with VMware View
• Novell and View
• Using Client Information in VMware View
• Vista and VMware View
• Hiding drives on the virtual desktop