OWA SSO issues in Exchange 2013 - 2007 co-existence

This may not be possible. For a multitude of reasons the client needs OWA authentication of Windows Integrated and Basic. As a result I''ve got a double prompt for users still on 2007 for OWA externally.
Do you have to use Forms Based Authentication to get SSO to work? Is it possible to enable FBA as well as basic and Windows auth?

FBA is required on the source and destination, yes. You would need to enable that and not use Basic or Windows Auth.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
CAS2013 in Site1 will authenticate the user, do a service discovery, and determine that the mailbox is located within the local AD site on an Exchange 2007 Mailbox server.
CAS2013 will initiate a single sign-on silent redirect (assumes FBA is enabled on source and target) to
legacy.contoso.com. CAS2007 will then facilitate the request and retrieve the necessary data from the Exchange 2007 Mailbox server.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Similar Messages

Exchange 2013 2007 co-existence Outlook Anywhere issues

Sorted out all other issues (apart from a SSO issue- another thread) . Activesync, autodiscover etc all working- but Outlook Anywhere does not work for Exchange 2007 external mailboxes. It does work for 2013 mailboxes internally and externally-
and 2007 mailboxes internally.
Exchange 2013 SP1. Exchange 2007 Sp3 RU10. Legacy namespace is in use and on certificate. Outlook Anywhere IIS Authentication is set to Basic and NTLM on both 2007 and 2013 servers. Outlook Anywhere external client authentication is set to Basic.
Any sugestions what to look at next?

Tony,
I apologize for the stupid question, but was Outlook Anywhere working on Exchange 2007 before you started the upgrade?
When you open command prompt on Exchange 2007 and ping the Exchange 2007 internal FQDN or NetBIOS name, do you get an IPv4 address or you get the IPv6 one?
Step by Step Screencasts and Video Tutorials

RPC over HTTP trouble Exchange 2013/2007 coexistence, 2013 RPCProxy cannot ping GC.

