Novell® Client™ 2 for Windows Vista*/2008 Readme

September 23, 2009

1.0 Naming Conventions

Novell Client for Windows Vista refers to the first version of the Novell Client for Windows Vista product.

Novell Client SP1 for Windows Vista refers to the first support pack release of the Novell Client for Windows Vista product.

Novell Client 2 for Windows Vista/2008 refers to the latest release of the Novell Client for Windows Vista/2008 product.

2.0 2. What’s New in Novell Client 2 for Windows Vista/2008

2.1 Support for Windows Server 2008

The Microsoft Windows Server 2008 platform is now supported by the Novell Client, in addition to the Microsoft Windows Vista platform. The same Novell Client 2 for Windows Vista/2008 installation set can be used to install the Novell Client on either platform.

The Novell Client 2 for Windows Vista/2008 does not support installation on Windows Server 2008 Server Core installations of Windows.

2.2 Support for TSClientAutoAdminLogon

Support for TSClientAutoAdminLogon has been added for use in regular terminal services and also with the Server 2008 Terminal Services RemoteApp (TS RemoteApp) feature.

As with the TSClientAutoAdminLogon support on Novell Client for Windows XP/2003, enabling this policy permits the otherwise Windows-only credentials being passed through a terminal connection to be used in conjunction with a Novell Client login profile and attempt an eDirectory login in addition to the otherwise Windows-only logon that would have occurred within the terminal session.

Establishing the TSClientAutoAdminLogon policy is performed by creating the following registry values:




2.3 Novell Client UNC Path Filter Feature Added

The Novell Client now installs and enables by default the UNC Path Filter feature. This feature intends to create performance improvements by preemptively failing UNC path requests that contain Novell NCP server names before they can be handled by the Microsoft Client for Microsoft Networks. In this way any delay that might have occurred in attempting to resolve the NCP server name through Microsoft name resolution methods or the delay of attempting to connect to the NCP server as though it's a Windows server can be avoided.

The feature is enabled by default, and can be controlled through the "UNC Path Filter" parameter in the "Advanced Settings" tab of the Novell Client Properties. Note that the "UNC Path Filter" has been completely redesigned, and does not share any of the known issues currently documented for the Novell Client for Windows XP/2003 NWFILTER.SYS-based UNC Path Filter.

2.4 Login Script Execution Starts Before User's Desktop

When logging in to both eDirectory and Windows through the credential provider of the Novell Client, processing of the eDirectory-based login scripts now starts at the same time other login scripts are processed, such as the Windows user login script. This means that eDirectory login script execution will start (but not necessarily finish) before the user's Desktop is built.

In addition, existing Windows policies such as Run logon scripts synchronously now apply to how the Novell logon script execution will be handled. This appears to be the default behavior in Windows Server 2008 with Terminal Services, but the policy may need to be explicitly set in other Windows configurations.

If you require that logon script processing must finish before the user's desktop is built, you can enable this Windows policy in the Group Policy Editor (GPEDIT.MSC) under Computer Configuration > Administrative Templates > System > Scripts > Run logon scripts synchronously. Note the same policy is also available as a User Configuration policy.

3.0 Installation

3.1 Supported Windows Platforms

IMPORTANT:The Novell Client for Windows Vista/2008 is only for Windows Vista x86 and x64 and Windows Server 2008 x86 and x64. This client will not run on Windows XP, 2003 or earlier Windows platforms.

The Novell Client for Windows Vista/2008 is supported on the following platforms:

  • Windows Server 2008 Standard Edition (x86 or x64)

  • Windows Server 2008 Enterprise Edition (x86 or x64)

  • Windows Vista Business (x86 or x64)

  • Windows Vista Enterprise (x86 or x64)

  • Windows Vista Ultimate (x86 or x64)

The Novell Client for Windows Vista/2008 might run but is not supported on the following platforms:

  • Windows Vista Starter, Home Basic, and Home Premium editions

  • Windows Server 2008 Datacenter Edition

  • Windows Server 2008 Web Server Edition

  • Windows Server 2008 Server Core installations (any edition)

3.2 Supported Server Platforms

The Novell Client for Windows Vista supports Novell Open Enterprise Server (OES) 1, OES 2, NetWare® 5.1, NetWare 6.0, and NetWare 6.5.

3.3 Installing the Novell Client

To install the Novell Client 2 for Windows Vista/2008, run the setup.exe file located in the C:\Novell\Novell Client 2 for Windows Vista-2008 directory.

3.4 Uninstalling Novell Client 2 or Novell Client SP1 to Reinstall the Initial Release

The NMAS client installed with Novell Client 2 for Windows Vista/2008 or Novell Client SP1 for Windows Vista uses NICI 2.7.4 by default, whereas the NMAS client included with initial release used NICI 2.7.3.

