Solved

exch 5.5 to exch 2003 migration

Posted on 2004-09-06
6
411 Views
Last Modified: 2008-04-29
I am performing an upgrade of exch 5.5 to exch 2003 and have upgraded some servers to win2003 OS in the same domain.  I now plan to install the AD connector on this win2003 server (to be new exch 2003) and install the first exch2003 server into existing 5.5 site.   Can you tell me what is the best practices for installing this first exch server.  ie should it be a DC.  should i have different mirror sets for system and transaction logs / exch databases etc? Once migration has completed to exch 2003 am i ok to rename the exch 2003 server to the same host name as old exch 5.5 server (once it is decommisioned and off the network) to save reconfiguring all the client outlook profiles?
0
Comment
Question by:dazzler1971
  • 3
  • 2
6 Comments
 
LVL 12

Expert Comment

by:ColinRoyds
Comment Utility
Few guidelines
1. Do not run Exchange on a DC if possible
2. RAID 1 for OS, RAID 5 for Databases + 1 Hot Spare, if you have the space and the budget perhaps RAID 1 logs
3. i would probably not rename the server but leave it as is, I have found after doing all migrations that when the mailbox is moved to the new server andbefore the old one is shut down and removed, the Outlook clients will most f the time detect the new server where the mailbox is, so no need to go run around each client to reconfigure it.

And here is a link that might help http://support.microsoft.com/default.aspx?kbid=822450&product=exch2003, but I would also read the white papers first
0
 
LVL 12

Expert Comment

by:ColinRoyds
Comment Utility
0
 
LVL 12

Expert Comment

by:ColinRoyds
Comment Utility
0
Are your corporate email signatures appalling?

Is it scary how unprofessional your email signatures look? Do users create their own terrible designs and give themselves stupid job titles? You can make this a lot easier for yourself by choosing an email signature management solution from Exclaimer today.

 
LVL 12

Expert Comment

by:BNettles73
Comment Utility

1. I agree with Colin ... if resources permit, do not run Exchange on the DC
2. RAID 1 is sufficient for TLogs and System ... I'd go with a mirrored stripe set (0 + 1) if you have the money, RAID 5 to a bare minimum ...
3. Don't rename the server ... if you are wanting to maintain the same name, you may consider using the Swing Method for your migration .. you should be able to google it for more info ...

If you migrate users in the same site - as long as the E5.5 box stays up, the clients will migrate ... if the mailbox is moving from a different site (Exchange 2k3 SP1) then you can use EXPROF.EXE, run it in the logon scripts to properly migrate the client settings.

That is pretty much it ... just more or less confirming what Colin already said ...
0
 

Author Comment

by:dazzler1971
Comment Utility
OK, thanks guys.  re the renaming of the server, im a little confused as to how the clients are going to automatically know the host name of the new exch 2003 server.  My plan is to decommision the exch 5.5 server and not leave it up and running so surely the outlook profiles will then be pointing to the old server name and email services will cease.  With 1800 clients im hoping to not visit each one individually.  Is there a known problem with renaming exchange 2003 servers??
0
 
LVL 12

Accepted Solution

by:
BNettles73 earned 125 total points
Comment Utility
Because the directories are synched, as long as the exchange 5.5 server is up and running, the outlook will see that the mailbox has been moved and will automatically connect to the new E2K3 server. You only have to leave the 5.5. box up until all of your clients have logged on to the new server. I've used this process for 8 or 9k clients and is the best way ... if you shut the 5.5 box down right after the migration then be prepared to slam the help desk!
0

Featured Post

Find Ransomware Secrets With All-Source Analysis

Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

Join & Write a Comment

Resolve DNS query failed errors for Exchange
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…

743 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

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now