I currently have an Exchange 2013/2007 coexistence scenario which gives me trouble with the RPC over HTTP part with users with a 2007 mailbox. the MS RCA website performs 2 tests with the MAPI address book endpoints, once against a 2007 mailbox server and
once a against a GC/DC, the last one fails. The logs are from our test domain, but the exact same happens in the production domain. running CU8 (recently upgraded, but problem was exactly the same with CU7)
Testing the MAPI Address Book endpoint on the Exchange server.
The address book endpoint was tested successfully.
Additional Details
Elapsed Time: 7872 ms.
Test Steps
Attempting to ping the MAPI Address Book endpoint with identity: exmb11.domain.test:6004.
The endpoint was pinged successfully.
Additional Details
The endpoint responded in 156 ms.
Elapsed Time: 4153 ms.
Testing the MAPI Address Book endpoint on the Exchange server.
An error occurred while testing the address book endpoint.
Additional Details
Elapsed Time: 3079 ms.
Test Steps
Attempting to ping the MAPI Address Book endpoint with identity: tdc01421.domain.test:6004.
The attempt to ping the endpoint failed.
<label for="testSelectWizard_ctl12_ctl06_ctl02_ctl09_ctl00_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
Elapsed Time: 3079 ms.
texmb11 = ex2007 mailbox
texfr11 = ex2007 CAS
tdc01421 = DC/GC
texch31 = 2013 multirole
other symptoms :
Browser test
https://texch31.domain.test/rpc/rpcproxy.dll?texmb11:6004
--> 503 (which is correct)
https://texch31.domain.test/rpc/rpcproxy.dll?tdc01421:6004
--> 404.0 Not Found
RPCPing
rpcping -t ncacn_http -s texmb11 -o RpcProxy=texch31.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Success
rpcping -t ncacn_http -s tdc01421 -o RpcProxy=texch31.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Fails!
so the Ex2013 RPCProxy doesn't proxy to the DC/GC, but the RPCProxy to an ex2007 mailbox server works fine, so the authentication methods configured are correct i'd say..
the same tests using the ex2007CAS server as RPC proxy all succeed!:
MS RCA is all green
https://texfr11.domain.test/rpc/rpcproxy.dll?texmb11:6004
--> 503
https://texfr11.domain.test/rpc/rpcproxy.dll?tdc01421:6004
--> 503
rpcping -t ncacn_http -s texmb11 -o RpcProxy=texfr11.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Success
rpcping -t ncacn_http -s tdc01421 -o RpcProxy=texfr11.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Success!!
Logs
all tries against the 2013 CAS server generate '404' log entries in several logs int the Logging directory, the most explicit being the one in Program Files\Microsoft\Exchange Server\V15\Logging\HttpProxy\RpcHttp : HttpProxy_xxxxxx.LOG
2015-04-30T19:58:00.153Z,895cdf07-f2eb-4beb-b787-da02ba11b0c2,15,0,1076,0,,RpcHttp,webmail.domain.test,/rpc/rpcproxy.dll,,Basic,true,DOM\user,,,MSRPC,10.10.142.132,TEXCH31,404,,MailboxGuidWithDomainNotFound,RPC_IN_DATA,,,,,,,,,4,,,,1,,,0,,0,,0,0,,0,2,0,,,,,,,,,1,1,0,,1,,2,2,,?TDC01422.domain.test:6004,,BeginRequest=2015-04-30T19:58:00.153Z;CorrelationID=<empty>;ProxyState-Run=None;ProxyState-Complete=CalculateBackEnd;EndRequest=2015-04-30T19:58:00.153Z;,HttpProxyException=Microsoft.Exchange.HttpProxy.HttpProxyException:
RPC server name passed in by client could not be resolved: TDC01422.domain.test at Microsoft.Exchange.HttpProxy.RpcHttpProxyRequestHandler.ResolveToDefaultAnchorMailbox(String originalRpcServerName String reason) at
Microsoft.Exchange.HttpProxy.RpcHttpProxyRequestHandler.ResolveAnchorMailbox() at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.InternalBeginCalculateTargetBackEnd(AnchorMailbox& anchorMailbox) at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<BeginCalculateTargetBackEnd>b__3b();
the error suggests the name could not be resolved. but nslookup works fine. i can ping the tdc01421 correctly form texch31, it returns me the ipv4 address. i can telnet to port 6004 from texch31 server to tdc01421 giving me the correct 'ncacn_http' answer..
i look at the 'ValidPorts' and ValidPorts_Autoconfig_Exchange reg keys and filled them with the same i have on the 2007cas servers (all ex servers, all dc/gc's, all of them with netbios & fqdn ports 6001,6002 & 6004..) but also no success.
im out of ideas by now..

Hello togehter,
if anyone is using the Interim Update (Hotfix) "Exchange2013-KB2997209_2997847-x64-en.msp" please be aware of the following bug in this hotfix:
NOTE: Another issue that we have seen only from some E2013 On-Premises customers who installed
fixes for any of the above E2013 CU6 related issues is that “Using OWA, users cannot create new messages or reply to existing messages” – These are mostly installer issues where OWA files are not copying correctly in the new version directory. Ideally the
content of these two folders, i.e. “V15\ClientAccess\Owa\prem\15.0.995.31” and “V15\ClientAccess\Owa\prem\15.0.995.29” should be identical, now if for any reason, they are not then it can break the OWA experience like described above. Take these steps if you
run into related issues:
-Backup the contents of “15.0.995.31” folder to a different folder/directory
-Copy the files and folders from “15.0.995.29” to “15.0.995.31” folder – this should fix the issue …
Best,
Martin

Exchange 2013/2007 coexistence: The Name on the Security Certificate is Invalid or Does Not Match the Name of the Site.

In the midst of Exchange 2013/2007 coexistence configuration.
Currently:
Exchange 2007:
2 CAS\HUB
1 Mailbox server
Exchange 2013 (2 sites):
LA:
1 CAS
2 MBX servers
MKE:
1 CAS
2 MBX servers.
We purchased a certificate from Digicert and added every SAN name we could think of including "legacy.companyname.com", just to be sure. Added certificate to Exchange 2013 CAS servers and 2007 CAS\HUB boxes. Configured virtual directories on Exchange
2013 MKE-CAS01 but not on Exchange 2013 LA-CAS01. Configured virtual directories to on Exchange 2007 CAS\HUB to point to "legacy.companyname.com".
Mailboxes have not been moved yet. I just wanted to get the coexistence between Exchange 2013/2007 up first but some users (not all) receiving
"The name of the security certificate is invalid or does not match the name of the site" for
"LEGACY.COMPANYNAME.COM". I remember configuring the AUTODISCOVER virtual directory for Exchange 2007. Any ideas? Thank you.

Hi,
Please make sure that the certificate with "legacy.companyname.com" name is enabled for IIS service. We can check it by running the following command in Exchange server 2007:
Get-ExchangeCertificate | FL
Thanks,
Winnie Liang
TechNet Community Support

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 2013 - 2007 coexistence legacy namespace issues

Got an odd config here. Exchange 2007 CCR mode co-existing with split role 2013 servers over 2 Data Centers. Each DC has its own subnet so DAG has 2 IPs. New Certificate purchased with extra legacy namespace and loaded onto ISA and F5 as well as the
exchange servers.
I can send and receive from the Exchange 2013 servers. But I'm struggling to deploy the legacy namespace
Here's where it gets ugly. The client wants to continue (short term) to put legacy.company.com through ISA2006 servers and 2013 traffic through F5 load balancers. On the f5 side the path goes through a firewall then an f5 to the mailgateway
When we cut over to legacy (dns changes etc) OWA suffered intermittent Internal 500 errors. Active sync had to be pointed to webmail to work (we had it set blank as per Steve Goodmans recommendation) and Outlook Anywhere had no connectivity.
Urls were set correctly
Outlook Anywhere -> webmail.company.com
Autodiscover -> webmail.company.com
WebServices -> legacy.company.com
OWA -> legacy.company.com
OAB -> legacy.company.com
UM -> legacy.company.com
ActiveSync -> legacy.company.com
This is our 4th attempt to get this working. We can only work in the small hours so we are all fairly tired. Pointers anyone?

Hello,
Do you mean when the user access mailbox from internet, the load balancing will not occur? If so, I recommend you check your configuration as the following article:
http://technet.microsoft.com/en-us/library/aa997148.aspx .
The user of ISA Server load balancing will eliminates the need for setting up the load balancing cluster on the exchange server CAS side.
If I have any misunderstanding, please free let me know.
Cara Chen
TechNet Community Support

Exchange 2013 - 2007 coexistence - activesync 2007 does not work correctly

Exchange 2013 SP1. On going Saga- Last night we cut over to full co-existence with DNS changes for use of legacy namespace and had to roll back again. We had only two issues but one was considered a show stopper.
The main issue was that Active Sync would not work correctly for 2007 users. It failed the exchange connectivity test and would only work on a device if the domain was entered - or if the legacy namespace was entered manually. That would have meant
chaos for several thousand users so we rolled back. (It worked perfectly for 2013 users).
The error given by the test was "foldersync failed" when I drilled down into the detail. It found autodiscover but failed after the initial handshake. (All other tests passed for 2007 and 2013 users)
We tried:
1. Populating both Autodisover internal and external urls with the legacy namespace
2. Populating only the internal url and leaving the external blank (both 1 and 2 had the same result)
3. Leaving both URLs blank to force 2013 to proxy to the 2007 cas (totally broke it- would not resolve at all)
I don't know if this is related but SSO is failing for 2007 OWA - two prompts.
Environment notes- all internal co-existence is working and the internal LTM F5's are working. Externally we use 2 GTM F5 to the LTM f5's to Ex2013. 2007 has SSL being passed through all the way to the CAS. Servers are split into CAS and MBX over 2 DC's.
Everything else externally was working when we cut over.
any and all help appreciated
Tony

Hi,
Glad to know that you have found the solution.
Thanks for your generous sharing.
Have a nice day : )
Thanks
Mavis
Mavis Huang
TechNet Community Support

