Exchange 2010/2013 coexistence: OWA proxy not working properly ":-( Something went wrong"

Hi
Exchange 2010 users are NOT able to connect to their mailboxes when they go through exchange 2013 OWA address. We get a message that says following ---> "Something went wrong"
Following is our URL. The address is pointing to 2013 CAS loadbalancer VIP. Outlook anywhere is working fine. What is going on?
Important: All my exchange 2010 / 2013 URIs are the same as suggested by Microsoft (Owa, ecp, activesync, ews, autodiscover): --> mail.domain.com/XXX

Hello Rawa,
Can you log on Exchange 2010 OWA using its localhost address?
Please make sure the intenralurl value is set to Exchange 2010’s local host name and set the Externalurl to Null.
http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).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

Similar Messages

OWA doesn't work internally - something went wrong

When trying to access OWA from internal network (external access is working):
something went wrong
Sorry, we can't get that information right now. Please try again later. If the problem continues, contact your helpdesk.
X-ClientId: NTAW - FMWI - PEOS - SRAWOFA
X-OWA-Error: Unknown;handle boot error failed
X-OWA-Version: undefined
X-FEServer: <server_name>
X-BEServer: undefined
Date: 2/23/2015 6:47:33 PM
Thanks.
Dario Woitasen | MCSE Lync Server 2013/Exchange Server 2013 | MCITP: Enterprise Messaging Administrator 2007/2010, Lync Server 2010 Administrator, Office 365 | MCSA Windows Server 2012

The date information is calculated based on the date of the Exchange server to which the user is connected. In some scenarios (such as network connectiivy failure), the Outlook Web App client-side script is unable to connect to the server to obtain the correct
date.
Please download the update
http://www.microsoft.com/en-us/download/details.aspx?id=44022
This update resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:
2961715
"Something went wrong" error in Outlook Web App may show an incorrect date
Regards,
Ben

Exchange 2010 Out of Office Assistant not working?

