Improve company productivity with a Business Account.Sign Up

x
?
Solved

Migrating to Windows 2003 server from 2000

Posted on 2006-06-12
4
Medium Priority
?
327 Views
Last Modified: 2011-08-18
I have a Dell Poweredge 2600 that runs Exchange 2003 server and I am going to by a new Poweredge server with Windows 2003 server.  What I want to do is just replace the machine I have with the new one and keep the same computer name an so forth.  My current server is the DC however.  Does anyone have any suggestions to the steps I would take to accomplish this correctly?  I would need to migrate the users  in active directory as well.  If oits easier to change computer names I can do that as well.  Please advise.
0
Comment
Question by:Matt Pessolano
  • 3
4 Comments
 
LVL 97

Expert Comment

by:Lee W, MVP
ID: 16885772
MUCH easier to change computer names.  Also, BEST to have Exchange NOT be installed on a Domain Controller.  Is this a Small Business Server (SBS 2000) system?  IF so, the procedures will be different.

If I were you, I keep BOTH servers running.  Install the new server, install Exchange on it, migrate exchange off the old server and leave the old server as your DC/File Server.
0
 
LVL 1

Author Comment

by:Matt Pessolano
ID: 16885812
not a bad idea.  the reason Im getting rid of the old server is because it keeps freezing and i have to reboot to get it up.  I might not have a choice except to put exchange on it.  But i can maybe make another server the DC.  This is not SBS.  MY DC is not a FS either.  My main concern is active directory.  How do I get the users to transfer
0
 
LVL 97

Expert Comment

by:Lee W, MVP
ID: 16885935
Transferring the users is easy.  Do you have any spare computers?  Even something old - like a Pentium 2 with 256 MB of RAM?  What you want to do is reinstall the existing server (again Exchange is NOT RECOMMENDED to run on a Domain Controller - it can, but when something is not recommended, I tend to follow the recommendations).

So, to that end, install 2000 server (and appropriate service packs) on a temporary machine.  Once installed, run DCPROMO - this will make the temporary machine a Domain controller.  Then setup the new machine with Exchange Server and move the mailboxes and other exchange services off the old system and onto the new system.  Once everything is working on the new system (PLEASE TEST - including STOPPING Exchange services for a day or two (preferrably a week) on the old system to make sure the new system is working appropriately) UNINSTALL Exchange from the existing server.  Once Exchange is uninstalled, on the temporary server, transfer the FSMO masters and make it a global catalog.  Transfer any services you may have on the old DC to the temp DC - such as DHCP and DNS.  Turn off the problem server for a few days (to make sure everything is working).  Once it's been working for a few days without the problem server on, run DCPROMO on it, demoting it.  Once demoted, FORMAT THE SUCKER!  Reinstall Windows on it and make it a domain controller again.  (If you are concerned the crashes are hardware related, do NOT make it a domain controller for a while - reinstall it and make sure its running as a server (even if it serves nothing) for a while).  Once made a DC, transfer the FSMO roles, GC, and other services back to it from the temp DC.  Again, TEST THINGS at each major step and don't "destroy" (format/erase) anything until your certain things are working.


BEFORE DOING ANYTHING, MAKE SURE YOU HAVE A GOOD BACKUP!  System State, Exchange Info Store, etc.  AND MAKE SURE YOU CHECK EVENT LOGS - The event logs will tell you if you have problems even when things SEEM to be working well.

Some reference Links:
http://www.amset.info/exchange/migration.asp
http://support.microsoft.com/kb/822931/

0
 
LVL 97

Accepted Solution

by:
Lee W, MVP earned 2000 total points
ID: 16885997
By the way, When you make another machine a domain controller, it replicates the user and computer account information - that's how the information "transfers" - making a machine a DC is done using DCPROMO as I mentioned using.

A couple more links on doing some of the things I spoke of:
http://www.petri.co.il/transferring_fsmo_roles.htm
http://www.petri.co.il/configure_a_new_global_catalog.htm
http://support.microsoft.com/kb/234790
http://support.microsoft.com/?kbid=313994
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

I guess it is not common knowledge to most Wintel engineers/administrators: If you have an SNMP-based monitoring system in your environment (and it's common to have SNMP or Syslog) it's reasonably easy to enable monitoring of the Windows Event logs,…
Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
If you are looking for an automated solution for backup single or multiple Office 365 user mailboxes to Outlook data file, then you can use Kernel Office 365 Backup & Restore tool. Go through the video to check out the steps to backup single or mult…
Through the video, you can check the migration process of Outlook PST file to PDF. Kernel for Outlook to PDF tool can convert Outlook emails with all attributes like Subject, To, From, Cc, Bcc and other folders such as Inbox, Outbox, Sent Items, Jun…

608 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question