Dear experts, I tried 2 times already to do the following by myself with no luck each time I mess up at a point unknowingly and it fails. My case is below and I do hope someone would assist me through it. I currently have a 2003 server 32 bit running AD/DNS/DHCP/IIS. which has no tape backup no RAID setups what so ever (not professional at all) I got a NEW server much much more powerful than the old one. and I installed on it windows server 2003 64bit edition since the new server has 16 GB of ram. (which is more professional has tape backup and RAID setup controlled via bios does not show on the windows manage disk management though that there is a mirror I think it's because it's controlled by the bios.) What I want to do is surely clear to you all by now I need to move AD/DNS/DHCP/IIS from server1 to server2 and after doing so remove server1 and completely replace it with server2 in other words I want the new machine to have the same name as old machine and same local IP address. I tried to do that several times and I manage I think half way through where the users are all in the new server but whenever I unplug the old server the new server goes offline. Now i've got all the information I did earlier from a friend so I do not recall much of them Would really really appreciate assistance!AJ

In regards to the RAID question, if you are using Hardware RAID, it will not show up as multiple drives in device manager. Now regarding the question on integrating/retiring the old server. Follow these high level steps. -Bring the new server online with a temporary name and IP -Set up all of the services (DNS, DHCP, etc...) -Point its DNS client settings to the other DC/DNS -Join it to the existing domain -Run DCPROMO to promote it to a DC -Begin migrating all of the data (DNS, DHCP, data, etc...) -Move all of the FSMO roles -Enable it as a Global Catalog server -Configure its DNS settings to point to itself -DCPROMO the old server down to a member server -REtire the old server -Make sure all of your clients' settings are pointing to the new server. Plan to add a second DC to ensure that your domain is protected by a single point of failure. Visit: anITKB.com, an IT Knowledge Base.

after all above steps shall i rename the new server to the exact name of old server? also use it's IP address? If possible can you give me a KB article for each step? many thanks for your quick and prompt replyAJ

AJ, Why not leave the old server as a secondary DC? Might come in handy one day ;-) Miguel Miguel Fra / Falcon ITS Computer & Network Support , Miami, FL Visit our Knowledgebase Sharepoint Site

after all above steps shall i rename the new server to the exact name of old server? also use it's IP address? AJ, that depends. If you have port forwarding set up on your router or network shares that point to the server's NetBios Name /IP Address. You can either change the server's Name/IP or you can reprogram your devices i.e. port forwarding, shares, etc. depending on what's less time consuming for you. Remember that if you change your server's name/IP you will have to take into consideration DNS, SQL, Bindings, etc. MiguelMiguel Fra / Falcon ITS Computer & Network Support, Miami, FL Visit our Knowledgebase Sharepoint Site

· Install new windows 2003 server and join it to Domain. · Perform DCPROMO and select “additional DC for an existing Domain option”. http://technet.microsoft.com/en-us/library/cc753720(WS.10).aspx · Make new DC and a GC. http://technet.microsoft.com/en-us/library/cc781329(WS.10).aspx · Transfer FMSO role to new DC. http://support.microsoft.com/kb/324801 · Update DHCP scope with new DC/DNS server info You can’t rename the domain controller. If you want to remove the DC, you need to perform a DCPROMO on the old DC. Also, it is a best practice to have at least 2 DC. Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX http://blogs.sivarajan.com/ http://publications.sivarajan.com/ This posting is provided "AS IS" with no warranties, and confers no rights.

Replied to your previous thread: http://social.technet.microsoft.com/Forums/en-US/winserverMigration/thread/c92c19f6-6b09-4e0c-80ae-441905221025 Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX http://blogs.sivarajan.com/ http://publications.sivarajan.com/ This posting is provided "AS IS" with no warranties, and confers no rights.

· Install new windows 2003 server and join it to Domain. · Perform DCPROMO and select “additional DC for an existing Domain option”. http://technet.microsoft.com/en-us/library/cc753720(WS.10).aspx · Make new DC and a GC. http://technet.microsoft.com/en-us/library/cc781329(WS.10).aspx · Transfer FMSO role to new DC. http://support.microsoft.com/kb/324801 · Update DHCP scope with new DC/DNS server info You can’t rename the domain controller. If you want to remove the DC, you need to perform a DCPROMO on the old DC. Also, it is a best practice to have at least 2 DC. Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX http://blogs.sivarajan.com/ http://publications.sivarajan.com/ This posting is provided "AS IS" with no warranties, and confers no rights. Since you don’t have any backup, you can’t restore everything onto a new DC. In that case, you need to use different DC name and IP address. But you don’t have to change anything on the client side. Why do you need to keep the same name and IP address? Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX http://blogs.sivarajan.com/ http://publications.sivarajan.com/ This posting is provided "AS IS" with no warranties, and confers no rights. Hi, Okay I've done all steps above and made sure everything was migrated. I also changed the IP address of DC2(new) to become like DC1(old) but still when I disconnect DC1 and try to log in to DC2 to access active directory it does not allow me. It gives error message that it can't find active directory. While on the other hand when I plug back the DC1 to the network DC2 functions normally! I made sure all steps you gave me were performed by the letter with no errors what so ever. I even migrated DNS and DHCP. I've also renamed DC1 to "OLDSERVER" but when I try to rename DC2 to "SERVER" it does not allow me and gives me error "The following error occurred attempting to rename the computer to"SERVER": The specified domain does not exist or could not be contacted." AJ

That would be my recommendation, also..... Move the FSMOs to the new server, but leave it a GC and with DNS installed. You might also consider splitting the DHCP scopes so that you are completely operational even if the new server goes off line... Regards, Hank Arnold Microsoft MVP Windows Server - Directory Services http://it.toolbox.com/blogs/personal-pc-assistant/ On 6/12/2010 7:04 PM, Falcon ITS wrote: > AJ, > > > Why not leave the old server as a secondary DC? Might come in handy one > day ;-) > > Miguel > > ------------------------------------------------------------------------ > > Miguel Fra / Falcon ITS <http://www.falconits.com/> > Computer & Network Support <http://www.miami-network-support.com> , > Miami, FL > Visit our Knowledgebase <http://www.falconits.net> Sharepoint Site > Regards, Hank Arnold (MVP - DS)

You can’t rename the domain controller. If you want to remove the DC, you need to perform a DCPROMO on the old DC. Also, it is a best practice to have at least 2 DC. Hello, I don't know what's behind the scenes here but in many cases I agree that it's better to NOT rename the DC but it can be done. http://www.petri.co.il/windows_2003_domain_controller_rename.htm Miguel Fra / Falcon ITS Computer & Network Support, Miami, FL Visit our Knowledgebase Sharepoint Site