New server with a new Exchange 2010 install into an existing domain...
When users on both the internal network and external network try to access the Out of Office Assistant they get an error message of: " Your Out of Office settings cannot be displayed, because the server is currently unavailable".
I have done tons of research on WebServicesVirtualDirectory and AutodiscoverVirtualDirectory and set both internal and external URL's that work if you go to them in IE )internally and externally offsite).
Here are the settings of Autodiscover and Webservices:
[PS] C:\Windows\system32>Get-WebServicesVirtualDirectory | Format-List
RunspaceId : 86aaf7fc-ca19-45b2-87d1-45ec432a670d
CertificateAuthentication :
InternalNLBBypassUrl : https://MAILSERVER.domain_name.local/ews/exchange.asmx
GzipLevel : High
Name : EWS (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
LiveIdSpNegoAuthentication : False
WSSecurityAuthentication : True
LiveIdBasicAuthentication : False
BasicAuthentication : True
DigestAuthentication : False
WindowsAuthentication : True
MetabasePath : IIS://MAILSERVER.domain_name.local/W3SVC/1/ROOT/EWS
Path : C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS
Server : MAILSERVER
InternalUrl : https://MAILSERVER.domain_name.local/EWS/Exchange.asmx
ExternalUrl : https://mail.domain_name.com/owa
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
DistinguishedName : CN=EWS (Default Web Site),CN=HTTP,CN=Protocols,CN=MAILSERVER,CN=Servers,CN=Exchange Adm
inistrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=M
icrosoft Exchange,CN=Services,CN=Configuration,DC=domain_name,DC=local
Identity : MAILSERVER\EWS (Default Web Site)
Guid : 4639e4b9-9cf3-4f92-8940-f7c31e07cd47
ObjectCategory : domain_name.local/Configuration/Schema/ms-Exch-Web-Services-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchWebServicesVirtualDirectory}
WhenChanged : 4/1/2010 2:47:37 PM
WhenCreated : 3/11/2010 11:02:22 AM
WhenChangedUTC : 4/1/2010 8:47:37 PM
WhenCreatedUTC : 3/11/2010 6:02:22 PM
OrganizationId :
OriginatingServer : DOMAINCONTROLLER.domain_name.local
IsValid : True
[PS] C:\Windows\system32>AutodiscoverVirtualDirectory | Format-List
RunspaceId : 86aaf7fc-ca19-45b2-87d1-45ec432a670d
Name : Autodiscover (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
LiveIdSpNegoAuthentication : False
WSSecurityAuthentication : True
LiveIdBasicAuthentication : False
BasicAuthentication : True
DigestAuthentication : False
WindowsAuthentication : True
MetabasePath : IIS://MAILSERVER.domain_name.local/W3SVC/1/ROOT/Autodiscover
Path : C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Autodiscover
Server : MAILSERVER
InternalUrl : https://MAILSERVER.domain_name.local/autodiscover/autodiscover.xml
ExternalUrl : https://mail.domain_name.com/autodiscover/autodiscover.xml
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
DistinguishedName : CN=Autodiscover (Default Web Site),CN=HTTP,CN=Protocols,CN=MAILSERVER,CN=Servers,CN=Exc
hange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organiza
tion,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain_name,DC=loca
l
Identity : MAILSERVER\Autodiscover (Default Web Site)
Guid : 7a234ea2-20fc-412b-bbf0-3ea5f965d8da
ObjectCategory : domain_name.local/Configuration/Schema/ms-Exch-Auto-Discover-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchAutoDiscoverVirtualDirectory}
WhenChanged : 4/1/2010 3:00:49 PM
WhenCreated : 3/11/2010 11:02:07 AM
WhenChangedUTC : 4/1/2010 9:00:49 PM
WhenCreatedUTC : 3/11/2010 6:02:07 PM
OrganizationId :
OriginatingServer : DOMAINCONTROLLER.domain_name.local
IsValid : True
Test-OutlookWebServices comes up with errors. The Test E-mail AutoConfiguration within Outlook still appears to be looking for Autodiscover at different URLs...
OOF within Outlook Web App functions.
Any suggestions would be helpful!

From your previous post, I understand that OOF doesn't work for both internal and external clients. Error message "Your Out of Office settings cannot be displayed, because the server is currently unavailable" was received from Outlook client side. Please correct me if I have any misunderstanding.
Before we go any further, I would appreciate your help in clarifying the following questions:
1. When did this issue begin to occur, since the installation of Exchange 2010?
2. Can we access and configure OOF from OWA?
As internal & external clients are using different methods/URL to access Autodiscover and EWS, which provided OOF service, I recommend we focus on the internal users first.
To troubleshoot this issue, please install the hotfix mentioned in the following KB on the Exchange Client Access Server first:
Outlook 2007 crashes or you cannot access OOF settings after you install a package that contains the .NET Framework 3.5 with SP1 and the .NET Framework 2.0 with SP2 on an Exchange 2007 Client Access server or on an Exchange 2010 Client Access server
http://support.microsoft.com/kb/958934
After that, check if the issue remains. If there is still problem, please help me collect:
1. Test E-mail AutoConfiguration from Outlook client
1. Launch Outlook 2007 using a correct configured profile.
2. Hold down the CTRL key on your keyboard and click the Outlook icon in the notification area of the Windows taskbar, also known as the notification area.
3. In the menu that appears, click Test E-mail AutoConfiguration.
4. Enter your E-mail Address and Password (if not logged into the domain) in the respective edit boxes.
5. Choose the desired auto configuration methods with Use Autodiscover, clear other selection.
6. Click Test.
7. Please send me the screenshot of the result tab and log tab.
2. Result files after running the following command on the Exchange 2007 server
Get-ExchangeCertificate | FL >C:\cert.txt
Get-WebServicesVirtualDirectory –Server ServerName | FL >C:\EWS.txt
Get-AutodiscoverVirtualDirectory –Server ServerName | FL >C:\Audis.txt
Get-ClientAccessServer | FL >C:\cas.txt
Email them to me at [email protected]
With the title as
"Exchange 2010 Out of Office Assistant not working?"
Regards
Fazal M khan

