Domain controller name -rename issue

I have a single label AD domain that I need to rename (Win2k3 SP2). I
recently took a job with a small company that was preparing to install
exchange. When the previous admin realized that exch would not install on a
single label domain it appears that he tried to rename one of the domain
controllers. I was preparing to run rendom.exe when I ran dcdiag to make
sure all was stable. I got the message below on one of the domain
controllers:

*** Warning: could not confirm the identity of this server in
the directory versus the names returned by DNS servers.
If there are problems accessing this directory server then
you may need to check that this server is correctly
registered
with DNS
......................... DC01 passed test Connectivity

This domain controller that gives this message is the one that has been
renamed. I do not know how the admin renamed it but in the computer
properites it shows up as "domain.local" instead of just "domain" (like the
other domain controller). DCdiag expects this server to be dc01.domain but
the server is named dc01.domain.local. Both "domain.local" and "domain" dns
zones are created and exist in DNS. My question is - do i need to fix this
before I run rendom.exe and if so where do I change it back.

In news:%23P8KrPIQJHA.4884@TK2MSFTNGP04.phx.gbl,
Clay Hilton <chilton@cypressrx.com> requesting assistance, typed the
following:
> I have a single label AD domain that I need to rename (Win2k3 SP2). I
> recently took a job with a small company that was preparing to install
> exchange. When the previous admin realized that exch would not
> install on a single label domain it appears that he tried to rename
> one of the domain controllers. I was preparing to run rendom.exe
> when I ran dcdiag to make sure all was stable. I got the message
> below on one of the domain controllers:
>
> *** Warning: could not confirm the identity of this server
> in the directory versus the names returned by DNS
> servers. If there are problems accessing this directory
> server then you may need to check that this server is
> correctly registered
> with DNS
> ......................... DC01 passed test Connectivity
>
> This domain controller that gives this message is the one that has
> been renamed. I do not know how the admin renamed it but in the
> computer properites it shows up as "domain.local" instead of just
> "domain" (like the other domain controller). DCdiag expects this
> server to be dc01.domain but the server is named dc01.domain.local. Both
> "domain.local" and "domain" dns zones are created and exist in
> DNS. My question is - do i need to fix this before I run rendom.exe
> and if so where do I change it back.

What is the Primary DNS Suffix of the DC? WHen you open ADUC, what domain
does it show?

See if the following tutorials help:

Domain Rename - Rename a Windows 2003 Forest with Exchange 2003 installed
(you can ignore the Exchange part)
http://www.msexchange.org/tutorials/Domain-Rename.html

Domain Rename Part 1 - Setup
http://thelazyadmin.com/blogs/thelaz...00_-Setup.aspx

Domain Rename Part 2 - Renaming
http://thelazyadmin.com/blogs/thelaz...-Renaming.aspx

Domain Rename Part 3 - Exchange 2003
http://thelazyadmin.com/blogs/thelaz...ange-2003.aspx

--�
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCT
Microsoft Certified Trainer

For urgent issues, you may want to contact Microsoft PSS directly.
Please check http://support.microsoft.com for regional support phone
numbers.

Hello Clay,

Just to get you correct, one DC is renamed and has now a FQDN of dc01.domain.local
before you start the domain rename to domain.local? Did he just change it
via System properties?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> I have a single label AD domain that I need to rename (Win2k3 SP2). I
> recently took a job with a small company that was preparing to install
> exchange. When the previous admin realized that exch would not
> install on a single label domain it appears that he tried to rename
> one of the domain controllers. I was preparing to run rendom.exe when
> I ran dcdiag to make sure all was stable. I got the message below on
> one of the domain controllers:
>
> *** Warning: could not confirm the identity of this server
> in
> the directory versus the names returned by DNS servers.
> If there are problems accessing this directory server
> then
> you may need to check that this server is correctly
> registered
> with DNS
> ......................... DC01 passed test Connectivity
> This domain controller that gives this message is the one that has
> been renamed. I do not know how the admin renamed it but in the
> computer properites it shows up as "domain.local" instead of just
> "domain" (like the other domain controller). DCdiag expects this
> server to be dc01.domain but the server is named dc01.domain.local.
> Both "domain.local" and "domain" dns zones are created and exist in
> DNS. My question is - do i need to fix this before I run rendom.exe
> and if so where do I change it back.
>

