Exchange 2013 Security Certificate
I am testing a new deployment of Exchange 2013. I have a new domain name purchased, and licensed from godaddy, have already made all of the DNS forwarding changes and MX pointers. I have email working on the server. Our domain is set as l*********p.net . This is our external, public domain. Our internal, private domain is just set as *example.com. This was setup before I ever even came on board years ago.
I have purchased a multi domain security certificate for our public domain, but this is where the issue comes into play. When I enable that certificate, I can access our Exchange server from the web-portal both internally and externally just fine, everything works as it is supposed to, EXCEPT for Outlook. If I try and add the Exchange account to Outlook (2013) it gives error codes that the Security Certificate does not match, as it is looking at the local name of the Exchange Server itself (dc4.example.com). The issue here is that I cannot purchase the *example.com domain as it is owned by someone else. This has not been an issue in the past, since we never needed to have a public facing domain before. Well, since we don't 'technically' own the rights to the public *example.com domain, I cannot get a third party certified certificate with that domain name in it. I can create a self-certified certificate through Exchange, that includes the domain, but then every web browser throws up security warnings every time you try to connect both internally and externally.
What is the best practice here to make both ends meet?
I have purchased a multi domain security certificate for our public domain, but this is where the issue comes into play. When I enable that certificate, I can access our Exchange server from the web-portal both internally and externally just fine, everything works as it is supposed to, EXCEPT for Outlook. If I try and add the Exchange account to Outlook (2013) it gives error codes that the Security Certificate does not match, as it is looking at the local name of the Exchange Server itself (dc4.example.com). The issue here is that I cannot purchase the *example.com domain as it is owned by someone else. This has not been an issue in the past, since we never needed to have a public facing domain before. Well, since we don't 'technically' own the rights to the public *example.com domain, I cannot get a third party certified certificate with that domain name in it. I can create a self-certified certificate through Exchange, that includes the domain, but then every web browser throws up security warnings every time you try to connect both internally and externally.
What is the best practice here to make both ends meet?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER