Manager

Mark Menefee

<div>
That's because you're cert doesn't cover the .local namespace, as wildcard certs can only cover one namespace.<br />
<br />
Also, you can never cover *.local with a public cert, as this cert will never generate (through a public/real issuance chain).<br />
<br />
Simple fix is to visit your .com site (not .local) letting your routing system optimize packets on your local network.<br />
<br />
Tip: Routing optimization has worked for decades now.
</div>


<div>
Missed about outlook provider. Updated the same in 1st comment.<br />

<pre><code class="code-1 nolinks" id="code-20-43076214-1"><span>Set-OutlookProvider EXPR –CertPrincipalName msstd:*.domain.com</span>
</code></pre>
</div>


<div>
Thanks for the very quick response. &nbsp;I did the above that MAS recommended and will ask the customer in the morning if it worked for them.
</div>


<div>
<div class="content wysiwyg-content">
I installed Exchange 2019 and created a wildcard SSL. &nbsp;Anyone from outside the office can connect with zero issues to the Exchange server using the normal autodiscovery process. Anyone inside the office though has a single issue. &nbsp;They get an SSL warning that says the name doesnt match &nbsp;the certificate. &nbsp;The name on the certificate is a .com name but the name that the SSL reports having an issue is the .local address. &nbsp;I know it has something to do with how the virtual directories are setup. &nbsp;There are two names there. &nbsp;The internal name and the external name. Which virtual directory do I need to change the Internal name to match the external name so the people in the office do not get this error? &nbsp;Or is that not the correct way to fix this issue?
</div>
</div>


I installed Exchange 2019 and created a wildcard SSL.  Anyone from outside the office can connect with zero issues to the Exchange server using the normal autodiscovery process. Anyone inside the office though has a single issue.  They get an SSL warning that says the name doesnt match  the certificate.  The name on the certificate is a .com name but the name that the SSL reports having an issue is the .local address.  I know it has something to do with how the virtual directories are setup.  There are two names there.  The internal name and the external name. Which virtual directory do I need to change the Internal name to match the external name so the people in the office do not get this error?  Or is that not the correct way to fix this issue?

Exchange 2019 SSL issue

Microsoft Office is an integrated suite of applications that includes Outlook, Word, Excel, Access, PowerPoint, Visio and InfoPath, along with a number of tools to assist in making the individual components work together. Coding within and between the projects is done in Visual Basic for Applications, known as VBA.

Microsoft Office

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

HTTPS is a protocol for secure communication over a computer network which is widely used on the Internet. HTTPS consists of communication over Hypertext Transfer Protocol (HTTP) within a connection encrypted by Transport Layer Security (TLS) or its predecessor, Secure Sockets Layer (SSL). The main motivation for HTTPS is authentication of the visited website and to protect the privacy and integrity of the exchanged data. HTTPS is widely used for protecting page authenticity on all types of websites, securing accounts and keeping user communications, identity and web browsing private.