Outlook Anywhere settings in a Exchange 2013 coexistence scenario with Exchange 2007

I have exchange 2013 and 2007 set up in a coexist environment. At the moment, the few mailboxes I am testing on Exchange 2013 are getting multiple pop ups in outlook and cannot connect to items like Public Folders on 2007. I found an article
that told me to change the authentication method from Negotiate to NTLM and that broke some of my Lync 2013 compatibility issues on users on exchange 2007 (ie conversation history and they got outlook integration errors.) I would like someone to confirm
if the change I am about to make from doing research will help me in my situation.
Current Setup:
Exchange 2007 OA CAS Settings
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod: NTLM
IISAuthenticationMethods : {Basic, Ntlm}
Exchange 2013 OA CAS Settings
ExternalClientAuthenticationMethod : Negotiate
InternalClientAuthenticationMethod: Negotiate
IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
New Settings I am considering based on research:
Exchange 2007 OA CAS Settings
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod: Basic
IISAuthenticationMethods : {NTLM}
Exchange 2013 OA CAS Settings
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod: Basic
IISAuthenticationMethods : {Basic}
Will this work and eliminate my popups?

Hi,
The following TechNet article indicates that:
“In order to support access for Outlook Anywhere clients whose mailboxes are on legacy versions of Exchange, you will need to make some changes to your environment which are documented in the steps within the
Exchange Deployment Assistant. Specifically,
you will need to enable Outlook Anywhere on your legacy Client Access servers and enable NTLM in addition to basic authentication for the IIS Authentication Method.”
Client Connectivity in an Exchange 2013 Coexistence Environment
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
As for the Autodiscover service, please make sure the Autodiscover.domain.com is pointed to your Exchange 2013 in Internal and External DNS. For more detailed information about Exchange 2013 coexistence with Exchange 2007, please refer to:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
Regards,
Winnie Liang
TechNet Community Support

Similar Messages

Exchange 2013 co-existence with Exchange 2010 proxying issue.

Hello,
I am testing Exchange 2010 and Exchange 2013 co-existence in my test lab at the moment, with
a view to migrating our production environment to 2013 later in the year.
The lab is setup, and the problem I'm having is that internal Outlook clients cannot open
their respective mailboxes once the 2013 CAS server is introduced into the mix.
The
setup is listed below:
EXCHANGE 2010 Servers
TESTLABEXCH01 - CAS,HT,MBX - Exchange 2010 SP3
TESTLABEXCH02 - CAS,HT,MBX - Exchange 2010 SP3
Both servers are part of a CAS Array - casarray01.testlab.local
Both servers are part of a DAG - DAG01.testlab.local
RpcClientAccessServer on all 2010 databases set to casarray01.testlab.local
The A record for casarray01.testlab.local points to the IP of the VIP of a load balancer.
The loadbalancer serves
the following ports: 25,80,443,143,993,110,995,135,60200,60201
OutlookAnywhere is enabled on both servers:
ClientAuthenticationMethod : Ntlm
IISAuthenticationMethods   : {Basic, Ntlm}
Internal and external mail flow works without issue before the 2013 server is introduced.
Internal and external client access works without issue before the 2013 server is introduced.
Part Two to follow.....
Matt

