Exchange 2013 - Prevent Outlook Clients From Connecting To A CAS Server In A Different AD Site

Hi all,
I could really do with your help!
We have 3 physical sites, A, B & C, with sites A & B having a really fast low latency links between them, so from an AD point of view they are 1 site. Site C has links to both sites A & B, but the link is a lot slower.
We have an exchange design with 3 servers (one located at each physical site) that will form a DAG spread over the 3 physical sites. Ideally we will separate the CAS and mailbox server roles out and have them controlled by a hardware load balancer,
however we can have both roles on the same server if required.
What we want, is to prevent is a situation where an outlook client in site C connects to a CAS server in site A/B with the mail being hosted on a mailbox server in site C therefore traversing the network twice to get its mail.
From doing the Microsoft training course, my understanding is that in Exchange 2013, the CAS server only proxy's the request on to the mailbox server and does not redirect the request to the CAS server in the site where the mailbox server resides.
I have seen information online stating that a single namespace is the way to go as long as your site links/network bandwidth is good, but nothing to help with our scenario.
Has anyone else come across this situation and how did you get round it?
Thanks in advance :)

Hi Johnson,
Based on my knowledge, Outlook Client will connect to the CAS server which in local first.
Please check whether the CAS server that in site C is healthy.
If the CAS server in site C is healthy, please disable the CAS Load Balance for testing.
Also found a useful blog for your reference:
Exchange 2013 Client Access Server Role
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
Thanks
Mavis
Mavis Huang
TechNet Community Support

Similar Messages

Connection beetween Exchange 2013 with outlook client 2007 SP3

Hi All,
My company reinstall exchange 2013 when the previous mailbox DB error. When I implemeted a new server. I configured step by step carefully. if we use outlook 2010 connect to exchange server, send/receive work normally. But someone, uses outlook 2007 SP3,
they have somer error. They work with "cached mode", the connection from outlook to exchange server connected normally, but mail items sometime disappear in outlook client, when i check in the OWA, the mailbox item appear on this.
I tested with "online mode", the mailbox items push into outlook.I switched to "cached mode", this items haven't in outlook. Everybody who's meet the problem, please help me the solution can resolve the problem? Many thanks.
Quoc Dao

Hi,
Would you please let me know edition information of the Windows Server? Is it a Windows Server 2012, Windows
Server 2012 R2 or other?
On current situation, please refer to following KB and check if can help you.
Sometimes e-mail messages do not appear in your
Cached mode Inbox even though they were synchronized down from your mailbox
By the way. Based on your description, this issue seems to be more related to Outlook 2007. If this issue still
exists, I suggest that you should post in
Outlook forum. I believe we will get a better assistance there.
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Exchange 2013 and Outlook 2007

Is there a new way to connect EX2013 to Outlook 2007 SP3?
MSB

Hi Baker,
According to the description, I notice that you want to migrate from Exchange 2010 to Exchange 2013 and want to know how to connect Exchange 2013 with Outlook Client 2007.
Following is an article about the migration, for your reference:
Upgrade from Exchange 2010 to Exchange 2013
http://technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx
Outlook client uses Autodiscover and Outlook Anywhere to connect to Exchange server, please make sure services’ URLs configured correctly.
If you want to communicate with external users, you need to apply a certificate issued from a Public CA.
After configuring all the points above, please run “Get-Mailbox –Identity allen | FL *GUID*” in EMS to get mailbox GUID of allen’. Input the GUID into server name filed.
More details on “Manual configuration guide for Outlook 2010 (Exchange 2013)” for your reference:
http://support.sherweb.com/Faqs/show/manual-configuration-guide-for-outlook-2010-exchange-2013
Disclaimer:
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.
Best Regards,
Allen Wang

Exchange 2013-SP1/Outlook 2013 connectivity issue.

We couldn't make Outlook 2013 (latest updates) to connect to our Exchange 2013-SP1 through the Internet.
Any PC inside the LAN (on the domain or outside the domain) can connect normally.
Any PC outside the LAN (WAN) cannot connect, it keep showing this error:
"The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
OWA is working fine from the WAN, smartphones (Android & Apple) are also working fine from the WAN.
Port 443 is open on the firewall.
So what we are missing!

Hi,
Firstly, I'd like to say, in Exchange 2013 SP1, Outlook 2013 SP1 clients may use MAPI over HTTP to connect to the server.
Before going further, let's confirm if they use MAPI over HTTP: Get-OrganizationConfig | FL MapiHttpEnabled
If the value of the above property is true, I recommend the following troubleshooting:
1. Check if your Exchange 2013 SP1 server is running on Windows Server 2012 R2.
2. Check MAPI virtual directory settings: get-MapiVirtualDirectory |fl
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Exchange 2013 Issue: Outlook 2010 auto populating the From Tab when forwarding email