Outlook client requirements and Exchange 2010/2013 coexistence

Good morning!
A question regarding Exchange 2010/2013 coexistence and the Outlook client requirement. I am upgrading and about to install Exhange 2013 into an existing Exchange 2010 Org. The current 2010 Org is patched to SP-3 and Outlook Anywhere is currently disabled.
I have Outlook clients that do not yet meet the minimun requirements for 2013 (Outlook 2007/2010). When I install my first 2013 server will it effect the current downlevel clients? The mailboxes are still in 2010 so my thoughts were since the Office upgrade
including Outlook has not yet taken place I didn't want to wait for them to at least get 2013 into the Org. The 2013 server should effect the clients until I configure the CAS on 2013 and only when they are at the proper version, is this correct? Does Outlook
Anywhere need to be first enabled and configured on the 2010 CAS before I attempt the confgiuration on the 2013 CAS? I just dont want to install 2013 and have Outlook connectivity issues right out of the gate...
Thanks in advance!

Outlook 2007 and 2010 are supported for Exchange 2013, you just need to push out the latest patches.
http://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
If you configure the URLs properly in Exchange 2013 to URLs that point to the Exchange 2010 servers, your clients shouldn't try to talk to the Exchange 2013 server.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Sharepoint 2010 windows authendication(NTLM) is not working properly in IPad safari browser

Hi Apple Team,
Sharepoint 2010 windows authendication(NTLM) is not working properly in IPad safari browser. When I enter the user name and password the page is keep on loading it never completes the page load. I installed chrome browser on my Ipad and opened my sharepoint windows authentication site it is working fine.
Device : IPad 2
OS : IOS 7.0.6
Thanks,
Baskar

Hi Suhasini,
Please refer below links for your issues. It seems you are having problem with 32 bit and 64 bit component in office and IE.
http://howididit-sharepoint.blogspot.in/2012/04/datasheet-view-not-working.html
http://alpesh.nakars.com/blog/datasheet-view-does-not-work-in-sharepoint-2010/http://support.microsoft.com/kb/2266203
Thanks and Regards, Shailesh B. Davara

Exchange 2010 CAS Mailbox Re-direction / Proxying Not Working Properly

Hello Team
In my Exchange 2010 Lab Setup, CAS proxy is not working properly
In Site A : One DC , One HUb Server , 2 CAS Server (CAS ARRAY WIndows NLB), Mailbox Server 2 (DAG)
In Site B : One ADC one hub and CAS( Both are in same box) One Mailbox
Internal and External for SITE A on Server CASARRAY1.labbites.co.in is https://casarray1.labbites.co.in/owa and https://casarray1.labbites.co.in/owa
Internal and External for SITE A on Server CASARRAY2.labbites.co.in is https://casarray2.labbites.co.in/owa and https://casarray2.labbites.co.in/owa
DNS recory casarray.labbites.co.in is present
Internal and External for SITE B on Server INDLBGUEX01.labbites.co.in is https://indlbguex01.labbites.co.in/owa and https://indlbguex01.labbites.co.in/owa
The problem is occurs , whenever the second CAS server casarray2.labbites.co.in is down (Shutdown)
Now , when the user ifrom site A s trying to log in to the OWA with SITE B OWA LINK https://indlbguex01.labbites.co.in/owa it redirects to always https://casarray2.labbites.co.in/owa , since casarray2 server is down the OWA page
is not opening
My Question is Why the proxy re-direction is always going to second casarray2 server instead of casarray.labbites.co.in
how to correct it . please help me to over come the issue

