2003 server 32bit migration to 64bit
I just finished migrating a NT 4PDC to Windows 2003 server 32 bit. everything on the domain seems to be working great. I now would like to know how I can easily migrate a windows 2003 64-bit server into the Active Directory, which will become my main DC.
1) I still have NT 4 BDC machines running necessary software and need to keep in mixed mode, so will migrating to a 64 bit 2003 controller effect that?
2) can I just run adprep /forest and adprep/domainprep, or do I need to transfer FSMO roles?
Re: 2003 server 32bit migration to 64bit
Try the below method for the migration:
Install Windows Server 2003 R2 onto the new server which is intended to be promoted as a Domain Controller. Ensure the new server is assigned a routable static IP address on your IP subnet. Ensure the IP address is not included in any of your existing DHCP scopes. The only DNS server entry at this stage should be the IP address of the existing domain controller on your network.
After installation, join the new machine to the existing domain as a member server. This procedure is exactly the same as joining a workstation to the domain.
Since you are upgrading the Operating System on the new Domain Controller, you will need to add some values to the existing Active Directory schema, in order for the new server to become a Domain Controller. Windows Server 2003 R2 supports more functionality than before, so a schema upgrade for the domain and forest is required to facilitate this and make this new feature set fully functional on the domain. To make the necessary changes, you must be logged on as the built-in Administrator user account, or a user with Domain, Schema and Enterprise Admin privileges.
Since you are trying to extend the schema of your 32-bit server but only have 64-bit R2 media, you need to download the 32-bit version of adprep from http://support.microsoft.com/kb/919151/en-us. Extract the download, then load a command prompt and execute the command adprep /forestprep.
Next, execute adprep /domainprep . You must be logged on as a Domain Admin user for these steps to work correctly. Once these commands have run your Active Directory schema will have been extended to support Windows Server 2003 R2 as a Domain Controller.
The next step is to promote the new server as a Domain Controller for the domain. Enter dcpromo at a command prompt and follow the wizard. When prompted, select the option for an additional domain controller in an existing domain. After the wizard completes, the new server will be acting as a Domain Controller for your domain. It is necessary at this point to restart the server for these changes to be applied.
In a single-domain Active Directory forest, all servers should also be Global Catalog servers. The Global Catalog is a required component of Active Directory which is used during logins to establish universal group membership for a user account. To promote the new server as a Global Catalog, open Active Directory Sites and Services from the Administrative Tools container within Control Panel or on the Start Menu. Double-click Sites, then Servers, followed by the name of the new server. Next, right-click "NTDS Settings" and select Properties. On the General tab, check the Global Catalog checkbox. Restart the new Domain Controller for changes to take effect.
Since you intend on removing the old Domain Controller from the domain, you need to transfer all the Operations (FSMO) roles to the new Domain Controller.
The current FSMO role configuration for your network can be found by running the command "netdom query fsmo" at a command prompt on a Domain Controller.
To transfer these FSMO roles to the new domain controller, follow the information detailed in the following Microsoft Support article: http://support.microsoft.com/kb/324801. Please ensure any other information you follow is information regarding the TRANSFER of FSMO roles. Seizing FSMO roles is an emergency operation which should not be performed during this procedure.
DNS is a critical component of your Active Directory network. The easiest way to install the DNS role onto the new server is to follow the instructions outlined at http://support.microsoft.com/kb/814591 You should be already using Active Directory-integrated DNS zones, which is the easiest method of allowing DNS replication to occur - DNS information is stored in Active Directory and replicates with Domain Controller replication traffic. To check if your DNS zones are AD-integrated (and convert them if not), please follow http://support.microsoft.com/kb/227844.
You probably want to enable DNS forwarding in the DNS console on the server, too. This forwards lookups for external domains to a DNS server at your ISP, which allows the server to effectively resolve DNS for external domains. More information on forwarders can be found at http://technet2.microsoft.com/Window...ad3821033.mspx.
To move DHCP to the new server, you will need to first install the role. Please see http://support.microsoft.com/kb/300429 for information on how to do this. To correctly configure DHCP after the role is installed on your new server, you will need to ensure you configure it to distribute IP addresses which are in a different range to the IP scope defined on the other DHCP server. You should also ensure the correct DNS and WINS servers are entered into the scope options. Remember that the only DNS servers which should be configured on workstations are the Domain Controllers which are also acting as DNS servers - no ISP DNS server should ever be set through DHCP.
Once all of these steps have been completed, you should have successfully transferred all of the Active Directory roles to the new domain controller. At this stage, I would suggest you shut down the old domain controller and check to ensure all services on workstations and servers are working correctly - including logins. If they are, you should be safe to switch the old DC back on, run dcpromo and demote it from its Domain Controller role. This will remove the DC as a Domain Controller, leaving it as a member server on the network.
To completely remove the DC from the network, you will need to remember that any other data - including folder redirection folders and user profiles - should be replicated or otherwise transferred to either the new server or another location on the network. ROBOCOPY is a tool from Microsoft which can move your data folders to the new server, as well as the NTFS ACLs on those files.
|Tags: active directory, domain, fsmo roles, server, windows 2003 server|
|Thread Tools||Search this Thread|
|Similar Threads for: "2003 server 32bit migration to 64bit"|
|Thread||Thread Starter||Forum||Replies||Last Post|
|Doubts on printer migration from windows server 2003 to Windows server 2008 R2||AapHo||Windows Server Help||8||08-03-2012 12:02 AM|
|SERVER 2003 - SBS 2011 Migration Issue||lbates70||Windows Software||1||01-10-2011 11:26 AM|
|How to Migrate user Profiles from 2003 Terminal Server 32bit to 2008 Terminal Server 64bit||Zweena||Operating Systems||5||22-08-2010 02:39 AM|
|Novell Netware 5.x Migration to Windows 2003 Server||Allanoo||Networking & Security||3||16-07-2009 12:07 PM|
|64 bit printer drivers on 32bit Windows Server 2003||MarcusB||Windows Server Help||1||12-03-2009 10:36 PM|