Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration 论坛
Viewing all articles
Browse latest Browse all 7008

Exchange2010 migration to Exchange 2013 federation trust failed (Outlook Provider Failure)

$
0
0

We are in a migration Exchange 2010 to Exchange 2013.

On the 'old' Exchange 2010 we are using a Federation Trust to 2 order company's. The federation trust for mailbox's on the exchange 2013 wont work.

We removed the federation trust on the old exchange 2010 server and create a new federation trust on the new Exchange 2013 server. We also changes the DNS TXT records. Creating the new federation trust without errors. But when the 2 order company's trying to connect (add our company name for trust) they get a error.

A have trying to run a couple tests on the new Exchange 2013 server and found this error:

 

[PS] C:\Windows\system32>Test-OutlookWebServices -debug -Identity mail@company.com -MailboxCredential(Get-Credential
)

cmdlet Get-Credential at command pipeline position 1
Supply values for the following parameters:
Credential

Source                              ServiceEndpoint                     Scenario                       Result  Latency
                                                                                                                  (MS)
------                              ---------------                     --------                       ------  -------
AM111.AM.LAN                        autodiscover.company.nl            Autodiscover: Outlook Provider Failure     144
AM111.AM.LAN                        webmail.company.nl                 Exchange Web Services          Success     134
AM111.AM.LAN                        webmail.company.nl                 Availability Service           Success     207
AM111.AM.LAN                                                            Offline Address Book           Skipped       0





Viewing all articles
Browse latest Browse all 7008

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>