User logon name disappears

[Guest]

Recently, we have been experience the following problem. A user will report
that they cannot log in using their domain account. When this is reported, I
check their user account properties in Active Directory User and Computers.
When viewing the Account tab it shows that the User logon name field is
blank. When I manually enter the user name the user can once again log in.
Is there a way to keep this field from being what is seemingly an unexplained
occurence of being erased?

 

[Herb Martin]

Recently, we have been experience the following problem. A user will
report
that they cannot log in using their domain account. When this is
reported, I
check their user account properties in Active Directory User and
Computers.
When viewing the Account tab it shows that the User logon name field is
blank. When I manually enter the user name the user can once again log
in.
Is there a way to keep this field from being what is seemingly an
unexplained
occurence of being erased?

Generally this doesn't happen -- seriously -- even though if
you see it then it obviously is happening for you.

The reason I mention this is that unless someone knows of
a specific bug that gives this behavior it isn't highly likely you
will get much help....

I would almost suspect sabotage OR some weird failure
to replicate but here the word 'weird' means that I cannot
even invent a viable scenario where such would happen.

Logon name is not something that I have ever seen disappear,
nor heard reports. In fact, there is no reason for ANY AD
property to randomly disappear unless someone/something
removes it.....

 

[Richard Mueller]

Recently, we have been experience the following problem. A user will
report
that they cannot log in using their domain account. When this is
reported, I
check their user account properties in Active Directory User and
Computers.
When viewing the Account tab it shows that the User logon name field is
blank. When I manually enter the user name the user can once again log
in.
Is there a way to keep this field from being what is seemingly an
unexplained
occurence of being erased?

Generally this doesn't happen -- seriously -- even though if
you see it then it obviously is happening for you.

The reason I mention this is that unless someone knows of
a specific bug that gives this behavior it isn't highly likely you
will get much help....

I would almost suspect sabotage OR some weird failure
to replicate but here the word 'weird' means that I cannot
even invent a viable scenario where such would happen.

Logon name is not something that I have ever seen disappear,
nor heard reports. In fact, there is no reason for ANY AD
property to randomly disappear unless someone/something
removes it.....


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

I believe you refer to the field labeled "User logon name" in ADUC, which
correponds to the userPrincipalName attribute. This field is not required.
However, even if it is blank (and the userPrincipalName attribute has no
value), the user can still logon with their NT Name (the value of the
sAMAccountName attribute, referred to as the "Pre-Windows 2000 logon name",
which is mandatory and cannot be missing) as their "User logon name". That
is, if the domain is MyDomain.com and the "Pre-Windows 2000 logon name" is
TSmith, the user can logon as (e-mail address removed). This despite the "User
logon name" field being blank in ADUC.

At least that's my experience. I have no explanation for either the value
disappearing, or the user being unable to logon (at least using the NT
Name). I have not figured out when userPrincipalName has a value and when it
does not (unless "User Logon Name" is different from the NT Name, in which
case the value must be assigned).