EXCHANGE 2013 Servers :
TESTLABEXCH03 - CAS,MBX - Exchange 2013 SP1
OutlookAnywhere is enabled on the server:
ClientAuthenticationMethod : Ntlm
IISAuthenticationMethods   : {Basic, Ntlm}
RpcClientAccessServer on all 2013 databases set to casarray01.testlab.local
(This an inherited setting I assume from the pre-existing 2010 organization)
Split DNS is in place and all internal/external URL's point to either:
autidiscover.external.com
mail.external.com
The A record for the mail.external.com points to the IP of the load balancer VIP
The CNAME record for autodiscover.external.com points to mail.external.com
When the TESTLABEXCH03 is added to the load balancer config,
and given highest priority this is when the Outlook clients stop working.
Any existing profiles in Outlook 2010/Outlook 2013 can no be opened as there is a persistent
credentials prompt.
Upon trying to create a new profile, the process errors when reaching the "Log onto server"
stage and again prompts for credentials.
Running the test-outlookconnectivity cmdlet from
either of the 2010 servers produces the following results.
[PS] C:\Windows\system32>Test-OutlookConnectivity -Protocol:http
ClientAccessServer   ServiceEndpoint
Scenario                            Result Latency
TESTLABEXCH02 autodiscover.external.com    Autodiscover:
Web service request. Success 343.20
TESTLABEXCH02 casarray01.testlab.local       RpcProxy::VerifyRpcProxy.
Success    0.00
TESTLABEXCH02 casarray01.testlab.local         RFRI::GetReferral.
Failure   -1.00
TESTLABEXCH02 casarray01.testlab.local        NSPI::GetProfileDetails.
Failure   -1.00
TESTLABEXCH02 casarray01.testlab.local
Mailbox::Connect.                   Failure   -1.00
TESTLABEXCH02 casarray01.testlab.local
Mailbox::Logon.                     Skipped   -1.00
If remove the 2013 CAS server from the loadbalancer config and
all connections go directly to the 2010 servers again, all of the above tests pass and Outlook connectivity is also restored.
IIS has been reset on all 3 servers incidentally, following any changes made whilst troubleshooting.
I'm struggling to see what I'm missing here, if anyone can assist in troubleshooting this
matter further, or point out any errors in my setup it would be greatly appreciated.
Regards
Matt
Matt

Internal outlook client connectivity in exchange 2010 when coexist with exchange 2013

Hi all ,
on my side i would like to clarify few queries.
Say for instance i am coexisting exchange 2010 with exchange 2013 .Unfortunately if all of my exchange 2013 servers goes down .
Q1 .On that time will the internal outlook users having their mailboxes on exchange 2010 can be able to connect mailboxes without any issues ? In case if they face any issues what kind of issues will they be? Because why i am asking is we should have pointed
the autodiscover service to exchange 2013 during coexistence.
When an user closes and reopens the outlook after whole exchange 2013 environment failure ,outlook will first query the autodiscover service for the profile changes to get it updated on users outlook profile.In such case autodiscover service will not be
reachable and i wanted to know will that affects the internal client connectivity for outlook users having their mailboxes on exchange 2010.
Q2. Apart from outlook internal users connectivity ,what kind of exchange services(i.e owa,active sync,pop,external OA and imap) will get affected when whole exchange 2013 environment goes down during coexistence ?
I have read the below mentioned statement on this awesome blog but still i wanted to clarify with you all on my scenario.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx<o:p></o:p>
Internal Outlook Connectivity
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array endpoint.
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2007, they will still connect directly to the Exchange 2007 Mailbox server instance hosting the mailbox.
Please share me your suggestions and that would help me a lot .
Regards
S.Nithyanandham

Hi Winnie Liang ,
Thanks a lot for your reply.
Scenario 1 : for internal outlook connectivity
We have below settings for exchange 2010 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2010 cas serves
We are going to have below settings for exchange 2013 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2013 cas serves
During coexistence mail.domain.com will be pointed to exchange 2013 cas servers . I mean to say if we try to resolve the mail.domain.com it will get resolved in to the exchange 2013 cas servers.
So on such case if anything happened wrong to the new environment or else if entire environment goes down .Do we face any issues while outlook users connect to existing mailboxes in exchange 2010 ?
Because why i am asking is ,on the below mentioned article i have read all the autodiscover request will go via exchange 2013 cas servers during coexistence.That means all the existing mailboxes in exchange 2010 will also have to query exchange 2013 cas
servers for autodiscover request.During the whole exchange 2013 environemnt failure whenever the user tries to close and open outlook .Outlook will first queries the autodiscover service for any changes happened on that particular mailbox and it will try to
get it updated on user profile.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Would it be possible to make the exchange 2010 mailbox users to query only the scp points which belongs to the exchange 2010 cas servers for autodiscover request ?
Scenario 2: For exchange services
mail.domain.com - will be the namespace for all the exchange 2010 services (i.e owa,activesync,external outlook anywhere,pop,imap)
mail.domain.com - will be the namespace for all the exchange 2013 services (i.e owa,activesync,external outlook anywhere,pop,imap)
What about the above services will it get affected during whole exchange 2013 environment failure ?
Note : We are not facing this issue , i hope everything goes well in my environment while doing coexistence i am just asking this question on my own interest?
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Exchange active sync cannot connect to server after migration mailbox user from exchange 2007 to exchange 2013 coexistence