Hi Albert
Thanks for you update
Get-mailboxdatabase | FT name, RPC*
Name RpcClientAccessServer
DB1 casarray.labbites.co.in
DB2 casarray.labbites.co.in
DB3 casarray.labbites.co.in
Site B Mbx -DB1 INDLBGUEX01.labbites.co.in
The user is administartor who beloings to DB1 and accesing the OWA from the SITE B CAS server link https://indlbguex01.labbites.co.in/owa
and it is redirecting to https://casarray2.labbites.co.in/owa
so as per the above
output , should i make RPCclientaccess server for Site B Mbx -DB1 as casarray.labbites.co.in

Search-Mailbox not attaching the infected emails in target folder and deleting the contents in exchange 2010 & 2013 coexistence

Dear All,
I have an issue with deleting circulated spam emails in my environment through search-mailbox
We have Exchange 2010 & 2013 CU5 environment
I followed the search and destroy document for exchange 2010
http://windowsitpro.com/exchange-server-2010/search-destroy-email-content-exchange-2010
Added the user to Discovery Management group
Created a new role group as below
New-RoleGroup "Mailbox Import-Export Management" -Roles "Mailbox Import Export"
Add-RoleGroupMember "Mailbox Import-Export Management" -Member Administrator
I ran the below commands
Search-Mailbox -Identity "[email protected]" -SearchQuery "Subject:'report'" -TargetMailbox "Administrator" -TargetFolder "Filter" -LogOnly -LogLevel Full
The above command gets completed successfully and sends the log report however im unable to see any attachments
Similarly the deletecontent also gets completed successfully and logs result. But it does not delete the infected emails
Search-Mailbox -Identity "[email protected]" -SearchQuery "Subject:'report'" -TargetMailbox "administrator" -TargetFolder "filter" -deletecontent -LogLevel Full
Any idea why it is not fetching the infected emails in zip file and why it is not deleting but it is able to log in the target folder
Any help much appreciated
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish (MVP)

Hi All
I managed to find the solution. Below command helped me in solving the issue
get-mailbox -ResultSize unlimited -IgnoreDefaultScope | search-mailbox -SearchQuery ‘Subject:"virus infected"’ -LogOnly -TargetMailbox administrator -TargetFolder filter -LogLevel Full
get-mailbox -ResultSize unlimited -IgnoreDefaultScope | search-mailbox -SearchQuery ‘Subject:"virus infected"’ -TargetMailbox administrator -TargetFolder filter -deletecontent -LogLevel Full
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

My Macbook is not working properly, I went to a Genius Bar appointment, they were not helpful at all and just told me to go off and reboot my Mac and then restore via TimeMachine. I dont know how to do this. I am extremely displeased with Apple, help me?

My late 2011 Macbook Pro is not working properly it is very slow and extremely painful to use, I went to a Genius Bar appointment, they were not helpful at all and just told me to go off and reboot my Mac and then restore via TimeMachine. I dont know how to do this. I am extremely displeased with Apple at the moment, can someone please help me?

Your problem description is generalized and non-specific. I would make another appointment at the Apple store and insist they help you execute their suggested fixes.
Incidentally, if you search this site, Apple has excellent articles re: restoring a system.
Barry

Exchange 2013 CU2 OWA Redirection not working

Hi,
I installed Exchange 2013 RTM in existing environment with Exchange 2010 Sp3 in our test environment. After installing Exchange 2013 RTM I checked when I access OWA using Internal URl it redirected to Exchange 2010 CAS server's Internal URL and I was
able to access Exchange 2010 mailbox.
I upgraded to CU2 and now Exchange 2013 internal URl not re-directing it to Exchange 2010 mailbox anymore. I checked all the settings on virtual directories and made sure that FBA authentication is selected. It is a test environment and I just wanted
to test the re-direction in co-existence environment using Internal URL. It should work out of the box but not sure what happened. There was no issue in CU2 instllation.
Exchange 2013 CAS and mailbox roles are on separate servers. Same with Exchange 2010. There is no certificate 3rd party certificate install on CAS servers since it is a test environment.
Not sure what else can I check.
I appreciate if any help I can get.
Thanks,
Regards
Raman
Raman

