Folks:
I have spent almost 7 days straight on the phone with Office365 to get this resolved nobody can give me an answer. I am trying to set up a Hybrid deployment with my onsite Exchange 2013 environment and my Office365 account. Every time we try (every 24 hours and after we've tried 3 times) we continue to get the same exact error message every single time. Once of the tech's thought maybe blowing away my domain on Office365 and starting over should fix the problem. So this weekend (09/20 - 09/21) I spent erasing all my users out of Office365 and removing the AD Sync then blowing my domain away. After doing all of that, I set everything back up and tried the domain verification on my Hybrid Deployment Wizard and once again I get stuck at the domina verification TXT issue. I have removed ALL TXT records except for the one that I was given by the wizard and I still get the error.
The wizard did not complete successfully. Please see the list below for error details.
Updating hybrid configuration failed with error 'Subtask Configure execution failed: Configure Organization Relationship Execution of the Set-FederatedOrganizationIdentifier cmdlet has thrown an exception. This may indicate invalid parameters in your hybrid configuration settings. Proof of domain ownership has failed. Make sure that the TXT record for the specified domain is available in DNS. The format of the TXT record should be "example.com IN TXT hash-value" where "example.com" is the domain you want to configure for Federation and "hash-value" is the proof value generated with "Get-FederatedDomainProof -DomainName example.com". at Microsoft.Exchange.Management.Hybrid.RemotePowershellSession.RunCommand(String cmdlet, SessionParameters parameters, Boolean ignoreNotFoundErrors) '. Additional troubleshooting information is available in the Update-HybridConfiguration log file on server DALNTPEXCHANGE2 located at C:\Program Files\Microsoft\Exchange Server\V15\Logging\Update-HybridConfiguration\HybridConfiguration_9_22_2014_1_48_26_635469473062112815.log.
My "other" Exchange (old) server is still turned on but was technically decommissioned. My old server was Exchange 2010.
Can someone please help me get this figured out promptly? I have spent numerous man hours on this and for what should be an "easy fix" is turning in to a HUGE pain in the ______ (you know what) and stopping progress.
Thanks