Rename Domain Controller

Hi Pros,

I been trying to rename the current DC, from WORLDGROUPC to WORLDGROUPC by
using Netdom.
WORLDGROUP is the old DC with Windows NT 4.0 and WORLDGROUPC is Windows
server 2003
we are going to replace the Old server to the new one, therefore, we need to
change the NEW server(WORLDGROUPC) to the name of the OLD server(WORLDGROUP).

the thing is, I have disconnected the NEW DC from the network when i tried
rename it, so that it won't crashes with the OLD DC (which is still running)
in the network.

so, now the DC (WORLDGROUPC) is standalone, doesn't connect to any network,
and i want to change the DC name to WORLDGROUP
but in the command Prompt:

>netdom computername WORLDGROUPC /add WORLDGROUP

When i enter this, it prompt up error:

RPC Server is unavailable.

please help me to solve this problem, thanks in advance

--
Message posted via http://www.winserverkb.com

In news:7e479e097753a@uwe,
ViNC3 via WinServerKB.com <u40010@uwe> typed:
> Hi Pros,
>
> I been trying to rename the current DC, from WORLDGROUPC to
> WORLDGROUPC by using Netdom.
> WORLDGROUP is the old DC with Windows NT 4.0 and WORLDGROUPC is
> Windows server 2003
> we are going to replace the Old server to the new one, therefore, we
> need to change the NEW server(WORLDGROUPC) to the name of the OLD
> server(WORLDGROUP).
>
> the thing is, I have disconnected the NEW DC from the network when i
> tried rename it, so that it won't crashes with the OLD DC (which is
> still running) in the network.
>
> so, now the DC (WORLDGROUPC) is standalone, doesn't connect to any
> network, and i want to change the DC name to WORLDGROUP
> but in the command Prompt:
>
> > netdom computername WORLDGROUPC /add WORLDGROUP
>
> When i enter this, it prompt up error:
>
> RPC Server is unavailable.
>
> please help me to solve this problem, thanks in advance

First, you've multi-posted this to numerous groups. Many of the folks here
monitor the groups you posted it to, but I can understand trying to get max
exposure. It would have actually been easier and *more* beneficial to you
and us if you had cross-posted it where it goes one time to all groups and
any responses would have gone to all groups simultaneously so YOU and us
would have only checked one group. But if going thru a news posting
website, they may not offer the option to do this.

That said...

Renaming a DC requires the domain FL to be at 2003. What FL is your domain
at?

Also, if trying to rename something to a name previously used as a DC (the
old one), and if it wasn't demoted properly, the name may still be in the AD
database, which you would need KB216498 to remove.

I don't know what article or instructions you followed to perform this task,
which you did not provide us (sometimes it's helpful to provide
configuration information such an unedited ipconfig /all of a sample DC and
of this machine, and other pertinent facts to better assist), here's more
info on renaming a DC:

Rename a domain controller:
http://technet2.microsoft.com/window....mspx?mfr=true

Renaming domain controllers
http://technet2.microsoft.com/window....mspx?mfr=true

I hope it helps. If not, please provide additional info as suggested above.


--
Regards,
Ace

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

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

Infinite Diversities in Infinite Combinations

Hi Ace,

sorry about the multiple posts though, cause i was not sure which section
should i posts into.Wont do it again next time.


The new DC was disconnected from the network, it's standalone now, so does
the Old DC (which are not demoted) will still matters?

