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

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 [email protected] -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

Hi,
Are you add primary SMTP domain as a federated domain? If not, please run below command to achieve this function:
Add-FederatedDomain -DomainName contoso.com
Configure federated sharing for the Exchange 2013 organization. Complete the steps in
Configure federated sharing.
Configure federated delegation (previous name for federated sharing) for the Exchange 2010 SP2 organization. Complete the steps in
Configure federated delegation.
Besides, I find an similar thread about Autodiscover service failed within federated trust, for your convenience:
https://social.technet.microsoft.com/Forums/ie/en-US/ea192e0a-1363-4cb6-9fc4-2973f64afc23/the-response-from-the-autodiscover-service-at?forum=exchange2010
Best Regards,
Allen Wang

Similar Messages

Free/Busy not working after mailbox migration to Exchange 2013

I'm in the process of migrating user mailboxes from Exchange 2007 to Exchange 2013
It seems that many of the users (not all) are having problems seeing free/busy once they have been migrated. If we remove the Outlook profile and recreate it, all is good. Problem is that this is happening to more and more people. Everyone
is on Outlook 2010
Test-OutlookWebServices -ClientAccessServer Ex2013 -identity MyName -MailboxCredential $cred    Results in:
Autodiscover: Outlook Provider Failure
Exchange Web Services          Failure
Availability Service           Skipped
Offline Address Book           Failure
The same if I run that command against the Exchange 2007 server.
What am I doing wrong?

I should have mentioned that. Yes, OWA works perfectly for the affected users. Just as deleting their Outlook profile and recreating a new one does.
Results of Get-WebServicesVirtualDirectory:
Identity    : Exch2007Srvr\EWS (Default Web Site)
InternalUrl : https://legacy.company.com/EWS/Exchange.asmx
ExternalUrl : https://legacy.company.com/EWS/Exchange.asmx
Identity    : Exch2013Srvr\EWS (Default Web Site)
InternalUrl : https://mail.company.com/ews/exchange.asmx
ExternalUrl : https://mail.company.com/ews/exchange.asmx
The URL you reference above is actually the site I used to perform migration.
What's interesting (at least to me) is that on my machine I did not have any issues with seeing calendars. The Test E-mail AutoConfiguration (without Guessmart), I get prompted for my password over and over; however, after clicking on cancel I
get:
Attempting URL
https://mail.company.com/autodiscover/autodisconver.xml found through SCP
Autodiscover to
https://mail.company.com/autodiscover/autodisconver.xml starting
GetLastError=0;httpStatus=401
GetLastError=0;httpStatus=401
GetLastError=0;httpStatus=401
GetLastError=0;httpStatus=401
GetLastError=0;httpStatus=401
Autodiscover to
https://mail.company.com/autodiscover/autodisconver.xml Failed (0x80040413)
Attempting URL
https://autodiscover.company.com/autodiscover/autodisconver.xml found through SCP
Autodiscover to
https://autodiscover.company.com/autodiscover/autodisconver.xml starting
GetLastError=0; httpStatus=200.
Autodiscover to
https://autodiscover.company.com/autodiscover/autodisconver.xml Failed (0x800C8203)
Autodiscover to https://company.local/autodiscover/autodiscover.xml starting
GetLastError=12029; httpStatus=0
Autodiscover to https://company.local/autodiscover/autodisconver.xml Failed (0x80004005)
Autodiscover to
https://autodiscover.company.local/autodiscover/autodisconver.xml starting
GetLastError=0; httpStatus=0
GetLastError=0; httpStatus=200
Autodiscover to
https://autodiscover.company.local/autodiscover/autodisconver.xml Failed (0x800C8203)
Local autodiscover for company.local starting
Local autodiscover for company.local Failed (0x8004010F)
Redirect check to
https://autodiscover.company.local/autodiscover/autodisconver.xml starting
Redirect check to
https://autodiscover.company.local/autodiscover/autodisconver.xml Failed (0x800C820D)
Srv Record lookup for hydraforce.ads starting
Srv Record lookup for hydraforce.ads Failed(0x8004010F)
However, when I did this on a system that cannot see any calendars, it all works perfectly.
Browsing to
https://autodiscover.hydraforce.com/autodiscover/autodiscover.xml does result in Error Code 600

