• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2093
  • Last Modified:

Hybrid Configuration WIzard - no entries in Domain Proof of Ownership screen

HI,
I'm just going through the configuration for setting up a hybrid configuration on my Exchange 2010 SP3 server for communication with Office 365. I'm running the wizard and get to the "Domain Proof of Ownership" screen, but no domains appear in the list (see attached).

I have separately run the Get-FederatedDomainProof command, got the TXT entry and tried running the wizard without anything on the screen, but I get a "Federation information could not be received from the external organization." error.(see attached)

Really grateful for any help you can offer.
Capture.PNG
Capture.PNG
0
browsw
Asked:
browsw
  • 3
  • 2
2 Solutions
 
David CarrCommented:
Do you have any entries in the Exchange Server Installation directory? Eg C:\Program Files\Microsoft\Exchange Server\V14\Logging\Update-HybridConfiguration

Have you run the Office 365 Readiness Tool? https://onramp.office365.com/onramp/

Also you need to complete the steps mentioned in  the Directory synchronization roadmap Technet Article http://technet.microsoft.com/en-us/library/hh967642.aspx

Are you using Exchange 2010 SP3?
0
 
browswAuthor Commented:
I've opened a case with Microsoft and apparently the problem is that the tenant is stuck being upgraded from FOPE to EOP.
0
 
browswAuthor Commented:
Solution found through 3rd party (MS)
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
perifelCommented:
Hi

Browsw

Can you tell us more about this issue?
right now I'm going through the same problem I can not see the records in the wizard but the wizard completes successfully but apparently not created automatically connectors in Exchange 2010?

I appreciate your time.

Greetings.
0
 
browswAuthor Commented:
Hi perifel,
Apparently it didn't matter that the domains weren't populated but the error of the wizard not finishing was due to the fact our tenant was stuck on FOPE. The reason for this was that we had another separate instance of FOPE for our domain as part of our Volume Licensing agreement and their automated system therefore didn't convert us to EOP.
0
 
perifelCommented:
Thanks, the information has been helpful

Regards.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now