Novell Directory Services Integration in Software

Painting QR Code in Software Novell Directory Services Integration

If Presentation Server is already installed on the server, complete the following tasks 1 Run regedt32 2 Edit the following registry key:

3 Double-click the GinaDLL entry located in the right-hand pane In the String Editor window that pops up, replace the value Ctxginadll with the value Msginadll 4 Install and configure the Novell Client for Windows NT/2000, Version 481 or later 5 Do not restart when prompted by the Novell Client setup program 6 Edit the registry entry for GinaDLL, as in step 2 In the String Editor window that appears, replace the value nwginadll with the value Ctxginadll 7 With the key path for Winlogon still selected, choose Add Value on the Edit menu 8 Type CTXGINADLL in the Add Value dialog box The data type is REG_SZ 9 Enter Nwginadll in the String Editor window to assign this value to the new CTXGINADLL entry 10 Restart the server On Presentation Servers, Ctxginadll is loaded by Winlogonexe to process the autologon information transmitted by ICA clients Ctxginadll can process autologon credentials in excess of 20 characters For example, if Ctxginadll is not loaded, autologon user names greater than 20 characters are truncated to 20 characters by Termsrvexe When Ctxginadll acquires the user s autologon credentials, they are passed in their entirety to the installed Ginadll file to complete the authentication process In most cases, the installed GINA is Msginadll When the Novell Client is installed, the GINA is Nwginadll The previous steps are required to ensure that CTXGINA is installed on the Presentation Server CTXGINA is required for logging on automatically with user names that exceed 20 characters If the Novell Client being installed is 49 or later, the previous steps are unnecessary because the 49 client detects GINA chaining and respects such chaining with Citrix NOTE If the Novell Client is upgraded after the installation of Presentation Server, the GINA values are overwritten and it is necessary to reconfigure the registry with the previous steps 1 To optimize logon and browsing response times, change the order of the network providers using the following steps: a Right-click the My Network Places icon on the server s desktop b Choose Properties from the shortcut menu that appears The Network and Dial-up Connections window appears

c Choose Advanced Settings on the Advanced menu The Advanced Settings dialog box appears d On the Provider Order tab, adjust the order of the network providers, so Microsoft Windows Network is above NetWare Services e Click OK to close the Advanced Settings dialog box 2 To optimize logon time, add the Windows fonts directory located in %systemroot% to the system-path environment variable The system is now ready to set up the Windows account authentication to be used to access Windows 2000/2003 servers

When a NetWare Client is running on a Windows NT or Windows 2000 Server, users are required to have two accounts: one for authentication to NDS and one to gain access to Windows Two different approaches can give Windows access to users The first option uses Novell s Dynamic Local User functionality, available in Novell s ZENworks for Desktop Product (this is the only supported method in FR1) The second option is by having the same user name and password in both NDS and NT or ADS domains for each user (this support is available for MetaFrame XP FR2 and higher) This allows integration of Presentation Server and NDS without the use of Novell s ZENworks If using Presentation Server with NDS integration using ZENworks, continue in the following section with Configuring ZENworks for Desktops Settings for Presentation Server Support If using Presentation Server with NDS integration without ZENworks, skip to the Configuring NDS Support in Citrix Presentation Server Without ZENworks section