Migrating AD Exchange 2013 Objects to a new AD Domain

I have a client 'new company' (NC) who is splitting from the 'parent company' (PC). They are using a 3rd party tool to conduct the AD migration/split.
The PC AD domain is on Windows 2012 Servers and has trust relationship with the NC AD domain also running on windows 2012 server. The users and computers have been successfully migrated/stubbed to the NC domain, however, the Exchange 2013 objects
are not migrating over to the NC AD domain using the 3rd party AD migration tool.
Question, does any one have suggestions on how to migrate the exchange 2013 objects from the PC AD to the NC AD ?
What techniques can be used ?
Thanks in advance
RK

What 3rd party tool are you using and have you contacted their support already? You can use the native tools to migrate mailboxes (I do all the time) but I wouldn't try and mix the native tools and a 3rd party tool on the same migration unless I was sure
what the end result would be.

Exchange 2007 migrate to Exchange 2013

Dear MS Support,
I did migrate Exchange 2007 to Exchange 2013
The install complete, the exchange 2007 and 2013 can work together successful
DAG has created and work fine
Below is capture on exchange group after migrate
The exchange 2007 work fine with outlook anywhere, all the users can connected and send and receive mail in 5 year
The cerificate enroll with
Alternative Names: mail.biendongpoc.vn
The autodiscover on exchange 2007:
[PS] C:\Windows\system32>Get-ClientAccessServer | ft Identity,*uri* -AutoSize
Creating a new session for implicit remoting of "Get-ClientAccessServer" command...
Identity AutoDiscoverServiceInternalUri
BDPOC-SERVER1 https://mail.biendongpoc.vn/Autodiscover/Autodiscover.xml
I have created new certificate for Two exchange 2013
The certificate enroll with
Alternative Names: cas.biendongpoc.vn
I have create cname cas point to dag on DNS server
I have create A record autodiscover.biendongpoc.vn point to IP of dag.biendongpoc.vn
I did migrate mailbox from exchange 2007 to exchange 2013, the migrate successful , the outlook can
connected to Exchange 2013 and working perfectly
Our problem, the account exchange 2007 work not stable ,
sometime it connect to mail.abc.com, sometime it connect to cas.abc.com
If the outlook connect to cas.biendongpoc.vn, the request put password and i can't connect to exchange 2007, if outlook connect to mail.biendongpoc.vn i can connect
It is not stable for current exchange 2007
Anyone who can help me ?
Thanks

Hi
huynhtrongnhatminh,
I suggest you please go through this article.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Please check this for step by step guide.
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
Please point your autodiscover and commonname to Exchange2013 CAS
Please configure your URLs. There is no CAS array in Exchange2013 but the concept of single name space remains.
You need to have an A record (e.g. legacy.domain.com) in yout external DNS and add that name (legacy.domain.com) in your certificate for exchange 2007 users to have access externally.
Configure your commonname URLs in Exchange2013. Point commonname and autodiscover to exchange2013 in both external and internal DNS servers
Configure URLshttp://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
No CASARRAY in 2013http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/
Please configure splitdns or pinpoint DNS in your internal DNS server if not configured
http://exchange.sembee.mobi/network/split-dns.asp
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Outlook 2007 on Terminal Server cannot manage Public Folder Favorites after Migration to Exchange 2013

