Discovered a problem with the following scenario:

Windows Vista Enterprise SP1
Novell Client 2.0
CS4 suite

Prior to the installation of CS4 the Novell Client would process login scripts just fine. After the installation of CS4, the Vista computer would stop processing login scripts. The user would be authenticated to the Novell tree but no drives would be present. Logging in from the desktop (right click on the red N in the systray and choose Novell Login), results in processing the login script and drives mapping.

Prior to logging in from the desktop we verified we could browse Novell shares, showing that the user was indeed authenticated. Only the login script processing during the initial login was not working.

We narrowed down the problem to Adobe Drive (part of the suite, usually installed with Photoshop).

What we discovered:
Adobe Drive places a network provider in the network provider list. The problem we saw was that the Adobe Drive network provider was listed first in the order. Seems this was interfering with the login script processing, not sure we saw this with the 1.0 SP1 client. It could be that changes in the login script processing with the 2.0 client (asynchronously script processing) has caused the problem. I believe that if Adobe Drive was listed first with the Novell Client 1.0 SP1 version was OK. After deploying the 2.0 client we started seeing this issue.

How we fixed it:
Using a ZCM policy to detect the network provider string in the

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\NetworkProvider\HwOrder key,

we looked to see if the string was equal to AdobeDriveCS4_NP,LCredMgr,NCFSD,LanmanWorkstation, RDPNP,webclient.

If this was true then we knew that the Novell client would NOT process the login script during the initial login. So if we detected the condition, we merged (over write) the keys
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\NetworkProvider\Order and
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\NetworkProvider\HwOrder.

Both settings were changed to LCredMgr,NCFSD,LanmanWorkstation,RDPNP,webclient,A dobeDriveCS4_NP

Hope this helps anyone that may be seeing the same behavior.