I have been seeing issue where 2013 OWA was not re-directing to Exchange 2013, as mentioned on top of this thread. After spending days over it.
Finally it resolved for me after doing the following: -
Go to CAS 2010 IIS
OWA directory -> Authentication -> Windows Authentication -> Add provider
Negotiate and NTLM.
Although, now when I click on "Options" once OWA is redirected to 2010. ECP does
not work. It just open up ECP page but no link works not even sign out. I had to click back on the browser's back button go get back to main OWA mail page.
OWA and ECP directory settings are same. I have checked several times.
Thanks,
Raman

Exchange Server 2013 OAB Web Distribution Configuration in Exchange 2010 & 2013 Coexistence.

Hi,
We have OAB Issue for Exchange 2010 Users in our Organization.
We have Exchange 2010 and Exchange 2013 Coexistence.While Checking in Exchange Server 2010 Server OAB properties in Org Configuration--> Mailbox-->OAB Properties -->Distribution we are not seeing any CAS servers and Its Grayed Out.
Please let us know How to add Exchange 2010 CAS in Exchange 2013 Web distribution.

They made alot changes with the OAB in Exchange 2013, and it doesn't really function in the same manner as it did in 2010. It might be best to take a look at the following blog posts from the Exchange Team, they should give you a better understanding
on how it works and how to manage it going forward.
http://blogs.technet.com/b/exchange/archive/2012/10/26/oab-in-exchange-server-2013.aspx
http://blogs.technet.com/b/exchange/archive/2013/01/14/managing-oab-in-exchange-server-2013.aspx
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

Missed Call Notification in Exchange 2010/2013 coexistence mode

Dear all,
Context:
Lync 2013 Enterprise Voice, Exchange 2010 and Exchange 2013 in coexistence mode
Waiting complete migration, some users are always on exchange 2010
UM role is installed on both exchange server
The exchange servers UM are attached to only one UM Dial Plan
Scenario :
A call to a lync user. The caller hang-up before user announcement
Problem: Missed call notification doesn't work for user on Exchange 2010 (it's work fine for user on Exchange 2013)
Voice Messaging works fine
Troubleshooting / SIP Traces:
SIP Info is always send to Exchange 2013 even if user is on exchange 2010
SIP Info sent from Lync FE to Exchange 2013 UM :
TL_INFO(TF_PROTOCOL) [0]6330.3AE8::02/12/2015-12:25:23.575.015c018e (S4,SipMessage.DataLoggingHelper:sipmessage.cs(774))[1718622663]
>>>>>>>>>>>>Outgoing SipMessage c=[<SipTlsConnection_13ECA29>], 192.168.5.110:49786->192.168.5.203:5061
INFO sip:outlook.mydomain.com:5061;ms-fe=exchange2013-UM.mydomain.localdomain;transport=Tls SIP/2.0
FROM: <sip:A410AA79-D874-4e56-9B46-709BDD0EB850>;epid=8C75BE2D95;tag=35c2d8a65a
TO: <sip:exchange2013-UM.mydomain.localdomain;opaque=app:rtcevent;transport=tls>;epid=C4C2F4F6BA;tag=ac126413f
CSEQ: 43 INFO
CALL-ID: 535a07e2-8e82-4d13-8e03-bf43ad97602d
MAX-FORWARDS: 70
VIA: SIP/2.0/TLS 192.168.5.110:49786;branch=z9hG4bKd66442be
CONTACT: <sip:LyncFE-2013.mydomain.localdomain;transport=Tls>
CONTENT-LENGTH: 454
USER-AGENT: RTCC/5.0.0.0 Inbound Routing (Microsoft Lync Server 2013 5.0.8308.726)
CONTENT-TYPE: application/ms-rtc-usernotification+xml
- <UserNotification>
       <User>sip:[email protected]</User>
       <EumProxyAddress>EUM:[email protected];phone-context=UMDialPlan.mydomain.localdomain</EumProxyAddress>
       <Time>2015-02-12 12:25:23Z</Time>
       <Template>RtcDefault</Template>
    + <Event type="missed">