Hello, everyone, my name is rafl
I have a problem with exchange 2013 active sync.
I have installed exchange 2013 coexistence with legacy exchange 2007, I have to migrate user mailboxes: [email protected] from exchange 2007 to exchange 2013.
but any problem with active sync connection on the mobile device after moving mailbox user. I reconfigure the exchange ActiveSync external connection domain (latest.domain.com) on mobile device replacing legacy exchange ActiveSync external connection domain
(legacy.domain.com)
the process of moving mailboxes successfully without error.
Access OWA for exchange 2007 and exchange 2013 is running normally
access mail from Outlook running normally
Certificate request has been installed and has no problem with it
The OWA virtual directory is configured for internal and external connections and different from the legacy exchange
The autodiscover virtual directory is configured for internal and external connections and different from the legacy exchange
ActiveSync virtual directory is configured for internal and external connections and different from the legacy exchange
user mailboxes are still on exchange 2007 is not problematic.
only problem with Exchange Active Sync on mobile devices, where I set up an email with android, iphone, windows phone. the error message: cannot connect to the server.
but, if I create a new user and create user mailboxes directly in exchange server 2013, ActiveSync can run without error on mobile device, access through OWA, MsOutlook, Outlook Anywhere also run normally.
only the results of user migration from exchange 2007 to exchange 2013 which is troubled with exchange ActiveSync connection.
any ideas for this problem, and what should I check on the exchange server ..?

i have run the activesync test connectivity and get some error :
Testing TCP port 443 on host domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 3091 ms.
Testing TCP port 443 on host autodiscover.domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 21072 ms.
Testing TCP port 80 on host autodiscover.domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 21049 ms.
I have allowed access to port 443 (https) and 80 (http) on the firewall and re-run testconnectivity, but still with the same results. if I enable active sync for users who created directly in Exch 2013 there is no problem with the ActiveSync, just a problem
for users who moved from Exch 2007 to Exch 2013. @Android, iPhone, and Blackberry the error message "cannot connect to the server"

Outlook Connectivity / Exchange 2010 Coexistence Scenarios

Hello,
I recently migrated to Exchange 2013, autodiscover.domain.com and mail.domain.com are pointing to CAS 2013 for external and internal access. For EX013 users, Outlook establishes connection with both CAS 2010 and CAS 2013 which is fine. For EX2010 users,
Outlook establishes the connection only with CAS 2010 for both internal and external access. My understanding is that CAS 2013 should proxy the connection to CAS 2010, but it doesn't and also after the migration I have to remove and add the profile again for
the changes to take effect for the migrated users. I haven't changed the namespaces, its the same. Any suggestions would be much appreciated.

Hi,
Your understadning is correct. Since only Exchange 2013 is Internet-facing, CAS2013 would proxy all requests for Exchange 2010 external user accessing.
Please make sure the External URL in Exchange 2010 services are all set to $Null and Outlook Anywhere is enabled with the external host name pointed to mail.domain.com. Then the external Exchange 2010 user would connect the Autodiscover service
with autodiscover.domain.com successfully. The other services such as EWS, OOF and OAB request would be send to Exchange 2013 then proxy to Exchange 2010.
For more infromation about the connectivity in Exchange 2013 coexistence environment, please refer to:
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Regards,
Winnie Liang
TechNet Community Support

