Client Access Server Logs that capture Outlook Anywhere Connections

Do Exchange 2010 Client Access Servers log Outlook Anywhere connections? Since it's RPC over HTTP, I'm thinking these would be in the IIS logs but don't see any entries in those logs that pertain to Outlook Anywhere. What logs contain Outlook Anywhere connections?
I suspect I have a CAS server that isn't working properly pertaining to OA and need to be able to review some sort of logs to confirm.
Thanks

ARay,
Do the below basic checks-
Running the Test-OutlookConnectivity cmdlet. The cmdlet tests for Outlook Anywhere (RPC over HTTP) and TCP/IP connections. If the cmdlet
test fails, the output notes the step that failed.
Running the Outlook Anywhere connectivity test using the Exchange Remote Connectivity Analyzer (ExRCA). When you run this test, you get a detailed summary showing where the test failed and what steps you can take to fix issues.
Both tests try to log on through Outlook Anywhere after obtaining server settings from the Autodiscover service. End-to-end verification includes the following:
Testing for Autodiscover connectivity
Validating DNS
Validating certificates (whether the certificate name matches the Web site, whether the certificate has expired, and whether it's trusted)
Checking that the firewall is set up correctly (ExRCA checks overall firewall setup. The cmdlet tests for Windows firewall configuration.)
Confirming client connectivity by logging on to the user's mailbox
Regards,
ASP20

Similar Messages

Exchange 2013 - Cleaning UP logs files (Client Access Server)

I have to client access server and it is running out of space
Is there anywhere in the C:\ drive where I can delete some space (e.g. log files)

Hello,
If you refer to C:\inetpub\logs\LogFiles, you can delete them manually or use a Powershell script to delete them.
Here is the similar thread for your reference.
http://social.technet.microsoft.com/Forums/exchange/en-US/703dc324-721e-4c52-b43a-263b5543cfda/how-to-control-iis-logs-on-cas-server?forum=exchange2010
If you refer to other log files, please free let me know.
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Office 365 Streaming Notifications, "One or more subscriptions in the request reside on another Client Access server."

Hello all,
I am maintaining a part of our product that requires monitoring mailboxes for events. This is currently being done by using streaming connections for getting the notifications. Our solution has been successful for situations with smaller numbers
of mailboxes, ~200 or less. However we are seeing some issues when scaling up to say, 5000 mailboxes.
The error and the sequence leading up to it are as follows:
Make an Exchange Service Account.
exchSvc.ConnectionGroupName = someGroupName;
add to the httpheaders ("X-AnchorMailbox", userSmtp) and ("X-PreferServerAffinity", "true");
create a new impersonated UserId for the userSmtp address that is our anchor mailbox.
set the Exchange Service account ImpersonatedUserID to the one we just made.
ExchangeServiceAccount.SubscribeToStreamingNotifications(new FolderId[] { WellKnownFolderName.Inbox }, _mailEvents);
to this point everything was successful, saw no error messages.
we create a second impersonated UserID for a different mailbox, and repeat the process above from that step forward. Upon the final step, subscribing to the streaming notifications we get the error:
Exception: Microsoft.Exchange.WebServices.Data.ServiceResponseException: One or more subscriptions in the request reside on another Client Access server. GetStreamingEvents won't proxy in the event of a batch request.
This is only the second subscription that we are trying to add to this connection, and it is to a different mailbox than the first.
Can anyone please help point me to where this is going wrong?

>> Is there a good way to verify the number of subscriptions in a group?
Not that I know of you should be tracking this in your code there are no server side operations in EWS to even tell you if there are active subscriptions on a mailbox.
>>The error I am getting is on the second subscription in a new group, just after doing the anchor mailbox so I don't think we are hitting the 200 limit.
It's hard to say without seeing your code but it sounds like there is problem with your grouping code. One way to validate this is that with every request you make with the EWS managed API there is a
RequestId header http://blogs.msdn.com/b/exchangedev/archive/2012/06/18/exchange-web-services-managed-api-1-2-1-now-released.aspx
you should be able to give that RequestId to the Office365 support people and they should be able to check the EWS Log on the server and tell you more about what's happening (it maybe server side bug). Something doesn't quite add up in that the X-BackEndOverrideCookie
is what ultimately determines what server the request ends up at and the error is essentially telling you its ending up at the wrong server (have you looked at the headers on the error message?). Is it always one group of users that fails have
you tried different groups and different combinations etc.
Cheers
Glen

Client Access Server per AD Site?

In a single forest, single domain, multi AD site environment, can users in Site-B using Outlook 2010 clients connect to Client Access array /OWA, Hub, Maibox in Site-A without the need to install a Client Access server in Site-B? or Do I actually
have to install a Client Access server in Site-B?
I've read this thread, but I am still a little confused
http://social.technet.microsoft.com/Forums/exchange/en-US/03b835b4-7ecb-47ee-9b34-20cb2f70c3d4/client-access-server-active-directory-site?forum=exchangesvradminlegacy
Per MS.."You must install the Client Access server role in every Exchange organization and every Active Directory site that has the Mailbox server role installed"
http://technet.microsoft.com/en-us/library/bb124915(v=exchg.141).aspx. My Site-B does not have a Mailbox server, so I don't really need to have a Client Access in Site-B, if I understand this correctly.
Greatly appreciated if anyone can provide some clarification.
Thanks!
Note: Right now, there's only a single, default site in AD (Site-A). I am planning to add a Site-B in AD and add a domain controller in Site-B, but a little confused about the exchange. Just want to make sure that once I add Site-B to AD,
users would still be able to access Outlook/Exchange properly.

yes you don't need to. Your site B users will connect directly to the CAS on the Site-A, make sure the link speed is good enough.
Where Technology Meets Talent

EWS - Office 365 - "One or more subscriptions in the request reside on another Client Access server. GetStreamingEvents won't proxy in the event of a batch request."

Hello
My goal is to subscribe for streaming notifications for multiple users in the same time.
One way to do that is to create multiple StreamingSubscriptionConnections each one should contain one StreamingSubscription for each user. The problem with this method is that in Office 365 the maximum
number of connections opened is 20.
Another method to solve this problem is by creating one StreamingSubscriptionConnection and then all StreamingSubscriptions for each user to the connection. This method solves the maximum number of connections
problem and it works fine with exchange onPrimises. But when trying it with Office 365 it will result with the SubscriptionError:
"One or more subscriptions in the request reside on another Client Access server. GetStreamingEvents won't proxy in the event of a batch request."
Can anyone help me here ?

With Office365 you need to Group your subscriptions and set the Affinityheaders see
http://msdn.microsoft.com/en-us/library/office/dn458789(v=exchg.150).aspx and
http://blogs.msdn.com/b/mstehle/archive/2013/07/17/more-affinity-considerations-for-exchange-online-and-exchange-2013.aspx . Take note of the restrictions on the Group and other throttling restrictions if your using only one service account.
Cheers
Glen

Exchange 2013 - Proxy through client access server not working

Hello All -
I recently migrated our company to Exchange 2013 and noticed that our email was leaving through the mailbox server. I put a check mark in the Send Connector where it says "Proxy through Client Access Server" and my mail is still coming from the
mailbox server. How can I go about fixing this problem?
Environment:
1 CAS Server
1 Mailbox Server
Both server are behind the firewall with only port 25 opened to the CAS. The CAS has a Send Connector to a smart host for all messages.
Thank you!
Ryan

Hi,
Please check if the outbound messages without smart host are coming from CAS .
I doubt it send to the smart host directly if you configure smart host, and not use proxy thogh CAS.
If you have any feedback on our support, please click
here
Wendy Liu
TechNet Community Support

Troubleshooting for RPC over https (Outlook Anywhere) connection issue

RPC over https (ROH), well known as Outlook Anywhere, is more frequently used. Even in Exchange 2013, Outlook no longer connects CAS server via MAPI.
In this thread, we will discuss about the troubleshoot checklist about the RPC over https (Outlook Anywhere) connection issue. In order to make it more logical, I’d like to divide the whole troubleshooting to the following processes:
1. Client side to CAS side
2. CAS side to MBX side
[Issues between Client side to CAS side]
In Exchange 2013, Outlook Anywhere is enabled by default. Different from this, Outlook Anywhere in Exchange 2007 and 2010 need to be manually enabled. Thus, please firstly check if the RPC over HTTP component has been installed:
Click Start, and then click Control Panel.
Double-click Programs and Features.
In the left pane of Server Manager, click Features.
In the right pane, click Add Features.
Check if the RPC over HTTP component has been selected.
If the ROH connectivity issue only happens on certain users, the property MAPIBlockOutlookRpcHTTP can be checked:
Get-CASMailbox name | fl MAPIBlockOutlookRpcHttp
2. Confirm if Exchange server is blocked. Ping the Exchange server FQDN on client machine and confirm if it can return the proper IP address.
3. Check if the RPC Proxy server is responding correctly:
rpcping -t ncacn_http -s ExchServer -o RpcProxy=RPCProxyServer -P "user,domain,*" -I "user,domain,*" -H 2 -u 10 -a connect -F 3 -v 3 -E -R none
If 200 code returns, the test is successful.
4. Check if Outlook Anywhere host names are added in the certificate:
To get host names, the following command can be used: get-outlookanywhere |fl *hostname
5. To use the Shell to test Outlook Anywhere connectivity, use the
Test-OutlookConnectivity cmdlet.
[Issues between CAS side to Mailbox side][RZ1]
A. Check if it can connect to store’s port:
RpcPing –t ncacn_http –s ExchangeMBXServer -o RpcProxy=RpcProxyServer -P "user,domain,password" -I "user,domain,password" -H 1 –F 3 –a connect –u 10 –v 3 –e 6001
If it returns as following: Completed 1 calls in 60 ms 16 T/S or 60.000 ms/T, it means the RPC Ping Utility test succeeds.
B. Check if it can Connect to DsProxy Service:
RpcPing –t ncacn_http –s ExchangeMBXServer -o RpcProxy=RpcProxyServer -P "user,domain,password" -I "user,domain,password" -H 2 –F 2 –a connect –u 10 –v 3 –e 6004
If it returns as following: Completed 1 calls in 60 ms 16 T/S or 60.000 ms/T, it means the RPC Ping Utility test succeeds.
C. Check the following registries:
[Disable the auto update]
1).Open Regedit and navigate to:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeServiceHost\RpcHttpConfigurator\RpcHttpConfigurator
2).Set the PeriodicPollingMinutes value to 0.
[Check the RpcProxy ValidPorts]
1).On the RPC proxy server, start Registry Editor (Regedit).
2). In the console tree, locate the following registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy
3). In the details pane, right-click the ValidPorts subkey, and then click Modify.
4). In Edit String, in the Value data box, type the following information:
ExchangeServer :6001-6002; ExchangeServerFQDN :6001-6002; ExchangeServer :6004; ExchangeServerFQDN :6004
Note:
ExchangeServer is the NetBIOS name of your Exchange server. ExchangeServerFQDN is the fully qualified domain name (FQDN) of your Exchange server. If the FQDN that is used to access the server from the Internet differs from the internal FQDN, you must use
the internal FQDN.
[Check the 6004 port settings in registry]
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeSA\Parameters
Value name: HTTP Port
Value type: REG_DWORD
Value data: 0x1772 (Decimal 6002)
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeSA\Parameters
Value name: Rpc/HTTP NSPI Port
Value type: REG_DWORD
Value data: 0x1774 (Decimal 6004)
D. Check if the RPC ports are used by other applications instead of Exchange by using : netstat –o
Then it will return all active TCP connections and the process ID (PID) for each connection.
After that, please check the application based on the PID on the Processes tab in Windows Task Manager and confirm if it’s Exchange server.
Additionally, ExRCA is a perfect tool to test the whole connection between client side and Mailbox side:
https://testconnectivity.microsoft.com/
1. On the ExRCA website, under Microsoft Office Outlook Connectivity Tests, select Outlook connectivity, and then select Next at the bottom of the page.
2. Enter the required information on the next screen, including email address, domain and user name, and password.
3. Choose whether to use Autodiscover to detect server settings or to manually specify server settings.
4. Accept the disclaimer, enter the verification code, and then select Verify.
5. Select Perform Test.
<Resource for reference>
How does Outlook Anywhere work (and not work):
http://blogs.technet.com/b/exchange/archive/2008/06/20/3405633.aspx
How to use the RPC Ping utility to troubleshoot connectivity issues with the Exchange over the Internet feature in Outlook 2007 and in Outlook 2003:
http://support.microsoft.com/kb/831051
Test Outlook Anywhere Connectivity:
http://technet.microsoft.com/en-us/library/ee633453(v=exchg.150).aspx
[RZ1]It’s part, please re-layout
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