OWA/ECP Custom Theme Exchange 2013

Hello,
I've read numerous posts on customizing OWA themes and currently have them in place in my 2010 Exchange environment. I've also used them in 2007 Exchange infrastructures. I've been trying to roll out a similar design in my lab before we go live
with our 2013 migration but I have a few questions. I've read the tech net article (http://technet.microsoft.com/en-us/library/bb201700%28v=exchg.150%29.aspx)
and found no issues with it. Everything works as it should. However, in my current 2010 environment, the paths to the image files are slightly different than they are in 2013.
The biggest problem is that I have to place the headerbgmain.png and headerbgright.png in the ECP folder (Program Files\Microsoft\Exchange Server\V14\ClientAccess\ecp\version\Themes\Default) in addition to the OWA folder (Program Files\Microsoft\Exchange
Server\V14\ClientAccess\Owa\version\themes\default). If I don't do this, the header and the OWA logo won't match when switching between OWA and ECP. So this has worked since the 2010 release of Exchange. Not certain if this is supported or
not.
Moving forward, how do I ensure that the two image files get propogated between OWA and ECP without a disconnect as the file path no longer exists for ECP and there is no documentation on how to go about doing this? I've got the OWA part working
without any issues in 2010. Just not certain how to go about it in my 2013 lab and would like to know before I can go ahead with the migration. Thanks for any help!