also, i need to know, if i have unplug the network cable from the New DC, can
i still rename the new DC (which doesn't connected to any network at all)?

the instruction I followed is
http://www.petri.co.il/windows_2003_...ler_rename.htm

i have read through the link u posted, but I only start the first part, which
is :> netdom computername WORLDGROUPC /add WORLDGROUP

and the error prompt up : RPC Server is unavailable.

thanks in adv

regards,
Vince


Ace Fekay [MVP] wrote:
>> Hi Pros,
>>
>[quoted text clipped - 21 lines]
>>
>> please help me to solve this problem, thanks in advance
>
>First, you've multi-posted this to numerous groups. Many of the folks here
>monitor the groups you posted it to, but I can understand trying to get max
>exposure. It would have actually been easier and *more* beneficial to you
>and us if you had cross-posted it where it goes one time to all groups and
>any responses would have gone to all groups simultaneously so YOU and us
>would have only checked one group. But if going thru a news posting
>website, they may not offer the option to do this.
>
>That said...
>
>Renaming a DC requires the domain FL to be at 2003. What FL is your domain
>at?
>
>Also, if trying to rename something to a name previously used as a DC (the
>old one), and if it wasn't demoted properly, the name may still be in the AD
>database, which you would need KB216498 to remove.
>
>I don't know what article or instructions you followed to perform this task,
>which you did not provide us (sometimes it's helpful to provide
>configuration information such an unedited ipconfig /all of a sample DC and
>of this machine, and other pertinent facts to better assist), here's more
>info on renaming a DC:
>
>Rename a domain controller:
>http://technet2.microsoft.com/window....mspx?mfr=true
>
>Renaming domain controllers
>http://technet2.microsoft.com/window....mspx?mfr=true
>
>I hope it helps. If not, please provide additional info as suggested above.
>

--
Message posted via http://www.winserverkb.com

In news:7e48278def628@uwe,
ViNC3 via WinServerKB.com <u40010@uwe> typed:
> Hi Ace,
>
> sorry about the multiple posts though, cause i was not sure which
> section should i posts into.Wont do it again next time.
>
>
> The new DC was disconnected from the network, it's standalone now, so
> does the Old DC (which are not demoted) will still matters?
>
> also, i need to know, if i have unplug the network cable from the New
> DC, can i still rename the new DC (which doesn't connected to any
> network at all)?
>
> the instruction I followed is
> http://www.petri.co.il/windows_2003_...ler_rename.htm
>
> i have read through the link u posted, but I only start the first
> part, which is :> netdom computername WORLDGROUPC /add WORLDGROUP
>
> and the error prompt up : RPC Server is unavailable.
>
> thanks in adv
>
> regards,
> Vince

It seems that a few mistakes may have been made. With an AD DC, you cannot
simply just unplug it and think it will go away. This is not NT4. With AD,
you MUST run the dcpromo wizard on the DC you want to demote and follow the
steps. There are dozens of tasks that run in the background to properly
remove it from AD.

If you simply unplugged it, then AD still thinks it is there. If the
unplugged DC was holding a FSMO role, and you never seized it to another DC,
and if DNS was installed and now the other DCs have no DNS server to ask,
then the RPC error is expected. Also... well... there are numerous questions
to ask.

Based on what you posted, there were things done that are not the way to do
it, unfortunately with all due respect. When you rename a DC, you MUST do it
while it is connected to the rest of the domain so the domain is aware of
the change. If you had an old DC, and you wanted to introduce a new DC with
the same name, you must FIRST demote the old one, give it time to replicate
the change to the other DCs, then rename the new member server to the same
name, then promote it into the domain as an additonal replica DC. Unplugging
it is the first error.

I you got the RPC error, this DC may be using another DC as it;s DNS
address. This is because it maybe asking for one of the FSMO role holders
about the name change. The DC (and any AD member) will ask DNS to "find" the
domain, including to "find" itself. RPC is a network communication protocol
and the networ services MUST be running with a valid IP address. DNS must be
available.

To properly answer for YOUR scenario, I would really need to know more
about what you did and what is left, what you didn't do, etc, such as:

Was the DC you removed the first one orginally created in the forest/domain?
Was DNS installed on it?
Was/is DNS installed on the other DC?
What DNS address was the DC you unplugged using? Was it using itself or
another DC's IP address?

Did you run dcpromo? If not:
Did you delete the compuer object out of Sites and Services?
Did you delete it out of the Domain Controllers OU?
Did you follow the steps to forcefully remove it from the AD database (as I
previousl asked you) using KB216498?
Did you seize the FSMO roles to the remaining DC(s)?
Is DNS on one of the remaining DCs? If so, do the SRV records show up?
Are the remaining DCs only using the DCs as their DNS address in IP
properties?

Ace

Hi,

previously i was wrong, about the Netdom thingy, as netdom only allow to
changed computer name, but i need to changed the Domain name.

here are the answer to your question.


Was the DC you removed the first one orginally created in the forest/domain?
No, I haven’t removed any DC yet.
The old one they have been using for years, Windows NT 4.0 with Domain Name
called (WORLDGROUP) – it is the PrimaryDC (which is still connected in the
Network and everyone is using it)
and now, a new DC installed with windows server 2003, firstly with the name
(WORLDGROUPC), but now they want me to change it to WORLDGROUP to replace the
old winNT (which is the current issue).

Was DNS installed on it?
The old winNT = no, it don’t have DNS
The new win2003 = yes, it have DNS

Was/is DNS installed on the other DC?
The answer is same as above, no other DC have DNS (actually the network
doesn’t have any other DC, just these two)

What DNS address was the DC you unplugged using? Was it using itself or
another DC's IP address?
Have asked the person who work here before me, he said we doesn’t use DNS
(but in the New win2003, i have installed DNS)

Did you run dcpromo? If not:
Yes, I did run dcpromo on the new win2003 to promote it to become DCs

Did you delete the compuer object out of Sites and Services?
no, I didn’t delete any computer object out of sites and services

Did you delete it out of the Domain Controllers OU?
No

Did you follow the steps to forcefully remove it from the AD database (as I
previousl asked you) using KB216498?
I haven’t demoted any DC

Did you seize the FSMO roles to the remaining DC(s)?
No, I didn’t know what is FSMO

Is DNS on one of the remaining DCs? If so, do the SRV records show up?
Yes, DNS on one of the remaining DCs, but I dunno what and how to find SRV
records.

Are the remaining DCs only using the DCs as their DNS address in IP
properties?
I have asked the person who work here before me, he said we doesn’t use DNS
server, just IP address (not sure that’s the answer you want)



I have been searching through the web, and found this tool called Microsoft
Domain Rename Tools, does that tool i can use?

or I need to first demote the Old winNT PDC and then only i can change Domain
name?

Can you give me step by step instruction on what I need to do to change the
New2003 Domain Name from WORLDGROUPC to WORLDGROUP to replace the old WinNT?

thankx

regards,
Vince

Ace Fekay [MVP] wrote:
>> Hi Ace,
>>
>[quoted text clipped - 20 lines]
>> regards,
>> Vince
>
>It seems that a few mistakes may have been made. With an AD DC, you cannot
>simply just unplug it and think it will go away. This is not NT4. With AD,
>you MUST run the dcpromo wizard on the DC you want to demote and follow the
>steps. There are dozens of tasks that run in the background to properly
>remove it from AD.
>
>If you simply unplugged it, then AD still thinks it is there. If the
>unplugged DC was holding a FSMO role, and you never seized it to another DC,
>and if DNS was installed and now the other DCs have no DNS server to ask,
>then the RPC error is expected. Also... well... there are numerous questions
>to ask.
>
>Based on what you posted, there were things done that are not the way to do
>it, unfortunately with all due respect. When you rename a DC, you MUST do it
>while it is connected to the rest of the domain so the domain is aware of
>the change. If you had an old DC, and you wanted to introduce a new DC with
>the same name, you must FIRST demote the old one, give it time to replicate
>the change to the other DCs, then rename the new member server to the same
>name, then promote it into the domain as an additonal replica DC. Unplugging
>it is the first error.
>
>I you got the RPC error, this DC may be using another DC as it;s DNS
>address. This is because it maybe asking for one of the FSMO role holders
>about the name change. The DC (and any AD member) will ask DNS to "find" the
>domain, including to "find" itself. RPC is a network communication protocol
>and the networ services MUST be running with a valid IP address. DNS must be
>available.
>
>To properly answer for YOUR scenario, I would really need to know more
>about what you did and what is left, what you didn't do, etc, such as:
>
>Was the DC you removed the first one orginally created in the forest/domain?
>Was DNS installed on it?
>Was/is DNS installed on the other DC?
>What DNS address was the DC you unplugged using? Was it using itself or
>another DC's IP address?
>
>Did you run dcpromo? If not:
>Did you delete the compuer object out of Sites and Services?
>Did you delete it out of the Domain Controllers OU?
>Did you follow the steps to forcefully remove it from the AD database (as I
>previousl asked you) using KB216498?
>Did you seize the FSMO roles to the remaining DC(s)?
>Is DNS on one of the remaining DCs? If so, do the SRV records show up?
>Are the remaining DCs only using the DCs as their DNS address in IP
>properties?
>
>Ace

--
Message posted via WinServerKB.com
http://www.winserverkb.com/Uwe/Forum...er-ad/200801/1

http://blogs.dirteam.com/blogs/jorge...11/19/109.aspx

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* How to ask a question --> http://support.microsoft.com/?id=555375
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"ViNC3 via WinServerKB.com" <u40010@uwe> wrote in message
news:7e479e097753a@uwe...
> Hi Pros,
>
> I been trying to rename the current DC, from WORLDGROUPC to WORLDGROUPC by
> using Netdom.
> WORLDGROUP is the old DC with Windows NT 4.0 and WORLDGROUPC is Windows
> server 2003
> we are going to replace the Old server to the new one, therefore, we need
> to
> change the NEW server(WORLDGROUPC) to the name of the OLD
> server(WORLDGROUP).
>
> the thing is, I have disconnected the NEW DC from the network when i tried
> rename it, so that it won't crashes with the OLD DC (which is still
> running)
> in the network.
>
> so, now the DC (WORLDGROUPC) is standalone, doesn't connect to any
> network,
> and i want to change the DC name to WORLDGROUP
> but in the command Prompt:
>
>>netdom computername WORLDGROUPC /add WORLDGROUP
>
> When i enter this, it prompt up error:
>
> RPC Server is unavailable.
>
> please help me to solve this problem, thanks in advance
>
> --
> Message posted via http://www.winserverkb.com
>