I've just restored the M11 to Windows XP with the disks provided and Outlook Anywhere connected without issue. As strange as it sounds, this looks to be isolated to this particular model of laptop and Windows 7.
I've used the same Enterprise copy of Windows 7 and Office on a variety of laptops and pc's and none have come across this problem. The only commonality I can see is the hardware and OS.
Aftery trying to troubleshoot this unsuccessfully with Microsoft tech support for a few hours, they eluded to the fact that this +could+ be a hardware related problem. (driver, adapter properties, etc)

Default Outlook Anywhere Connections

I'm using an Exchange 2013 SP1 environment with almost no customization. Only 2 servers exists - one holding CAS+MBX, and a second one being an MBX. No DAGs, balancers, etc. Mapi over HTTP is not enabled. The default self-signed certificates are used
(no new certificate was installed, nor any self-signed certificate manually installed on any server/client). A mailbox is provisioned on a database located on the first server. Outlook is configured for the corresponding user on a client machine and started.
Everything works just fine, with the 'Outlook Connection status' window showing 2 Exchange Directory + 2 Exchange Mail connections. Authentication is NTLM. Ports for all 4 connections are 6001 - which hint that Outlook Anywhere is indeed used.
From time to time, the familiar "Security Alert" comes up warning about the self-signed certificate, but this is usually traced in my experience to the various services Outlook is using, that are running on HTTPS (OAB, EWS, Availability...).
Here we find that in Exchange 2013 "Outlook Anywhere is enabled by default, because all Outlook connectivity takes place via Outlook Anywhere". Then
here it's stated that "Outlook Anywhere won't work with a self-signed certificate on the Client Access server". I remember the latter being true against Exchange 2010
instances, but seems not to be the case in Exchange 2013 anymore. Unless I'm missing something, from the standpoint of a default installation, the 2 articles contradict each other.
Second issue - even though Outlook is set for "Negotiate" in its Security setting, it looks like the Kerberos preferred option is never chosen. Would it have to do with the self-signed certificate and Outlook Anywhere ?

First article says "[...]In Exchange 2013, Outlook Anywhere is enabled by default, because all Outlook connectivity takes place via Outlook Anywhere.[...]". A simple Exchange 2013 SP1 setup, using defaults - including the built-in self-signed certs
- can be reached with no problems with a regular Outlook client. Since RPC over TCP is now defunct, and MAPI over HTTP isn't enabled (it's a regular installation, hence this feature is disabled) it can only be Outlook Anywhere being used by the Outlook client
to connect to the vanilla Exchange 2013 SP1 installation. Hence we can conclude that Outlook Anywhere works by default.
Second article comes around and says "[...] Outlook Anywhere won't work with a self-signed certificate on the Client Access server.[...]". Yet this is contrary to what I'm experiencing - since Outlook Anywhere is working (what other method of connecting
is left, right ? plus even the connections over :6001 in the Connection Status window hint at this) and there hasn't been any CA-emitted certificate installed on that stock CAS server.
So either the sentence in the second article is flat wrong (ONLY for 2013, Exchange 2010 NEEDS trusted certs), or it's missing a clause. Am I missing something ?
Hi,
Yes, Outlook Anywhere is enabled by default. Because all Outlook connectivity from Internal and External are using Outlook Anywhere.
For your second question, "[...] Outlook Anywhere won't work with a self-signed certificate on the Client Access server.[...]". Based on my knowledge, the Self-signed certificate which is installed with Exchange 2013 installation is not issued
by any CA. It is issued by the Exchange server.
Outlook Anywhere won't work with a self-signed certificate on the Client Access server because there would be a certificate untrusted issue on every user's clients. If you don't install the untrusted certificate in your trusted root certificate store on
the client computer, the client will be always prompted for the certificate error even through you can work with Exchange services after clicking Yes when the Security Alert asking you “Do you want to proceed”.
Regards,
Winnie Liang
TechNet Community Support