Uninstalling the Novell Client 2 or Novell Client SP1 automatically uninstalls the NMAS client, but it doesn’t uninstall NICI 2.7.4 because other applications on the workstation might need NICI services.

If you uninstall the Novell Client 2 or Novell Client SP1 with the intention of reinstalling the initial release version, you must also uninstall NICI 2.7.4 (and NICI 2.7.4 for Windows x64, if running Windows Vista x64) before re-installing the initial Novell Client for Windows Vista release.

Attempting to install the initial Novell Client for Windows Vista without first removing NICI 2.7.4 results in the following issues:

  • During installation of the Novell Client for Windows Vista on Windows Vista x64, the NMAS Challenge/Response method will report a 1603 error. This is because the NMAS client included in the initial release cannot resolve its required dependencies using NICI 2.7.4.

  • When starting up, the Windows Vista welcome screen on Windows Vista x64 displays an error, such as The procedure entry point CCSX_Authenticate could not be located in the dynamic link library ccswx64.dll.

  • The NICI 2.7.3 installer damages the existing NICI 2.7.4 installation. Subsequent attempts to use NICI cause -1471 0xFFFFFA41 NICI_E_SELF_VERIFICATION errors.

If you fail to follow these guidelines, features that require NMAS will not function, due to one or all of the above conditions.

3.5 The Total Path to the Installation Set Must Not Exceed 214 Characters.

The path to any and all files within a Novell Client for Windows installation set must not exceed 256 characters.

Currently this means the directory path into which you extract the installation set must not exceed 214 characters. This limit is relative to the traditional MAX_PATH or 256-character limit in Windows applications, but also takes into account additional path space that is needed for running the installation.

If the installation set is being accessed from a remote network location, for example \\servername\volumename, the length of the network server and volume name also counts against the maximum depth, due to underlying processing that makes use of the real path to the installation set. Even if a mapped drive letter and/or the map root feature is used for accessing the installation set, the limit is measured as if a UNC path had been used.

4.0 Known Issues

4.1 Novell Products Not Supported with the Novell Client for Windows Vista

The NetWare Administrator utility (nwadmn32.exe) and ConsoleOne® are not supported on Windows Vista or with the Novell Client for Windows Vista.

4.2 Welcome Screen Issues

4.2.1 After Installing the Novell Client, Local User Tiles Are No Longer Visible During Login

If you install the Novell Client for Vista on a machine with multiple local users, after rebooting, you are asked to log in to the Novell Client. At this point, there are only two available tiles: one for the local administrator user, and one for the Novell Client. You will no longer see the individual tiles for the local users.

This is working as designed. The Novell Client for Windows Vista follows Microsoft’s recommendations to filter out the local user accounts after installing the Novell Client. If you install the workstation into a Microsoft Domain, the local user tiles are also filtered out, and the Novell Client follows this behavior.

4.2.2 Welcome Screen Cancel Button

When logging in to eDirectory via the Windows welcome screen, the Cancel button that is displayed is not active and therefore cannot be clicked.

4.2.3 Fast User Switching/Connecting via Remote Desktop Connection

When logging in to a Windows Vista workstation using the Novell welcome screen, Novell connections made during the login will persist only if you are not currently logged in to the workstation. If your Vista account is already logged in, you will be restored to that existing session when you log back in to the workstation. This applies to both Fast User Switching and connecting via Remote Desktop Connection.

4.3 Authenticating to a Novell Server Through a UNC Path

If you log in to a Novell server using a UNC path in Windows Explorer and specify more than just the server and volume, the Windows Explorer window will appear in the foreground and the Results page will appear in the background.

If you specify only the server and volume, authenticating with a UNC path works correctly.

4.4 Using Ctrl+Alt+Del to Change Your Password

If you are currently authenticated to eDirectory, after entering your old password and new password, you will see a Change Password dialog box after clicking the Submit button. From the Change Password dialog box, you can choose which resources you want the password change to go to.

If you are not currently authenticated to eDirectory, the password change will only be submitted to Windows Vista.

4.5 MSDIA80.DLL File Installed to Root of Windows System Drive

When installing the Novell Client for Windows Vista on an x64 version of Windows, an MSDIA80.DLL file might appear in the root of the Windows system drive. This is a known issue of the Microsoft Visual Studio 2005 SP1 VCREDIST_x64.EXE installer. For more information, see KB 927665. Note the hotfix available for KB 927665 is for Microsoft Visual Studio 2005, not SP1.

4.6 Enabling 802.1X Authentication

The Novell Client for Windows Vista/2008 includes the ability to enable 802.1X authentication, but this feature is supported on Windows Vista platforms only.

To enable 802.1X authentication, right-click the Red N icon, then click Novell Client Properties. On the Advanced Login tab, select 802.1X Authentication in the Parameter list box, then set it to On. The 802.1X tab now appears on the Novell Login dialog box. You can use the 802.1X tab on the Novell Login dialog box to turning 802.1x on or off on a per-login basis.

