Middle Tier authentication breaks after installing Novell Client 4.9 SP2

On a Windows Middle Tier server, it is common (although not required) to see that server also hosting eDirectory and ZENworks Desktop Management components. In this case, the Novell Client will exist on the Windows midtier. The recommended installation order would be:

Novell Client

eDirectory

ZDM 6.5 Desktop Management Server

ZDM 6.5 Middle Tier Server

In order to see the issue in this TID, the following would have to apply:

> before installing the midtier, the Novell Client either was non-existent or was a version prior to Novell Client 4.90

AND

> after installing ZDM 6.5 Middle Tier, the Novell Client was upgraded to 4.9 SP2

AND

> when upgrading to 4.9 SP2, SETUPSP.EXE was used. When using the SETUPSP.EXE the user will be prompted with a message during install asking if you wanted to overwrite a newer file, if the user answered YES the problem will occur.

OR

> when upgrading to Novell Client 4.9 SP2 running a full Client installation (SETUPNW.EXE).
Middle Tier authentication breaks after installing Novell Client 4.9 SP2
Users and workstations can no longer authenticate through the middle tier after installing the Novell Client 4.9 SP2 on the midtier using SETUPNW.EXE
Users and workstations can no longer authenticate through the middle tier after installing the Novell Client 4.9 SP2 on the midtier using SETEPSP.EXE and answering YES to the file overwrite prompt.

Additional Situation:
An attempt to uninstall the Novell Client with Middle Tier installed will result in both Middle Tier and the Novell Client to be irrepairably broken. The uninstall process is skipped and jumps directly to the prompt to Reboot the machine. After a reboot, the Novell Client is still installed. If a re-install of the Novell Client is attempted, the installation will run part way through, then fail with the following error:

An unknown error ocurred while installing the Novell Client for Windows. Installation incomplete.

C:\WINDOWS\Setupapi.log shows the reason the Novell Client can't install:

Add service: Failed to modify existing server "nwsns" Error 1078. The name is already in use as a service name or a service display name.

There is no recovering from this situation.

Workaround if you don't already have the problem: To avoid this issue, you should use SETUPSP to upgrade your client version, and be sure to answer NO when asked about overwriting newer files. However, SETUPSP cannot be used if you are upgrading from a 4.8x client version; in this case, you have to use SETUPNWEXE. Prior to upgrading the client using SETUPNW, make a copy of the %SystemRoot%\System32\drivers\NICM.SYS; and then after upgrading to 4.9sp2, replace the May 2004 version of NICM.SYS with the saved copy of the June 2004 version.
Workaround if you already have the problem: Copy the newer version of NICM.SYS into the %SystemRoot%\system32\drivers directory. The Client 4.9 SP2 has a NICM.SYS 3.0.0.2 and the ZfD 6.5 has a NICM.SYS 3.0.0.3. To do this, you can re-install the Middle Tier or you can obtain the file from another Windows Middle Tier that has not yet been upgraded to Novell Client 4.9 SP2.

When using SETUPNW from an overlay directory - the %SystemRoot%\System32\drivers\NICM.SYS file is replaced with an older (midtier-incompatible) version. Specifically, the May 2004 version of NICM.SYS replaces the June 2004 version of NICM.SYS.
When using SETUPSP, the install prompts the administrator to overwrite a newer file or not. If YES was chosen, the %SystemRoot%\System32\drivers\NICM.SYS file is replaced with an older (midtier- incompatible) version. Specifically, the May 2004 version of NICM.SYS replaces the June 2004 version of NICM.SYS.

Formerly known as TID# 10093371