Quantcast
Channel: Exchange Server 2013 - Outlook, OWA, POP, and IMAP Clients forum
Viewing all articles
Browse latest Browse all 10580

OWA 2013 Redirect to CAS Servers 2010 Randomly

$
0
0

Hello there!!

I think my case is not a problem, I just need a workaround or some fine adjustment to serve my needs. Follow my scenario:

  • One Exchange 2013 Server (CU3) with Mailbox and CAS role (coexisting with the 2010 Servers, ready for migration)
  • Two Exchange 2010 CAS Servers SP3 no rollups
  • Two Exchange 2010 Mailbox Servers SP3 no rollups (in a DAG)

I have two organizations who share the same exchange infrastructure, just using different smtp address, for example, some users use @yyy.com addresses and others use @zzz.com. We have two CAS servers just to use two different and customized OWA layouts (with distinct OWA Internet addresses), one for @yyy.com users and other for the @zzz.com users

Also, I have the following database organization:

DB01 - @yyy.com mailboxes - 2010

DB02 - @zzz.com mailboxes - 2010

DB03 - @zzz.com mailboxes - will migrate to 2013

I need to do a partial migration to Exchange 2013, which is to migrate all mailboxes from DB03 database to Exchange 2013,which will use the owa address for the @zzz.com addresses (We will point it to the new 2013 server).The problem is that when users from DB02 try to use the 2013 OWA (@zzz.com), Exchange will bring up one of the 2010 OWA interfaces, sometimes the yyy.com customized interface and sometimes the zzz.com customized interface, and I need them to use just the zzz.com interface.

There is any way that I can force Exchange 2013 to redirect the 2010 OWA users from a specific database to a specific CAS server? I found the command "Set-MailboxDatabase "Database Name" -RpcClientAccessServer EX2010-1.domain.local"", but this work only for internal use (Outlook over RPC)

Best Regards Folks


Viewing all articles
Browse latest Browse all 10580

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>