Outlook anywhere settings, in Autodiscover?

So in Outlook, I got all my Outlook Anywhere settings configured, great! But where do I go to edit them on the server?
I don't have a GPO for any of this and I gather Outlook Anywhere is configured in Autodiscover? Is it EMS?

First, run set-outlookprovider -identity EXPR -Server servername and get-outlookanywhere |fl command in EMS. This command will let you know about the configuration of Outlook. You can edit the Outlook Anywhere configuration by using the custom installation
wizard. Autodiscover is simply the best way for managing Outlook configurations.
Set-OutlookProvider EXPR -OutlookProviderFlags:ServerExclusiveConnect
You can run this powershell command to make connection with the Outlook Anywhere using TCP/IP.
You can easily change the OutlookProviderFlags to change/edit the Outlok anywhere seetings e.g. you can set the value to ServerExclusiveConnect or to None to clear the flag
Hi Blake - can you change the first line to be get-outlook provider -identity EXPR ? Its currently at "set-"
Not sure if I'd be recommending the serverExclusiveConnect option off the bat, most customers I see do not leverage that.   Do they want to do OA internally too? I don't see that mentioned above
The OutlookProviderFlags parameter specifies that Outlook 2010 clients should connect using RPC over HTTP (Outlook Anywhere) before trying RPC over TCP connections. This increases the speed at which Outlook 2010 clients will connect when clients
are primarily accessing Exchange over the Internet. The value can be set to
ServerExclusiveConnect or to None to clear the flags. For Outlook 2010 clients that access Exchange over both organization intranets and the Internet, the recommended value is
None, which is also the default setting.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2013 coexistence with 2010

Who all has had problems with 2013 proxing requests to 2010? I tried a migration and couldn't even get OWA to proxy or redirect. I was receiving errors like this:
Autodiscover would fail for 2010 users but fine for 2013 users:
HTTP Response Headers:
request-id: d1e90875-53e1-4be5-ad64-24a9a5eb0c19
X-CasErrorCode: ServerNotFound
Persistent-Auth: true
X-FEServer: CPC8000-CAS01
Content-Length: 0
Cache-Control: private
Date: Sun, 01 Jun 2014 01:22:50 GMT
Server: Microsoft-IIS/8.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Elapsed Time: 153 ms
and
Created a new user on 2010 and login to OWA does this:
Microsoft.Exchange.Data.Storage.NotSupportedWithServerVersionException
I've tried it multiple ways and I've actually done this migration before. Either way this was the same AD site, and I checked/tried the following:
Checked AD Replication and it was fine
Exchange 2013 was at SP1
Exchange 2010 was at SP3 Rollup 6
Exchange 2010 was a single server with CAS/HUB/Mailbox
Exchange 2010 was not using a CAS Array
Exchange 2013 had two mailbox servers in a DAG and one CAS server
I've tried both setting all external URL's on 2010 to https://legacy.domain.com/* and also not setting External URL's. Neither fixed the issue
https://legacy.domain.com/autodiscover/autodiscover.xml worked fine (600 invalid request response) and https://owa.domain.com/autodiscover/autodiscover.xml worked fine too (2013) but Test Connectivity and Outlook didn't work
I checked for bad HTTP Redirections on new and old servers and made sure there were no HTTP redirections added
Would really love some input to see what I did wrong. Thank you!

