Current Environment one front end and two backend Exchange 2003 servers. https url running on front end for both owa and RPC over HTTP.
Transitioning to Exchange 2007SP1 with HT&CAS –NLB and CCR cluster for mailboxes.
When is the best time to move owa and rpc over http url from Exchange 2003 front end to Exchange 2007 CAS without affecting users on Exchange 2003? Are there any known issues?
Main concerned is with RPC over HTTP users, few hundred users outlook running with RPC over HTTP settings.
Posts: 897
Joined: 4.Jan.2007
From: Chicago, IL
Status: offline
You should be able to do this anytime. You must ensure that the CAS role is not on a server that also has the Mailbox role as this will break CAS to Exchange 2003 BE proxying.
You can access both /owa and /exchange via a CAS which makes it viaable for accessing both Exchange 2003 and Exchange 2007 Mailboxes. Do the following to test:
Test Client #1: 1. Create Test1 Mailbox on Exchange 2003 BE1 2. Test RPC/HTTP and OWA 3. Create Hosts file for your mail.domain.com to go to your CAS IP 4. Ipconfig /flushdns 5. Might have to do a dnscmd /clearcache as well to clear the server cache 6. Test RPC/HTTP and OWA to ensure CAS to Exchange 2003 BE proxying works. 7. Migrate Mailbox over to Exchange 2007 8. Test Outlook Anywhere and OWA to ensure CAS to Exchange 2007 Mailbox is working as intended
Test Client #2 Do the same thing as Test Client #1 but do this on your other Exchange 2003 BE to ensure both BE's work with the CAS to Exchange 2003 BE proxying for both servers as well as migration of users.
If all goes well, it should be safe to change the production host record to point to the CAS as a CAS can do proxying to an Exchange 2003 BE servers as long as the CAS role is not on a box with the Mailbox Role.
So just to re-iterate, if you want CAS to Exchange 2003 BE proxying to work, put the CAS on a server that does not contain the Mailbox Server role.
Our mailboxes will be on CCR, CAS and HT will be on NLB.
I am going to try this in 2weeks. First will install CAS and HT- NLB and then test OWA and RPC Over HTTP on BE Exchange2003 Mailboxes. Then install CCR cluster and move mailboxes.
Posts: 897
Joined: 4.Jan.2007
From: Chicago, IL
Status: offline
Oh and btw, I just realized you won't have to do a dnscmd /clearcache since you'll be using hosts which is used before a dns server.
Also, do you have more than 1 public folder database in your organization? If so, you'll need to do the following before introducing CCR:
You'll need to bring up a non-CCR mailbox server to migrate public folder contents to it. You can bring up CCR any time after you introduce the mailbox server for public folders. The reason for this, is you can't create public folder database on a CCR when there's any type of replication occuring in the environment.
So what'd you do is: Bring up mailbox server, create a public folder database. Bring up CCR Migrate public folder content to mailbox server Migrate mailboxes (this can happen at the same time public folder information is being migrated)
Once you end up de-comissioning Exchange 2000/2003, you'll be left with 1 public folder database. You can then create the PF database on CCR, migrate to it, then de-comission your Exchange 2007 mailbox server and leave yourself with the CCR.
we have two backend and one front exchange 2003 servers running. both backends host public folder data.
planing to install exchange2007 SP1CCR in same exchange org and move mailboxes and Public folders.
if i understood you correctly you are saying install single exchange 2007 mailbox server and move public folders and then move on to CCR cluster, could you be specific on the problems we are going to face if i replicate public folders from Exchange 2003 to 2007 CCR cluster.