dannydanny
IS-IT--Management
Hi,
We are all using W2k Pro SP3, and are in an AD domain.
Recently I migrated all our computers from an NT4 domain into the AD one.
Before migration, usre only had to type their password when loggin on as the username field was filled already with the previous logon username.
After migration, upon logging into their computers, some users have to type their username and password all the time, whereas other only have to type the password, with the username already filled in from the last logon.
All my users just want to type the password, so I made a registry change to the Local Machine hive using regedt32. There is key software\Microsoft\Windows\CurrentVersion\policies\system\dontdisplaylastusername.
I set this key to 0, then re-boot. Upon logging in again, the user name does appear as wanted, so the user only has to type the password, but the next day, the username field is blank and I have to go into the registry to change the key again.
What could make the registry "reset" itself? Is it a group policy? But half of our other users don`t have this problem......
Any ideas much appreciated,
Danny
We are all using W2k Pro SP3, and are in an AD domain.
Recently I migrated all our computers from an NT4 domain into the AD one.
Before migration, usre only had to type their password when loggin on as the username field was filled already with the previous logon username.
After migration, upon logging into their computers, some users have to type their username and password all the time, whereas other only have to type the password, with the username already filled in from the last logon.
All my users just want to type the password, so I made a registry change to the Local Machine hive using regedt32. There is key software\Microsoft\Windows\CurrentVersion\policies\system\dontdisplaylastusername.
I set this key to 0, then re-boot. Upon logging in again, the user name does appear as wanted, so the user only has to type the password, but the next day, the username field is blank and I have to go into the registry to change the key again.
What could make the registry "reset" itself? Is it a group policy? But half of our other users don`t have this problem......
Any ideas much appreciated,
Danny