Re: Empty Administrator Username ... IT's possible!!

From: "Paul Williams [MVP]" <ptw2001@xxxxxxxxxxx>
Date: Mon, 20 Jun 2005 21:36:17 +0100

How did you change the username? Which user name did you change?
sAMAccountName or userPrincipalName? You can use the UPN if you only set
the Pre-Windows 2000 name.

You can also logon as another user with permissions to make changes to
restricted group members.

--
Paul Williams
Microsoft MVP - Windows Server - Directory Services
http://www.msresource.net | http://forums.msresource.net

.

References:
- Empty Administrator Username ... IT's possible!!
  - From: vincio

Prev by Date: Re: ADSI Script to create Alternate Recipient has some problem !!
Next by Date: Re: How/Can we export Global Address List?
Previous by thread: Empty Administrator Username ... IT's possible!!
Next by thread: I need an advice please
Index(es):
- Date
- Thread

Relevant Pages

Re: Possible scenario? was Re: HELP! Really strange problem w/AD and LDAP/LDIFDE
... be SAMACCOUNTNAME@DOMAIN so if you have someuser in the test.loc domain you will have a default UPN of someuser@xxxxxxxxx This is in place whether or not you have specified anything for the UPN attribute. ... This tends to come into play when people are setting UPNs that differ for the first portion from the sAMAccountName and they create an accidental collision. ... objectClass: user ... *IF* somehow we ended up with two users as the above, with the same userPrincipalName, could that cause the symptoms that I'm seeing, where I can do the simple bind with full DN, but not with UPN? ...
(microsoft.public.windows.server.active_directory)
Duplicate UPNs and "default UPN"
... I've been continuing to try to figure out what was going on with a situation that I described in an earlier thread where an LDAP authentication was failing when using the user's name in UPN format: ... As mentioned at the end of the last thread, I was able to create a situation where attempting to authenticate using the user's UPN, as contained in the "userPrincipalName" attribute, would fail, by creating two different users, in two different containers, with both users having their userPrincipalName attribute set to the same value. ... ldifde with a simple bind with that UPN formatted username would then fail, but using a full DN, I could authenticate. ...
(microsoft.public.windows.server.active_directory)
Re: ActiveDirectoryMembershipProvider & ValidateUser
... It is entirely possible that your company is using implicit ... userPrincipalName values instead of expliciting setting them. ... if UPN isn't set, then the user will have an implicit UPN of ... Co-author of "The .NET Developer's Guide to Directory Services Programming" ...
(microsoft.public.dotnet.framework.aspnet.security)
Re: Character limit
... 2000 and pre-Windows 2000 name for Active Directory object. ... practice" or Microsoft Knowledge Base article that to speak about it? ... This link discusses what I have learned about the characters that are ... sAMAccountName is limited to 20 characters. ...
(microsoft.public.windows.server.active_directory)
Re: using UPN to auth
... Windows will then use the UPN instead of the samaccountname to ... BTW If your client support client canonicalisation you can authenticate as ... privileged information or confidential information or both. ...
(comp.protocols.kerberos)