After Windows in-place upgrade, Novell Client does not run login scripts or shows drives as disconnected
This document (7013477) is provided subject to the disclaimer at the end of this document.
Novell Client for Windows 8
Novell Client for Windows 8.1
Novell Client for Windows Server 2012 R2
Novell Client for Windows Server 2012
Novell Client for Windows Server 2008 R2
Windows Server 2012 R2
Windows Server 2012
Windows Server 2008 R2
the Windows upgrade is complete, login through the Novell Client
credential provider to login to both eDirectory and Windows still
appears to be successful. The "Novell Connections"
dialog confirms that authenticated eDirectory connections were
successfully created during login. But if
the eDirectory user had login scripts associated, it will be noted
that the eDirectory login scripts did not run, and any script-based
drive mappings are missing.
"Novell Login" from the red 'N' to login to eDirectory
and/or to run eDirectory login scripts again will show that
eDirectory scripts now run and the drives will map
successfully. But in Windows Explorer the status of the mapped
drives will show as "Disconnected", even though the drives
to use the "Map Network Drive" dialog in Windows Explorer
to attempt mapping to a Novell NCP-based path will fail, unless the
exact same name and path happens to also resolve and connect
successfully using the CIFS emulation on the Novell server.
In Windows Explorer, browsing the "Network" section will fail to list any of the Novell servers and eDirectory trees you are successfully logged in to, nor will it list any eDirectory trees or servers that should have been successfully visible using SLP.
After successfully completing the Windows upgrade, once you can login to Windows you should proceed with re-running the Novell Client for Windows SETUP.EXE installation program in order to re-establish the installed Novell Client files and configuration. This will resolve all of the above symptoms listed which can be observed when upgrading Windows on a machine where the Novell Client was already installed
Certain applications require re-installation after the completion of a Windows upgrade; for example when upgrading from Windows 8 to Windows 8.1 using the upgrade option from the Microsoft Store, or when upgrading from one version of Windows to another using the "Keep Windows personal files, settings and apps" upgrade option provided on Windows DVD media. In some cases the Windows upgrade process will advise you of these applications, either before the Windows upgrade process or once you attempt to run the application again after Windows was successfully upgraded.
The primary issue in the case of Novell Client for Windows is that the Windows upgrade process has reset the Windows "Network Provider Order", such that the Novell Client's "NCFSD" network provider is no longer considered part of the Windows network providers. As such all Windows network provider-dependent actions which needed the Novell Client NCFSD network provider begin to fail, until you re-run the Novell Client SETUP.EXE which will ensure that NCFSD is added back to the Windows "Network Provider Order" list.
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7013477
- Creation Date:18-OCT-13
- Modified Date:21-OCT-13
- NovellClient for Open Enterprise Server (Client)
Did this document solve your problem? Provide Feedback