Changing Domain

R

Rob

Our company recently changed its name from company a to
company b. My Active Direcory Domain is still
companya.com but I want to cange the domain name to our
new name companyb.com Is there any way to accomlish this?
I would appriciate any input

Thanks,


Rob
 
S

Simon Geary

If you are using Windows 2000 this has no domain renaming capability.
Windows 2003 allows domain rename under strict caveats i.e. if you use
Exchange you can't rename. So it might be possible to upgrade to Windows
2003 and then do the rename.

If you are in Windows 2000 mixed mode and have an NT BDC handy you could
synchronise the domain, blitz the Windows 2000 servers, promote the BDC to a
PDC and then start all over again. That's just theoretical though, I
wouldn't suggest you actually did that.
 
S

S.J.Haribabu

Hi Rob,

Although you can rename a Windows 2000 domain in some situations that are
described in this article, Microsoft highly recommends that you decide on
the Fully Qualified Domain Name (FQDN) for DNS before you actually create a
new domain or before you upgrade the domain from Windows NT 4.0 to Windows
2000. After you create the domain, you cannot rename a Windows 2000 domain
controller. Renaming the domain involves a considerable amount of work, and
it is only possible in a scenario that meets the following conditions:

You have to keep the Windows 2000 domain in Mixed mode. After you change it
to Native mode, you cannot return the domain to Mixed mode, thereby
rendering renaming impossible. To determine the mode in which the domain is
currently running, expand Active Directory Users and Computers, right-click
the domain name, and then click Properties. The mode appears in the Domain
operation mode dialog box.

Because the domain is in Mixed mode, it must also either have one or more
existing Windows NT 4.0 backup domain controllers (BDCs), or computers that
are available to use as Windows NT 4.0 BDCs.

Because you must demote all existing Windows 2000 domain controllers to
member servers before you rename the domain controller, review the
following information in terms of logistics:

The renaming can only take place after you revert the domain back to
Windows NT 4.0, and then during the upgrade to Windows 2000, after you have
renamed it with the desired DNS (FQDN) name. The NetBIOS domain name
remains the same.

If you have created one or more child domains, you have to revert the child
domains back to Windows NT 4.0 first, and then revert the parent domain.
Next, you rename the parent when you upgrade it to Windows 2000, and then
you bring the child domain up again when you upgrade it to Windows 2000.
The amount of time that this process requires depends on the number of
Windows 2000 domain controllers that are in the domain, in addition to
their physical location.

If your scenario meets the conditions listed in the "Summary" section of
this article, you can use the following steps to rename the Windows 2000
domain. These steps involve a single domain situation. If a child domain
exists:

Complete the same steps to revert the domain back to Windows NT 4.0 on the
child domain first, and then you stop after you complete step 6.

Complete steps 1 through 8 on the parent domain.

After you revert the parent domain back to Windows NT 4.0, and then upgrade
it back to Windows 2000 with the desired name, you can complete the final
upgrade steps to Windows 2000 on the former child domain, during which you
make it a Windows 2000 child domain again.

To Rename a Windows 2000 Domain
Create a backup of any and/or all domain controllers that may be involved
in this process.

If there are no existing Windows NT 4.0 BDCs in the Windows 2000 domain,
then you have to install one that is preferably running service pack 6 or
6a. If you want, you can install a second BDC and then physically remove it
from the domain to serve as a backup for the domain information as it
contains all of the domain user accounts, and the Security Accounts Manager
(SAM) and security information.

Allow sufficient time for this BDC to acquire all domain security and SAM
information. To force a full SAM/security database replication, run the
following command on the BDC:

net accounts /sync

A record of the successful full replication events should be logged in the
System log.

If there is only one Windows 2000 domain controller in the domain, leave
the Windows NT 4.0 BDC connected to the network, and then physically remove
the Windows 2000 domain controller from the network. Make sure that the
Windows 2000 domain controller is isolated from the rest of the network. If
it is plugged into a hub, make sure it is not connected to the rest of the
domain. If you have only one Windows 2000 domain controller, you can
perform step 6 now before you continue with the demotion of the Windows
2000 domain controller.

You must now demote all the Windows 2000 domain controllers to member
servers by running the dcpromo command on the actual domain controller. To
run this command, click Start, click Run, type dcpromo, and then click OK.
If there are more than one Windows 2000 domain controller, run dcpromo on
each of them to make each one a member server, until there is only one
Windows 2000 domain controller remaining.

Now you can disconnect the Windows 2000 domain controller from the network,
while leaving the Windows NT 4.0 BDC connected. Run dcpromo on this last
domain controller, and be sure to choose the last domain controller in the
domain option. When this completes, and the computer restarts, it will be a
member server in a work group, which you can then rejoin to the domain if
you want to. If you disconnected one Windows 2000 domain controller in step
4, then you simply run the dcpromo command on it as described in this step.

Note: To run dcpromo successfully, the network adapter must detect a
network connection. Therefore, the Windows 2000 domain controller must be
attached to an active hub or switch, even if there are no other connections
to the hub or switch, and it is isolated from everything else which is
desired.

Open Server Manager on the Windows NT 4.0 BDC and promote this computer to
a primary domain controller (PDC). If a message appears stating that it
cannot contact the PDC and asks if you want to continue, click Yes, and
then complete the promotion. When this is complete and the server restarts,
verify in Server Manager that the computer it is now described as the PDC.

Upgrade this Windows NT 4.0 PDC to Windows 2000. When the Windows 2000
upgrade is complete, the computer restarts to begin the Active Directory
installation. During this process, enter the desired domain name.

If you have demoted other Windows 2000 domain controllers earlier, you can
now promote them back to domain controllers by running dcpromo on them.

Rob - I have given some links below for better understanding. please have a
look at those articles before the implementation.

How to Rename a Windows 2000 Domain Controller
http://support.microsoft.com/?kbid=296592
How to Rename the DNS Name of a Windows 2000 Domain
http://support.microsoft.com/default.aspx?scid=KB;EN-US;q292541&


Thanks,

(e-mail address removed)

This posting is provided "AS IS" with no warranties, and confers no rights.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top