Microsoft has announced a new policy for Certificate Authorities (CAs) that deprecates the use of the SHA1 algorithm in SSL and code signing certificates, in favor of SHA2. The policy affects CAs who are members of the Windows Root Certificate Program who issue publicly trusted certificates.  It will allow CAs to continue to issue SSL and code signing certificates until January 1 2016, and thereafter issue SHA2 certificates only.

Windows PKI blog, "SHA1 Deprecation Policy". https://docs.microsoft.com/en-us/security-updates/securityadvisories/2017/4010323 , December 12/17/2013

Key Dates:

• 1 Jan 2016 – CAs must stop issuing SHA1 certificates
• 1 Jan 2017 – Windows will stop accepting SHA1 SSL certificates
• 1 Jan 2016 – Windows will stop accepting SHA1 code signing certificates without time stamps

Details:

For SSL certificates, Windows will stop accepting SHA-1 end-entity certificates by January 1, 2017. This means for Windows, a three-year SHA-1 certificate issued after January 1, 2014 won’t work after that date. Same for a two-year SHA-1 certificate issued after January 1, 2015, and a one-year SHA-1 certificate issued after January 1, 2016. It’s time to plan ahead when ordering or renewing your certificates.

For code signing certificates, Windows will stop accepting SHA-1 code signing certificates without time stamps after January 1, 2016.

Internet Explorer and  new versions of Mac OSX, Firefox, Chrome, Opera, Safari, Java and Adobe Acrobat/Reader all support SHA-2

Some enterprises might be running a non-browser application that does not support SHA-2. If you are unaware, you need to do some investigation or testing to see if your system supports SHA-2 and consider your migration plan.

If you have any questions or concerns please contact the Entrust Certificate Services Support department for further assistance:

Hours of Operation:
Sunday 8:00 PM ET to Friday 8:00 PM ET
North America (toll free): 1-866-267-9297
Outside North America: 1-613-270-2680 (or see the list below)
NOTE: Smart Phone users may use the 1-800 numbers shown in the table below.
Otherwise, it is very important that international callers dial the UITF format exactly as indicated. Do not dial an extra "1" before the "800" or your call will not be accepted as an UITF toll free call.