</UserNotification>
------------EndOfOutgoing SipMessage
Answer from Exchange 2013 UM
TL_INFO(TF_PROTOCOL) [1]6330.2DF4::02/12/2015-12:25:23.642.015c2481 (S4,SipMessage.DataLoggingHelper:sipmessage.cs(774))[1718622663]
<<<<<<<<<<<<Incoming SipMessage c=[<SipTlsConnection_13ECA29>], 192.168.5.110:49786<-192.168.5.203:5061
SIP/2.0 200 OK
FROM: <sip:A410AA79-D874-4e56-9B46-709BDD0EB850>;tag=35c2d8a65a;epid=8C75BE2D95
TO: <sip:exchange2013-UM.mydomain.localdomain;opaque=app:rtcevent;transport=tls>;tag=ac126413f;epid=C4C2F4F6BA
CSEQ: 43 INFO
CALL-ID: 535a07e2-8e82-4d13-8e03-bf43ad97602d
VIA: SIP/2.0/TLS 192.168.5.110:49786;branch=z9hG4bKd66442be
CONTENT-LENGTH: 0
SUPPORTED: ms-dialog-route-set-update
SERVER: RTCC/5.0.0.0 MSExchangeUM/15.00.0995.028
ms-diagnostics-public: 15642;reason="Lync SIP INFO notifications are not supported for legacy users. User: EUM:[email protected];phone-context=UMDialPlan.mydomain.localdomain"
------------EndOfIncoming SipMessage
Gerald Cheminant

Hi,
This behavior is by design. Exchange 2010 server is not going to accept any SIP messages from Exchange 2013 server because it is not listed as UM IP Gateway. Therefore, even if Exchange 2013 redirected the SIP INFO packet to Exchange 2010, it will fail.
During migration\coexistance scenario, this feature (Missed call notifications from Lync server) will not work for legacy users whose mailbox is still in Exchange 2010.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Exchange 2010+Outlook Anywhere+Windows XP not working together

Hello,
We have Exchange 2010 installed on Server 2008 R2. CAS/Hub/mailbox roles on same server. Outlook Anywhere is enabled and using a Go Daddy signed certificate for OWA. Now my problem is that Windows XP (w SP3) PC's that are not located inside domain and
shoud use Outlook Anywhere cannot connect to that service. Outlook version is 2007 SP2. On the other hand, that same user can connect from a Windows 7 pc what is also located outside domain without problems. On XP pc windows keeps asking for password repeatedly,
on W7 pc it asks it and accepts and logs the user in and connects it to his mailbox. I have read numerous posts about this kind of issue, put so far none of them helped me. The certificate is issued to mail.domainname.ee and autodiscover.domainname.ee. The
internal name of the server is excha.domainname.ee, external name is mail.domainname.ee. Also I used the Set-OutlookProvider cmdlet to set EXPR to msstd:mail.domainname.ee and also tried msstd:excha.domainname.ee this change did not have any effect on XP pc.
What is wrong in XP and Outlook 2007 combination not being able to connect to Echange 2010?