Clean Access Server could not establish a secure connection

I have a OOB Real IP GW setup on v4.1.2
I seem to have a problem with the CAS connecting to the CAM although I have added the CAS to the CAM and can manage the CAS from the CAM.
I noticed while troubleshooting client authentication that the client was not being redirected to the logon web page and it had full access to the trusted network from the untrusted authentication vlan. I eventually figured out that if I change the CAS Filter Fallback method from Allow to ignore then it tries to authenticate the client. However the fact that the fallback is activated tells you that something is not right.
I have 2 problems:
A) The clients web page is redirected for authentication but it only lists the domain name in the URL and not the hostname or host IP. In the lab I do not have a DNS server and it would not help as it does not include the hostname in the URL anyway. How do I fix this or perhaps it's related to the 2nd problem.
B) When I manually change the URL by replacing the domain name with the IP of the CAS (untrusted OOB Real IP GW) then I get the following error message when logging on:
Network Error:
Clean Access Server could not establish a secure connection to Clean Access Manager at mydomain.com.
This could be due to one or more of the following reasons: 1) Clean Access Manager certificate has expired 2) Clean Access Manager certificate cannot be trusted or 3) Clean Access Manager cannot be reached.
Please report this to your network administrator.
I would guess the culprit is No 2 but surely the system can run on self signed certificates? I have an NTP server so time is in sync. I have even tried regenerating the cetificates on the CAM
& CAS.
Any ideas?

