Exchange with Local Domain – Your Certificate will Expire by Nov 2015

Recently, I noticed that the Certificate Authorities like GoDaddy are issuing a warning when you purchase a Certificate with Internal Sever name (example: domain.local). The use of internal domain names has been discontinued by Certification Authorities and Browsers (CAB). If you intend to issue a certificate with .local or any internal domain name, then your certificate will expire by November 2015. After November 2015, you’ll loose the ability to purchase an SSL Certificate if you include a .local domain or any other internal domain in it. If you already have one, and you have not done anything about it till Nov 2015, it will expire. You must have a question in your mind, why not purchase the certificate without the internal domain (.local) and use it. Yes, you can use it, however if your Internal domain is .local, then your users will continuously get Certificate warning on Outlook when launched and while using it. What does it mean for you? Since Active Directory was introduced by Microsoft, most of the users have promoted their internal domain separate from an external domain. Exchange Servers were configured with the internal domain names as well. Outlook always contacted the Exchange Server via its .local domain name. Now, if you also have a similar environment, you must be thinking about how you can avoid this from happening, and also issue a proper certificate for your Exchange Organization. How do you fix it – Redirect your Exchange Server to use External URL You’ll need to run the following commands on your Exchange 2007 or Exchange 2010 Management Shell. These commands will update the URL for three services:...