>I inherited a homogenous mix of computers and OS's when I started here a while back. W95, Wp5A, W95B, W98, etc. The password behavior on all of these is slightly different. On some when you change the NT password the local Windows password DOES NOT CHANGE. The user ends up having two passwords, one for NT and one for their local security. It stinks.

This has been an ongoing support problem for us. We mix NT4 and Win95 on the desktop have NDS for networking. I _try_ to keep the Win95 passwords empty, but this is ultimately in the hands of the users since there is no way to completely disable the Win95 passwords.

If a user changes there password on a Win95 box, the WinNT box chokes... The smoothest seems to be if they change their password on the NT box.

I have found no solution other that to keep trying to get rid of Win95 boxes and move to NT4 only.

>About the only way I've found to deal with this is to keep the local password empty. Then it never changes.

Yup, but this is problematic.

>My hope is that at some point there will be enough $$ to upgrade and migrate everyone to NT Workstation. Better yet would be W2K workstation (or whatever the new name is).

Yup, much better. More control.

>So, I'm waiting. I see no reason yet to change as I want to change everyone to W2K.

I will use it at home, and perhaps get the network boys to install it on my machine at work. No "must have" features yet... although Craig mentioned something about automatic software install. Put an EXE on the network, if a user clicks on it, it will realize the user doesn't have the runtime DLLS and such and install them. Have to see how this will pan out.