Vista Client SP1 or IR1 password sync does not work

[jchipman]

Scenario:
If the eDir password and the local Windows Vista password are out of sync, the Novell client prompts the user that the local password is incorrect and will then give the user an opportunity to sync the local user password, once they enter the correct local windows password (as it should). All accounts are correctly named eDir user = itslab, local user = itslab

However the password does not get set to the Novell eDir password, no errors are indicated (have not looked in the windows security log yet). What does happen is, that the local password is completely removed (meaning it was changed, but it was changed to nothing and is now blank). We have verified this by logging in computer only with a blank password after the initial sync was attempted.

Password changes do work as long as the passwords match prior to the change. Changing your password from the ctrl-alt-del change password method works as advertised. Passwords that are expired and require the user to specify a new password after a successful login works.

Only passwords that are not sync'd have this problem. The problem appears to be syncing the passwords from the initial login prior to desktop being loaded.

Tested SP1 and IR1 both clients have this problem.

Novell client options:
Show login Windows password synchronization option = on
Login Windows password synchronization option default = on
Windows password synchronization = on

Submitted a SR via the web today.

Has anyone else seen this or tested this?

[jchipman]

Might be getting somewhere on this one. I removed the Zenworks Adaptive Agent and the password sync began working as advertised.

It would appear that the Zenworks login (CASA really, I think), is getting in the way of the password pass-through. This may be why the password is being set to a blank password. It is certainly changing from what the password was previously to a blank password.

I reinstalled the Zenworks Adaptive Agent to see if the problem would return. After making the passwords different I rebooted the computer and logged in with the Novell password that was different than the local windows password. The Novell login succeeded but then I receive a warning that the local computer username or password is not valid with a corresponding red X icon. When the Zenworks Adaptive Agent was not on the computer the Novell client would immediately go to the password sync option and bypass the warning message altogether, so that is very different. When I choose OK at the warning, I am then given the opportunity to sync the password with the Novell password. Entering the windows password, the computer accepts it and I'm left with thinking that the password sync operation was successful. However when I logout and then re-login, the windows password is now blank.

To further isolate the problem I disabled the Zenworks login by inserting the registry keys to prevent the zenworks login. The Zenworks Agent did not authenticate the user (can see that in the Zen Agent properties). However the problem of the password being set to a blank password still persisted.

At this point I started looking at the provider order in the advance settings of the networking properties. Nothing I did there helped.

Removing the ZAA is not an option as I need to manage these Vista machines.

Hoping the SR will help me.

[jefferyscottsmi]

We are experiencing the same problem. With our without the ZEN agent the problem is the same for us.

At this point we're on the verge as well of opening a SR and also disabling the 'sync password' option via the Novell Client so that option is not available for our users.

If you can keep me informed as to you progress with the SR I would appreciate it.

Thanks,

Jeff

[jchipman]

Good news for the Jeff's (yes that's my first name too), the Vista Novell Client 2.0 beta absolutely fixes the password syncing problem I described in this thread.

Tested it on several computers and several scenarios and in each case the update fixes the problem.

On another note, Novell also added the UNC path filter back into the Vista client. We've had really good performance with the UNC filter enabled. Prior to adding this feature back into the client we disabled netbios to sort of achieve something similar.

[kevgo]

Jeff,

I am a coworker of the other Jeff.. and I'd be interested in giving the beta client a try. I believe your statement;

"we disabled netbios to sort of achieve something similar."

actually explains a few other issues (confirmed via wireshark) we have been seeing which I hope are resolved.

Thanks,

kevgo. (kevgo at unb dot ca)

[jefferyscottsmi]

Great to hear. I've just downloaded the beta and I'll see how it works for us. Thanks very much for the update!

Jeff

[jefferyscottsmi]

Just ignore that post from Kevin... you'd think we don't talk to each other 🙂