Hi,
we are running a Server 2008 R2 as a Terminal Server with Outlook 2007 SP3 (incl Nov 2012 Update 12.0.6665.5000) which is known as fully supported with Exchange 2013.
With Exchange Server 2007 we did not have any issues. But after having successfully migrated to Exchange 2013 we cannot manage our public folders favorites from these clients anymore.
As we are running Outlook 2007 on a WTS we can not use Exchange Cache Mode and so we can also not download Public-Folders-Favorites as an option. Whenever we try to delete existing favorites or when we try to delete public folders with content or subfolders
there will be an error msg that says that it cannot be deleted and that there may be no sufficient permissions. But this IS NOT the issue NOR the solution as I have full admin rights and am owner of the public folders.
On single fat clients with Outlook 2007 with Exchange Cache Mode enabled we can manage the favorites and the public folders without problem.
We need to be able to manage the favorites of all users (circa 50-60 users) from the WTS with Outlookm 2007. I have no more ideas right now. Does anyone know how to get this settled?
Thanks, Paula

Hi,
Based on the description, users could access public folders successfully, but when they tried to manage public folder favorites or wanted to remove specified folders, they got error message of no sufficient permissions.
Is it right?
You mentioned on single fat clients with Outlook 2007 with Exchange Cache Mode enabled, user can operate normally. Is this a WTS with Outlook 2007 installed?
If possible, please switch this Outlook client from cached mode to online mode to check result.
Best regards,
Belinda Ma
TechNet Community Support

Cross-forest migration to Exchange 2013 SP1 and Outlook 2013 SP1

Hello! I have two forest: Exchange 2010 SP2 RU5 - resource forest and Exchange 2013 SP1 - account forest. I make cross-forest migration from resource forest (linked mailboxes with account forest) to forest with Exchange 2013 SP1.
I have moved mailbox from resource forest exchange 2010 to exchange 2013 sp1 forest.
Outlook 2010 connect to migrated mailbox without any problem, but outlook 2013 sp1 cannot connect to migrated mailbox.
Error look like - cannot find exchange server.
I created new mailbox in Exchange 2013 organization and can connect to it with outlook 2010 and outlook 2013 sp1.
Someone have the same problem with migrated mailbox? How to solve it?
Truly, Valery Tyurin