In news:7e55d1042fbe9@uwe,
ViNC3 via WinServerKB.com <u40010@uwe> typed:
> Hi,
>
> previously i was wrong, about the Netdom thingy, as netdom only allow
> to changed computer name, but i need to changed the Domain name.
>
> here are the answer to your question.
>
>
> Was the DC you removed the first one orginally created in the
> forest/domain? No, I haven't removed any DC yet.
> The old one they have been using for years, Windows NT 4.0 with
> Domain Name called (WORLDGROUP) - it is the PrimaryDC (which is still
> connected in the Network and everyone is using it)
> and now, a new DC installed with windows server 2003, firstly with
> the name (WORLDGROUPC), but now they want me to change it to
> WORLDGROUP to replace the old winNT (which is the current issue).
>
> Was DNS installed on it?
> The old winNT = no, it don't have DNS
> The new win2003 = yes, it have DNS
>
> Was/is DNS installed on the other DC?
> The answer is same as above, no other DC have DNS (actually the
> network doesn't have any other DC, just these two)
>
> What DNS address was the DC you unplugged using? Was it using itself
> or another DC's IP address?
> Have asked the person who work here before me, he said we doesn't use
> DNS (but in the New win2003, i have installed DNS)
>
> Did you run dcpromo? If not:
> Yes, I did run dcpromo on the new win2003 to promote it to become DCs
>
> Did you delete the compuer object out of Sites and Services?
> no, I didn't delete any computer object out of sites and services
>
> Did you delete it out of the Domain Controllers OU?
> No
>
> Did you follow the steps to forcefully remove it from the AD database
> (as I previousl asked you) using KB216498?
> I haven't demoted any DC
>
> Did you seize the FSMO roles to the remaining DC(s)?
> No, I didn't know what is FSMO
>
> Is DNS on one of the remaining DCs? If so, do the SRV records show up?
> Yes, DNS on one of the remaining DCs, but I dunno what and how to
> find SRV records.
>
> Are the remaining DCs only using the DCs as their DNS address in IP
> properties?
> I have asked the person who work here before me, he said we doesn't
> use DNS server, just IP address (not sure that's the answer you want)
>
>
>
> I have been searching through the web, and found this tool called
> Microsoft Domain Rename Tools, does that tool i can use?
>
> or I need to first demote the Old winNT PDC and then only i can
> change Domain name?


No, just unplug the NT4 domain controller and NEVER put it online again.


>
> Can you give me step by step instruction on what I need to do to
> change the New2003 Domain Name from WORLDGROUPC to WORLDGROUP to
> replace the old WinNT?
>
> thankx
>
> regards,
> Vince


Rename the domain? I see. That changes everything. This is a completely
different animal. This can be tricky because many services and apps are
probably running and referencing it by the old domain name, including
possibly having a trust from the current domain to this domain, shared
resources, etc, will all have to be deleted, removed, etc.

Forget what I asked about DNS since now I realize the old box is NT4. I
missed that earlier. Sorry.

Do you have Exchange installed? If so, which version? If Exchange 2000,
forget it. If 2003, it has provisions for the rename. Either way, it will
greatly complicate it and it's suggested to not bother. Excerpt from the
second link below:

"If you do have Exchange 2000 installed in the forest, and you do need to
carry out a domain rename operation (slide 24), then what are your options?
Well, option 1 is you could remove and then reinstall Exchange 2000, kind of
treating it as a complete disaster recovery scenario, in which you remove
Exchange 2000; you rename the domains in the forest; you reinstall Exchange
2000; and then you reassociate all the mailboxes. Now obviously this is an
example of a case where this could be a pretty heavy-weight and a
substantially administration-intensive operation."
Do you have a PKI (Cert services) installed?
You will need to take an inventory of apps and services that may need to be
uninstalled and reinstalled with the domain rename too, that is if you can
save the data and go with the rename.

Lot's of info on renaming domains with Exchange 2000 or 2003::
819145 - Support WebCast Microsoft Windows Server 2003 Implementing an
Active Directory Domain Rename Operation:
http://support.microsoft.com/default...uct=winsvr2003

Taken from the webcast above but written into a report and much easier to
read:
Microsoft Windows Server 2003 Implementing an Active Directory Domain Rename
Operation:
http://support.microsoft.com/default...Fwct052103.asp

Now if you have Exchange 2003, here is what you need as well:
Supplemental steps for using the Exchange Server Domain Rename Fixup tool
together with the Windows Server 2003 domain rename tools:
http://support.microsoft.com/default...b/842116/en-us

Microsoft's take on it:
Windows Server 2003 Domain Rename Tools, Procedure and Step by Step Guide:
http://www.microsoft.com/windowsserv...ainrename.mspx

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

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

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

Also, a huge factor: Is your Windows 2003 AD DNS domain name a single label
name in DNS? In other words, under DNS Forward Lookup Zones, is the domain
name "WORLDGROUPC" instead of "worldgroupc.local," "worldgroupc.com,"
"worldgroupc.vince," etc? If so, then that is another huge problem. That was
why I would have liked to have seen an unedited ipconfig /all from the DCs.

You've been tasked something very involved that will cut into your drinking
(or personal - whichever) time. If the domain is a single label name, well
this will give you a chance to fix that too. I wish you lot's of luck.

Ace

Hi,

For NT4.0 and Win2003 Server, both of them doesn't use Exchange Server,
From what I know, there Network flow for this company should be a very simple,

CURRENT - PDC NT4.0 (WORLDGROUP) >>>connected to >>> alots of WorkStation
(Computer)

According to the Senior Tech, he told me that this company just used simple a
PDC to hosts User account and thats it, they didn't use Exchanged Server.

and as for the Win2003 AD DNS it is WORLDGROUPC.kldc4
kldc4 is the computername
and the domain is WORLDGROUPC

and i have tried the Microsoft Domain Rename Tools
In the Command Prompt:-

C:\Program Files\Microsoft Domain Rename Tools>:rendom /list
then the message prompt stating that :

"The Behavior version of the Forest is 0, it must be 2 or greater to preform
a domain rename; the server is unwilling to process the request. :8245"

what should I do?

thanks

regards,
Vince

Ace Fekay [MVP] wrote:
>> Hi,
>>
>[quoted text clipped - 55 lines]
>> or I need to first demote the Old winNT PDC and then only i can
>> change Domain name?
>
>No, just unplug the NT4 domain controller and NEVER put it online again.
>
>> Can you give me step by step instruction on what I need to do to
>> change the New2003 Domain Name from WORLDGROUPC to WORLDGROUP to
>[quoted text clipped - 4 lines]
>> regards,
>> Vince
>
>Rename the domain? I see. That changes everything. This is a completely
>different animal. This can be tricky because many services and apps are
>probably running and referencing it by the old domain name, including
>possibly having a trust from the current domain to this domain, shared
>resources, etc, will all have to be deleted, removed, etc.
>
>Forget what I asked about DNS since now I realize the old box is NT4. I
>missed that earlier. Sorry.
>
>Do you have Exchange installed? If so, which version? If Exchange 2000,
>forget it. If 2003, it has provisions for the rename. Either way, it will
>greatly complicate it and it's suggested to not bother. Excerpt from the
>second link below:
>
>"If you do have Exchange 2000 installed in the forest, and you do need to
>carry out a domain rename operation (slide 24), then what are your options?
>Well, option 1 is you could remove and then reinstall Exchange 2000, kind of
>treating it as a complete disaster recovery scenario, in which you remove
>Exchange 2000; you rename the domains in the forest; you reinstall Exchange
>2000; and then you reassociate all the mailboxes. Now obviously this is an
>example of a case where this could be a pretty heavy-weight and a
>substantially administration-intensive operation."
>Do you have a PKI (Cert services) installed?
>You will need to take an inventory of apps and services that may need to be
>uninstalled and reinstalled with the domain rename too, that is if you can
>save the data and go with the rename.
>
>Lot's of info on renaming domains with Exchange 2000 or 2003::
>819145 - Support WebCast Microsoft Windows Server 2003 Implementing an
>Active Directory Domain Rename Operation:
>http://support.microsoft.com/default...uct=winsvr2003
>
>Taken from the webcast above but written into a report and much easier to
>read:
>Microsoft Windows Server 2003 Implementing an Active Directory Domain Rename
>Operation:
>http://support.microsoft.com/default...Fwct052103.asp
>
>Now if you have Exchange 2003, here is what you need as well:
>Supplemental steps for using the Exchange Server Domain Rename Fixup tool
>together with the Windows Server 2003 domain rename tools:
>http://support.microsoft.com/default...b/842116/en-us
>
>Microsoft's take on it:
>Windows Server 2003 Domain Rename Tools, Procedure and Step by Step Guide:
>http://www.microsoft.com/windowsserv...ainrename.mspx
>
>The Lazy Admin - Domain Rename Part 1 - Setup:
>http://thelazyadmin.com/blogs/thelaz...00_-Setup.aspx
>
>The Lazy Admin - Domain Rename Part 2 - Renaming:
>http://thelazyadmin.com/blogs/thelaz...-Renaming.aspx
>
>The Lazy Admin - Domain Rename Part 3 - Exchange 2003:
>http://thelazyadmin.com/blogs/thelaz...ange-2003.aspx
>
>Also, a huge factor: Is your Windows 2003 AD DNS domain name a single label
>name in DNS? In other words, under DNS Forward Lookup Zones, is the domain
>name "WORLDGROUPC" instead of "worldgroupc.local," "worldgroupc.com,"
>"worldgroupc.vince," etc? If so, then that is another huge problem. That was
>why I would have liked to have seen an unedited ipconfig /all from the DCs.
>
>You've been tasked something very involved that will cut into your drinking
>(or personal - whichever) time. If the domain is a single label name, well
>this will give you a chance to fix that too. I wish you lot's of luck.
>
>Ace

--
Message posted via WinServerKB.com
http://www.winserverkb.com/Uwe/Forum...er-ad/200801/1

In news:7e88c7bb41929@uwe,
ViNC3 via WinServerKB.com <u40010@uwe> typed:
> Hi,
>
> For NT4.0 and Win2003 Server, both of them doesn't use Exchange
> Server,
> From what I know, there Network flow for this company should be a
> very simple,
>
> CURRENT - PDC NT4.0 (WORLDGROUP) >>>connected to >>> alots of
> WorkStation (Computer)
>
> According to the Senior Tech, he told me that this company just used
> simple a PDC to hosts User account and thats it, they didn't use
> Exchanged Server.
>
> and as for the Win2003 AD DNS it is WORLDGROUPC.kldc4
> kldc4 is the computername
> and the domain is WORLDGROUPC
>
> and i have tried the Microsoft Domain Rename Tools
> In the Command Prompt:-
>
> C:\Program Files\Microsoft Domain Rename Tools>:rendom /list
> then the message prompt stating that :
>
> "The Behavior version of the Forest is 0, it must be 2 or greater to
> preform a domain rename; the server is unwilling to process the
> request. :8245"
>
> what should I do?
>
> thanks
>
> regards,
> Vince

I asked if you had Exchange because if you did, it would complicate matters
because Exchange is a directory-enabled app, meaning it has numerous roots
in AD.

As for the error you are getting, it means the Forest Functional Leven must
be at 2, which is "Windows Server 2003 Forest Level." Look at this for more
specific info and limitationts:
How to raise domain and forest functional levels in Windows Server 2003:
http://support.microsoft.com/kb/322692

I hope that helps.

As for this statement:
> and as for the Win2003 AD DNS it is WORLDGROUPC.kldc4
> kldc4 is the computername
> and the domain is WORLDGROUPC

What exactly is the AD DNS domain name?
That would be the domain name that shows up in ADUC as well as the zone name
in DNS.

Is it in the form of worldgroupc.com, or worldgroupc.local, or is it just
WORLDGROUPC without a TLD? The TLD is the top level domain name such as com,
local, edu, etc.

Ace

Hi,

thanks dude, i finally able to rename it.
anything i should know about after renaming server, just drop a msg.

thanks again, and have a nice day





Ace Fekay [MVP] wrote:
>> Hi,
>>
>[quoted text clipped - 30 lines]
>> regards,
>> Vince
>
>I asked if you had Exchange because if you did, it would complicate matters
>because Exchange is a directory-enabled app, meaning it has numerous roots
>in AD.
>
>As for the error you are getting, it means the Forest Functional Leven must
>be at 2, which is "Windows Server 2003 Forest Level." Look at this for more
>specific info and limitationts:
>How to raise domain and forest functional levels in Windows Server 2003:
>http://support.microsoft.com/kb/322692
>
>I hope that helps.
>
>As for this statement:
>> and as for the Win2003 AD DNS it is WORLDGROUPC.kldc4
>> kldc4 is the computername
>> and the domain is WORLDGROUPC
>
>What exactly is the AD DNS domain name?
>That would be the domain name that shows up in ADUC as well as the zone name
>in DNS.
>
>Is it in the form of worldgroupc.com, or worldgroupc.local, or is it just
>WORLDGROUPC without a TLD? The TLD is the top level domain name such as com,
>local, edu, etc.
>
>Ace

--
Message posted via WinServerKB.com
http://www.winserverkb.com/Uwe/Forum...er-ad/200802/1

In news:7f3563d9f7c9c@uwe,
ViNC3 via WinServerKB.com <u40010@uwe> typed:
> Hi,
>
> thanks dude, i finally able to rename it.
> anything i should know about after renaming server, just drop a msg.
>
> thanks again, and have a nice day

Good to hear. Just make sure any apps that reference the domain name get
updated.

Cheers!

Ace

[aarshad]

Hi

I am working on a similar type of issue. I have to migrate nt4 domain to server 2003 active directory with no effect to the users being done.
This are the steps that i have done
1. Created a new domain on server2003 with a new domain name.
2.Established relationship between nt4 domain and server2003.
3. Migrated 2 users and ran the test of accessing drives and communicating to the old nt4 domain.

Heres the issue
1. I have to migrate all users from old nt4 domain with no effect to their domain access on workstations.
2.Rename the domain back to the old nt4 name.

Any sort of help will be appreciated.

Thanks in advance

[Carley]

If you want to rename the domain then you will be able to do that with the System Properties dialog box. For example If you wish to rename a DC having name from SERVER101 within DPETRI.NET domain to ZEUS the go through the steps below.

1. First of all open the System applet from Control Panel.
2. Click on change from the Computer Name tab.
3. You will see one warning message appears. Read that and to accept it click on OK button.
4. Enter the In the new host name in computer name box of the Domain Controller and click Ok.
5. From the Computer Name modify window, type the name as well as password for a user who is a member for the Domain Admins group.
6. You will see the warning that says that you have to restart your computer. Acknowledge it.
7. Click the Ok button and reboot your computer.

[aarshad]

After renaming the domain can i retire the old nt4 domain by just shutting it down?

Also after domain is renamed all users and groups will they have the same persmission to files folders vpn and work station logons as they had on the old nt4 domain?

Thanks.