Is Your Microsoft Exchange Server Ready For November 1st, 2015?

 Are You Still Running An In-house Microsoft Exchange Server?

We want to bring awareness to changes on November 1^st.  Microsoft Exchange servers with a non-public domain name attached to the SSL certificate will no longer be able to acquire this essential security keeping your company data secure.  These changes mean that email may be negatively impacted by changes, if you’re using Microsoft’s Exchange Server.

What Are SSL Certificates?

SSL Certificates are established to provide a secure and encrypted connection between a server (website) and a browser (user’s computer).  This SSL connection protects sensitive company data, such as credit card information during each time (session) of exchanged data.

What Should You Do?

If you’re uncertain whether your current SSL Certificates are going to be affected by this change, feel free to contact our support team at {company} or by an email to {email}.  Our support team will ensure we help you navigate your way through these changes without any disruptions in your business operations and minimize potential downtime associated with the reconfiguration.

These new rules are designed to improve security and allow for proper use of new top level domain names (for instance, .nyc is a public TLD now).  However, that means changes need to be made to your network and security to cooperate with these new rules.  Failing to have this done may negatively impact your mail traffic, your business and/or your reputation.

If certificate and client access settings are not changed, Outlook users will receive pop-up warnings of untrusted certificates, invalid names in the certificates, etc.

Don’t take any chances with your livelihood and contact {company} Support Team now to ensure that your business operations are not disrupted!  We want to make sure your business grows and thrives during these new changes!