r0guenj
asked on
AD naming convention issue
example:
firstname.lastname (as a login will work as long as it is less than 20 characters and matches the pre win2k name)
firstname.lastname @ mysite.com (will work regardless of the length of the users name, even if the pre-win2k name is truncated like so: firstname.lastnam)
it seems we are running into a 20 character limit because of the user logon name (pre-windows 2000) and this is a feature according to microsoft (with no fix since this is a feature).
so #1, is there a way to append the @mysite.com automatically? or 2, make a change so that it does not default to the pre win2k name? the reason this is needed as we are not going to change our naming convention for this and we are not going to have our users shorten their names (all names and logins are based on full legal names EX: someone named jim robbins full name is james robbins so his login would be james.robbins@mysite.com, not what he would be informally known as, in this case jim robbins)
i don't know much about this (active directory) but i am researching this to learn more and to fix an issue we are having with several users.
thanks for the help.
firstname.lastname (as a login will work as long as it is less than 20 characters and matches the pre win2k name)
firstname.lastname @ mysite.com (will work regardless of the length of the users name, even if the pre-win2k name is truncated like so: firstname.lastnam)
it seems we are running into a 20 character limit because of the user logon name (pre-windows 2000) and this is a feature according to microsoft (with no fix since this is a feature).
so #1, is there a way to append the @mysite.com automatically? or 2, make a change so that it does not default to the pre win2k name? the reason this is needed as we are not going to change our naming convention for this and we are not going to have our users shorten their names (all names and logins are based on full legal names EX: someone named jim robbins full name is james robbins so his login would be james.robbins@mysite.com, not what he would be informally known as, in this case jim robbins)
i don't know much about this (active directory) but i am researching this to learn more and to fix an issue we are having with several users.
thanks for the help.
ocon827679
I think your problem is due to using older operating systems on your client. On W2K Pro and later, this shouldn't be an issue since you are using the SMTP name of the user to login. Since you have AD, you have a domain that is represented by a DNS naming convention. The domain name, mysite.com, is automatically appended to the login name. With older OS's you are stuck with the NetBIOS naming convention and older "NT rules." This is done to maintain compatiblity.
This is correct about the older naming convention.
Larger AD implementations that I have worked on, typically formulate short names with (first 5 letters of last name)(first initial)(middle inital). You can set this in the AD properties as the "Name", and then use the longer login name for the "User Principal Name" value. So, Brandon P. Comer would be name = comerbp and User Principal Name Brandon.Comer@mydomain.com
CHeers,
-Brandon Comer
Larger AD implementations that I have worked on, typically formulate short names with (first 5 letters of last name)(first initial)(middle inital). You can set this in the AD properties as the "Name", and then use the longer login name for the "User Principal Name" value. So, Brandon P. Comer would be name = comerbp and User Principal Name Brandon.Comer@mydomain.com
CHeers,
-Brandon Comer
Hi r0guenj,
depending on what you've mentionned, changing your policy toward naming convention would simplify logons and administration for both you as system admin and end-user.
for example, Jim John Robbins can use : j.robbins as his username or using his middle name: jj.robbins.
however, if you are using AD in mixed/hybrid mode then pre-windows2k users must have their username less or equal to 20 chr.
as for the "@mysite.com", simply add the "mysite.com" to your DNS as suffix and the problem is sovled.
depending on what you've mentionned, changing your policy toward naming convention would simplify logons and administration for both you as system admin and end-user.
for example, Jim John Robbins can use : j.robbins as his username or using his middle name: jj.robbins.
however, if you are using AD in mixed/hybrid mode then pre-windows2k users must have their username less or equal to 20 chr.
as for the "@mysite.com", simply add the "mysite.com" to your DNS as suffix and the problem is sovled.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
after researching this issue here and using other resources, jagerhill97 gave the same information that i have been able to find out on my own.