Thanks for responding!
The internal URL's for 2010 I set to https://legacy.domain.com/*. So the OWA internal URL is https://legacy.domain.com/owa. The external URL was set to the same and I also tried not settings the external URL at all.
Just FYI.. legacy.domain.com pointed to the internal IP when using internal DNS servers and legacy.domain.com pointed to the external IP when external which all went to the 2010 server
The detailed error from ExRCA is listed above. It failed autodiscovered and wouldn't continue. The thing is autodiscover seemed to work fine going to 2010 and to 2013 but it failed when it tried to proxy to 2010. So if a mailbox was on 2013 then ExRCA was
fine. If I opened a url to https://legacy.domain.com/autodiscover/autodiscover.xml and logged in I got the XML 600 error like I should. This is what autodiscover said:
HTTP Response Headers:
request-id: d1e90875-53e1-4be5-ad64-24a9a5eb0c19
X-CasErrorCode: ServerNotFound
Persistent-Auth: true
X-FEServer: CPC8000-CAS01
Content-Length: 0
Cache-Control: private
Date: Sun, 01 Jun 2014 01:22:50 GMT
Server: Microsoft-IIS/8.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Elapsed Time: 153 ms

Outlook 2013 connection issue with exchange 2013

my exchange 2013 was upgrade from exchange 2010. after the upgrade (migration), i using outlook 2013 connect to exchange 2013. some very
weird issues happened.
when i using auto discovery to create profile and connect to exchange will success. but when i manually create the profilewill failed. the following pic for your reference. (same account, same PC)
please help, thanks lots!!!!

This is what changed in Exchange 2013. It uses RPC or HTTPs (Outlook Anywhere) and uses Server GUID to connect...
"As a result of these architectural changes, there have been some changes to client connectivity. First, RPC is no longer a supported direct access protocol. This means that all Outlook connectivity must take place using RPC over HTTP (also known as
Outlook Anywhere). At first glance, this may seem like a limitation, but it actually has some added benefits. The most obvious benefit is that there is no need to have the RPC client access service on the Client Access server. This results in the reduction
of two namespaces that would normally be required for a site-resilient solution. In addition, there is no longer any requirement to provide affinity for the RPC client access service.
Second, Outlook clients no longer connect to a server FQDN as they have done in all previous versions of Exchange. Outlook uses Autodiscover to create a new connection point comprised of mailbox GUID, @ symbol, and the domain portion of the user’s primary
SMTP address. This simple change results in a near elimination of the unwelcome message of “Your administrator has made a change to your mailbox. Please restart.” Only Outlook 2007 and higher versions are supported with Exchange 2013."
From : What's New in Exchange 2013-
http://technet.microsoft.com/library/jj150540%28EXCHG.150%29.aspx#BKMK_arch
Blog |
Get Your Exchange Powershell Tip of the Day from here

Edge Transport Server - Exchange 2013 coexistence Exchange 2007

Hi Exchange-Gurus,
We have one Exchange Org.
sub AD Domain1: A.domain.com (with Exchange 2007 SP3 R10)
sub AD Domain2: B.domain.com (with Exchange 2013 CU6); DMZ contains Exchange Transport Server - Exchange 2013
Is it possible to install within the DMZ of AD Domain1 a Edge Transport Server - Exchange 2013?
Thanks.
Guitarman

Hi Guitar,
Thank you for your question.
Is it possible to install within the DMZ of AD Domain1
an Edge Transport Server - Exchange 2013?
A: Yes, we could create an Exchange 2013 Edge server on the DMZ of AD domain1.
Notice: Before we create an EdgeSync Subscription between an Exchange 2007 Hub Transport server and an Exchange 2013 SP1 Edge Transport server, we need to install Exchange 2007 SP3
Update Rollup 13 or later on the Exchange 2007 Hub Transport server.
We could refer to the following link:
https://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim

Migrating Users from Exchange 2007 to Exchange 2013 Without redirection through exchange 2013.

