UNSOLVED
Closed
K
kevin_carlson
2 Posts
0
4171
January 25th, 2007 14:00
Remember domain login
I have a curious little glitch. The Embassy Wave software (or maybe windows) does not remember the domain name under which I usually log in. If I lock my computer (Win-L) I get the standard dialogues:
1. Computer Locked - Only CorpDomain\Kevin.Carlson or an Administrator can unlock this computer
2. Please wait... - Updating user policies, please wait.
3. Unlock Computer - User name: kevin.carlson
Log on to: KevsComputer (This computer)
It is the 'Log on to:' that is not retained. It always defaults to the local computer, instead of the domain.
It is similar on initial boot. The Embassy Wave software shows its dialog:
1. Please wait... - Updating user policies, please wait.
then shows...
2. Logon Message - There are no active fingerprints registered for this user.
This is because my user name 'kevin.carlson' only exists on the domain, not the local computer, and only has fingerprints registered for the domain.
Certainly not a fatal issue, but other people here with the same DELL do not have this problem. Any ideas?
1. Computer Locked - Only CorpDomain\Kevin.Carlson or an Administrator can unlock this computer
2. Please wait... - Updating user policies, please wait.
3. Unlock Computer - User name: kevin.carlson
Log on to: KevsComputer (This computer)
It is the 'Log on to:' that is not retained. It always defaults to the local computer, instead of the domain.
It is similar on initial boot. The Embassy Wave software shows its dialog:
1. Please wait... - Updating user policies, please wait.
then shows...
2. Logon Message - There are no active fingerprints registered for this user.
This is because my user name 'kevin.carlson' only exists on the domain, not the local computer, and only has fingerprints registered for the domain.
Certainly not a fatal issue, but other people here with the same DELL do not have this problem. Any ideas?
chris.simons
1 Message
307
0
Posted August 11th, 2008 19:00
Were you able to get this resolved and if so how? I am having the exact same problem with a Precision M4300 after having the same problem on 2 Latitude D830s. I returned the D830s for some M4300s but I am still having the same issue. Tech support was lost as to what the problem was/is.
Thanks!