Windows 10: Authenticode cert

My tech support is running security check and finding Authenticodetm Root certificate expiration.What is this, is this legit, why would it expire, and what are my options?

:)

 

Unable to Connect to Exchange 2010 - Cert Error 80072F06

Hi,

Thanks for your reply. I ended up coming to the same conclusion about it being a problem with the CN in the cert. It's weird because if you viewed the cert, you would see that it did have a matching CN. However, browsers (Firefox, IE, and Chrome) pointed
to OWA all reported a problem with the cert -- both due to not trusting the CA (it was self-signed) and due to a name mismatch.

This cert did show the proper CN when you viewed the cert, so the browser error was odd, but the CN address was missing from the list of Alternate Names, which is apparently what the browser (and WP7) look at to determine whether or not a site is valid for
the cert. Anyway, the Exchange admin issued a new cert and included the CN in the AN list and all was good.

Since I had previously installed the root cert to my WP7, I was able to immediately set up my Exchange 2010 account on the phone.

Someone else in my office has an Android phone, and he had problems with the cert too. But for him, he just checked the "Accept all certs" box, and he was good to go. It would be great if MS offered that in cases like this, where I, the user, explicitly
trust the cert in question.

--

tl;dr +1 rep to Tobias D. It was a problem with the CN. Issued new cert to Exchange server and all is good.

 

Chrome cert not importing

I have a cert with SAN that I want to use for my localhost projects so I can stop getting warnings from Chrome.

When I go to Settings => Advanced => Manage Certs => Personal => Import, I can import my cert and I see a message that says "The import was successful".

But I don't see the localhost cert listed in my Personal list of certs.

Why is this failing to import? OR why is it showing a success message while not showing the cert in the list of Personal certs?

 

SHA1 to SHA256 - Existing certs

Hi there,

I am working on a migration of our Win2K8 workloads and one of these is our CA. I have seen lots of great KB articles about migrating from SHA1/ CSP to SHA2556 (KSP), but what I am not sure about is what happens to existing certs such as those issues to
domain workstations/ servers, local web servers, services, etc.

My plan is to spin up a new Win2K16 box, import the CA functions to this and upgrade to KSP but some of the questions I have around this are:

1. Will this impact these existing services, etc?
2. Is there a way to determine all the workloads that have been issued or are using a cert from the current CA?
3. Can I run two CAs side by side for a phased migration?