Hi,
Please refer to the following article :
How to Customize the Outlook Web App (OWA)Sign-In page in Exchange 2013
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.
Best regards,
Niko Cheng
TechNet Community Support

Read receipt issue in exchange 2013

Hi All,
In my environment ,we are having exchange 2013 sp1 ENT edition with outlook 2010 and 2013 as the email client for the exchange users having their default email delivery to pst file .
In addition to that , if anyone of the sender send an email with read recipient option to the particular recipient who is having the default email delivery to pst file will generate an error message to the sender .
Note : Above issue is not happening for all the users having their default email delivery to pst file but for some users .
Error message : Your message was deleted without being read .
Steps handled :
1.) I have set the recipient mailbox message configuration to never send an read response but still the response is going to the sender.
2.) Checked the outlook versions.
Please do not ask us to have the default email delivery to exchange mailbox and it is not possible in our environment.
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Hi Niko Cheng ,
Sorry for delay and thanks for your response.
Did the sender use outlook 2010 or 2013?
We are facing the same issue in both the versions
Is there the same issue when send an email with read recipient option via OWA?
Same is happening in outlook as well as in owa.
How did you set the outlook 2013 client to deliver email to pst file?
When we go to outlook account settings there is an option called "change folder" ,on that we
have set the pst file as the default delivery mail location .
As suggested ,We have moved the mailboxes from one database to another database , But still we are facing
the issue.
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Cross-forest access to public folders Exchange 2013-2007

Dear.
We have an Exchange 2007 org in one forest and an Exchange 2013 org in another forest.
User accounts remain in the 2007 AD, mailbox moved to Exchange 2013 in the other forest, so a linked mailbox.
What do I need to do in the Exchange 2007 public folders to give the migrated mailboxes (not migrated users) access to these public folders?
Thanks for the support.
Regards.
Peter Van Keymeulen, IT Infrastructure Solution Architect, www.edeconsulting.be

Hi Stephen,<o:p></o:p>
<o:p> </o:p>
Do you have trust between Exchange 2007 forest and Exchange 2013 forest? Please set up a trust between the two forests. Then set the public folder client permission
to see if we can access the
public folders.<o:p></o:p>
<o:p> </o:p>
If not, since Public folder cross forest migration is not supported in from an Exchange 2007/2010 forest to an exchange 2013 forest, refer to forum:
http://social.technet.microsoft.com/Forums/office/en-US/51da1b97-fbb1-4f81-87da-c3370960c4ab/crossforest-public-folder-migration?forum=exchangesvrdeploy
http://social.technet.microsoft.com/Forums/office/en-US/663f0dc3-a977-408a-93c7-94584fbefc62/public-folder-issue-cross-forest-migration-exchange-2010-to-2013?forum=exchangesvrdeploy
<o:p></o:p>
Title: Migrate Public Folders to Exchange 2013 From Previous Versions<o:p></o:p>
Link:
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx<o:p></o:p>
<o:p> </o:p>
So for public folder migration,
the only supported path is cross forest 2007/2010 to 2007/2010 and then inter forest 2007/010 to 2013. Or
we can first export all the public folder to PST from the Exchange 2007 forest, then import the PST to the Exchange 2013 forest.
<o:p></o:p>
Regards, Eric Zou