I was suffering from a very similar issue. The one major difference for me is that I was using a wildcard ssl certificate for "*.contoso.com" which was not matching with the server name of owa.contoso.com.
Behaviour definitely seemed to only manifest with Windows XP on the open internet (not domain joined or internal) trying to use either Outlook 2007 or 2010 to connect to our internal Exchange 2010 server via RPC over HTTPS. Autodiscover was successful
but user would be repeatedly prompted for their credentials but they would never match.
The key changes that seemed to fix this for us were to make these updates -
Set-OutlookProvider EXPR -CertPrincipalName msstd:*.contoso.com
alternatively if you dont care whether the proxy server name exactly matches your ssl cert you can do this (not recommended) -
Set-OutlookProvider EXPR -CertPrincipalName none
These commands manipulate the Microsoft Exchange Proxy Settings under the Outlook Anywhere options under the connection tab of your mail profile. In particular the field labeled "Only connect to proxy servers that have this principal name in their
certificate"
Also, to force RPC over HTTPS and never try and timeout on TCP/IP connection (which cannot work through the firewall) -
Set-OutlookProvider EXPR -OutlookProviderFlags:ServerExclusiveConnect
This should click the checkbox for "On fast networks, connect using HTTP first, then connect using TCP/IP"
This should then allow autoconfigure to work fine when setting up your mail profile. If you want to check the settings page you should have something that looks like this -
Finally, please note that Autodiscover settings are updated periodically not instantly. I believe it is something like every 15m or so. As such, make the changes above and then wait for at least 15-30mins before making any other changes.
I ended up chasing my tail and then some complete red-herring *seemed* to fix the problem. It was actually something that I had changed 20mins before!

Exchange 2013 + 2007 OWA coexistance not redirecting properly (HTTP 400)

Hello. I am using this document to funnel our new Exchange 2013 external traffic through an IIS ARR reverse proxy, much like we already do for MIcrosoft
Lync 2013 on this machine.
http://blogs.technet.com/b/exchange/archive/2013/08/02/part-2-reverse-proxy-for-exchange-server-2013-using-iis-arr.aspx
I followed this guide to a T. especially the part on the page 2 that I linked above about creating the legacy.domain.com server farm and URL rewrite rule. This
IIS ARR proxy seems to work fine for Outlook Anywhere, ActiveSync, OWA if the user's mailbox is on the Exchange 2013 server, but it does not work if an OWA user logs in with a mailbox on 2007.
When the user has a mailbox on 2007, after logging into OWA they get HTTP 400 error. The URL bar in the browser is changed to https://legacy.domain.com/owa/auth/owaauth.dll
The Exchange 2007 server IIS logs show this:
70.x.x.x, -, 11/1/2014, 9:45:48, W3SVC1, MAIL, 10.1.1.3, 0, 523, 132, 400, 0, POST, /owa/auth/owaauth.dll, -,
I can't figure out why this is happening. DNS is correct. legacy.domain.com points to the 2007 Exchange server. webm.domain.com points to the
Exchange 2013 server.
Any ideas?

Doing more testing, I almost think the Exchange 2007 server keeps redirecting. So the HTTP 400 is because when you hit legacy.domain.com, it redirects
to webm.domain.com which redirects back to legacy.domain.com and vice versa.
I put a test.txt file in the Exchange 2007 owa virtual directory and I cannot access it in any browser. I tried https://legacy.domain.com/owa/test.txt and
It redirects me to https://webm.domain.com(Exchange 2013). I can however go
one level (or more) deep on the legacy server and get a file such as https://legacy.doamin.com/owa/8.3.342.1/themes/base/logon.css and
in the browser I see the code (both externally AND internally, so I know DNS and firewall is working).
I can't find anywhere on IIS 6.0 on the Exchange 2007 server where any kind of redirection is taking place though. Virtual Directory properies for owa say
"A directory located on this computer: "C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa" Enable default content page is checked with default.aspx but I looked at default.aspx in notepad and I don't see ANY code telling it to
redirect.
In Exchange 2007 management console OWA internal URL and External URL both sayhttps://legacy.domain.com/owa .
I have no idea what is causing this redirection. I did an iisreset and also recycled the OwaAppPool and no change.

Exchange 2010/2013 coexistence published in TMG 2010

