Learn how to a build a cloud-first strategyRegister Now

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

Exchange 2010 - two servers, but clients connect to wrong one?? (CAS ?)

Hi,
We had one exchange server that we needed to retire (called Exchange1.domain.local )(running exchange 2010), so we built a second exchange server (Exchange2.domain.local), and moved all the mailboxes to it.

All Outlook clients are working just fine, but they're showing connected to "Exchange1.domain.local" in Outlook, even though their mailboxes are on the other server.

How do I get them to point to the new Exchange server so I can decomission the old one?
0
Mystical_Ice
Asked:
Mystical_Ice
  • 2
  • 2
1 Solution
 
ctc1900Commented:
You most likely need to update the RPCClientAccessServer for the new Exchange server mailbox databases

http://www.shudnow.net/2010/04/18/creating-databases-and-the-rpcclientaccessserver-database-parameter/
0
 
Mystical_IceAuthor Commented:
That apparently can't be done after the exchange client mailboxes have been moved to the new server?
0
 
ctc1900Commented:
The RPCClientAccessServer is a setting at the mailbox database level, you should be able to update if necessary.  Why do you think it can't be done?
0
 
Mystical_IceAuthor Commented:
Was just following the article
0

Featured Post

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.

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