You can use New-MoveRequest to perform a cross-forest move. Here is a well post and step-wise explanation you can check for cross forest migration from exchange 2010 to exchange 2013(http://msexchangeguru.com/2013/11/03/e2013crossforestmigration/).
Moreover, you can try this utility (
http://www.exchangemigrationtool.com/ ) to accomplish this task.

Cutover Migration to Exchange 2013 On-premises

I have two clients who will be merging their on-prem Exchange
organizations. Different forests. I've done many cutover migrations to
Office 365 for other clients so I'm familiar with the process. My
question is: Is it possible to do an O365-style cutover migration (create migration endpoint, cutover batch, etc.) from
an on-prem Exchange 2010 server to an on-prem Exchange 2013 server using
the same steps?
Thanks in advance for any input.
Steve

Hi,
Based on my knowledge, the Cutover Migration is used for migration to Exchange online. There is no related document about
Cutover Migration from Exchange 2010 to Exchange 2013.
To perform Exchange 2010 corss-forest migration to Exchange 2013, you need to use Active Directory Migration Tool (ADMT) migrate user accounts.
Here is a related blog which may help you. (Even though this article is for Exchange 2010 corss-forest migration, it's also applies to cross-forest migration from Exchange 2010 to Exchange 2013.)
http://blogs.technet.com/b/meamcs/archive/2011/06/10/exchange-2010-cross-forest-migration-step-by-step-guide-part-i.aspx
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

After migration to Exchange 2013 the old outlook clients do not automatically reconfigure

After migration to Exchange 2013 the old outlook clients do not automatically reconfigure
we use outlook 2013

Hi ,
I hope you would be having exchange 2013 coexistence environment with exchange 2010 or 2007.
Autodiscover is the feature which will make the outlook profiles to configure automatically.So please make sure the following things are in place.
1.Autodiscover record on the internal dns need to be configured and it has to be resolved properly to the cas servers or else to the LB if you have.
2.Please check the autodiscover internal url.
get-clientaccessserver -identity "server name" | fl *internaluri*
3.Make sure the name used for the autodisocver and internal outlook anywhere are available on the SAN certificate installed in exchange.Same time we need to enable the installed SAN certificate for the exchange services like iis,pop,imap,smtp.
4.You need to have the autodicover name and internal outlook anywhere name on the internet explorer proxy exceptions when you have proxy servers available on your network for internet access.
Note : moreover we need an additional information's from your side about your environment.
Thanks & Regards S.Nithyanandham

After Migrating To Exchange 2013 All Outlook 2010 Users Constantly Prompted For Password (BUT OUTLOOK WORKS).

I have two servers. One is Exchange 2010 and the other is Exchange 2013.
Three of our users had mailboxes on Exchange 2013 for the last few weeks with no problems. They used Outlook 2013 and Outlook 2010. After moving the rest of our ~25 users to Exchange 2013 the users with Outlook 2010 began to be prompted for their
password constantly.
They try entering it and it immediately reappears.
The odd thing is it shows connected and they are able to send and receive emails correctly.
I've tested our exchange connectivity using www.testexchangeconnectivity.com and all is well there.
I'm not really sure what's going on.
Any help is appreciated.
Luke
Thanks, Luke Pickard

This can appear if Outlook clients are trying to connect to OAB virtual directory, and don't succeed for some reason. Mailbox and mailflow will work, but password prompt will appear when Outlook tries to contact OAB. Try to investigate in that direction.
Also, perform Outlook Configuration test (right click Outlook icon in task bar while holding CTRL and select Test email autoconfiguration.
Please 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. Thank you! Damir

Exchange 2013/2010 Co-existance Outlook Users Always Prompted for Password

Hello,
We are in the process of attempting to migrate to Exchange 2013, but during the migration time, we need to coexist with the two versions. Our outlook clients are a mix of Office 2007, 2010, and 2013. When a user is migrated from 2010 to 2013,
they start getting prompted for their password in Outlook every few minutes. They can click cancel and continue working, but they continue to get prompts for their password. If they click the update folder button in outlook, it updates fine, and
the password prompt goes away for awhile.
Most topics on this state that this is caused by a certificate issue. We have an internally deployed CA, with the Root certificate trusted by all clients. The exchange 2013 server has a certificate that was created by this CA.
I believe that this is caused by OAB (address book) still being hosted on the Exchange 2010 server (with a self signed cert), that is causing the connection to fail. Is there anyway to test this without breaking outlook connections for the users that
are on Exchange 2010? Or is there any other reason that this would occur?
Thanks for any assistance.

Sorry for taking so long to reply, other items came up that rank higher then this migration.
I ran the Test-OutlookWebServices CMD and got this result:
[PS] C:\Windows\system32> Test-OutlookWebServices
Source                              ServiceEndpoint
Scenario                       Result Latency
(MS)
EXCHANGE13.company.local           exchange10.company.local           Autodiscover: Outlook Provider Failure     229
EXCHANGE13.company.local
Exchange Web Services          Skipped       0
EXCHANGE13.company.local
Availability Service           Skipped       0
EXCHANGE13.company.local
Offline Address Book           Skipped       0
I
am currently thinking that this may be the error. Is there a way to
change the first failing result to the hostname of the
exchange13.company.local without breaking the current settings for the
exchange10.company.local autodiscover?

Exchange 2013 / 2010 co-existence - Outlook won't connect to Exchange 2010 mailboxes

Greetings! I have a lab set up at home where I have been testing co-existence of Exchange 2013 and 2010 for a future corporate upgrade project.
I am running into some odd behavior. Any mailbox that has been migrated to Exchange 2013 works just fine, however, when I try to set up Outlook for a mailbox still on Exchange 2010 I receive errors. OWA works just fine for these Exchange
2010 mailboxes, it is just Outlook that has the problem. This is what I am running into:
1. Outlook uses autodiscover to locate server settings. It fails at the 'logging on to mail server' step saying that Exchange isn't available; Outlook must be connected, etc.
2. It then gives me the settings box for Exchange server and Mailbox. This is auto populated with one of the Exchange 2013 servers (there are 3 of them, all have both MBX and CAS role). If I then change the server to the Exchange 2010 CAS server,
and hit 'check names', it underlines the very same entries (like it found them this time) that were there initially and goes on to finish the configuration.
3. When I launch Outlook with this Exchange 2010 user, it fails to open with the error message that the set of folders couldn't be opened.
I've been doing as much research on this as I can. I've tried disabling IPv6 to no avail. It seems as if perhaps the issue is with Exchange 2013 proxying the request back to the Exchange 2010 servers but I am not sure what to check in that regards.
Any suggestions? Thanks in advance!

Hi,
Don´t disable IPV6 on an Exchange Server, it is, in my opinion not necessary - also applies for AD.
You can use your original SSL Cert for your new Ex 2013 environment.
In dns you want two host A records: mail.domain.com and autodiscover.domain.com
On your 2013 set your internal and external virtual directories to mail.domain.com
leave autodiscover and Powershell alone.
Also set the autodiscover URI to your Certificate name ie. mail.domain.com
Set-ClientAccessServer -Identity "YourCASServer" -AutoDiscoverServiceInternalUri "https://mail.domain.com/autodiscover/autodiscover.xml"
Thanks. I wanted to give some additional info before I run any commands. I currently have an A record for autodiscover and it is pointed to the Exchange 2013 DAG/cluster IP. I have a 3 entries for mail.domain, for DNS round robin; basically
it is listed 3 times for the IP of each of my Exchange 2013 servers. Does any of this sound problematic?

Exchange 2013 how to disable outlook anywhere

Hi Team,
I have migrated some mailboxes from Exchange 2010 to 2013. But i want to restrict some users to use outlook anywhere.
How can i do this?
Also, Some outlook 2010 clients are not able to open outlook after migrating to Exchange 2013. Please help.
Thanks.
Regards, Sunny Kewalramani.

Hi,
Firstly, I'm afraid that we cannot disable Outlook Anywhere for certain users only when they use OA externally. And if the property MAPIBLOCKOutlookRpcHttp of a user is set to true, the user cannot access Exchange server both internally and externally.
Thanks,
Angela Shi
TechNet Community Support

Exchange 2013 federation

Hi guys,
Im strugling with the following scenario:
We try to setup Exchange federation between Exchange 2010 sp2 and Exchange 2013. Everything is setup as described on Technet.
The problem I'm having is the following:
WHen i run test-organizationrelationship i get this.
RunspaceId : 09496e7f-2a7c-4e3a-b15d-0c8d6a1a867b
Identity    :
Id          : ApplicationUrisDiffer
Status      : Error
Description : The TargetApplicationUri of the remote organization doesn't match the local ApplicationUri of the
              Federation Trust object. The remote URI value is
http://fydibohf25spdlt.aldum.co.za/. The local URI
              value is FYDIBOHF25SPDLT.aldum.co.za.
IsValid     : True
ObjectState : New
RunspaceId : 09496e7f-2a7c-4e3a-b15d-0c8d6a1a867b
Identity    :
Id          : VerificationOfRemoteOrganizationRelationshipFailed
Status      : Error
Description : There were errors while verifying the remote organization relationship Aldum.
IsValid     : True
ObjectState : New
For the life of me the application uri on Exchange 2010 is FYDIBOHF25SPDLT.aldum.co.za
Here is the proof:
RunspaceId            : e58ad1c2-2910-42c7-a624-748dd0ffbb57
DomainNames           : {aldum.co.za}
FreeBusyAccessEnabled : True
FreeBusyAccessLevel   : LimitedDetails
FreeBusyAccessScope   :
MailboxMoveEnabled    : False
DeliveryReportEnabled : False
MailTipsAccessEnabled : False
MailTipsAccessLevel   : None
MailTipsAccessScope   :
TargetApplicationUri : FYDIBOHF25SPDLT.aldum.co.za
TargetSharingEpr      :
TargetOwaURL          :
TargetAutodiscoverEpr :
https://autodiscover.aldum.co.za/autodiscover/autodiscover.svc/WSSecurity
OrganizationContact   :
Enabled               : True
ArchiveAccessEnabled : False
AdminDisplayName      :
ExchangeVersion       : 0.10 (14.0.100.0)
Name                  : Aldum
DistinguishedName     : CN=Aldum,CN=Federation,CN=Onesys,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=onesys,D
                        C=local
Identity              : Aldum
Guid                  : 7e806cf3-69d3-40ca-bd29-4ebbecb6e2f9
ObjectCategory        : onesys.local/Configuration/Schema/ms-Exch-Fed-Sharing-Relationship
ObjectClass           : {top, msExchFedSharingRelationship}
WhenChanged           : 2013/05/16 12:45:12 PM
WhenCreated           : 2013/05/16 12:44:57 PM
WhenChangedUTC        : 2013/05/16 10:45:12 AM
WhenCreatedUTC        : 2013/05/16 10:44:57 AM
OrganizationId        :
OriginatingServer     : isdc01.onesys.local
IsValid               : True
I allready deleted the federation trust and organization relationship and recreated it but the problem persists.
Your help will be appreciated.
Regards

Hi
Check xxxxxxx1234's reply on that link
I would just like to add that I encountered the same problem, but
Get-WebServicesVirtualDirectory | fl was already showing WSSecurity enabled:
So I figured this wasn't going to help me... However, after trying other things without success, i decided it wouldn't hurt to run the
Set-WebServicesVirtualDirectory –identity "EWS (default web site)" –WSSecurityAuthentication $true command. As soon as I did it, the cloud users started to be able to see the free/busy information
of on-premise users.
So just have a try
Cheers
Zi Feng
TechNet Community Support

Exchange 2013 Co-Existence Fail

I went ahead, installed new 2 multi-role exchange 2013 servers. Followed the exchange deploy assist. setup external urls, updated exchange 2010 outlook-anywhere, bla bla, changed dns to proxy through my 2013 servers. All services were fine,
except outlook clients with mailboxes still on 2010.
http://blogs.technet.com/b/exchange/archive/2013/05/23/ambiguous-urls-and-their-effect-on-exchange-2010-to-exchange-2013-migrations.aspx
I found and read this article and it seems to describe my problem. Pretty ticked that the deployment assist didn't say anything about it.
None of my external outlook anywhere clients can connet anymore. I have pretty much reversed as much as possible and 'removed' exchange 2013 out of the mix, my fqdn points back to my Exchange 2010 again, but still external OA cannot connect.
CAS config;
ServerName                         : CAS1
SSLOffloading                      : True
ExternalHostname                   : webmail.domain.com
InternalHostname                   :
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm}
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : False
AdminDisplayVersion                : Version 14.3 (Build 123.4)
ExchangeVersion                    : 0.10 (14.0.100.0)
Name                               : Rpc (Default Web Site)
ServerName                         : CAS2
SSLOffloading                      : True
ExternalHostname                   : webmail.domain.com
InternalHostname                   :
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods           : {Basic, Ntlm}
ExternalClientsRequireSsl          : True
InternalClientsRequireSsl          : False
AdminDisplayVersion                : Version 14.3 (Build 123.4)
ExchangeVersion                    : 0.10 (14.0.100.0)
Name                               : Rpc (Default Web Site)
I use a single url for ALL protocols/services including outlookanywhere. All databases have rpc url set.. Any clues?
Andrew Huddleston | Hillsong Church | Sydney

My Outlook-Anywhere settings, with names changed. I have the same external hostname for rpc endpoint and exchange 2010 cas array. Exchange 2010 mailbox are proxying through the 2013 seemingly fine, no problems.
Identity                           : EX15SVR1\Rpc (Default Web Site)
ExternalHostname                   : webmail.domain.com
ExternalClientAuthenticationMethod : Basic
ExternalClientsRequireSsl          : True
InternalHostname                   : webmail.domain.com
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl          : False
SSLOffloading                      : True
IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
Identity                           : EX15SVR2\Rpc (Default Web Site)
ExternalHostname                   : webmail.domain.com
ExternalClientAuthenticationMethod : Basic
ExternalClientsRequireSsl          : True
InternalHostname                   : webmail.domain.com
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl          : False
SSLOffloading                      : True
IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
Identity                           : EX10SVR1\Rpc (Default Web Site)
ExternalHostname                   : webmail.domain.com
ExternalClientAuthenticationMethod : Basic
ExternalClientsRequireSsl          : True
InternalHostname                   :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl          : False
SSLOffloading                      : True
IISAuthenticationMethods           : {Basic, Ntlm}
Identity                           : EX10SVR2\Rpc (Default Web Site)
ExternalHostname                   : webmail.domain.com
ExternalClientAuthenticationMethod : Basic
ExternalClientsRequireSsl          : True
InternalHostname                   :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl          : False
SSLOffloading                      : True
IISAuthenticationMethods           : {Basic, Ntlm}
My problem is with 2013 mailboxes that have migrated. I have a 2013 mailbox but it cannot connect, why I do not know. its mailbox is in a 2013 database on a 2013 mailbox server using outlook 2013. I have removed profile, readded (autodiscover
works perfectly), but cannot connect.
EXRCA fails with
Attempting to ping RPC endpoint 6001 (Exchange Information Store) on server
[email protected].
The attempt to ping the endpoint failed.
<label for="testSelectWizard_ctl12_ctl06_ctl09_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: 4314 ms.
Andrew Huddleston | Hillsong Church | Sydney

Exchange 2013 SP1 Setup fails

I am getting very frustrated. It really shouldn't take over a week to install Exchange.
I have two domain controllers, Windows 2003 and Windows 2008 R2. The 2008 is now all Operations Masters for all roles.
I have a clean install of W2K8 R2 SP1 installed under Hyper-V on a separate physical W2K8 server. Before starting the install I used ADSIEdit to ensure there was nothing left in the AD of prior Exchange install attempts. This is the first and only installation
of Exchange.
I am running the install as the Domain\Administrator and naturally that account is a member of all the appropriate security groups. RSAT are installed on the Exchange server and using them to access Users and Computers clearly shows this. The install fails
with the errors below, all of which appear to be incorrect.
*** BEGIN ERROR ***
Error:
Global updates need to be made to Active Directory, and this user account isn't a member of the 'Enterprise Admins' group.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalUpdateRequired.aspx
Error:
You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx
Error:
Setup encountered a problem while validating the state of Active Directory: Couldn't find the Enterprise Organization container. See the Exchange setup log for more information on this error.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
Error:
The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To install Exchange Server 2013, the forest functional level must be at least Windows Server 2003 native.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ForestLevelNotWin2003Native.aspx
Error:
This computer requires the Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit. Please install the software from http://go.microsoft.com/fwlink/?LinkId=260990.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.UcmaRedistMsi.aspx
Error:
This computer requires the update described in Microsoft Knowledge Base article KB974405 (http://go.microsoft.com/fwlink/?LinkId=262357). Please install the update, and then restart Setup.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.Win7WindowsIdentityFoundationUpdateNotInstalled.aspx
Error:
Either Active Directory doesn't exist, or it can't be contacted.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
*** END ERROR
Why can't Exchange installation see the AD when everything else can?

It appears that these error messages are pure fiction. I went back to ADSI Edit and removed some MS Exchange container and then reran setup /prepareschema again followed by setup /preparead and finally setup /mosde:install /role:clientaccess,mailbox and
it churned away for a long time, apparently working.
It appears than when it says you aren't a member of Schema Admins and that it can't access Active Directory, what it really means is it could find the AD just fine, but didn't like what it saw.
My guess would be very sloppy programming in which the low level error doesn't bubble up and so when something fails it just assumed you didn't have permissions.
It's not quite finished yet, but I am beginning to believe it will finish. So that's almost 6 days of non stop effort to install Exchange. It's hard top believe they are allowed to charge for this stuff.

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

Similar Messages

Maybe you are looking for