The actual server (netbios) name did not change. Originally the server were
named:
dc01.domain
dc02.domain
Now they are named
dc01.domain.local
dc02.domain

I do not know how he changed the DNS name. It does not look like it is
possible to do this in system properties. In ADUC the DNS names are :
dc01.domain.local
dc02.domain

So it appears the only changes that the former admin made were to change the
name of this server to dc01.domain.local and set up the DNS zone
domain.local.

Any help is much appreciated.
thanks,
Clay

"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb66d3298cb0eda46c76a20@msnews.microsoft.com...
> Hello Clay,
>
> Just to get you correct, one DC is renamed and has now a FQDN of
> dc01.domain.local before you start the domain rename to domain.local? Did
> he just change it via System properties?
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> I have a single label AD domain that I need to rename (Win2k3 SP2). I
>> recently took a job with a small company that was preparing to install
>> exchange. When the previous admin realized that exch would not
>> install on a single label domain it appears that he tried to rename
>> one of the domain controllers. I was preparing to run rendom.exe when
>> I ran dcdiag to make sure all was stable. I got the message below on
>> one of the domain controllers:
>>
>> *** Warning: could not confirm the identity of this server
>> in
>> the directory versus the names returned by DNS servers.
>> If there are problems accessing this directory server
>> then
>> you may need to check that this server is correctly
>> registered
>> with DNS
>> ......................... DC01 passed test Connectivity
>> This domain controller that gives this message is the one that has
>> been renamed. I do not know how the admin renamed it but in the
>> computer properites it shows up as "domain.local" instead of just
>> "domain" (like the other domain controller). DCdiag expects this
>> server to be dc01.domain but the server is named dc01.domain.local.
>> Both "domain.local" and "domain" dns zones are created and exist in
>> DNS. My question is - do i need to fix this before I run rendom.exe
>> and if so where do I change it back.
>>
>
>

Hello Clay,

Check with "netdom query fsmo" from the command line which DC is the FSMO
roles holder. If this is the old DC1, which seems to not longer existing
in AD i think you have start with clenaing up your AD.

Because you did not know what your predecessor have done with the DC1 renaming,
i would make sure that the correct existing DC2 have all 5 FSMO roles and
is GC server and DNS with AD integrated zones only for the correct old named
"domain" domain.

Then i would disconnect the renamed DC from the network and demote it with
dcpromo /forceremoval to member server.

