[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 255
  • Last Modified:

Exchange 2000 to 2003 Upgrade Questions

Current environment:
Win2k3 AD running in 2000 Native mode, 1 (one) Exchange 2000 Server running in Exchange 2000 Native mode
I am ready to upgrade to Exchange 2003 using new hardware .....the new box is running Win2k3 R2 and I've performed all pre-requisites (I think)...eg., InetOrgPerson fix when I upgraded to 2003 AD, made the recommended memory adjustments for Exchange 2003 on the server, run dcdiag and netdiag and analyzed the results, etc..
I plan to use the latest version of ExDeploy for the install....installing the new server by choosing to "Upgrade from Exchange 2000 Native Mode"....if all goes well, I will then have two Exchange servers in the Org, one 2000 and the new 2003. I then plan to move the mailboxes, public folders, etc..to the new server.
We are running OWA as well.

Questions:
1.) Can I move the mailboxes and public folders a few at a time , or is this an all or nothing process? If they are moved a few at a time over the course a couple of weeks, will internet mail find its way to the correct mailboxes on the new server....will mail flow be interrupted in any way ?
2.) I understand that an SMTP connector is not needed In pure Exchange 200x environments.....but through ESM in the current Exchange setup in the "Connectors" group I see a "Company" Internet Mail connector ?

Bottom line......when the installation is completed and the mailboxes, public folders, etc., are moved, what are the critical points that I need to be aware of to ensure that mail will flow as it did before ?
This is my first stab at this kind of upgrade and any input would be greatly appreciated !

0
ccherman3
Asked:
ccherman3
3 Solutions
 
ganongjCommented:
Hi ccherman3,

Answers:

1 - yes - you can move them one-by-one - mailflow will be fine.  I have done this several times through several versions and it will be fine.
2 - you will not need that connector in the new setup.  Maintain it until you are fully converted/moved over, then remove it.

In your case, there won't be any "gotchas", it should be staightforward - make sure you point your mx (dns) record to the new exchange server after you're all migrated.  If you are running a firewall that directs smtp traffic, make the appropriate change there, too.

good luck, let us know if you run into anything else.

Jim
0
 
questionforrajaCommented:
Hi

With Exchange 2003 the move mailbox wizard has become multithreaded so you can move atleast four mailboxes, And you can also schedule this move and the conditions on what happens when a error is encountered. Please check the below article.

http://support.microsoft.com/?id=822892.


As far as moving the public folder content is concerned create replica's in the Ex2003 server and check the following tool

http://support.microsoft.com/?id=822892, Make sure that you also rehome the system folders before decommision the Ex2000 server.
0
 
folksamericaCommented:
I just completed this very upgrade. However I went from a single 2000 to three 2003 servers. But that's the only differentiator between our projects.

If you've gone ahead and patched up the box to current, ran the MBSA utility, and taken a look at the "decomissioning the first exchange 2000 server in your organization" (KB 307917) document.

For question #1 I'll answer in two parts.

Public folders you will have to Replicate. Meaning they will be running on both servers. After replication is complete (which can take days if you've got a big enough public folder store) you will be able to stop replication to the SOURCE server. Which again, is outlined in the 307917 knowledge base article.

As for moving the mailboxes, if you have SMTP enabled on both boxes you will be able to send mail throughout the whole migration. If you have successfully brought up both servers and you can see both of them in your management tools then you will be able to receive throughout the whole migration. Note: un-install the MANAGEMENT tools from the 2000 server and install the 2003 management tools on the 2000 server. Avoid making any adjustments to the 2000 server using 2000 tools once you have both servers up in parallel. As was noted earlier you will have to change your DNS, either to point the MX record to the new server, or to take the old servers IP after the migration is complete. The IP switch will take no time to change over the internet, MX record change will take 12-24 hours.

Some things to consider.

For OWA, you may want to enable forms-based authentication and re-do the logon.asp so you don't have to type in domain\username to login, just username. You should also look into acquiring an SSL certificate for secure access to OWA (otherwise it's all broadcast in clear-text).

Modify the heapdecommitfreeblockthreshold registry key on the new server and then add /3GB /USERVA=3030 to the boot.ini

Obviously you're going to want to implement some type of anti-virus. Best practice is to install file-level and e-mail level scanning. When configuring file level be sure to EXCLUDE the mdbdata folder and any functional folders of the e-mail level anti-virus. Reason for doing the dual protection is the e-mail level scanning is useless if the box itself gets infected.

RUN Exchange Best Practices Analyzer after you're finished installing/migrating/a few times along the way. Just search google for ExBPA.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
ccherman3Author Commented:
thanks for the quick replies......just to clarify....

After a mailbox is moved to the new server, for example "User1" mailbox, "User1"s Outlook client will automatically resolve to the new server ?
And inbound (internet) mail will automatically be routed to the "User1" mailbox on the new server as well ? Outbound (internet) mail should also work automatically ?

Our firewall is currently pointing to the old server ip address  for port 25 traffic, so after I decommission the old server, I will point to the new server ip address.
As far as the ISP MX record is concerned, I should not have to make any changes there, correct ?
the MX record "mail.company.com" is referring back to an A record for "company.com" public ip address.....so, again, I shouldnt need to make any changes here ??

thanks again for all of your valuable help....

ccherman3
0
 
folksamericaCommented:
If you are using Exchange connectivity for your clients Outlook will lookup on AD for which server to receive mail from. As for your internal you will need to setup the SMTP connector between the two servers so your first server will relay to the second.

Most importantly.

Create a test account on your old server, send and receive some mail on that account. Then migrate the account over and continue the testing. If you have a problem after all of this is said and done then you have a more specific question to ask :)
0
 
ccherman3Author Commented:
FOLKSAMERICA,

thanks again for your input.....i'm sorting and processing the info as I go....

you stated in your first reply that -  "As for moving the mailboxes, if you have SMTP enabled on both boxes you will be able to send mail throughout the whole migration. If you have successfully brought up both servers and you can see both of them in your management tools then you will be able to receive throughout the whole migration."
Your second reply stated - "If you are using Exchange connectivity for your clients Outlook will lookup on AD for which server to receive mail from. As for your internal you will need to setup the SMTP connector between the two servers so your first server will relay to the second."

SMTP service is running on both servers at this time....I'm still not clear on why I would need to setup the SMTP connector ?
In other words, after the new server is installed into the org and I can see both of them within ESM, and I then start to move mailboxes to the new server, will both INTERNET mail and INTERNAL mail sent to those moved mailboxes make it to those mailboxes without the SMTP connector ?
GANONGI also indicated that mailflow should be ok....
I apologize for being a pain in the butt about this, but I'm scheduled to do this tomorrow evening and I want to be sure I have a clear understanding.

Again, thanks for the input and your patience.....
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now