Re: nt 4 upgrade to windows 2003 server question

From: Todd J Heron (todd_heron_no_spam_at_hotmail.com)
Date: 01/23/05 

Date: Sun, 23 Jan 2005 13:34:07 -0500

Yes. While it's possible to have a single label dns domain and dynamic
registration if you add a registry setting on the machines or use a group
policy setting depending on the OS but this is a workaround to solve a
design weakness in the particular DNS infrastructure and as such I
personally would not recommend it.

Renaming a Domain: Process and Side Effects
http://support.microsoft.com/default.aspx?scid=kb;en-us;178009

The following procedure describes how to safely rename a Windows NT domain.
This will work for a single domain, or for an accounts domain or resource
domain in a network using the master domain model.

To change a domain name, follow these steps:
 1) Document and then break all trust relationships between the domain whose
name you will be changing and all other domains. Be sure to remove the trust
entry on both sides of the trust (in User Manager for Domains for both
domains in the trust).

 2) Stop all BackOffice services such as Microsoft Exchange Server, SQL
Server, and Internet Information Server. Set startup to manual on all these
services.

 3) Change the domain name on the PDC.

 4) Restart the PDC. This will cause the <1Bh> entry for the new domain to
appear in the WINS server.

 5) If you are using WINS for NetBIOS over TCP/IP name resolution, force
replication from the PDC's primary WINS server to all other WINS servers to
propagate the <1Bh> entry for the new domain. Name resolution to the PDC is
necessary for each BDC to successfully change to the new domain name. If you
are using TCP/IP without using WINS, create an LMHOSTS file with a <1Bh>
entry for the new domain and put it on each BDC.

 6) On each BDC, change the domain name and restart. The restart is
necessary for the BDC to correctly register its <1Ch> entry with WINS. For
additional information about what to do if the BDC refuses the domain name
change, please see the following article in the Microsoft Knowledge Base:
Q139471 Unable to Change Domain Name of Windows NT BDC
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q139471

 7) Force replication from all WINS servers to propagate the <1Ch> entry.

 8) Re-establish the trust relationships. Using Server Manager, synchronize
both domains involved in each trust.

 9) In the Services tool in Control Panel, re-enter the service account for
each of the BackOffice services that were stopped in step 2. Pick the
account by using the Startup button rather than typing in the account name.
Set the services back to Automatic startup, if appropriate. Restart the
services in the correct order.

10) Make any necessary service-specific changes, as detailed elsewhere in
this article.

11) Change the domain name on each member server or workstation. For
downlevel clients such as Windows 95 or Windows for Workgroups, change the
workgroup name to the new domain name.

12) Synchronize the entire domain.

Important notes:
*Do not install any primary domain controller (PDC) or backup domain
controller (BDC) during this procedure, under either the old or new domain
name.

*Do not promote any BDC to PDC during this procedure.

*This procedure should only be undertaken during a time when ALL network
services related to this domain can be disrupted. All clients should log off
and remain logged off until the rename is complete and all computers
involved have been restarted.

*Perform a full backup on all computers involved immediately before
beginning this process.

*Create separate, updated Emergency Repair Disks for each computer involved
immediately before and after the update.

*Have a copy of the Windows NT Server compact disc, the latest service pack,
and Windows NT boot disks (appropriate to your version of Windows NT)
available during the procedure.

*The NETDOM utility in the Windows NT Server Resource Kit, Supplement 2, can
be used to change the domain name remotely on some computers, preventing a
visit to each computer involved. 

-- 
Todd J Heron, MCSE
Windows Server 2003/2000/NT
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights
Loading