Expiring Today—Celebrate National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17


Exchange 2000 server crappy....new exchange 2003 server ready to go...how do i move everything properly?

Posted on 2004-04-01
Medium Priority
Last Modified: 2010-03-05
I have an existing Exchange 2000 server on Win2k
I have built a new Win2k box with exchange 2003 up and running.
The end result is to replace the old with the new.
I would like someone to confirm that i will be doing all the required steps to successfully make the switch over

1 - Replicate Public folders
2 - Replicate subfolders
3 - Run move mailbox wizard
4 - Remove replications
5 - Remove exchange 2000 from old server
6 - Remove AD from old server
7 - Remove old server from domain
8 - Change new servers ip and add appropriate "A" record to dns to point new server name to the original servers name

Im sure its not that simple so maybe you could help be with adding the steps i missed...i have search Microsnots site but only get results for large environment scenarios.
This is a single mail server environment....no front end and backend mail servers to worry about.
Question by:MIKEV
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
LVL 24

Expert Comment

by:David Wilhoit
ID: 10735029
are the 2 exchange servers part of the same org, or is this a new org? Give me a couple more details on your setup here... it looks like you're on the right track..


Author Comment

ID: 10735123
Both machines reside on the same Domain and the same ORG...

System Manger can see both servers no problem...
The old machine is still functioning properly (thank god) but may die anytime....im down to the last drive in the raid array...one more dies and were toast (outside of tape backup of course)
LVL 24

Accepted Solution

David Wilhoit earned 1000 total points
ID: 10735164
Ok, just making sure that you can see both servers in the EXchange system manager. Now, make sure that you recalc the routing by making the new server the RG master, but changing the IP address on the box would seem unnecessary. Is this box a DC/GC/DNS?

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!


Author Comment

ID: 10735216
I have to change the ip as i use Managed ip's in the firewall. public to private mapping

The new box is a DC as is the old one...GC and DNS are on other machines.
LVL 24

Expert Comment

by:David Wilhoit
ID: 10735269
ok, so just ensure the proper DNS settings, and make sure the recipient policies are pointing at the new Exchange server, or those will stop working. If you feel like it, you can manually point the new Exchange server's DSAccess settings manually, so that the other DC won't affect the Exchange services when you are ready to demote it. there's lots of little things, but you've definitely done your homework :)

Author Comment

ID: 10735389
ok....how do make sure that the recipient policies are pointing at the new Exchange server...if i do this am i not creating a front end server for the policies alone ?
LVL 24

Expert Comment

by:David Wilhoit
ID: 10735531
well no, not at all. If you open an RP, you'll see that it points to an Excahnge server, and a GC. If it's pointing to the E2K server when you remove E2K, it doesn't automatically flip over to the other Exchange server. You have to repoint it.


Expert Comment

ID: 11197916
I am curious as to the end results of this adventure.
I am in the same boat with two exceptions.
1) E2K Server is PDC, DNS, DHCP.
2) I am not only upgrading to Exchange 2003 but also OS will be 2003 Server.

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
If you troubleshoot Outlook for clients, you may want to know a bit more about the OST file before doing your next job. IMAP can cause a lot of drama if removed in the accounts without backing up.
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…

719 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