Comments on: Exchange 2010 RPC Client Access Service and Multiple Sites http://www.shudnow.net/2010/03/04/exchange-2010-rpc-client-access-service-and-multiple-sites/ Just another IT guy! Thu, 09 Feb 2012 12:04:04 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Elan Shudnow http://www.shudnow.net/2010/03/04/exchange-2010-rpc-client-access-service-and-multiple-sites/comment-page-1/#comment-13415 Elan Shudnow Wed, 25 Jan 2012 22:08:02 +0000 http://www.shudnow.net/?p=1663#comment-13415 You said you don't see anything with get-clientaccessarray. Yet you say you checked and the CAS Array with the FQDN does exist for the AD Site. What you're not telling me is how you saw that so not sure how I can help you since you just contradicted yourself. You said you don't see anything with get-clientaccessarray. Yet you say you checked and the CAS Array with the FQDN does exist for the AD Site. What you're not telling me is how you saw that so not sure how I can help you since you just contradicted yourself.

]]> By: Tash http://www.shudnow.net/2010/03/04/exchange-2010-rpc-client-access-service-and-multiple-sites/comment-page-1/#comment-13397 Tash Thu, 19 Jan 2012 20:36:22 +0000 http://www.shudnow.net/?p=1663#comment-13397 Hi Elan, I have an existing client access array for exchange 2007. I have now installed 2 exchange 2010 CAS servers (Same AD site.Same forest, same subnet where the exchange 2007 cas/ht/mbx servers reside). When I run the get-clientaccessarray cmdlet on Exchange 2010, I get a blank response. I checked and the CAS array with the FQDN of prod-mailbox.xyz.com does exist for this AD site. So here's my question, when the clients mailboxes are moved to the new exchange 2010 database, the outlook user profile will still point to the existing cas array (prod-mailbox.xyz.com) yet, the mailbox will not be there. The existing exchange 2010 mailbox servers and databases are pointing the localhostname.server.name for CAS. How can I create or add these servers to the existing CAS array or can't I? What will happen? I hope I didn't' ramble on too much, but this is a huge concern. Thanks in advance for your response. Tash Hi Elan,
I have an existing client access array for exchange 2007. I have now installed 2 exchange 2010 CAS servers (Same AD site.Same forest, same subnet where the exchange 2007 cas/ht/mbx servers reside). When I run the get-clientaccessarray cmdlet on Exchange 2010, I get a blank response. I checked and the CAS array with the FQDN of prod-mailbox.xyz.com does exist for this AD site. So here's my question, when the clients mailboxes are moved to the new exchange 2010 database, the outlook user profile will still point to the existing cas array (prod-mailbox.xyz.com) yet, the mailbox will not be there.
The existing exchange 2010 mailbox servers and databases are pointing the localhostname.server.name for CAS. How can I create or add these servers to the existing CAS array or can't I?
What will happen? I hope I didn't' ramble on too much, but this is a huge concern.
Thanks in advance for your response.
Tash

]]> By: David Stubblefield http://www.shudnow.net/2010/03/04/exchange-2010-rpc-client-access-service-and-multiple-sites/comment-page-1/#comment-13292 David Stubblefield Tue, 29 Nov 2011 19:37:41 +0000 http://www.shudnow.net/?p=1663#comment-13292 Yes you can configure the autoactivation policy to be blocked on the DR site, in the event that you want it activated you reset it to unrestricted. Set-MailboxServer –identity DRdag –DatabaseCopyAutoActivationPolicy Blocked I agree design wise a site fail over should be manual. Yes you can configure the autoactivation policy to be blocked on the DR site, in the event that you want it activated you reset it to unrestricted.

Set-MailboxServer –identity DRdag –DatabaseCopyAutoActivationPolicy Blocked

I agree design wise a site fail over should be manual.

]]> By: Elan Shudnow http://www.shudnow.net/2010/03/04/exchange-2010-rpc-client-access-service-and-multiple-sites/comment-page-1/#comment-13290 Elan Shudnow Tue, 29 Nov 2011 06:32:04 +0000 http://www.shudnow.net/?p=1663#comment-13290 Looks good. You can use multi-role servers. Just make sure you spec the servers out with enough resources. Here's a start: <a href="http://technet.microsoft.com/en-us/library/dd298121.aspx" rel="nofollow">http://technet.microsoft.com/en-us/library/dd2981...</a> Looks good. You can use multi-role servers. Just make sure you spec the servers out with enough resources. Here's a start: http://technet.microsoft.com/en-us/library/dd2981…

]]> By: Mauricio http://www.shudnow.net/2010/03/04/exchange-2010-rpc-client-access-service-and-multiple-sites/comment-page-1/#comment-13286 Mauricio Fri, 25 Nov 2011 14:28:31 +0000 http://www.shudnow.net/?p=1663#comment-13286 Hi, I'm planning an Exchange 2010 site resilient for my company with the Active/pasive architecture using diferents namespaces. I have 2 sites with one server on each with the 3 roles (cas,hub and mailbox). My idea is to implement 1 DAG in order to have 1 active database in primary site and the replicated in the passive site. Also have 1 witness server on active site for the quorum requirement Do I need to have Exchange server roles separately on diferents servers or its works having all the roles in the same machine? I don't have load balancer, only 1 CAS, hub and mailbox. Summarizing: Active Site 1 server with roles mailbox, hub and CAS 1 witness Passive site 1 server with roles mailbox, hub and CAS Both sites with differents namespaces. Thanks! Mauricio Hi,
I'm planning an Exchange 2010 site resilient for my company with the Active/pasive architecture using diferents namespaces.

I have 2 sites with one server on each with the 3 roles (cas,hub and mailbox). My idea is to implement 1 DAG in order to have 1 active database in primary site and the replicated in the passive site.

