September 30, 2008
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.
For a list of issues addressed since the last release, see Section 6.0, Fixes Since the Last Release.
Novell Client for Windows Vista now includes the Send Message functionality that has previously been available in Novell Client for Windows XP/2003.
Send Message functionality is controlled by four different client property settings. To see the settings, right-click Red N and select .
Under the tab is the setting that sets which broadcast messages the Novell Client can receive:
All: Receive all broadcast messages
Server Only: Receive broadcast messages sent by the server only
None: Do not receive any broadcast messages.
The tab lets you enable or disable the following functions.
Enable Send Message: This lets you specify whether the Send Message function is available.
The Send Message function is accessed from the context menu for the selected server or from the Red N menu under > .
Enable Send Message to Server Dialog: This lets you send messages to the server.
Enable Send Message to User Dialog settings: This lets you send messages to specific users.
To send a broadcast message:
From the Red N menu select > >
Double-click the server to see a list of users and groups connected to it.
Type the message.
Select the users and/or groups to send the message to.
Click .
The Send Message Results dialog appears, showing the users and groups that the message was sent to.
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.
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 is not supported on the following platforms:
Windows Vista Starter, Home Basic, and Home Premium editions
The client might run on these platforms, but it is not supported.
Windows Server 2008 (any edition)
This is not supported with this version of the Novell Client. Novell will be releasing an updated client that will support Windows Server 2008 in due course. For more information or to register for updates, please visit the Novell Clients product page.
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.
To install the Novell Client for Windows Vista, run the setup.exe file located in the C:\Novell\Novell Client for Windows Vista directory.
The NMAS client installed with 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 SP1 client 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 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 installing the initial release.
Attempting to install 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.
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 feature is used for accessing the installation set, the limit is measured as if a UNC path had been used.
The NetWare Administrator utility (nwadmn32.exe) and ConsoleOne® are not supported on Windows Vista or with the Novell Client for Windows Vista.
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.
When logging in to eDirectory via the Windows welcome screen, the button that is displayed is not active and therefore cannot be clicked.
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.
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.
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 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.
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.
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 . On the tab, select in the Parameter list box, then set it to . The tab now appears on the Novell Login dialog box. You can use the 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 SP1 for Windows Vista Administration Guide.
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 option when you originally mapped the drive), the mapped drive icon does not update to show that the drive is accessible again.
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 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 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 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.
If 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 is enabled for that field. This is working as designed.
If you set the option (available on the Advanced Login tab in the Novell Client for Windows Properties dialog box) to (meaning that the 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 option is turned off, make sure that you log in using the default before you turn the option off.
If you set the option (available on the Advanced Login tab in the Novell Client for Windows Properties dialog box) to (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.
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.
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:
Right-click the Red N in the System Tray.
Click .
Select the tab.
Select and set it to .
For information on File Caching, see “Advanced Settings” in the administration guide for the client.
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.
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.
The following bugs have been fixed with the release of Novell Client SP1 for Windows Vista.
BSOD when mapping drive with 32-character server name
Vista can not open MS office document files on NSS as read-only when the files are already opened by another machine
Need "Computer Only Logon" setting added to Advanced Login tab of client properties
Need to return STATUS_NOT_IMPLEMENTED-type return rather than bugcheck unhandled IOCTLs
Bug Check 0x3B: SYSTEM_SERVICE_EXCEPTION on IRP_MJ_WRITE to NCIOCTL
Bug Check 0x1: APC_INDEX_MISMATCH when calling NWCCGetPrefServerName
Credential provider needs to support NMAS ID plugins
NWC_GET_TREE_MONITORED_CONN_REF returns invalid connection reference
NWDSCreateContextHandle doesn't set name context to default
Enabling the Login Windows password synchronization option default
setting under Advanced Login tab in Novell Client Properties changes the password of windows user to “blank”
After the RPC error occured, the client is displaying that "Novell Login is succeeded" in the credential login
Security vulnerability in NICM.SYS
Need to enable support for sending messages on the Vista client
Vista system crash in ncfsd.sys
BSOD occurs when mapping drives with IP address using Shell Extension in Novell Client for Windows Vista
Cannot access files and folders when Unicode characters are used in their names
Explorer is not refreshed after actions
Vista Client can not search at certained double byte chracter folder on NetWare server
Improper error message is displayed while changing the password if only the Password Hint is given with Old Password and New Password text fields are blank
Wildcard searches with 8 question marks do not work
Random failure reading Login Script stream attribute
AD Password not synchronized
Getting Error The save failed due to out of memory or disk space
Presence of Novell Client prevents LPT ports from being redirected
Credential provider needs to support customized password text string
"Internal error OX77777727 occurred" at the time of clicking "Did you forget password?" for the user who has limited concurrent connection
An error message is displayed while viewing the “Inherited rights and filters” from Novell Utilities
Address METHOD_NEITHER vulnerabilities across all Novell Client drivers
Vista Credential Provider Needs to invoke NMAS for workstation unlock
Modification of "Computer Only Logon after failed Novell Logon" setting should not require a reboot
Problems logging in with alias user containing dots in the alias username
Provide confirmation when deleting a login profile
No error message is displayed when user logs into Novell Client with incorrect password through Credential Provider after disabling the password field
Add "Prompt for Novell login during Windows AutoAdminLogon" setting to Novell Client Properties
On entering <username\profilename> in username text box, adds it to Login profile list of "Novell Login" window
Advanced Login options are not recognized by the Credential Provider
Novell client for windows vista shows the Novell Picture for local system users having . (dot) in the username instead of picture set for the user
Login fails when a user tries to login to Novell Client for windows vista with DN from credential provider
BSOD running Delphi/Paradox database app
Add bitmap configuration settings to "Advanced Login" of Novell Client Properties
Modification of "Windows Password Synchronization" setting should not require a reboot
Remove Tree/Context pairs from Client tab of Novell Client Properties
Add "change windows password to match Novell password" settings to Novell Client Properties
File read for successfully locked file byte range fails with lock error
Entering an external script file in the "Profile" tab of the login profile doesn't work
Vista calls for an \IPC$ share AFTER the Novell Client resolves NCP shares
Add "Login With Non-Novell Credential Provider" to Novell Client Properties
BSOD when opening large files
Windows tab of login dialog should display what Windows domain we'll be logging in to
Login error when member of domain and "change password at next login" selected
Change your Windows password to match your NetWare password after a successful login is not supported in Vista
External User Login and Profile scripts are not executed when logging through the credential provider in windows vista
No login tiles appear after installing Novell Client for Windows Vista
Blue screen when opening a file on a mapped drive through application
Login Crashes On A Buffer Overflow
Login script is behaving inconsistently for Novell client for Windows vista
Drive information is not updated when a user maps to a volume and disconnects and later tries to map to a different volume with the same drive letter
Novell Copy - Novell File/Folder
Map Novell network drive to Netware cluster, verify after failover
Enable password field in profile not honored by Credential Provider
loginw32 from command line breaks client login screen
Password Expires with NMAS ON (Password Field Off)
Cred Provider displays Profiles Menu even though there's only one entry
LDAP Tree-less login NEEDS to be disabled during shell-login
Windows tab of login dialog doesn't account for change in computer name
You are already logged in as <typeless name>. Do you still want to log in as <typeful name>?
Error message is not displayed when attempting to create a new Folder & Brief case in the volume for which the user doesn't have the rights
Save profile checkbox stays checked
Some login syntax to not create full login profiles
Create definitive NCCredProvider behavior when NCCredProvider wasn't used for login
Cannot change password via CTRL + ALT + DEL after RDN login
In Login Profile Editor, Windows Tab, edit fields enabled when tab is not enabled
Vista checked build assertion regarding NCFSD and FsRtlRegisterUncProviderEx
Vista checked build assertion regarding NCCredProvider
button on Results window is too small
Login Profile user: RDN username not the same as CN
Advanced Setting First Network Drive
does not work
Login Profile tab: Windows displays WORKGROUP as possible login method
Lock / unlock workstation asks for wrong authentication
Forgotten Password link on credential provider is non-responsive
Blank passwords are not attempted from login profile to windows credential provider
Blank history items being maintained in history lists
Add feature to have a default Windows username and password
Turning the Novell Credential Provider requires you to log out before changing password via CTRL + ALT + DEL
Turning on Force Grace Login Password Change
makes expired password
warning
Can't disable display Last Logged On User
Support customer-specified Novell Logon tile bitmap
RED N crashes when opening profile manager if RESULTS window is open
Need to turn off Forgotten Password option when NMAS is disabled
NMAS sequences are not displayed in the advanced settings NMAS tab for novell client gina window
Credential Provider Did you forget your password
link cannot be reached by keyboard
Specifying invalid domain name does not cause failure during Windows login
Remove remaining Tree/Context pairs usage from Novell Client code
Password Policy (legacy) display page is confusing
Login Profile Administration dialog does not support double-click of profile
[Polish, German, Swedish] Login tab 802.1x
has been translated as X400
IDS_NO_CLIENT_ERROR message should use different version information
Install bitmaps should be changed
Credential Provider may need Switch User
-specific checks and messages
Non-localized default string in login profile list
Login script tree command not working
Disallow incompatible login extensions from registering (within Vista 64-bit only)
No error or warning when deleting files w/o permissions
NpLogonNotify calls login when workstation only is set
Need wait cursor around attempt to read policy for forgotten password
Modification of the Novell Logon Property does not need to require a reboot
Global login profile can be edited and deleted by any user
Login attempts bindery connection - bindery login is not supported in Vista Client
Update Agent Previous Install Location text box shows wrong location
Login using RDN for username (with context, no tree)
Should be error message when looking up password policy and NMAS is off
Inconsistency in 'password doesn't conform to password policy' message
Enable Disconnect Dialog in Advanced Menu Settings
Finish SETUP.EXE /L command line parameter implementation
There are inconsistencies in changing a password when it expires and using password administration
Unexpected errors during file-manipulation in size-restricted folder
Network Not Ready prompt seems to occur too early
Legacy password restrictions do not appear the same in imanager and password administration.
Possible error in NWCCCloseConn
Getting an error when trying to add files to VSS projects
Consistent Capitalization Errors in Property Sheets
UTF-8 Characters don't display correctly when mapping a drive through RED N
SLP not resolving during login
First time Install of client using ACU via UNC path, receive error about a newer version being available and asking about upgrading
ACU only allows 138 characters in command line
Script truncation by White-Space in Vista32
Need to support receiving broadcast messages on the Vista client
Minimum Password length restriction
Added Section 4.13, Use Administrator Privileges Functionality Might Not Work on Non-English Windows on April 9, 2009.
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.
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 © 2008 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.