After that is done run metadata cleanup on DC2's AD database according to
this article (http://support.microsoft.com/kb/555846/en-us) to remove the
DC1, either old or renamed, complete from AD so that only DC2 is listed.

Also delete the zone in DNS where only DC1 is listed and use only the correct
zone for DC2.

Then run dcdiag /v, netdiag /v on DC2 to make sure no errors exist. If you
have some, post the complete output here.

If DNS, AD users and computers and AD sites and services is cleaned up you
can now promote the old DC1 again to domain controller.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> The actual server (netbios) name did not change. Originally the
> server were
> named:
> dc01.domain
> dc02.domain
> Now they are named
> dc01.domain.local
> dc02.domain
> I do not know how he changed the DNS name. It does not look like it
> is
> possible to do this in system properties. In ADUC the DNS names are :
> dc01.domain.local
> dc02.domain
> So it appears the only changes that the former admin made were to
> change the name of this server to dc01.domain.local and set up the DNS
> zone domain.local.
>
> Any help is much appreciated.
> thanks,
> Clay
> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
> news:ff16fb66d3298cb0eda46c76a20@msnews.microsoft.com...
>
>> Hello Clay,
>>
>> Just to get you correct, one DC is renamed and has now a FQDN of
>> dc01.domain.local before you start the domain rename to domain.local?
>> Did he just change it via System properties?
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> I have a single label AD domain that I need to rename (Win2k3 SP2).
>>> I recently took a job with a small company that was preparing to
>>> install exchange. When the previous admin realized that exch would
>>> not install on a single label domain it appears that he tried to
>>> rename one of the domain controllers. I was preparing to run
>>> rendom.exe when I ran dcdiag to make sure all was stable. I got the
>>> message below on one of the domain controllers:
>>>
>>> *** Warning: could not confirm the identity of this server
>>> in
>>> the directory versus the names returned by DNS servers.
>>> If there are problems accessing this directory server
>>> then
>>> you may need to check that this server is correctly
>>> registered
>>> with DNS
>>> ......................... DC01 passed test Connectivity
>>> This domain controller that gives this message is the one that has
>>> been renamed. I do not know how the admin renamed it but in the
>>> computer properites it shows up as "domain.local" instead of just
>>> "domain" (like the other domain controller). DCdiag expects this
>>> server to be dc01.domain but the server is named dc01.domain.local.
>>> Both "domain.local" and "domain" dns zones are created and exist in
>>> DNS. My question is - do i need to fix this before I run rendom.exe
>>> and if so where do I change it back.

Before running all above mentioned steps by Mr. Weber make sure that your
predecessor never tried running Rendom...

http://technet.microsoft.com/en-us/l.../cc738208.aspx
Note (copied from above link)
The DNS host names of domain controllers in a renamed domain are not changed
automatically to use the new domain DNS name as the primary DNS suffix,
regardless of the primary DNS suffix configuration. In other words, unlike
the names of member computers, the DNS names of domain controllers in a
renamed domain will remain unchanged. The domain controllers can be renamed
in a separate step, using a special domain controller rename procedure, after
the domain rename operation is complete.

DCs name suffix to new domain doesn't change automatically you need to
change it as different procedure as mentioned below:

257623 The DNS suffix of the computer name of a new domain controller may
not match the name of the domain after you upgrade a Windows NT 4.0 primary
domain controller to Windows 2000
http://support.microsoft.com/default...b;EN-US;257623

Regards,
ProADGuy


"Meinolf Weber" wrote:

> Hello Clay,
>
> Check with "netdom query fsmo" from the command line which DC is the FSMO
> roles holder. If this is the old DC1, which seems to not longer existing
> in AD i think you have start with clenaing up your AD.
>
> Because you did not know what your predecessor have done with the DC1 renaming,
> i would make sure that the correct existing DC2 have all 5 FSMO roles and
> is GC server and DNS with AD integrated zones only for the correct old named
> "domain" domain.
>
> Then i would disconnect the renamed DC from the network and demote it with
> dcpromo /forceremoval to member server.
>
> After that is done run metadata cleanup on DC2's AD database according to
> this article (http://support.microsoft.com/kb/555846/en-us) to remove the
> DC1, either old or renamed, complete from AD so that only DC2 is listed.
>
> Also delete the zone in DNS where only DC1 is listed and use only the correct
> zone for DC2.
>
> Then run dcdiag /v, netdiag /v on DC2 to make sure no errors exist. If you
> have some, post the complete output here.
>
> If DNS, AD users and computers and AD sites and services is cleaned up you
> can now promote the old DC1 again to domain controller.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
> > The actual server (netbios) name did not change. Originally the
> > server were
> > named:
> > dc01.domain
> > dc02.domain
> > Now they are named
> > dc01.domain.local
> > dc02.domain
> > I do not know how he changed the DNS name. It does not look like it
> > is
> > possible to do this in system properties. In ADUC the DNS names are :
> > dc01.domain.local
> > dc02.domain
> > So it appears the only changes that the former admin made were to
> > change the name of this server to dc01.domain.local and set up the DNS
> > zone domain.local.
> >
> > Any help is much appreciated.
> > thanks,
> > Clay
> > "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
> > news:ff16fb66d3298cb0eda46c76a20@msnews.microsoft.com...
> >
> >> Hello Clay,
> >>
> >> Just to get you correct, one DC is renamed and has now a FQDN of
> >> dc01.domain.local before you start the domain rename to domain.local?
> >> Did he just change it via System properties?
> >>
> >> Best regards
> >>
> >> Meinolf Weber
> >> Disclaimer: This posting is provided "AS IS" with no warranties, and
> >> confers no rights.
> >> ** Please do NOT email, only reply to Newsgroups
> >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
> >>> I have a single label AD domain that I need to rename (Win2k3 SP2).
> >>> I recently took a job with a small company that was preparing to
> >>> install exchange. When the previous admin realized that exch would
> >>> not install on a single label domain it appears that he tried to
> >>> rename one of the domain controllers. I was preparing to run
> >>> rendom.exe when I ran dcdiag to make sure all was stable. I got the
> >>> message below on one of the domain controllers:
> >>>
> >>> *** Warning: could not confirm the identity of this server
> >>> in
> >>> the directory versus the names returned by DNS servers.
> >>> If there are problems accessing this directory server
> >>> then
> >>> you may need to check that this server is correctly
> >>> registered
> >>> with DNS
> >>> ......................... DC01 passed test Connectivity
> >>> This domain controller that gives this message is the one that has
> >>> been renamed. I do not know how the admin renamed it but in the
> >>> computer properites it shows up as "domain.local" instead of just
> >>> "domain" (like the other domain controller). DCdiag expects this
> >>> server to be dc01.domain but the server is named dc01.domain.local.
> >>> Both "domain.local" and "domain" dns zones are created and exist in
> >>> DNS. My question is - do i need to fix this before I run rendom.exe
> >>> and if so where do I change it back.
>
>
>

Hello ProADGuy,

domainlist.xml and dclist.xml can exist on the DC's if the rendom tool was
used or if renamed other .xml file, maybe check them.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Before running all above mentioned steps by Mr. Weber make sure that
> your predecessor never tried running Rendom...
>
> http://technet.microsoft.com/en-us/l.../cc738208.aspx
> Note (copied from above link)
> The DNS host names of domain controllers in a renamed domain are not
> changed
> automatically to use the new domain DNS name as the primary DNS
> suffix,
> regardless of the primary DNS suffix configuration. In other words,
> unlike
> the names of member computers, the DNS names of domain controllers in
> a
> renamed domain will remain unchanged. The domain controllers can be
> renamed
> in a separate step, using a special domain controller rename
> procedure, after
> the domain rename operation is complete.
> DCs name suffix to new domain doesn't change automatically you need to
> change it as different procedure as mentioned below:
>
> 257623 The DNS suffix of the computer name of a new domain controller
> may not match the name of the domain after you upgrade a Windows NT
> 4.0 primary domain controller to Windows 2000
> http://support.microsoft.com/default...b;EN-US;257623
>
> Regards,
> ProADGuy
> "Meinolf Weber" wrote:
>
>> Hello Clay,
>>
>> Check with "netdom query fsmo" from the command line which DC is the
>> FSMO roles holder. If this is the old DC1, which seems to not longer
>> existing in AD i think you have start with clenaing up your AD.
>>
>> Because you did not know what your predecessor have done with the DC1
>> renaming, i would make sure that the correct existing DC2 have all 5
>> FSMO roles and is GC server and DNS with AD integrated zones only for
>> the correct old named "domain" domain.
>>
>> Then i would disconnect the renamed DC from the network and demote it
>> with dcpromo /forceremoval to member server.
>>
>> After that is done run metadata cleanup on DC2's AD database
>> according to this article
>> (http://support.microsoft.com/kb/555846/en-us) to remove the DC1,
>> either old or renamed, complete from AD so that only DC2 is listed.
>>
>> Also delete the zone in DNS where only DC1 is listed and use only the
>> correct zone for DC2.
>>
>> Then run dcdiag /v, netdiag /v on DC2 to make sure no errors exist.
>> If you have some, post the complete output here.
>>
>> If DNS, AD users and computers and AD sites and services is cleaned
>> up you can now promote the old DC1 again to domain controller.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> The actual server (netbios) name did not change. Originally the
>>> server were
>>> named:
>>> dc01.domain
>>> dc02.domain
>>> Now they are named
>>> dc01.domain.local
>>> dc02.domain
>>> I do not know how he changed the DNS name. It does not look like it
>>> is
>>> possible to do this in system properties. In ADUC the DNS names are
>>> :
>>> dc01.domain.local
>>> dc02.domain
>>> So it appears the only changes that the former admin made were to
>>> change the name of this server to dc01.domain.local and set up the
>>> DNS
>>> zone domain.local.
>>> Any help is much appreciated.
>>> thanks,
>>> Clay
>>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
>>> news:ff16fb66d3298cb0eda46c76a20@msnews.microsoft.com...
>>>> Hello Clay,
>>>>
>>>> Just to get you correct, one DC is renamed and has now a FQDN of
>>>> dc01.domain.local before you start the domain rename to
>>>> domain.local? Did he just change it via System properties?
>>>>
>>>> Best regards
>>>>
>>>> Meinolf Weber
>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
>>>> and
>>>> confers no rights.
>>>> ** Please do NOT email, only reply to Newsgroups
>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>>> I have a single label AD domain that I need to rename (Win2k3
>>>>> SP2). I recently took a job with a small company that was
>>>>> preparing to install exchange. When the previous admin realized
>>>>> that exch would not install on a single label domain it appears
>>>>> that he tried to rename one of the domain controllers. I was
>>>>> preparing to run rendom.exe when I ran dcdiag to make sure all was
>>>>> stable. I got the message below on one of the domain controllers:
>>>>>
>>>>> *** Warning: could not confirm the identity of this server
>>>>> in
>>>>> the directory versus the names returned by DNS servers.
>>>>> If there are problems accessing this directory server
>>>>> then
>>>>> you may need to check that this server is correctly
>>>>> registered
>>>>> with DNS
>>>>> ......................... DC01 passed test Connectivity
>>>>> This domain controller that gives this message is the one that has
>>>>> been renamed. I do not know how the admin renamed it but in the
>>>>> computer properites it shows up as "domain.local" instead of just
>>>>> "domain" (like the other domain controller). DCdiag expects this
>>>>> server to be dc01.domain but the server is named
>>>>> dc01.domain.local.
>>>>> Both "domain.local" and "domain" dns zones are created and exist
>>>>> in
>>>>> DNS. My question is - do i need to fix this before I run
>>>>> rendom.exe
>>>>> and if so where do I change it back.

Thanks much Meinolf and ProADGuy. I will check to make sure a botched
rendom was not run. I also am going to decommission this DC before I try
rendom. After I decommission the DC I will only have one domain controller.
I plan to build another. I am thinking I will run rendom while I only have
one though to simplify things. Or would there be any advantage to adding a
DC back so I will have two before I run rendom?

"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb66d5058cb0f43bb67bc90@msnews.microsoft.com...
> Hello ProADGuy,
>
> domainlist.xml and dclist.xml can exist on the DC's if the rendom tool was
> used or if renamed other .xml file, maybe check them.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> Before running all above mentioned steps by Mr. Weber make sure that
>> your predecessor never tried running Rendom...
>>
>> http://technet.microsoft.com/en-us/l.../cc738208.aspx
>> Note (copied from above link)
>> The DNS host names of domain controllers in a renamed domain are not
>> changed
>> automatically to use the new domain DNS name as the primary DNS
>> suffix,
>> regardless of the primary DNS suffix configuration. In other words,
>> unlike
>> the names of member computers, the DNS names of domain controllers in
>> a
>> renamed domain will remain unchanged. The domain controllers can be
>> renamed
>> in a separate step, using a special domain controller rename
>> procedure, after
>> the domain rename operation is complete.
>> DCs name suffix to new domain doesn't change automatically you need to
>> change it as different procedure as mentioned below:
>>
>> 257623 The DNS suffix of the computer name of a new domain controller
>> may not match the name of the domain after you upgrade a Windows NT
>> 4.0 primary domain controller to Windows 2000
>> http://support.microsoft.com/default...b;EN-US;257623
>>
>> Regards,
>> ProADGuy
>> "Meinolf Weber" wrote:
>>
>>> Hello Clay,
>>>
>>> Check with "netdom query fsmo" from the command line which DC is the
>>> FSMO roles holder. If this is the old DC1, which seems to not longer
>>> existing in AD i think you have start with clenaing up your AD.
>>>
>>> Because you did not know what your predecessor have done with the DC1
>>> renaming, i would make sure that the correct existing DC2 have all 5
>>> FSMO roles and is GC server and DNS with AD integrated zones only for
>>> the correct old named "domain" domain.
>>>
>>> Then i would disconnect the renamed DC from the network and demote it
>>> with dcpromo /forceremoval to member server.
>>>
>>> After that is done run metadata cleanup on DC2's AD database
>>> according to this article
>>> (http://support.microsoft.com/kb/555846/en-us) to remove the DC1,
>>> either old or renamed, complete from AD so that only DC2 is listed.
>>>
>>> Also delete the zone in DNS where only DC1 is listed and use only the
>>> correct zone for DC2.
>>>
>>> Then run dcdiag /v, netdiag /v on DC2 to make sure no errors exist.
>>> If you have some, post the complete output here.
>>>
>>> If DNS, AD users and computers and AD sites and services is cleaned
>>> up you can now promote the old DC1 again to domain controller.
>>>
>>> Best regards
>>>
>>> Meinolf Weber
>>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>>> confers
>>> no rights.
>>> ** Please do NOT email, only reply to Newsgroups
>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>> The actual server (netbios) name did not change. Originally the
>>>> server were
>>>> named:
>>>> dc01.domain
>>>> dc02.domain
>>>> Now they are named
>>>> dc01.domain.local
>>>> dc02.domain
>>>> I do not know how he changed the DNS name. It does not look like it
>>>> is
>>>> possible to do this in system properties. In ADUC the DNS names are
>>>> :
>>>> dc01.domain.local
>>>> dc02.domain
>>>> So it appears the only changes that the former admin made were to
>>>> change the name of this server to dc01.domain.local and set up the
>>>> DNS
>>>> zone domain.local.
>>>> Any help is much appreciated.
>>>> thanks,
>>>> Clay
>>>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
>>>> news:ff16fb66d3298cb0eda46c76a20@msnews.microsoft.com...
>>>>> Hello Clay,
>>>>>
>>>>> Just to get you correct, one DC is renamed and has now a FQDN of
>>>>> dc01.domain.local before you start the domain rename to
>>>>> domain.local? Did he just change it via System properties?
>>>>>
>>>>> Best regards
>>>>>
>>>>> Meinolf Weber
>>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
>>>>> and
>>>>> confers no rights.
>>>>> ** Please do NOT email, only reply to Newsgroups
>>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>>>> I have a single label AD domain that I need to rename (Win2k3
>>>>>> SP2). I recently took a job with a small company that was
>>>>>> preparing to install exchange. When the previous admin realized
>>>>>> that exch would not install on a single label domain it appears
>>>>>> that he tried to rename one of the domain controllers. I was
>>>>>> preparing to run rendom.exe when I ran dcdiag to make sure all was
>>>>>> stable. I got the message below on one of the domain controllers:
>>>>>>
>>>>>> *** Warning: could not confirm the identity of this server
>>>>>> in
>>>>>> the directory versus the names returned by DNS servers.
>>>>>> If there are problems accessing this directory server
>>>>>> then
>>>>>> you may need to check that this server is correctly
>>>>>> registered
>>>>>> with DNS
>>>>>> ......................... DC01 passed test Connectivity
>>>>>> This domain controller that gives this message is the one that has
>>>>>> been renamed. I do not know how the admin renamed it but in the
>>>>>> computer properites it shows up as "domain.local" instead of just
>>>>>> "domain" (like the other domain controller). DCdiag expects this
>>>>>> server to be dc01.domain but the server is named
>>>>>> dc01.domain.local.
>>>>>> Both "domain.local" and "domain" dns zones are created and exist
>>>>>> in
>>>>>> DNS. My question is - do i need to fix this before I run
>>>>>> rendom.exe
>>>>>> and if so where do I change it back.
>
>

Hello Clay,

Before starting with the renaming make a test in a virtual environment, so
you become familiar with the steps and see if it works as expected.

Make sure you have at least a system state backup before starting the rename
of the production one.

Well, because you and also nobody else know exactly what was going on before
i would do it this way, demote the renamed DC and remove it complete from
AD. After check with diagnostic tools and no errors i would start with renaming.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Thanks much Meinolf and ProADGuy. I will check to make sure a botched
> rendom was not run. I also am going to decommission this DC before I
> try rendom. After I decommission the DC I will only have one domain
> controller. I plan to build another. I am thinking I will run rendom
> while I only have one though to simplify things. Or would there be
> any advantage to adding a DC back so I will have two before I run
> rendom?
>
> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
> news:ff16fb66d5058cb0f43bb67bc90@msnews.microsoft.com...
>
>> Hello ProADGuy,
>>
>> domainlist.xml and dclist.xml can exist on the DC's if the rendom
>> tool was used or if renamed other .xml file, maybe check them.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> Before running all above mentioned steps by Mr. Weber make sure that
>>> your predecessor never tried running Rendom...
>>>
>>> http://technet.microsoft.com/en-us/l.../cc738208.aspx
>>> Note (copied from above link)
>>> The DNS host names of domain controllers in a renamed domain are not
>>> changed
>>> automatically to use the new domain DNS name as the primary DNS
>>> suffix,
>>> regardless of the primary DNS suffix configuration. In other words,
>>> unlike
>>> the names of member computers, the DNS names of domain controllers
>>> in
>>> a
>>> renamed domain will remain unchanged. The domain controllers can be
>>> renamed
>>> in a separate step, using a special domain controller rename
>>> procedure, after
>>> the domain rename operation is complete.
>>> DCs name suffix to new domain doesn't change automatically you need
>>> to
>>> change it as different procedure as mentioned below:
>>> 257623 The DNS suffix of the computer name of a new domain
>>> controller may not match the name of the domain after you upgrade a
>>> Windows NT 4.0 primary domain controller to Windows 2000
>>> http://support.microsoft.com/default...b;EN-US;257623
>>>
>>> Regards,
>>> ProADGuy
>>> "Meinolf Weber" wrote:
>>>> Hello Clay,
>>>>
>>>> Check with "netdom query fsmo" from the command line which DC is
>>>> the FSMO roles holder. If this is the old DC1, which seems to not
>>>> longer existing in AD i think you have start with clenaing up your
>>>> AD.
>>>>
>>>> Because you did not know what your predecessor have done with the
>>>> DC1 renaming, i would make sure that the correct existing DC2 have
>>>> all 5 FSMO roles and is GC server and DNS with AD integrated zones
>>>> only for the correct old named "domain" domain.
>>>>
>>>> Then i would disconnect the renamed DC from the network and demote
>>>> it with dcpromo /forceremoval to member server.
>>>>
>>>> After that is done run metadata cleanup on DC2's AD database
>>>> according to this article
>>>> (http://support.microsoft.com/kb/555846/en-us) to remove the DC1,
>>>> either old or renamed, complete from AD so that only DC2 is listed.
>>>>
>>>> Also delete the zone in DNS where only DC1 is listed and use only
>>>> the correct zone for DC2.
>>>>
>>>> Then run dcdiag /v, netdiag /v on DC2 to make sure no errors exist.
>>>> If you have some, post the complete output here.
>>>>
>>>> If DNS, AD users and computers and AD sites and services is cleaned
>>>> up you can now promote the old DC1 again to domain controller.
>>>>
>>>> Best regards
>>>>
>>>> Meinolf Weber
>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
>>>> and
>>>> confers
>>>> no rights.
>>>> ** Please do NOT email, only reply to Newsgroups
>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>>> The actual server (netbios) name did not change. Originally the
>>>>> server were
>>>>> named:
>>>>> dc01.domain
>>>>> dc02.domain
>>>>> Now they are named
>>>>> dc01.domain.local
>>>>> dc02.domain
>>>>> I do not know how he changed the DNS name. It does not look like
>>>>> it
>>>>> is
>>>>> possible to do this in system properties. In ADUC the DNS names
>>>>> are
>>>>> :
>>>>> dc01.domain.local
>>>>> dc02.domain
>>>>> So it appears the only changes that the former admin made were to
>>>>> change the name of this server to dc01.domain.local and set up the
>>>>> DNS
>>>>> zone domain.local.
>>>>> Any help is much appreciated.
>>>>> thanks,
>>>>> Clay
>>>>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
>>>>> news:ff16fb66d3298cb0eda46c76a20@msnews.microsoft.com...
>>>>>> Hello Clay,
>>>>>>
>>>>>> Just to get you correct, one DC is renamed and has now a FQDN of
>>>>>> dc01.domain.local before you start the domain rename to
>>>>>> domain.local? Did he just change it via System properties?
>>>>>>
>>>>>> Best regards
>>>>>>
>>>>>> Meinolf Weber
>>>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
>>>>>> and
>>>>>> confers no rights.
>>>>>> ** Please do NOT email, only reply to Newsgroups
>>>>>> ** HELP us help YOU!!!
>>>>>> http://www.blakjak.demon.co.uk/mul_crss.htm
>>>>>>> I have a single label AD domain that I need to rename (Win2k3
>>>>>>> SP2). I recently took a job with a small company that was
>>>>>>> preparing to install exchange. When the previous admin realized
>>>>>>> that exch would not install on a single label domain it appears
>>>>>>> that he tried to rename one of the domain controllers. I was
>>>>>>> preparing to run rendom.exe when I ran dcdiag to make sure all
>>>>>>> was stable. I got the message below on one of the domain
>>>>>>> controllers:
>>>>>>>
>>>>>>> *** Warning: could not confirm the identity of this server
>>>>>>> in
>>>>>>> the directory versus the names returned by DNS servers.
>>>>>>> If there are problems accessing this directory server
>>>>>>> then
>>>>>>> you may need to check that this server is correctly
>>>>>>> registered
>>>>>>> with DNS
>>>>>>> ......................... DC01 passed test Connectivity
>>>>>>> This domain controller that gives this message is the one that
>>>>>>> has
>>>>>>> been renamed. I do not know how the admin renamed it but in the
>>>>>>> computer properites it shows up as "domain.local" instead of
>>>>>>> just
>>>>>>> "domain" (like the other domain controller). DCdiag expects
>>>>>>> this
>>>>>>> server to be dc01.domain but the server is named
>>>>>>> dc01.domain.local.
>>>>>>> Both "domain.local" and "domain" dns zones are created and exist
>>>>>>> in
>>>>>>> DNS. My question is - do i need to fix this before I run
>>>>>>> rendom.exe
>>>>>>> and if so where do I change it back.