Also have 1 witness server on active site for the quorum requirement

Do I need to have Exchange server roles separately on diferents servers or its works having all the roles in the same machine? I don't have load balancer, only 1 CAS, hub and mailbox.

Summarizing:
Active Site
1 server with roles mailbox, hub and CAS
1 witness

Passive site
1 server with roles mailbox, hub and CAS

Both sites with differents namespaces.

Thanks!
Mauricio

]]> By: Exchange 2010 CAS Role Multiple Site & High Availability « Unified Collaboration http://www.shudnow.net/2010/03/04/exchange-2010-rpc-client-access-service-and-multiple-sites/comment-page-1/#comment-12908 Exchange 2010 CAS Role Multiple Site & High Availability « Unified Collaboration Tue, 16 Aug 2011 11:04:14 +0000 http://www.shudnow.net/?p=1663#comment-12908 [...] http://www.shudnow.net/2010/03/04/exchange-2010-rpc-client-access-service-and-multiple-sites/ [...] [...] http://www.shudnow.net/2010/03/04/exchange-2010-rpc-client-access-service-and-multiple-sites/ [...]

]]> By: Elan Shudnow http://www.shudnow.net/2010/03/04/exchange-2010-rpc-client-access-service-and-multiple-sites/comment-page-1/#comment-12881 Elan Shudnow Sat, 06 Aug 2011 00:33:54 +0000 http://www.shudnow.net/?p=1663#comment-12881 That's definitely not normal. Not sure what would be causing this. Sorry. That's definitely not normal. Not sure what would be causing this. Sorry.

]]> By: Mark http://www.shudnow.net/2010/03/04/exchange-2010-rpc-client-access-service-and-multiple-sites/comment-page-1/#comment-12848 Mark Wed, 13 Jul 2011 10:14:48 +0000 http://www.shudnow.net/?p=1663#comment-12848 Hi, We have 2 Datacenters/AD sites (primary and DR), 1 DAG with 2 members, 1 DAG member in each AD Site. Active DB and all users in primary site passive copy in the DR site. We also have 2 CAS Arrays, 1 in each site. FWS in primary site and alt-FWS in DR site. DAC enabled. The problem is that when the FWS in the primary site is down (e.g. restarted for updates etc) then the active databases automatically failover to the DR site. Is there any way to stop this happening? Ideally failover should only occur if the primary DB is down or the primary site fails not if the FWS fails. thx Mark Hi,
We have 2 Datacenters/AD sites (primary and DR), 1 DAG with 2 members, 1 DAG member in each AD Site. Active DB and all users in primary site passive copy in the DR site. We also have 2 CAS Arrays, 1 in each site. FWS in primary site and alt-FWS in DR site. DAC enabled.

The problem is that when the FWS in the primary site is down (e.g. restarted for updates etc) then the active databases automatically failover to the DR site. Is there any way to stop this happening? Ideally failover should only occur if the primary DB is down or the primary site fails not if the FWS fails.

thx
Mark

]]> By: Franko http://www.shudnow.net/2010/03/04/exchange-2010-rpc-client-access-service-and-multiple-sites/comment-page-1/#comment-12689 Franko Sun, 15 May 2011 19:50:19 +0000 http://www.shudnow.net/?p=1663#comment-12689 Hi Elan, Please Help 300 users divided equally between 2 sites, A & B. Single Ad domain but 2 corresponding AS sites. Each site with 1 CAS/HT server and 1 MBX . Mailbox server resilience to be provided y DAG. I.e Site A will have a DAG on the Site B MBX server. The challenge i have is following; I want to provide resilience for CAS. Ideally , A CAS Array would be great if not for the fact that my 2 CAS servers live in different AD sites. What I would like to happen is following; 1. IN normal use when both CAS servers are operating ok, I want users to be able to use the CAS server that is relative local to them. If site A is in Europe and Site B is in the US, I want european based users to use the europe CAS server in site A. 2. If the CAS server in Site A (europe) goes down , I want the user to then be directed to the CAS server in Site B ( in the USA) and from their get connected back to the mailbox server at site A or if that server is down as well, to be connected to the DAG in site B Hi Elan,

Please Help

300 users divided equally between 2 sites, A & B. Single Ad domain but 2 corresponding AS sites. Each site with 1 CAS/HT server and 1 MBX . Mailbox server resilience to be provided y DAG. I.e Site A will have a DAG on the Site B MBX server.

The challenge i have is following; I want to provide resilience for CAS. Ideally , A CAS Array would be great if not for the fact that my 2 CAS servers live in different AD sites. What I would like to happen is following;

1. IN normal use when both CAS servers are operating ok, I want users to be able to use the CAS server that is relative local to them. If site A is in Europe and Site B is in the US, I want european based users to use the europe CAS server in site A.
2. If the CAS server in Site A (europe) goes down , I want the user to then be directed to the CAS server in Site B ( in the USA) and from their get connected back to the mailbox server at site A or if that server is down as well, to be connected to the DAG in site B

]]> By: Elan Shudnow http://www.shudnow.net/2010/03/04/exchange-2010-rpc-client-access-service-and-multiple-sites/comment-page-1/#comment-12648 Elan Shudnow Tue, 03 May 2011 01:46:33 +0000 http://www.shudnow.net/?p=1663#comment-12648 Completely second DAG or put FSW in 3rd site. Problem with FSW in 3rd site is if your primary site is very important and the WAN link goes down preventing access to the secondary datacenter and the site that has the FSW, that primary datacenter goes offline. Completely second DAG or put FSW in 3rd site. Problem with FSW in 3rd site is if your primary site is very important and the WAN link goes down preventing access to the secondary datacenter and the site that has the FSW, that primary datacenter goes offline.

]]>