exch 5.5 to exch 2003 migration

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?
dazzler1971Asked:
Who is Participating?
 
BNettles73Connect With a Mentor Commented:
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
 
ColinRoydsCommented:
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
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.

 
BNettles73Commented:

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
 
dazzler1971Author Commented:
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
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.

All Courses

From novice to tech pro — start learning today.