OWA :( something went wromg -exchange 2013

hi
I have another fresh exchange 2013
i cant login to owa with error : :) something went wrong
It seems authentication issue
Ecp is working with no issues .
Identity : EXCHCASSRV1\owa (Default Web Site)
Name : owa (Default Web Site)
InternalUrl : https://exchcassrv1.corp.net/owa
ExternalUrl :
ClientAuthCleanupLevel : High
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : True
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Identity : EXCHCASSRV2\owa (Default Web Site)
Name : owa (Default Web Site)
InternalUrl : https://exchcassrv2.corp.net/owa
ExternalUrl :
ClientAuthCleanupLevel : High
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : True
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Identity : EXCHMBXSRV1\owa (Exchange Back End)
Name : owa (Exchange Back End)
InternalUrl :
ExternalUrl :
ClientAuthCleanupLevel : High
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated}
BasicAuthentication : False
WindowsAuthentication : True
DigestAuthentication : False
FormsAuthentication : False
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Identity : EXCHMBXSRV2\owa (Exchange Back End)
Name : owa (Exchange Back End)
InternalUrl :
ExternalUrl :
ClientAuthCleanupLevel : High
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated}
BasicAuthentication : False
WindowsAuthentication : True
DigestAuthentication : False
FormsAuthentication : False
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
[PS] C:\Windows\system32>^A
need help
MCP MCSA MCSE MCT MCTS CCNA

Hi,
Since your ECP can work fine, please run the following command and post the results here:
Get-EcpVirtualDirectory | FL Identity,*Authentication*,*URL*
Please note to set the Authentication method by using EMS or EAC instead of IIS manager. Just restart IIS service after changing any authentication settings in Exchange.
Regards,
Winnie Liang
TechNet Community Support
[PS] C:\Windows\system32>Get-EcpVirtualDirectory | FL Identity,*Authenticat
Identity                      : EXCHCASSRV1\ecp (Default Web Site)
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication           : True
WindowsAuthentication        : False
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
InternalUrl                   :
https://exchcassrv1/ecp
ExternalUrl                   :
https://exchcassrv1/ecp
Identity                      : EXCHCASSRV2\ecp (Default Web Site)
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated}
BasicAuthentication           : False
WindowsAuthentication         : True
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
InternalUrl                   :
https://exchcassrv2.corp.net/ecp
ExternalUrl                   :
[PS] C:\Windows\system32>
Also find the same from EXCHCASSRV2:
[PS] C:\Windows\system32>Get-EcpVirtualDirectory | FL Identity,*Authentication*,*URL*
Identity                      : EXCHCASSRV1\ecp (Default Web Site)
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
InternalUrl                   :
https://exchcassrv1/ecp
ExternalUrl                   :
https://exchcassrv1/ecp
Identity                      : EXCHCASSRV2\ecp (Default Web Site)
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated}
BasicAuthentication           : False
WindowsAuthentication         : True
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
InternalUrl                   :
https://exchcassrv2.corp.net/ecp
ExternalUrl                   :
[PS] C:\Windows\system32>
MCP MCSA MCSE MCT MCTS CCNA

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

Backup Issue of exchange server 2007 mailbox store

Dears
Exchange server 2007 with CCR clustering
I have got a problem with the backup of one of my mailbox store. Its going till the last and giveing the final error as follows:-
V-79-57344-65247 - A failure occurred reading an object.
Also the warning as follows:-
Backup- \\mailserver.domain\Microsoft Information Store\First Storage Group
WARNING: "\\mailserver.domain\Microsoft Information Store\First Storage Group\Database" is a corrupt file. This file cannot verify.
Backup V-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. Confirm that all snapped volumes are correctly resynchronized with the original volumes.
Does it mean my information store is really a corrupted file. It has been properly monted and logs are genearting.
Even when I checked the last full backedup log file from the management shell it clearly shows the backing up is properly happened on the log files.
When I checked the event log of Exchnage server I can see these logs:-
Event ID 401, 403 errors
The size of the problem store is 308 GB.
One of the other store with 46 GB is backing up without any issue

Hi,
If you have a space issue with the Exchange server, you can upgrade drives on active node and passive node one by one. It is not recommended to upgrade them at the same time.
For more information about upgrading Exchange 2007 CCR active node or passive node, here are some helpful threads for your reference.
Upgrade hard drives on passive node. Process and procedure
http://social.technet.microsoft.com/Forums/exchange/en-US/08b9e893-87c9-48c3-bab2-91027cc09949/upgrade-hard-drives-on-passive-node-process-and-procedure?forum=exchangesvravailabilityandisasterrecoverylegacy
Upgrading hard drives in exchange server
http://social.technet.microsoft.com/Forums/exchange/en-US/0e4514f9-76da-44d2-9dec-a3be5add79b1/upgrading-hard-drives-in-exchange-server?forum=exchangesvravailabilityandisasterrecoverylegacy
Hope it helps.
Best regards,
Amy
Amy Wang
TechNet Community Support

