AutoAdminLogon Gone wrong

ok here goes, i wrote a replacment Gui for the windows 2000 logon dialog box, it works replacing the default gina and by having AutoAdminlogon enabled and then entering the correct username and password into the registry when a user clicks on a username(looks somewhat similar to xp's logon screen).  The two registry keys are DefaultUserName and DefaultPassword.

Now here is the problem, this works fine on most of the computers its running on. But some seem to develop a problem over time.  The account that causes the problem has no password.  But on the affected pc's when the logon fails and the windows 2000 dialog box pops up telling you that the username and password are incorrect the password box has characters in it.  

I know these characters where not entered into the registry so where are they coming from.  

I assumed this was my program causing the problems so i disabled it and tried a normal autologon but the problem remained.  It just seems to be a side affect of long term autologon.  

So basically i need to know why some of theses pc's start to develop this problem, how to reverse it, and how to stop it happening again?


Thanks
LVL 1
seitouAsked:
Who is Participating?
 
oBdAConnect With a Mentor Commented:
According to the following articles, what it comes down to is that the account you're using needs to have a password, you need to set the ForceAutoLogon key as well in W2k, and then there's an issue with the msgina.dll.

HOW TO: Enable Automatic Logon in Windows 2000 Professional
http://support.microsoft.com/?kbid=234562

HOW TO: Enable Automatic Logon in Windows
http://support.microsoft.com/?kbid=310584

Automatic logon is not successful in Windows 2000
http://support.microsoft.com/?kbid=833880
0
 
seitouAuthor Commented:
We are running this program on about 50 computers and only about 5 of them have these problems.  Enabling the password on the account would be a last resort as the account is still used without the graphical interface and would just cause hassle with a password.

The issue with msgina you have the link for deals with the domain key, it doesnt seem to have anything to do with the password.

The fact that the majority of the computers are running this succesfully suggests that the password is not required. But the small number develop a problem and thats what i need to find out how to reverse.
0
 
oBdACommented:
Do the machines that show this behaviour have a different service pack level than the other ones, and did you try to set the ForceAutoLogon key?
0
[Webinar] Improve your customer journey

A positive customer journey is important in attracting and retaining business. To improve this experience, you can use Google Maps APIs to increase checkout conversions, boost user engagement, and optimize order fulfillment. Learn how in this webinar presented by Dito.

 
seitouAuthor Commented:
I actually always had the forceautologon set. That is the same on all the machines.  
And the its service pack 3 installed on  all the machines.

0
 
oBdACommented:
Have you compared the versions of msgina.dll on a machine where it works and on another one?
Other than the "empty password" explanation, I'm pretty much out of ideas at the moment, sorry.
0
 
seitouAuthor Commented:
Didnt think to check the msgina versions yet, will check it tomorrow morning and see what happens.  Other than that i guess ill have to try it with a password and hope this fixes it. But another solution would be much better. Thanks
0
 
seitouAuthor Commented:
ok The versions of msgina are exactly the same version 5.0.2195.4733.  I have tried installing sp4 with no change.

Anybody have any other suggestions, im running out of ideas.
0
 
seitouAuthor Commented:
ok, not exactly the solution i was trying to get, but i guess ill have to enable the password.  Thanks oBda, the points are yours.
0
All Courses

From novice to tech pro — start learning today.