Environment:
Two Windows 2008 R2, Exchange 2010 SP3 servers, currently holding all mailboxes
Two Windows 2012 R2, Exchange 2013 SP1 servers, setup in progress
Two Windows 2008 R2, TMG 2010, V7.0.9193.540 publishing both Exchange 2010 servers.
Scenario:
I need to continue having Exchange 2010 setup in TMG as is as the mailbox migration to 2013 will take weeks if not months and I have a project requirement to have Exchange Database Availability Group (DAG) functionality for all mailboxes throughout the project,
so 4 servers are an absolute must. So I need to add Exchange 2013 in TMG and not just replace the 2010 setup with the 2013 setup and I cannot run one 2010 and one 2013 server.
Questions:
1. I currently only have 2 public IP addresses available to SMTP, mapped to the external interfaces of TMG, to allow my environment to be able receive emails on 4 Exchange servers (two 2010 and two 2013) I need to have 4 public IP addresses, is that correct?
2. Does anyone have a good general guide/blog for doing this (setting up Exchange 2013 in TMG in a coexistance scenario)?
This is nice, but doesn't really approach it from a coexistance scenario:
http://blogs.technet.com/b/exchange/archive/2012/11/21/publishing-exchange-server-2013-using-tmg.aspx
Thanks!

Hi Trana,
In TMG you can use single IP address to publish multiple Web address and below are the options which you can explore.
Hope your OWA ECP etc are Https
You need a SSL certificate which has all the URL SAN entry of both old and new Exchange server.
Create a listener and select the IP address (Say public IP address 195.219.x.x)
Link the SSL certificate
Public DNS entry
A record , Single IP
195.219.x.x
Point to
Owa1.exchange1.com   - Old Server
195.219.x.x
Point to
ECP1.exchange1.com     - Old Server
195.219.x.x
Point to
ECP2.exchange2.com      - New Server
195.219.x.x
Point to
Owa2.exchange2.com     - New Server
Create a Web publishing rule as below
Old server Exchange 1
Owa1.exchange1.com
ECP1.exchange1.com
One Web publishing Rule with all the URL added on it and link the Rule with the listener we created
Point the Web publishing to Exchange1.com server which is old
New server Exchange 2
Web publishing Rule with all the URL added on it and link the Rule with the listener we created
Point the Web publishing to Exchange2.com server which is New
ECP2.exchange2.com
Owa2.exchange2.com

Exchange 2010 - 2013 Coexistence Issues

I am migrating from Exchange 2010 to Exchange 2013, the Exchange 2013 is built in a different Geo-location site with its dedicated domain controllers in the new site. I have confirmed the mail flow between Exchange 2010 and 2013 mailboxes. I am able to discover
Exchange 2010 servers from 2013 environment via Get-ExchangeServer shell command. However, I am not to discover Exchange 2013 servers from 2010 environment.
I need to configure Outlook Anywhere and Service Connection Point (Autodiscover) on Exchange 2010 to accept connections from Exchange 2013 servers.
Any suggestions would be much appreciated, thanks!

Hi ,
Please have a look in to the below mentioned blog after reading that blog i came to know few things .
I am not sure ,i thought exchange 2013 servers will not be displayed in exchange 2010 management shell.
Better and advisable method is to configure your exchange 2010 and 2013 servers via EAC or Shell in exchange 2013.
http://exchangeserverpro.com/exchange-server-2010-2013-migration-managing-co-existence-environment/
Taken from the above blog :
You can’t use the Exchange 2010 EMC to manage Exchange 2013 objects and servers. While customers upgrade to Exchange 2013, we encourage them to use the EAC to:
Manage Exchange 2013 mailboxes, servers, and corresponding services.
View and update Exchange 2010 mailboxes and properties.
View and update Exchange 2007 mailboxes and properties.
We encourage customers to use Exchange 2010 EMC to create Exchange 2010 mailboxes.
We encourage customers to use Exchange 2007 EMC to create Exchange 2007 mailboxes.
Customers can continue to perform management tasks using the Exchange Management Shell and script tasks.
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Exchange 2010/2013 coexistence: OWA proxy not working properly ":-( Something went wrong"

Similar Messages

Maybe you are looking for