We have all our users and mailboxes on Exchange 2007 and I have introduced two Exchange 2013 servers in my organization and both have mailbox and CAS server installed on them.
With Exchange 2007 server, I had not modified any of the internal and external url/uri and had stayed with the defaults.
For migration most of the documents are suggesting of changing the default internal URL and Auto Discover Service internal URI values.
In my case, I want to migrate all the users and mailbox (everything that is on Exchange 2007) form 2007 to 2013 and decommission exchange 2007 completely from our organization.
I am in the phase of transferring users from Exchange 2007 to Exchange 2013 and do not want to change any settings on the existing 2007 servers.
I have created new dns entry mailx.abc.com with two IPs of both exchange 2013 and changed the Outlook Anywhere internal URL on both Exchange 2013 server to mailx.abc.com.
So by doing these, I think all existing clients will still connect to exchange 2007 and after moving their mailbox they will be connect to exchange 2013.
In short I am not redirecting or using 2013 as proxy for 2007 clients and clients whose mailbox is on exchange 2013 will directly connect to 2013 server.
Questions are, Is this the right way to migrate all the users to Exchange 2013?
Will it affect the operation of existing Exchange 2007 server?

Read the below blog on Client Connectivity in Exchange co-existence. There can't be better blog than this on this topic.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Clients connect to Exchange from Internal-Outlook, External-Outlook, Web & Active Sync.
For Internal the configuration that you have mentioned should work as clients would get Autodiscover information from Active Directory (SCP) and get connected to right server.
However, for external connectivity it makes sense to use External URL on Exchange 2013 servers (keep the Exchange exposed to Internet), configure legacy URL for exchange 2007 and use Exchange 2013 external URL for mailboxes that are Exchange 2007 and Exchange
2013 for standardization.
Refer article for configuring URLs -
http://silbers.net/blog/2014/01/22/exchange-20072013-coexistence-urls/
- Sarvesh Goel - Enterprise Messaging Administrator

Exchange 2013 owa integration with ADFS and cooexistance with exchange 2007

Team,
I have successfully integrated adfs 3.0 and Exchange 2013 owa and ecp. However, we have a coexistence environment with exchange 2007. When you access owa, which then redirects you to adfs, sign-in, and then get redirected back to owa. If your
mailbox is still within exchange 2007, you get a blank login page. If you mailbox is in exchange 2013 then you successfully get the owa page for 2013. The problem is that all exchange 2007 mailbox users get blank pages at login. So I have determined
that exchange 2013 cas is not doing the service location lookup on the mailbox to determine if a redirect to the legacy owa address is needed. Is there a configuration setting that I might be missing? Or does the integration with adfs and owa not support
the much needed mailbox lookup for a coexistance environment? A side note: if we enable FBA with owa, both login scenarios work just fine (legacy and new 2013). The legacy namespace has been created, and applied to the exchange 2007 urls.

Hi,
Try using AD FS claims-based authentication with Outlook Web App and EAC
http://technet.microsoft.com/en-us/library/dn635116(v=exchg.150).aspx
Thanks,
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 Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Autodiscover after deploying Exchange 2013 CAS in a Exchange 2007 organization

I am deploying Exchange 2013 CAS in a Exchange 2007 organization. Will all the clients be directed to the Exchange 2013 CAS servers for autodiscover. Will there be any issue with outlook clients connecting to their mailbox servers in Exchange 2007

All clients should be pointed to the Exchange 2013 CAS for the autodiscover service. This means:
A. For local clients
You need to modify the autodiscover Internal URI on the Exchange 2007 server and point it to Exchange 2013. For example, if you are using split-brain DNS on the Local Network and mail.yourdomain.com is resolved to Exchange 2013 local IP, the Exchange 2007
Autodiscover Internal URI should be "https://mail.yourdomain.com/Autodiscover/Autodiscover.xml"
Exactly the same way, you should modify the Exchange 2013 Autodiscover Internal URI and use the same address "https://mail.yourdomain.com/Autodiscover/Autodiscover.xml"
B. For remote clients - all clients will hit the Exchange 2013 CAS first (ex. mail.yourdomain.com)
If the user's mailbox is on Exchange 2007 server, the correct XML will be generated and provided, and the user will be proxied for Outlook Anywhere/ActiveSync and redirected for OWA/WebServices
If the user's mailbox is on Exchange 2013 server, the correct XML will be generated and provided
Bottom line - based on the location of the user's mailbox, Exchange 2013 will generate and provide the correct XML file (there is not proxying involved in providing the Autodiscover info).

