<div>
I did and today was good. I was to early in regards to the wait time for records to be created in DNS. <br />
<br />
In conclusion all is working just fine today.
</div>


I did and today was good. I was to early in regards to the wait time for records to be created in DNS.

In conclusion all is working just fine today.

<div>
All is working fine today. Thank you for your assistance.
</div>


All is working fine today. Thank you for your assistance.

<div>
<div class="content wysiwyg-content">
Hi guys<br />
I have built a lab with an Exchange 2013. And i have setup dirsync and all is good until i run through the Hybrid Exchange configuration wizard which goes well untill i get the error as show on picture &nbsp;<a href="https://filedb.experts-exchange.com/incoming/2017/10_w40/1197260/autodiscover.JPG" target="_blank" title="Screen at end (57 KB)"><img alt="Screen at end" class="file-block lazyload" style="max-width: 666px;" data-src="https://filedb.experts-exchange.com/incoming/2017/10_w40/1197260/autodiscover.JPG" /></a><br />
I have setup the autodiscover on the server with powershell in the cas useing the same as in the error. The public dns autodicover is setup as an a record matching the public IP<br />
<br />
I can telenet to the server on port 443 so firewall cant be the issue. <br />
<br />
There is no edge server but Centralized mail setup has been choosen. The mail servere has both mailbox and cas role.<br />
<br />
In mu opinion firewall and autodiscover should be ok but clearly there is an issue.
</div>
</div>


autodiscover.JPG

Hi guys
I have built a lab with an Exchange 2013. And i have setup dirsync and all is good until i run through the Hybrid Exchange configuration wizard which goes well untill i get the error as show on picture  

I have setup the autodiscover on the server with powershell in the cas useing the same as in the error. The public dns autodicover is setup as an a record matching the public IP

I can telenet to the server on port 443 so firewall cant be the issue. 

There is no edge server but Centralized mail setup has been choosen. The mail servere has both mailbox and cas role.

In mu opinion firewall and autodiscover should be ok but clearly there is an issue.

Hybrid Exchange configuration problem

Windows PowerShell is a task automation and configuration management framework from Microsoft, consisting of a command-line shell and associated scripting language built on the .NET Framework. PowerShell provides full access to the Component Object Model (COM) and Windows Management Instrumentation (WMI), enabling administrators to perform administrative tasks on both local and remote Windows systems as well as WS-Management and Common Information Model (CIM) enabling management of remote Linux systems and network devices.

Powershell

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.