Announcement

Collapse
No announcement yet.

Server Name Change

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Server Name Change

    Domain is Windows 2003 AD (native)
    Two DCs and both are also DNS,GC & both running Win2K3 R2 Std w/all updates

    The second DC was just put in to place not too long ago and repl seems to be working fine.

    I am about to embark on migrating to Exchange 2K7, so of course I started with some Active Directory tests...

    Well a while back DC1 had a name change (prior to my time here) and I believe it was done incorrectly (I've been finding references to the old name in quite a few places). On this DC1, I run a netdiag /v and find all sorts of references to the old server name within the Registered Service Principal Names section.

    I've changed the correct name references to, well uhhh 'correctname' and same for the BADNAME

    E.G.
    Registered Service Principal Names:
    Dfsr-12F9A27C-BF97-4787-9364-D31B6C55EB04/correctname.domain.local
    exchangeAB/BADNAME
    HOST/BADNAME
    ldap/BADNAME
    exchangeAB/correctname.domain.local
    exchangeAB/correctname
    NtFrs-88f5d2bd-b646-11d2-a6d3-00c04fc9b232/correctname.domain.local
    ldap/correctname.domain.local/ForestDnsZones.domain.local
    GC/correctname.domain.local/domain.local
    HOST/correctname.domain.local/DOMAIN
    HOST/correctname.domain.local/domain.local
    ldap/correctname.domain.local/DOMAIN
    ldap/correctname.domain.local
    ldap/correctname.domain.local/DomainDnsZones.domain.local
    ldap/correctname.domain.local/domain.local
    DNS/correctname.domain.local
    HOST/correctname.domain.local
    HOST/correctname
    ldap/correctname
    exchangeAB/BADNAME.domain.local
    Dfsr-12F9A27C-BF97-4787-9364-D31B6C55EB04/BADNAME.domain.local
    ldap/BADNAME.domain.local/ForestDnsZones.domain.local
    GC/BADNAME.domain.local/domain.local
    HOST/BADNAME.domain.local/DOMAIN
    HOST/BADNAME.domain.local/domain.local
    ldap/BADNAME.domain.local/DOMAIN
    ldap/BADNAME.domain.local
    ldap/BADNAME.domain.local/DomainDnsZones.domain.local
    ldap/BADNAME.domain.local/domain.local
    DNS/BADNAME.domain.local
    HOST/BADNAME.domain.local
    E3514235-4B06-11D1-AB04-00C04FC2DCD2/eb13ab73-dd6c-445f-866e-7e4604f90a48/domain.local
    ldap/eb13ab73-dd6c-445f-866e-7e4604f90a48._msdcs.domain.local

    The only place I find this, is on the DC1 server (one that had the name change) and not to any other servers.

    Can anyone help out in getting rid of the references to that old name.
    Thanks ahead of time & Hope all have a Great Holiday

  • #2
    Re: Server Name Change

    Look at http://www.petri.com/windows_2003_do...ler_rename.htm

    Try step 4, maybe they forgot that when they did the rename.

    Comment


    • #3
      Re: Server Name Change

      Originally posted by Garen View Post
      Look at http://www.petri.com/windows_2003_do...ler_rename.htm

      Try step 4, maybe they forgot that when they did the rename.
      Thanks Garen,
      I came up with 'Unable to remove....Element not Found'
      The command I entered was:
      netdom computername correctname.domain.local /remove:badname.domain.local

      Comment


      • #4
        Re: Server Name Change

        Now I'm getting even more frustrated.
        Go in and do a setspn -D blablawoofwoof to remove all of the Registered ServicePrincipalNames referencing the 'badname' server, then a little while later all of those entries that I had removed show back up again. Same thing happens when I remove those entries via ADSIEDIT too.

        How can I get rid of the Registered ServicePrincipalNames that point to the 'badname' once and for all?

        Comment

        Working...
        X