replacing Win2k3 domain controller

0 pts.
Tags:
Desktops
Management
Microsoft Windows
OS
Security
Servers
SQL Server
Tech support
I want to replace / upgrade a 2k3 DC. Is there any advise for this process? i know which services and roles the current server provides and figured I need to move those serives from the server to be replaced and then move them back to the new server once it's installed and dc promo'd. Any words of wisdom or observations?
ASKED: August 19, 2005  12:20 PM
UPDATED: August 21, 2005  12:27 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.

Hello,
Myself Shiraz working at Oracle Corp India as a Desktop Support. I m much interested to Troubleshoot n help friend.
U know, your is too good, where i see. Here are some few tips n sites u can get it out.der.
Also i Have worked alot day n night.

just Check it out first.

http://www.microsoft.com/windowsserver2003/downloads/tools/default.mspx

http://www.eggheadcafe.com/ng/microsoft.public.windows.server.migration conversations

You Install Fresh Win2k3 and migrate ADC From old win2k3 server to new win2k3 server

The Active Directory Migration Tool (ADMT) version 2.0 provides an easy, secure, and fast way to either upgrade from Windows NT Server 4.0 to Windows Server Active Directory service or restructure Windows Server Active Directory domains between forests or within a forest. The tool migrates users, groups, and computers between domains in a way that allows users to have access to their resources and applications at all times. Version 2.0 includes new features, such as password migration, a scripting interface, and a command line interface, that make migrations easier.

Here are few Specifications:

ADMT can run on any computer capable of running the Windows 2000 Server operating system or the Windows Server 2003 operating system.
Target domain: The target domain must be running either Windows 2000 Server or Windows Server 2003.
Source domain: The source domain must be running Windows 2000 Server, Windows Server 2003, or Windows NT Server 4.0.
The primary domain controller (PDC) of a Windows NT Server 4.0 source domain must have SP4 or higher installed.
The ADMT agent (installed by ADMT on the source computers) can operate on computers running Windows NT Server 4.0 (with SP4 or higher); Windows 2000 Server, Windows XP, and Windows Server 2003.

Basically you set up a server that is identical to yours, except of course set up the way you need it.. Even though i believe SBS cannot trust another domain.. you basically just need to export out of one the user & comp info and import it into the new..Also if you setup a new server/domain you will have to rejoin all the client machines to the new domain.
Server 2003 has various migration tools

http://www.microsoft.com/windowsserver2003/downloads/tools/default.mspx

http://www.microsoft.com/downloads/details.aspx?FamilyID=788975b1-5849-4707-9817-8c9773c25c6c&DisplayLang=en

http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/windowsserv/2003/all/deployguide/en-us/dssbi_reer_overview.asp

Solution Title: Migrating Windows Server 2003 to different hardware
asked by jmelika on 03/18/2005 01:34PM PST

Hello,

DONT DO IT

ur going to cause your self undue stress doing it this way,

build the new server up, and use a network to copy the data over, and bach files to copy share infomation etc….

if you ghost a server, windows is NOT clever enought to detect the hardware, it may work for the first month or so then after that youwill problery get errors, the server will disapear of the network etc….

do it proplery dont take short cuts with something like a server, ghost is designed to be used for images, back to the same machine, or a mahicne with the same hardware, exactly the same hardware.

Forget Ghost for this one.
i did the exact same thing, and here is the process.
1. i built 2003 server on an AMD 3gh with 1gig ram and installed Exchange, virusshield, office, and other apps.
2. tested server using terminal services, once happy with operation.
3. had to move entire operation to a Dell quad zeon, 4gig ram, raid 1 for OS and raid 5 for data, blah blah blah. You get the idea.
solution
create system restore backup using the 2003 built in backup utility. Finally MS have released a half decent backup solution. this will allow backup to a hard drive, i used a large ide HDD and created a bootable restore floppy.
you then need to alter the ini file on the boot floppy as your backup drive may have a different location on your new server, and install the backup hdd (that big ide one) into the new server.
then it was a simple restore as the floppy guides you.
at the end you will have to re-register your 2003 with MS as there will be too many hardware changes. a simple phone call to licencing will resolve this once you explain what you have done, so they dont think you are pirating it.

this works a treat
Cheers Andy
MCSE

Luckily you have windows 2003. With 2003 Microsoft lets you backup the entire system state to tape and likewise restore it. This is probably the easiest way to restore to new hardware. Follow this :http://www.petri.co.il/install_dc_from_media_in_windows_server_2003.htm

Trying to do it with 2000 is even more difficult microsoft states you basically have a 50/50 chance of it working, beacuse of HAL limitations. I’ve tried restoring windows 2000 server to a different server and had to “repair” the installation. It would have been faster just to do a clean install.

I think ghosting would be a waste of time. I tried doing something similar with Windows 2000 Server and it bluescreened when I booted up the new hardware. Wasted 6 hours running ghost to see if it would work.

Don’t Don’t Don’t. You are never going to get the image to work properly going to such a different piece of hardware. Your hardware is of such different animals that your drivers will choke. If it WERE same hardware, you could do it, but to be safest, you should run sysprep first.

The best thing you can do is to build up the new server the way you want it. Install the applications on the new server that are on the old server and then restore the Data from the old server. This is your best bet for making the migration and for everything to work correctly.

I used the Windows 2003 ntbackup utility. Man! Did they actually fix this thing up or what?! I remember in the Windows 2000 enviornment, they said the same thing. Use the ntbackup utility and backup/restore system state. That should work. It never did for Win2k. I tried it at least 5 times before I gave up on it. That’s the reason I didn’t want to try it with this Win2K3 upgrade. But it actually works. Not one service failed. Everything went over smoothly. The only thing I had to do manually was the IP addressing (static IP’s on servers of course). Other than that, NOTHING!

I guess I should have tried the ntbackup utility before. I’m all set now!

Discuss This Question:  

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following