Exchange 2013 Issue: Outlook 2010 auto populating the From Tab when forwarding email
I am running Exchange 2013 and I have an end user who connects to it via Outlook 2010. All was going well till he went to forward an email and he noticed that the From button appeared and auto populated the sender's email address.
I have clicked the Empty Auto Complete List in Outlook's Send messages... still displayed the From tab when forwarding.
I recreated the profile in outlook... same thing.
I created the profile with outlook 2013... same thing.
There is only one user profile setup in Outlook.
(I know the from tab usually appears when you have multiple profiles setup in Outlook and/or when you configure the "From" tab.)
I opened the end user's email in Exch 2013's OWA... what was different here was when I clicked on the email and it opened, it did NOT have the Reply or Forward option... and it displayed as a "Draft" email.
Does anyone have any ideas?

So are you saying that the from button is filling the option with the original senders address (eg the person who sent the message to your user), or that it's filling in the your users address (in which case I don't understand what the issue is, since
it IS going from your user)?

How to find out what server the outlook client is connected to/change it automatically

Hi,
I am performing a server migration from Exchange 2010 to Exchange 2010 (the previous installation was installed by an outsourced provider and is rubbish so I'm configuring it properly). On the of things the existing server lacks is a CAS array configured,
so I have built the new Exchange 2010 server, configured a new DB and CASArray. I have created a brand new mailbox for a new user and the user's outlook shows it is connected to casarray.domain.local, I have migrated my own mailbox but internally my outlook
shows it is connected to oldserver.domain.local (under the account settings when you go to change the settings for the account), this is on a domain joined internal desktop. But at home on my personal laptop non-domain joined, it has appeared to reflect the
new casarray.domain.local. The outlook client is 2007 in both situations.
When I run the following command, it shows my mailbox is indeed connected to the new exchange server, but this is not true in outlook
Get-LogonStatistics -Server "new-exch2010" | where {$_.clientname -eq "new-exch2010"}| ft username,servername,clientname
If I run the above command against the old server my name shows on that list as well. When I look at the connection status of my outlook it shows that it is connected to casarray for directory, but the old server for mail.
A couple of other things:
Mailflow is now going to the new exchange server from the gateway over port 25, the autodiscover record in the internal DNS is now also pointing to the new exchange server, outlook clients and users computers have been completely restarted but still don’t
seem to pick up the new settings, both the old server and new server functions as a multi-role exchange having the Hub, CAS and MBX roles.
Now that you have all that background info my question is two parts:
What is the correct powershell command I can run on the exchange server to ensure that all my outlook clients are connected to the new exchange server for all connection types (or identify those which are connected against the old server)?
How do I get the outlook clients to automatically pick up the casarray servername once their mailboxes have been migrated?
I am considering removing the CAS from the old server which may force outlook to find it’s new server but am unsure whether this will work or not, and I think I should migrate all the mailboxes into the new DB before I do this.
Other than that, I am out of ideas.
Appreciate, any help. Thanks
Steve

I had already run the command Get-MailboxDatabase | FL Identity,RpcClientAccessServer
and it only identified the old database as being tied to the server name, the new database has the correct casarray and all mailboxes are in this new database. should I also set the old database to point to my casarray as the second command indicates? can't
do any harm right?
also, I have outlook 2007 and 2013 at home and both of them had automatically reconfigured
themselves to point to casarray, my problem is with the internal clients.
today I have also noticed in DNS there is a Zone which points to autodiscover.domain.co.uk
and in there it points to my old server.
a few things to note about the above:
1. the zone is pointing to the .co.uk domain not the .local - is this correct?
2. should that zone even be in our internal DNS, i hadn't noticed on previous implementation
of Exchange I have done
3. if i change the record within that zone to point to my new server, will this likely show
up the popup message shown in this link http://www.rackspace.com/apps/support/portal/1218 I havent yet got a certificate for the new exchange server (few more days) and i dont want users seeing any kind of untrusted unsecure connection box or it
will only lead to panic and flooding the helpdesk
many thanks
Steve

Exchange 2013 w/Outlook 2013 "The name of the security certificate is invalid or does not match the name of the site"

I've completed an upgrade from Exchange 2003 to Exchange 2013 and I have one last SSL message that I can't get rid of. I've installed a 3rd party cert that is working great for webmail and cell phone access but for some reason the Outlook 2010/2013
clients get prompted for a security warning. I just implemented the SSL cert yesterday and I've noticed that new installs of Outlook seem to work just fine. My Outlook 2013 client doesn't prompt me with the message but I have other users who are
still getting the "The name of the security certificate is invalid or does not match the name of the site" error. The domain on the cert error show up as server.mydomain.local. I've gone through all the virtual directories and pointed
all of my internal and external URL's to https://mail.mydomain.com. This made one of the two warnings go away but not the second. I've dug around on google and gone through everything I could find here and as far as I can tell my internal
and external url's are configured properly and I can't figure out where this error is originating from. Any ideas on where I should look outside of the virtual directories?
I'm including a good link I found that contains all of the virtual directories I updated. I've checked them through both CLI and GUI and everything looks good.
http://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
http://jaworskiblog.com/2013/04/13/setting-internal-and-external-urls-in-exchange-2013/

Hi,
When the Outlook connect to Exchange 2013/Exchange 2010, the client would connect to Autodiscover service to retrieve Exchange service automatically from server side. This feature is not available in Exchange 2003 Outlook profile.
Generally, when mailbox is moved to Exchange 2013, the Outlook would connect to server to automatically update these information. It needs time to detect and update the changes in server side. I suggest we can do the following setting For autodiscover service:
Get-ClientAccessServer | Set-ClientAccessServer –AutodiscoverServiceInternalUri https://mail.mydomain.com/autodiscover/autodiscover.xml
Please restart IIS service by running IISReset in a Command Prompt window after all configuraions.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 autodiscover not working from Externally

Hi
i have exchange 2010 sp3(2Mb, 2hub/cas). I installed exchange 2013 servers(2MB, 2CAS). For coexistence i generated new certifcate with new cas from third party. I installed that certificate in that cas and assigned all services. i changed all my virtual
directories service url. I didnt import the new certificate to exchange 2010 cas server and i didnt change url to legacy link.But still iam able to check exchange 2010 user mailbox owa, activesync and autodiscover without any certificate error.
If i try to browse owa, its going to 2013 server, if user is exchange 2010 user and its redirecting to exchange 2010 owa with same link.
But i dont know how above things is working without importing to new certificate...
Main problem is i am not able to configure exchange 2013 users outlookanywhere, Autodiscover from externally...
So in tmg i pointed the outlook anywhere ip address new cas server, now both exchange 2010 and exchange 2013 users while OA from external, its keep on asking password... Not accepting it...
Please help me to fix this issue..

Hi ,
On TMG please have the outlook anywhere rule like below and check the status.
Step
1 :
On the TMG rule - >authentication delegation ---> select the option "no delegation users can authenticate directly"
Step
2 :
on the users tab in the TMG rule - just add "all users" group on that rule.
By having the above settings we have avoided the issues in your environment.
Note : Based on the above setting's , Each and everyone in exchange will have a access to the outlook anywhere from external world , because there would not be having any restriction on the TMG rules.
Please have a look in to the below link , it will give you some ideas which is related to TMG
http://blogs.technet.com/b/exchange/archive/2012/11/21/publishing-exchange-server-2013-using-tmg.aspx
Thanks & Regards S.Nithyanandham

Open source web calendar client to connect Mac OS X Server iCal service?

Is there any open source web calendar client to connect Mac OS X Server iCal service?

[Here is a crib sheet for connecting Windows to Samba|http://labs.hoffmanlabs.com/node/1590]

Outlook Profile Not Updated to New CAS Array After Mailbox Move Between Sites

I am working on a large mailbox migration from one AD site to another.
Exchange version at both sites:Exchange 2010 SP2
Two Mailbox Servers: MBX01 in site A / MBX02 in site B
(There is a DAG but keeping this simple)
Two CAS Arrays: CASA.domain.com / CASB.domain.com
The RPCClientAccessServer property is set accordingly. Where MBX01 is set to CASA.domain.com and MBX02 is set to CASB.domain.com
Clients:Outlook 2010 SP1
Scenario: I successfully move a mailbox from Site A to Site B. The Outlook client does not automatically update its server settings to point to the new cas array (CASB.domain.com) and continues to connect to the old CAS server (CASA.domain.com).
I have seen a few articles regarding this pointing to workarounds such as:
- repairing the outlook profile on the client
- delete the existing outlook profile
- run a script to update the prf file (re-cache's email at the client)
I am interested in knowing if anyone else has experienced this, what their solution was for a large migration and if any roll-ups or service packs have possibly fixed this problem.
I would also like to know if you have seen this affect ActiveSync devices. I am getting mixed results in my tests and thought it may be contributed toward different device types, mobile os versions, etc...
I have posted this to the Outlook forum as well, just wasn't sure where to start.
Thanks.
Mike

Hi,
Firstly, I’d like to say, in Exchange 2010 and prior to SP2 CU3 version,
when we move mailboxes between AD sites, users will not receive any notice about restarting Outlook and their RPC endpoint won’t update to reflect the RPC Client Access Server array associated with the mailbox database in the AD site where the mailbox now resides.
Depending on repairing or recreating profile, we can force Outlook to use the new RPC endpoint.
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Outlook clients cannot connect Exchange 2013 cutover from 2010

Hello,
My company has been running an Exchange 2013/2010 coexistence. Currently, Exch 2013 (2mbx and 1 CAS) utilizes "mail2.domain.com" for the name space. Exch 2010 (1MBX 1 CAS) uses "mail.domain.com"
We recently attempted to cutover external and internal DNS to point "mail.domain.com" and "autodiscover.domain.com" to the Exch 2013 server.
We changed all virtual directories on 2013 to use "https://mail.domain.com/owa" (ECP, EWS, etc. were changed too) for the internal and external URL. The Exch 2010 virtual directories internal URL are set to "https://internalFQDN.domain.com/owa"
the external URLs are $null
Both CAS servers were setup to use Outlook Anywhere since this is how 2013 proxies to 2010. The internal URLs for both were set to "mail.domain.com" IIS authentication Methods (Basic, NTLM). ClientAuthenicsationMethod: NTLM.
For both servers the autodiscoverserviceinternaluri was set to: https://autodiscover.domain.com/autodiscover/autodiscover.xml
The 2013 server has two SSL certificates installed. One is a wildcard cert for "*.domain.com" and the other includes our SANs (mail.domain.com, mail2.domain.com, webmail.domain.com, autodiscover.domain.com) it also includes the FQDN for the 2010
and 2013 CAS servers.
I'm speaking in the past tense because we had to roll back. The problem was no Outlook user could connect. This goes for mailboxes hosted on the Exchange 2013 and 2010 servers. The error was: "Cannot
open your default e-mail folder" to "The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete".
Everything else worked fine during the cutover. OWA 2013 login page proxied 2010 logins properly, Outlook 2011 could connect with EWS fine, Active-Sync worked without issues too.
It was only the Outlook 2010 and 2013 clients that could not connect.
We rolled back and everything is working as it was before with the separate namespace. That leads me to think it's something with Outlook Anywhere (RPC/HTTPS)
but the settings seem correct unless I'm missing something. Any help is appreciated.
Thanks!

Hard to say. I've had to change the router to point to the old server as mail wasnt getting in. But OWA did seem ok, although I couldn't send messages... I could only see the inbox and contacts etc.

Outlook client not connecting when a user is moved from 2010 to 2013

Dear all,
we are exchange 2010 SP3 we migrate to exchange server 2013 sp1 cu7 all the mailbox migrated cannot connect to outlook client
howver, user on 2010 cannot redirect from exchange 2013 to 2010.
jibmud

Greetings! Just want to make sure I understand. You are saying that user mailboxes migrated to Exchange 2013 cannot connect? When you say Exchange 2010 users cannot connect to Exchange 2010 via 2013, how are they doing that? OWA?
What does Outlook connection status indicate?
How are your 2010 clients connecting and have all records been updated to point to Exchange 2013 servers? Do you happen to be using Outlook Anywhere internally?
Not sure if it applies to your environment but you may want to check this out:
http://blogs.technet.com/b/exchange/archive/2013/05/23/ambiguous-urls-and-their-effect-on-exchange-2010-to-exchange-2013-migrations.aspx

Exchange 2013 Upgrade to CU7 from SP1 - installs successfully - Can no longer connect via ECP/OWA/Powershell/Outlook/Autodiscover

Hi There,
I am having massive issues with my Exchange Server.
I have 2 Nodes, one has CAS and Mailbox Roles, the other just Mailbox.
I "upgraded" the CAS server to CU7 without any errors / issues.
Once I had restarted, nothing worked any more.. I couldn't access ECP, OWA, Powershell, Autodiscover or get outlook to connect.
I managed to get Powershell working, but changing the physical directory to "C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PowerShell" from "C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\PowerShell"
But for the life of me I cannot get ECP or OWA working (haven't even tried anything else)!
I am getting a load of Events with ID 1003.
The only error I am getting is:
Server Error in '/ecp' Application.
Method not found: 'Boolean Microsoft.Exchange.Net.Wopi.WopiRequestPathHandler.IsWopiRequest(System.Web.HttpRequest)'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.MissingMethodException: Method not found: 'Boolean Microsoft.Exchange.Net.Wopi.WopiRequestPathHandler.IsWopiRequest(System.Web.HttpRequest)'.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[MissingMethodException: Method not found: 'Boolean Microsoft.Exchange.Net.Wopi.WopiRequestPathHandler.IsWopiRequest(System.Web.HttpRequest)'.]
Microsoft.Exchange.HttpProxy.ProxyModule.AllowAnonymousRequest(HttpRequest httpRequest) +0
Microsoft.Exchange.HttpProxy.ProxyModule.OnAuthenticateInternal(HttpApplication httpApplication) +51
Microsoft.Exchange.HttpProxy.<>c__DisplayClass5.<OnAuthenticateRequest>b__4() +447
Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate) +40
Microsoft.Exchange.HttpProxy.Diagnostics.SendWatsonReportOnUnhandledException(MethodDelegate methodDelegate) +408
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +165
Which is almost meaningless... but maybe someone out there has some idea?
Unfortunately this is very urgent for me a these are production servers and currently there is no email for my company.
So Please please please can someone help.
I have tried many many many things from various sites, and so far nothing has worked.
Thanks,
-Tim

Hi Tim,
We can do the following steps to have a try:
1. Check Application settings in IIS Application under Exchange Back End web site for BinSearchFolders value.
a. Open IIS Manager. Expand Sites > Exchange Back End.
b. Click ecp. Open Application Settings in /ecp Home.
c. Please check whether the value for “BinSearchFolders” is changed to an invalid value.
2. Verify Authentication settings for OWA and ECP.
a. In IIS manager > Default Web Site, make sure Anonymous Authentication is Enabled in Authentication.
b. Confirm that "Require SSL" is checked on the root of the default website.
c. Make sure the Basic and Forms authentications are enabled in Default Web Site and Ntlm, WindowsIntegrated authentication methods are enabled in Exchange Back End for both OWA and ECP.
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

Exchange 2010-2013 Migration - Outlook Client gets "Your administrator has made a change..."

So we're migrating from an Exchange 2010 environment to Exchange 2013. We use a single namespace ("exchange.contoso.com") for both internal and external clients.
In testing, we have taken a few machines running outlook 2013 and 2010, and edited their hosts file such that "exchange.contoso.com" points toward the new exchange 2013 environment, rather than the 2010 environment for our users. So far so good,
they can connect, no issues.
However, when we move a mailbox to the 2013 environment, the outlook client comes back with "Your Exchange Administrator has made a change which requires you to restart outlook". This error affects both Outlook 2013 and 2010. We do have public
folders in place in exchange 2010, but we have not yet migrated them to 2013 (because the user's still are on 2010).
Repairing the profile is no help, and recreating the profile does not work either. Any thoughts?

Hi ,'
On you first post you have said you have put host file entries for the namespace "exchange.contoso.com"
in few of the client machines .
what about for autodiscover namespace did you have put any host entries for that .If not please put that
too in the host file of the client machines and then check by moving anyone of the mailbox from exchange 2010 to exchange 2013 .
Same time please check this blog especially on the end of the page .
http://blogs.msdn.com/b/aljackie/archive/2013/11/14/outlook-and-rpc-end-point-the-microsoft-exchange-administrator-has-made-a-change-that-requires-you-quit-and-restart-outlook.aspx
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Exchange 2013 with Outlook 2010 anywhere - Public Folders disappear from Outlook favourites

Hi,
we have a 3 server Exchange 2013 SP1 DAG published with Forefront TMG.
Outlook 2010 anywhere connection works fine (only anywhere connection is possible, there are no clients in the exchange server AD).
The users are adding public folders to their local Outlook favorites. In about 10% of the Outlook starts, those public folders are missing in the favorites. Local favorites folders are still there, public folders are connected.
After restarting the Outlook a few times, the favorites are back.
Deleting the outlook.xml brought no success, the favorites seem to be saved somewhere on the exchange server.
Outlook 2010 is up to date, all hotfixes are installed.
There are no related entries in servers or clients eventlogs, the logs of the TMG server are normal.
Does anyone have a simular behavior?
Thanks in advance!

Hi,
According to your description,it is clear that something got corrupted, but it is hard to say directly what caused it. However, there are a few troubleshooting steps to determine what caused it and you can also make a backup of your Favorite Folders list
so you can easily restore it when it still happens.
Pleaser refer to the following article:
Favorite Folders empty upon restart
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.
Hope this helps!
Thanks.
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Niko Cheng
TechNet Community Support

Exchange 2013 - Prevent Outlook Clients From Connecting To A CAS Server In A Different AD Site

Similar Messages

Maybe you are looking for