To overcome problem B, I regenerated the SSL Certificates using the host IP address instead of the name for all the CAM & CAS appliances. This seems to have resolved this problem.
I also SSH'd from each of the CAS's to each of the CAM's from the CLI and it then prompts to permanently store the certificates. I'm not sure it this was necessary though.

Re: Tecra M11 - Outlook anywhere connection issue

Hello,
Has anyone tried to connect to an Exchange server with Outlook Anywhere on the factory installation of Windows 7 and Office 2010? The authentication window keeps popping up asking for a user name and password. (DOMAIN\Username)
I've been trying to get this working (with Microsoft tech support also), but haven't been able to. I've installed an Enterprise copy of Win 7 with Office 2010 & 2007 and got the same result. I tried this with a Tecra M10 with both a factory restore of Win7 and an Enterprise copy of Win7 from my company and it worked flawlessly.
This leads me to believe that this particular model of laptop could be the culprit. I have 2 M11's, and this happens on both. These are not connected to any domain. I don't believe this is an Exchange issue because Outlook Anywhere works with other models of Toshiba Tecras running Win7 and also several standalone Win7 PCs running both Office 2010 and 2007.
Any ideas or suggestions would be greatly appreciated!
Thanks

I've just restored the M11 to Windows XP with the disks provided and Outlook Anywhere connected without issue. As strange as it sounds, this looks to be isolated to this particular model of laptop and Windows 7.
I've used the same Enterprise copy of Windows 7 and Office on a variety of laptops and pc's and none have come across this problem. The only commonality I can see is the hardware and OS.
Aftery trying to troubleshoot this unsuccessfully with Microsoft tech support for a few hours, they eluded to the fact that this +could+ be a hardware related problem. (driver, adapter properties, etc)

Network Error: Clean Access Server could not establish a secure connection to Clean Access Manager

Hello everyone
I am implementing a failover solution of NAC in OOB VG version 4.8, I have 2 CAS and 2 CAM.
The Error I am getting is when I connect to both IP address and the FQDN of the CAS.
===========
Network Error:
Clean Access Server could not establish a secure connection to Clean Access Manager at camsrv3.cadivi.gob.ve.
This could be due to one or more of the following reasons: 1) Clean Access Manager certificate has expired 2) Clean Access Manager certificate cannot be trusted or 3) Clean Access Manager cannot be reached.
Please report this to your network administrator.
==========
For the CAM's I use this names camsrv1 and camsrv2. then generate a CSR in the camsrv1 with the name camsrv3.mycompany.com corresponding to virtual ip and it exported to camsrv2, Install the CA certificate of the company and everything works perfect.
This is the failover configuration
CAM:
Primary:     10.1.206.248 camsrv1.mycompany.com
Secondary: 10.1.206.249 camsrv2.mycompany.com
Virtual:       10.1.206.250 camsrv3.mycompany.com
Then I do exactly the same steps for the CAS's and this is the failover configuration:
Primary:     10.1.216.248 cassrv1.mycompany.com
Secondary: 10.1.216.249 cassrv2.mycompany.com
Virtual:       10.1.216.250 cassrv3.mycompany.com
Then I add the certificate of CAM in the CAS on the tab "Trusted Certificate Authorities" and vice versa.
The communication between all the CAM´s and CAS´s is correct (Primary, Secondary and Virtual). I can ping the IP and the FQDN and I can also manage the CAS through the CAM.
I verify that the time was right in the CAM and the CAS and all good up there.
Appreciate your help
Eduardo Navas

Eduardo,
Bump up the CAS/CAS communications logging on both the CAS and CAMs, and then look in the log files for clues.
On CAM they live in /perfigo/control/tomcat/logs and on CAS in /perfigo/access/tomcat/logs
HTH,
Faisal
If you find this post helpful, please rate so others can find the answer easily

Exchange 2013, Outlook 2007 clients Problems with Outlook Anywhere connection

