Go Premium for a chance to win a PS4. Enter to Win

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

Moving Exchange 2010 to Exchange 2010

Hello All,

My company is planning an internal move. We have a single current Exchange 2010 server running on Server 2008 R2. It holds all of the Exchange roles. We have purchased new server hardware and want to move Exchagne to that server. Our plan is to setup the server and mimic all the same settings as the old server. Then, we will migrate the mailboxes, replicate PF, etc.

Now, here is my question. I have read on many different wed postings that some users are doing that very thing, but their OUtlook clients are not updating the account information to the new CAS server. My question is this. Assuming I don't want to do a complete uninstall of the CAS role after the mailbox migration, will just taking the old server offline force Outlook to find the new CAS server, and will that switch be made on the fly? Do I have to uninstall CAS on the old server first?

We have a couple of weeks on this, but I want to get it tested before the move. Thanks.
0
itsupportva
Asked:
itsupportva
  • 4
  • 4
2 Solutions
 
e_aravindCommented:
My view on your setup is
MBX server, CAS servers ...both are OLD, moving to the new MBX and CAS server correct?

>> uninstall of the CAS role after the mailbox migration, will just taking the old server offline force Outlook to find the new CAS server

Here in E2010, on the databases we have an additional property RPCClientAccessserver parameter to point\assign the correct\new CAS server

http://technet.microsoft.com/en-us/library/bb123971.aspx 

No need to shutdown the CAS server for testing pupose.
>> if you keep the CAS server in shutdown state...this would give us some issues in Autodiscover process.


0
 
itsupportvaAuthor Commented:
Thanks for the reply, but I am not sure I fully understand. Yesterday I setup a testing environment to work this. I had a 2008 server, with Exchange, and all CAS roles. I setup 5 mailboxes and tested. I then setup another 2008 server with Exchange 2010 with all of the roles as well. I moved all of the mailboxes to the new server using a straight mailbox move. That went well. When I pulled up Outlook using one of those user accounts, I get prompted for a username and password. Any my account information still shows the old mail server. Now, I have not removed CAS on the old server. I checked any my rpcclientaccessserver shows the new server for the new mail store. Why aren't my Outlook clients automatically switching? Thanks.
0
 
e_aravindCommented:
I checked any my rpcclientaccessserver shows the new server for the new mail store. Why aren't my Outlook clients automatically switching?
>> Are you testing the above setup with "Outlook 2007 SP2"

0
Industry Leaders: 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!

 
e_aravindCommented:
outlook prompts would be because of the Autodiscover
Need to check the responses of the "Test email Autoconfiguration" window\dialog-box with the mailbox on server1 and server2
0
 
itsupportvaAuthor Commented:
I am testing with Outlook 2010. Now, that DOES show the new server as the mailbox server. However, when I shut down the Exchange RPC Client Access Service and MS Exchange Information Store on the OLD server, all of my clients cannot connect. Outlook 2010, 2007, and 2003. I don't understand why, when I have moved all mailboxes to the new server, my clients care if I shut down the old services. Will that resolve if I remove the CAS role from the server? ALso, as an FYI, I attempted to set the RPCCLIENTACCESSERVER for the old MB DB to use the new CAS server, none of my clients could connect. So, I don't know where to start. I don't want to remove CAS on the new server, I feel it will just kill everything.

Also, with both servers on, all clients can connnect, but each one gets prompted for a username and password. Never happened until we moved to the other server.

Thanks in advance for your assistance!
0
 
e_aravindCommented:
First Question:
Even if the rpcclientaccesserver is pointed to the second server on the new or old databases...still there are some roles for the first installed CAS server on the setup

Note: Check "Test email autoconfiguration" Log tab..you would find the first CAS servers FQDN name over there for the SCP object

>> No need to shutdown the CAS server for testing pupose.
if you keep the CAS server in shutdown state...this would give us some issues in Autodiscover process.

Second question:
each one gets prompted for a username and password
> Once or twice?
-- During that time what is the result of the Test email autoconfiguration" Log tab..? is that waiting for the auth. dialog box?
-- What is the server value the auth. dialog box shares only old or new server's FQDN?

0
 
itsupportvaAuthor Commented:
Problem resolved over the weekend. What I did was add a 3rd server, create a CAS Array, point the DB to that array, and removed the first server. Then I was able to remove the third server.

So, ultimately, the best method would be to establish a CAS Array FIRST, even if you have only one server. I did have to change the Outlook client to point to the new CAS array, but after that, it worked fine.
0
 
itsupportvaAuthor Commented:
Accepted my own solution since it was part of the soluton that fixed the problem
0

Featured Post

Technology Partners: 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!

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