Novell® Client™ for Windows Vista* Readme

February 6, 2008

NOTE:For the latest version of the Novell Client for Windows Vista Readme, see http://www.novell.com/documentation/vista_client/readme/ncwv_readme.html.

1.0 Installation

1.1 Supported Windows Platforms

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

  • Windows Vista Business (x86 or x64)

  • Windows Vista Enterprise (x86 or x64)

  • Windows Vista Ultimate (x86 or x64)

The Novell Client for Windows Vista might run but is not supported on Windows Vista Starter, Home Basic, and Home Premium editions.

IMPORTANT:The Novell Client for Windows Vista is only for Windows Vista x86 and x64. This Client will not run on Windows XP, 2000, or 2003.

1.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.

1.3 Installing the Novell Client

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

IMPORTANT:Upgrading from the Novell Client for Windows Vista Technology Preview or any of the Beta releases to the release version of the Novell Client 1.0 for Windows Vista is not supported.

2.0 Known Issues

2.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.

2.2 Welcome Screen Issues

2.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.

2.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.

2.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.

2.2.4 Novell Login Keeps Previous Computer or Domain Name

If the Windows computer name or domain name is changed after a Novell Client login profile has been established for a user, the user login profile will continue to pass the previous computer name or domain name. This can result in undesired behavior if the old name is still valid and represents something the user cannot log in to.

In the Windows Welcome screen, select Show Advanced Options before attempting to log in as the user. On the Windows tab, change the From field to be the correct Windows computer name or domain name, then click OK to save this change prior to attempting to log in.

2.3 Using the TREE Login Script Command

If you use the TREE login script command to log into multiples trees, a login dialog box will display for each tree listed in the command after the first tree when you log in from the Windows welcome screen.

You can enter the required information in the login dialog boxes for each tree, or you can click Cancel on the second login prompt, then use the Red N menu to log in. When logging in from the Red N menu, you can log in to multiple trees without additional login prompts.

2.4 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.

2.5 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.

2.6 Sending or Receiving Broadcast Messages

The Novell Client for Windows Vista cannot receive NetWare broadcast messages sent from the NetWare server console or from other Novell Client workstations. The Novell Client for Windows Vista also does not include the ability to send broadcast messages.

2.7 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.

2.8 Enabling 802.1X Authentication

The Novell Client for Windows Vista includes the ability to enable 802.1X authentication. 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 for Windows Vista Administration Guide.

2.9 Specifying an Invalid Domain Name During Login

If you specify an invalid domain name during the Novell Client login along with a valid local username and password, the local Windows login will succeed even with the invalid domain name. If a workstation is not a member of a domain, Windows Vista ignores any information included in the domain name field.

2.10 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.

2.11 Mapped Drives Do Not Disconnect When a Different User Logs In

If multiple users with drives mapped via a login script (for example, MAP H:=%HOME_DIRECTORY) log in on the same machine and both users are in the same Windows session, the previous user’s mapped drives do not automatically disconnect when a new user logs in, giving the current user the ability to view the previous user's mapped drives. If the previous user logs out of the session, the previously mapped drives will not be available to the new user.

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

The LDAP Contextless Login feature in the Novell Client for Windows Vista 1.0 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 1.0 release.

2.13 Login Profiles

2.13.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.

2.13.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.

2.14 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.

2.15 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.

3.0 Readme Changes

The following changes have been made to this readme since its initial release.

4.0 Documentation

For information on installing, using, and administering the Novell Client for Windows Vista, see http://www.novell.com/documentation/vista_client/index.html.

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

5.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 www.novell.com/info/exports/ for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.

Copyright © 2007 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 http://www.novell.com/company/legal/patents/ 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.