For more detailed information, see Configuring 802.1X Authentication in the Novell Client 2 for Windows Vista/2008 Administration Guide.

4.7 Mapped Drive Icon Doesn’t Update on Re-Authentication

When you detach from a mapped Novell drive, the mapped drive icon displayed in Windows Explorer changes to a red X to indicate that the mapped drive is no longer accessible. If you use the Red N icon to re-authenticate to the Novell tree (and you selected the Check to always map this drive letter when you start Windows option when you originally mapped the drive), the mapped drive icon does not update to show that the drive is accessible again.

4.8 LDAP Contextless Login Differences in the Novell Client for Windows Vista

The LDAP Contextless Login feature in the Novell Client for Windows Vista includes the following limitations for those familiar with the Novell Client 4.x for Windows XP/2003.

  • When invoking Show Advanced Options from the Novell welcome screen (the login dialog seen at boot time and when logging out of Windows Vista), the LDAP Contextless Login lookup cannot be triggered when viewing the eDirectory tab. If LDAP Contextless Login is enabled, a lookup is performed after the user attempts to log in to eDirectory from the welcome screen.

    This is different from the LDAP Contextless Login behavior when running LOGINW32.EXE or selecting the Novell Login option from the Red N menu on the desktop. In those instances, you can see the effect of the LDAP Contextless Login lookup prior to actually proceeding with the eDirectory login.

  • The options to search by attributes other than username (for example, phone number or e-mail address) have been disabled for the Novell Client for Windows Vista release.

4.9 Login Profiles

4.9.1 Using DHCP in Login Profiles

If <DHCP> is chosen as an option in a login profile for Tree, Context, or Server, it cannot be removed by simply editing the field when logging in or by saving the profile on successful login. Any values entered in these fields during login will not be saved when <DHCP> is enabled for that field. This is working as designed.

4.9.2 Disabling the Login Profile List

If you set the Login Profile List option (available on the Advanced Login tab in the Novell Client for Windows Properties dialog box) to Off (meaning that the Login Profile drop-down list will not be displayed on the Novell Login dialog box), your next login will automatically use the last profile you logged in with.

If you want to use the default profile when the Login Profile List option is turned off, make sure that you log in using the default before you turn the option off.

4.10 Using the Force Grace Login Password Change Option

If you set the Force Grace Login Password Change option (available on the Advanced Login tab in the Novell Client for Windows Properties dialog box) to On (it is Off by default), the Novell Login will require a password change on the next-to-last grace login instead of the last grace login. This issue will be corrected in a future release of the Novell Client.

To work around this issue, use one of the following options:

  • Avoid this setting. Users are prompted to change the password on every grace login, but on the last one they have the option of canceling out and potentially getting locked out if they log out one more time without changing the password.

  • Add one to the number of grace logins. The message will tell users that they have four, three, then two grace logins, and then they will be required to change the password.

  • Suggest that users change their password while they still have two or more grace logins.

4.11 Disk Space Restrictions Ignored

If File Caching is enabled for the client, both user and directory disk space restrictions (quotas) on NSS volumes are ignored. Novell does not plan to remove this limitation in the future.

For information on File Caching, see “Advanced Settings” in the administration guide for the client.

For information on disk space restrictions, see the NSS documentation in the Open Enterprise Server 2 documentation or the equivalent for your servers.

4.12 Potential System Crash with File Caching Enabled

When accessing files from a Novell server, under certain conditions the Windows machine may potentially freeze or blue screen. This issue is known to be related to the File Caching functionality in the Novell Client, but no corrective fix is currently available to eliminate this issue if it occurs.

To work around this issue, do the following:.

  1. Right-click the Red N in the System Tray.

  2. Click Novell Client Properties.

  3. Select the Advanced Settings tab.

  4. Select File Caching and set it to off.

For additional information, see TID 3532535.

4.13 File Caching Settings Ignored

The Novell Client for Windows Vista ignores the SET CLIENT FILE CACHING ENABLED parameter on NetWare servers. Caching is on by default. Setting the parameter to on or off has no effect on the Novell Client behavior. This set parameter does still affect the NCP server’s behavior with regard to granting level 1 oplocks when requested.

To disable caching for a client, do the following:

  1. Right-click the Red N in the System Tray.

  2. Click Novell Client Properties.

  3. Select the Advanced Settings tab.

  4. Select File Caching and set it to off.

For information on File Caching, see “Advanced Settings” in the administration guide for the client.

4.14 Use Administrator Privileges Functionality Might Not Work on Non-English Windows

The Update Agent feature may be unable to successfully provide the Use Administrator Privileges functionality on some non-English versions of Windows, or on any machine where the built-in Windows Administrators group has been renamed.