First Exchange 2013 server in an Exchange 2010 SP3 organization

I've read the documentation that states to install Exchange 2013 with CU2 as the first Exchange 2013 server in an organization running Exchange 2010 SP3. Maybe I over-read this to mean "Exchange 2013 with at least CU2" (meaning to start with Exchange2013-x64-cu3.exe),
but when I installed the CU3 version I ended up with Standard rather than Enterprise. I need to run 2013 with Enterprise. I've looked around for an Enterprise version of Exchange2013-x64-cu3.exe but cannot find one.
How do I install Exchange 2013 Enterprise into my Exchange 2010 SP3 organization? Thank you.

Please review
http://technet.microsoft.com/en-us/library/bb232170(v=exchg.150).aspx
These (Exchange 2013 Standard Edition and Enterprise Edition)
licensing editions are defined by a product key. When you enter a valid license product key, the supported edition for the server is established. Product keys can be used for the same edition key swaps and upgrades only; they can't be used
for downgrades. You can use a valid product key to move from the evaluation version (Trial Edition) of Exchange 2013 to either Standard Edition or Enterprise Edition.
You can also use a valid product key to move from Standard Edition to Enterprise Edition.

Incorrect Outlook Anywhere Settings

Hi
We are using Exchange 2013 and everything seems to be working ok. However, if I look at any of our Outlook clients (2007 & 2010) there seems to be incorrect information in the Exchange Proxy Settings under the advanced account settings.
For some reason the Use this URL to connect to my proxy server for Exchange box is populated with the server name of our CAS server. I've checked on the Exchange 2013 admin centre and the internal and external hostnames for Outlook Anywhere are correct
but the setting in Outlook is always set to the server name.
I've even tried going into Outlook and manually amending the setting but as soon as I restart Outlook the setting automatically changes back. Am I missing something or is there another place where this setting could be picked up from?
Many thanks for your help.

Hi,
As far as I know, Outlook Exchange Proxy Settings dialog box always displays the internal host name as the Proxy server in an Exchange Server 2013 environment:
http://support.microsoft.com/kb/2754898/en-US
Thus, I’d like to confirm if the server name is the internal host name.
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Outlook 2013 not connect with Exchange server 2013 in internal network

Hello All,
I Have two Exchange server 2013 in our environment. Both server install mailbox and CAS role. After configure exchange server 2013, Outlook 2013 not connect in internal network. I have configure outlook manually. i tried by using the suggestion from blog
but not work. Outlook show that Server cannot connect/ server name could not be resolved. in outlook setting i also put exchange proxy setting. In exchange admin center i have changed the OWA, OAB, Auto discover name. But still not work.
I know that outlook can be connect from external by using ssl certificate and publish outlook anywhere but i did my configure from internal network.
Can you please suggest as soon as possible.
Thanks,
Parvez

Hi,
Firstly, I’d like to explain, same with external users, internal users use Outlook Anywhere to connect with Exchange server and use Autodiscover get all settings.
Thus, let’s try the following resolutions:
1. run the following command: get-clientaccessservice |fl autodiscoverserviceinternaluri
2. check if the host name in the above URL is in the DNS server and there is a DNS entry about the host name points to the proper IP address.
3. Check if the above host name is in your certificate.
Thanks,
Angela
Angela Shi
TechNet Community Support

Outlook Anywhere settings in a Exchange 2013 coexistence scenario with Exchange 2007

Similar Messages

Maybe you are looking for