It’s no mystery that shops who are deep into the Novell weeds tend to have a little more difficulty with technologies that are more Microsoft Centric. To Novell’s credit, they have built in some options for their clients that help facilitate a smoother transition into the VMWare View and Microsoft Terminals Services for enterprises who choose to use them.
The preferred method that I have found to use the Novell Client on Windows XP is to actually disable SSO and have the Desktop show the Novell Client login, this still has it’s limitations. One thing that I have noticed is if you are at the Novell Login screen and you disconnect your session through a physical or software based client, the next time you try to reconnect to that same desktop, you will get a blue screen. This blue screen will hang until there is a timeout period, which is not consistent, but eventually will go away.
Should you want to do SSO on Windows XP with the Novell client and over PCoIP you’ll need to setup the Passive Mode Login Function as defined in Novell’s documentation. I have tried this method with mixed results, which is why I prefer to turn off SSO.
To enable passive mode login, set the following registry keys:
“PassiveModeNDSLoginSilent”=dword:00000000 or 00000001
“PassiveModeNDSLoginRequired”=dword:00000000 or 00000001
“nwscript=reg_expand_sz:loginw32.exe %username% /NA /CONT
Windows 7 is pretty straight forward as Novell implemented some features in their Service Pack 2 release to use a “Non-Novell Credential Provider;” they must have been feeling the pressure to make this work consistently. This method is still considered a Passive Mode login, and is outlined here on Novell’s site.
In the Novell Client properties, under “Advanced Login,” Setting “Novell Logon” to “Off” and setting “Login With Non-Novell Credential Provider” to “On” achieves the desired SSO capability.
There are times in which the SSO doesn’t function, such as when you disconnect from the desktop but not the View Server, so to circumvent this, I would recommend disabling the CTRL+ALT+DELETE Sequence, and clear the LastLoggedOnUser registry key unless you have a policy not to.
Something to mention for certain circumstances where you need to disable SSO because of lab or kiosk. Ive noticed that if I disable SSO through a Windows GPO for the desktops in which the above procedure has been applied, that the desktop doesn’t connect properly, it shows a black screen. This may be another configuration issue that im not aware of, but i’ve yet to come across a resolution.