Exchange certificate with an invalid internal domain

I just upgraded Exchange 2003 to 2010. I wanted to get a real certificate for this client. The problem is their internal domain is a vaild Internet domain name ending in .com that is owned by someone else

I can't use that domain name in a certificate.

I know I can get a certificate with just the external domain but I want to elimintate the certificate error that pops up in Outlook on the internal network

How can I get around this problem?.
ajdratchAsked:
Who is Participating?
 
satshahCommented:
Create an internal certificate for your domain and modify the URL in the exchange management shell.

http://support.microsoft.com/kb/940726


To resolve this issue, modify the URLs for the appropriate Exchange 2007 components. To do this, follow these steps:
Start the Exchange Management Shell.
Modify the Autodiscover URL in the Service Connection Point. The Service Connection Point is stored in the Active Directory directory service. To modify this URL, type the following command, and then press ENTER:
Set-ClientAccessServer -Identity CAS_Server_Name -AutodiscoverServiceInternalUri https://mail.contoso.com/autodiscover/autodiscover.xml
Modify the InternalUrl attribute of the EWS. To do this, type the following command, and then press ENTER:
Set-WebServicesVirtualDirectory -Identity "CAS_Server_Name\EWS (Default Web Site)" -InternalUrl https://mail.contoso.com/ews/exchange.asmx
Modify the InternalUrl attribute for Web-based Offline Address Book distribution. To do this, type the following command, and then press ENTER:
Set-OABVirtualDirectory -Identity "CAS_Server_name\oab (Default Web Site)" -InternalUrl https://mail.contoso.com/oab
Modify the InternalUrl attribute of the UM Web service. To do this, type the following command, and then press ENTER:
Set-UMVirtualDirectory -Identity "CAS_Server_Name\unifiedmessaging (Default Web Site)" -InternalUrl https://mail.contoso.com/unifiedmessaging/service.asmx
Note This command is required only in an Exchange 2007 environment. This command no longer exists in an Exchange 2010 environment. Instead, the WebServices URL is used for this purpose.
Open IIS Manager.
Expand the local computer, and then expand Application Pools.
Right-click MSExchangeAutodiscoverAppPool, and then click Recycle.

0
 
wynandkunkelCommented:
I have not implemented it myself but can imagine the following:

-Install a CA on one of the DC's in the domain (Backup of thei machine becomes (EXTREMELY!!!!) important.
-issue a certificate (with the .com domain) on the internal CA
-publish/install that internal domain cert on the internal network to all machines using GPO mechanism.

Assuming that the external domain cert has already bee issued, this way the machines should trust the (internal) CA when on the LAN and also trust the (external) CA when roaming.

Best of luck!
0
 
TheTullCommented:
If all you want to really accomplish is to eliminate the certificate error notification then your clients just need to trust the CA root certificate.  I see no reason why not to just use a self-signed certificate on the internal LAN, and then have your clients import the root certificate into the trusted root certificate authorities.  
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.