Hi everyone,
I have a mail system Exchange 2013 SP1, on Windows Server 2012 R2.
I have only one mail server with the Client Access and Mailbox roles Server.
I have a Wildcard certificate type *. Mydomain.com.
All connections to the Outlook Anywhere Outlook 2010, Outook 2013 work correctly.
The ActiveSync connections are working properly, too.
But Outlook 2007 clients connecting with Outlook Anywhere asking for credentials continuously fail continuously.
How can I solve this?
thank you very much
Microsoft Certified IT Professional Server Administrator

Hi,
Based on my experience, we need to set Outlook provider with the domain name if it's wildcard certificate:
Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:*.domain.com
http://technet.microsoft.com/en-us/library/cc535023(EXCHG.80).aspx
Thus, I recommend you try the above configuration and test the Outlook connection again.
Thanks,
Angela Shi
TechNet Community Support

Accessing Server Logs Question

I'm working on converting an old ASP application to a Java one, and have some questions.
The customer wants a semi-sophisticated auditing system built in to the application, but I'm not sure OAS can provide the same level of detailed logs that IIS did (at least, not without a JNI DLL somewhere).
One of the reports requested, "Client Errors", wants to output the following fields:
- Requested File
- Error Code
- Total Requests
- Client Description
- Error Description
- Win32 Description
There are about 2 dozen other reports, as well.
The questions:
1. Can OAS log this sort of information in an extended w3c log format (Win32 Description might not be possible without JNI)?
2. How is the best way for the application to get to these logs? (I currently envision a regular job running to read the log into a database table)
Sorry if these are dumb questions. Any help would be appreciated.

Each Report Server has a log in which it record each time a report is run.

Exchange 2010 and Client Access Server Roll

Hi,
We have one CAS/HUB server, two mailbox roll servers in a DAG. Both mailbox roll servers have public folder database and both are replicate each other. Now we are going to office365. Now we
need to install client access roll on public folder database server(mailbox roll server) for office365 users to access the public folder from on premises according to
http://technet.microsoft.com/en-us/library/dn249373(v=exchg.150).aspx
We don't want get any problem after installing another CAS server roll. Our users' outlook should not interrupt with new installation. We are not setup client access array here. We are installing
this for public folders access to office365 mailboxes. How to install and configure?
Please help us to achieve this.
Thanks & Regards.

http://public.wsu.edu/~brians/errors/role.html
Exchange 2013 doesn't have a public folder database. If you're asking about an older version of Exchange, the Exchange previous versions forums are here:
http://social.technet.microsoft.com/Forums/en-US/category/exchangeserverlegacy
You shouldn't have any problem installing the CAS role. To be sure, after installing the server change all the URLs in the virtual directories to point to one of the real CAS servers, and run Set-ClientAccessServer -AutodiscoverServiceInternalUri to
to a valid Autodiscover URL.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Add Client access server with DR MBX to server clients from DR site.

Hello,
We have a medium size implementation at our company. It is as below,
- Two mail box servers (MBX1, MBX2) at production Site.
- One mail box server (MBXDR01 at DR site (Active))
- One DAG (name: IDKUDAG ) (MBX1,MBX2 and MBXDR01 are members)
- Two Client access servers at production site (with MBX1 and MBX2)
There is a high speed WAN connection between two sites.
What I need to do, I want to add additional CAS server at DR site as in case of production site maintenance or outage I want to migrate the DBs to DR MBX and the CAS server handle mail
client’s access.
Can I add a new server at the DR site with the same configuration as the production site???
Or there is another solution for this case.
Please advise.
Best regards,
Ahmed Salah
BR Ahmed Aboutabl

Hi Ahmed,
The CAS configuration for Exchange service in the second datacenter can be the same configuration as you mentioned. For example, the same internal&external namespaces for OWA, Autodiscover, EWS, OAB etc. in two datacenters.
Also make sure the certificate has included all needed namespace for the second site. For your reference, here is an article talked about the details of site resilients:
https://technet.microsoft.com/en-us/library/dd638129(v=exchg.150).aspx
http://www.msexchange.org/articles-tutorials/exchange-server-2010/high-availability-recovery/designing-site-resilient-exchange-2010-solution-part1.html
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
sure that you completely understand the risk before retrieving any suggestions from the above link.
Regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Winnie Liang
TechNet Community Support

Client Access Server Logs that capture Outlook Anywhere Connections

Similar Messages

Maybe you are looking for