Re: Rendom does not modify default suffix upn ?

Tech-Archive recommends: Fix windows errors by optimizing your registry

Thanks a lot guys.

I dont have any explicit UPN defined.
I can change the value quite quickly by selecting all my user accounts,
then Properties and modify UPN.

When I tried to create a new user, I had the old upn suffixe still
listed by default.
All I did then was to launche the Domain and trust MMC and adsiedit
(without modifying anything), and then the old upn suffixe wasn't
listed anymore during the creation of a new user.

Quite strange but everything is ok now :)

Thanks


Jorge Silva a écrit :

Hi

What the document says is:

If a user account in Active Directory has an explicitly assigned value for
its UPN attribute, it is said to have an explicit UPN used for
authentication purposes. When the DNS name of a domain changes as a result
of the domain rename operation the explicit UPNs of user accounts in the
domain are not impacted. Hence, if you are using explicit UPNs for user
accounts, no maintenance is necessary after the domain rename operation.



So as Jorge Pinto said you'll need to change all UPNs manually or
scripting...






--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"bigstyle" <bigstyler@xxxxxxxxx> wrote in message
news:1149147330.437733.294430@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello,

I am testing rendom to change the domain name of my AD but I have a
problem.

Indeed, everything seems to work well after the rendom operation
(replication, dcdiag etc... are OK) but when I look into the user's
properties,User account tab, I see the "user logon name" @
oldsuffix.dns .
I have my newsuffix.dns but it is not the default UPN used.

Is it normal ? Microsoft doesn't say anything about that.

Do I have to run a script to modify every existing account?
Do I have to use adsiedit to modify the default value for the new users
?

Thanks in advance.


.

Relevant Pages

  • ADMT and UPNs
    ... I am testing the migration of user accounts from NT to W2K3 using ADMT. ... appears that it is setting the UPN of the migrated account to that of the ...
    (microsoft.public.windows.server.migration)
  • ADMT version 3 NT to Windows 2003 Migration
    ... I am testing a migration of user accounts from NT to W2K3 using ADMT ... appears that it is setting the UPN of the migrated account to that of ...
    (microsoft.public.windows.server.migration)
  • Re: NT domain users missing username@domain entries
    ... This posting is provided "AS IS" with no warranties, ... the explicit UPN COULD BE: ... Implicit UPN: Has the form "username@FQDNDomainName". ... Explicit UPN: Has the form "userIDstring@FQDNstring". ...
    (microsoft.public.windows.server.active_directory)
  • Re: NT domain users missing username@domain entries
    ... Please no e-mails, any questions should be posted in the NewsGroup ... This posting is provided "AS IS" with no warranties, ... Implicit UPN: Has the form "username@FQDNDomainName". ... Explicit UPN: Has the form "userIDstring@FQDNstring". ...
    (microsoft.public.windows.server.active_directory)
  • Re: NT domain users missing username@domain entries
    ... you could still use the IMPLICIT UPN which is there automatically.... ... the explicit UPN COULD BE: MY.SPECIAL.USER@xxxxxxxxxxxxxxxxx ... Always test ANY suggestion in a test environment before implementing! ...
    (microsoft.public.windows.server.active_directory)