For more information and potential workarounds, please see TID 7002896.

5.0 Unsupported Functionality

5.1 Mapping RDN Paths

Relative distinguished name paths are not supported for mapping network drives. For example \\tree\server_volume.context. (note the trailing period) is not supported whereas \\tree\server_volume.context (no trailing period) is.

6.0 Fixes Since the Last Release

  • Providing incorrect credentials once results in never being able to login even with correct credentials.

  • Login variables defined on the Script tab are not available during credential provider logins.

  • LDAP Contextless login fails to retain server field data from login profile.

  • Need visual confirmation on login dialog for when contextless login will or will not be performed.

  • Unable to add trustees and assign rights on the cluster volumes.

  • Cannot save from application to a mapped drive.

  • Novell Client workstation unlock operation using pcProx NMAS login method is not working.

  • System crash when browsing DFS junctions.

  • Cannot update a file correctly on server volume from Vista only.

  • Unable to save MS Office file to DFS location.

  • Need to check WTSInitialProgram when reconnecting to existing session.

  • Need mode to support AutoAdminQueryNDS behavior for terminal sessions.

  • NWTRAY launch for login script processing fails due to info discrepancy.

  • NWCCGETAllConnRefInfo fails on 64-bit Vista.

  • Visual Studio LINK or CVTRES step fails against mapped Novell drive.

  • Novell Client install with properties file can fail if properties file will require reboot.

  • After disabling the password field Novell Login dialog box is showing password field.

  • Installation continues without warning when Local Area Connections window open.

  • Uninstall halts but shows no error when Local Area Connections window open.

  • Temporary admin user directories from Update Agent remain on the machine.

  • NCSetup/NCIMAN System Login Profiles tab needs to reflect translated version of word "Default".

  • NCIMAN.exe crashes if Client is not installed instead of reporting error message.

  • Should not be able to open multiple Novell Client Properties windows.

  • Unable to set file attributes with Novell Client shell extension property pages.

  • Change Windows password to match Novell password not recovering properly if existing password is mis-typed.

  • NWC_CONN_INFO_RETURN_ALL processing blue screens the machine.

  • Selection of Novell Logon tile required even when Novell Logon is the only option.

  • Failure of Windows account password change during login is not reported.

  • Freeze/crash when accessing DFS Junction.

  • Default mode of credential provider cannot be controlled.

  • Better error message when the user is copying files through Netware Copy if the user has directory space restriction.

  • Unable to change password from Windows Vista.

  • Provide confirmation when deleting a System Login Profile.

  • NWTray crashes on sending message to a group and closing the sent message result window.

  • NMAS Pcprox authentication using Novell Client 1.0 SP1 is not working.

  • Workstation password is getting changed even when Change your Windows password to match your Novell password is not selected.

  • Blank Client tab being displayed in NCIMAN.

  • Credential provider window is not showing the icon of already logged in user when switch user operation is performed.

  • Invalid password is accepted for unlocking the workstation if the network connection is disabled.

  • Better error message if Did you forget your password? link is clicked with blank user name in the credential provider.

  • Blank window is displayed when a folder under volume is accessed using invalid UNC path containing a colon character.

  • Username having UTF characters is not displayed correctly in Password policy window.

  • Cease attempting restore point creation on Windows Server 2008 since service does not exist.

  • Bitmap image for Novell Login dialog does not return to using default image when de-configured with Novell Client Properties.

  • Unable to unlock the workstation after uninstalling the components of Novell Client and locking the workstation.

  • An error message is displayed while performing remote desktop connection for the first time.

  • Source window hangs in Novell Copy after canceling the large file transfer and leaves the partial file in the destination directory.

  • NWTRAY.EXE stops working when the user tries to close multiple Send Message Results windows.

  • Multiple instances of Novell Client SETUP.EXE allowed to execute.

  • Better error message while cancelling the installation of Novell Client for Vista.

  • Incorrect Password Restrictions settings names are shown in Novell Client User Password Administration window.

  • An error message is displayed while viewing Inherited Rights and Filters for the trustees who doesn't have Access Control trustee right on volume.

  • Invalid Last Login Time is displayed for the new user logging on for the first time.

  • Make Receive Message Dialog TopMost option is obsolete.

  • Novell Client is not getting updated when the option Use Administrator Privileges is checked for non-admin user.

7.0 Readme Changes

Added Potential System Crash with File Caching Enabled on September 23, 2009.

8.0 Documentation

For information on installing, using, and administering the Novell Client for Windows Vista, see

For information on Login Scripts, see the Novell Login Scripts Guide.

9.0 Legal Notices

Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.

Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.

Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.

Copyright © 2008-2009 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.

Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at and one or more additional patents or pending patent applications in the U.S. and in other countries.

For Novell trademarks, see the Novell Trademark and Service Mark list.

All third-party trademarks are the property of their respective owners.