Novell Client 2 SP2 for Windows Vista
Novell Client 2 SP2 for Windows 7
Novell Client 2 SP2 for Windows 2008
Novell Client 2 SP2 for Windows 2008 R2

Windows is installed such that the user can use the German or the English version by simply switching from one language to the other. The Novell Client is installed while using German (the default setting), using the Novell Client installer's "Use Windows language" option.
 
When using German, drive mappings specified in the login script are mapped as expected. However, after switching to English, the user is successfully logged in, but no drive mappings occur.

After the desktop loads, logging in again (Red N > "Novell login") executes the login script and the network drives are mapped. After logoff/reboot, the problem reappears.

Workaround

Set up the workstation to /not/ have or use the "DEFAULT" / "STANDARD" / "PAR DÉFAUT" / etc. Novell Client login  profile.

On a machine where Novell Client has already been installed and a user has logged in:

1. In the "System Login Profiles" tab, delete the "STANDARD"/"DEFAULT" login profile, and then also delete any per-user versions of that profile already created on the machine under [HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Login\Profiles\Users] so that the profile "STANDARD"/"DEFAULT" no longer exists as a system profile or a user-specific profile name.

2. Delete the "unnamed default value" RegEDIT shows under [HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Authentication\NCCredProvider\CachedLogon].  Not the "1", "2", etc. value, but the one an English RegEDIT.EXE shows as "(Default)" and German shows as "(Standard)" since it's actually an unnamed value and RegEDIT is just showing this description itself.

This unnamed default value under [HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Authentication\NCCredProvider\CachedLogon] is where the "last logged-on user" information is stored.  So deleting that will prevent NCCredProvider from still seeing a reference to the previous login profile name when it retrieves information about the previous successful user
logon.

3. In "System Login Profiles", create a single profile name such as "MyDefault" or similar, different from the "DEFAULT"/"STANDARD" profile name.

Now when the Novell Client credential provider is invoked, it will find only a single profile "MyDefault" defined, and use this for login without having to resort to "DEFAULT"/"STANDARD".  Because this administrator-defined profile name is not involved in translation, "MyDefault" will be the correct profile name regardless of the current Windows user language.


1. Install Novell Client, then login using "Computer Only Logon"

2. Go to "System Login Profiles" and make the "MyDefault" as the only profile before any user actually logs into eDirectory from this machine.

The Novell Client always tries to display the login profile "Default" using a translated version of the word "Default", so that the profile name will make sense in the current language.  i.e. The login profile actually created in the registry is always "DEFAULT", but on German we display this profile choice as "STANDARD", on French as "PAR DÉFAUT", etc.

In the case of German, "STANDARD" is the correct translation of the profile named "DEFAULT" during the first phase of the login because the default Windows language (the language in effect before any Windows user actually logs on) is still German. But once the Windows user logs on, the Windows language configured for that user is English, and the translated profile name is now expected to be "DEFAULT" instead of "STANDARD".  So referencing "STANDARD" at that point seems like a reference to "some other profile" besides the default profile, which is why no "Run Scripts" setting or profile of that name can be found.