Outlook 2007 - single profile connecting to Exchange 2013 / 2007 mailboxes

Hi,
I am in the early part of a migration from Exchange 2007 to Exchange 2013. So far I have 2013 installed and running in a DAG and just moved my own mailbox to the new server.
I set up a new profile in Outlook 2007 which connects to my mailbox on Exchange 2013. The problem is that I need to add additional mailboxes to my profile which are still hosted on Exchange 2007, however this is not working.
I thought at one stage I tested this and was able to get it work with a test mailbox also hosted on Exchange 2013.. but maybe I never did.
Does anyone know if this is possible at all (single Outlook profile, primary mailbox hosted on Exchange 2013 and other mailboxes on Exchange 2007). Most of our users have an additional mailbox mapped in their profile so I hope there is some way around this.
Thank you!

Hi,
It is possible to open a shared mailboxes on a legacy server.
Your problem could be caused by:
Not having one of the later CU installed (read CU4 or CU5)
Incorrect authentication methods configured (see link below)
Outlook is not at the latest patch level
Users of Exchange Server 2013 can't open public folders or shared mailboxes on an Exchange 2010 or Exchange 2007 server
http://support.microsoft.com/kb/2834139
Martina Miskovic

Search issues with Exchange 2013

The search service no longer works. I have tried with stopping the Exchange Search Service and deleting the folder associated with the databases to no avail.<o:p></o:p>
When I run Get-MailboxDatabaseCopyStatus -Server "NAMEofServer" | Format-Table Name,Status,ContentIndex* -Auto through PS I receive
the below output.<o:p></o:p>
"Database" Mounted Unknown Could not find registry value of Index Status for database {a8281541-35b3-4e9b-b124-4adfa7ebf2d1}.
<o:p></o:p>
I then look to the registry location below to find absolutely nothing in there! No keys, no reference, nothing!<o:p></o:p>
\HLM\Software\Microsoft\ExchangeServer\v15\Search\IndexStatus\<o:p></o:p>
I cannot seem to resolve the search / indexing issues at all. The server is NOT a part of a DAG and issues extend to all 4 databases.<o:p></o:p>
I also am having issues that might be related when trying to move mailboxes to a different databases (same server). "I did try restarting the
replication service"<o:p></o:p>
The RPC call failed with result 'StorageTransientError'<o:p></o:p>
Any help in the right direction would be appreciated. I have had this issues since CU6.<o:p></o:p>
Thank you!<o:p></o:p>

Hi,
Well, we can try to recreate those registry entries.
Since your server is not a member of DAG, then the registry key should be like this:
{79853a57-6c9e-46a2-a5e3-70db036754f1} : 1,1,4294967297,2013-07-16 00:33:17Z,0,
The initial {GUID} is the GUID of the database.
The double numeric values (1,1;) signify the state[s] of the CI
The first number in the series is the Index Status. The second number in the series is the error code.
Index Status:
Unknown = 0
Healthy = 1
Crawling =2
Failed = 3
Seeding = 4
Failed And Suspended = 5
Suspended = 6
Disabled = 7
Auto-Suspended = 8
Healthy And Upgrading = 9
Error Code:
1 Success
2 Internal Error
3 Crawling Database
4 DatabaseOffline
5 MapiNetworkError
6 Catalog Corruption
7 Seeding Catalog
8 Catalog Suspended
9 Catalog Reseed
10 Index Not Enabled
11 Catalog Excluded
12 Activation Preference skipped
13 Lag Copy skipped
14 Recovery Database Skipped
15 Fast Error
16 Service Not Running
17 Index Timestamp too Old
Note: Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number
to view the article in the Microsoft Knowledge Base: 256986 Description of the Microsoft Windows Registry
Refer from this blog:
http://blogs.technet.com/b/johnbai/archive/2013/07/16/exchange-2013-high-availability-fast-search-and-the-windows-registry.aspx
Please also check if there are any event logs indicated this issue, that will help us to troubleshoot.
Thanks.

OWA SSO issues in Exchange 2013 - 2007 co-existence

Similar Messages

Maybe you are looking for