Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SOLVED Client show self-signed in console even it use PKI

Marek Belan

Well-Known Member
Messages
105
Solutions
2
Reaction score
9
Points
18
After update to 2107 all clients start showing in console as self-signed but on client in ClientIDManagerStartup.log they have PKI cert.
I try restart client , computer , server nothing help.
On 2013 all cliens was on PKI.

If client have old 2013 version its show OK, with new version show self-signed.

1632844476903.png1632844455937.png
 
Solution
If you are using PKI certs, on the primary site properties window, why have you selected HTTP or HTTPS and why not only HTTPS ?.
OMFG OK its feature not bug. No one who have 2107 dont see this?

Or noone use PKI ?
If you are using PKI certs, on the primary site properties window, why have you selected HTTP or HTTPS and why not only HTTPS ?.
Starting with SCCM 2103 you will require to select HTTPS communication or enhanced HTTP configuration. You must plan to configure the site for HTTPS only or to use Configuration Manager-generated certificates for HTTP site systems. If you don’t select between the two you may encounter a warning during the SCCM 2103 update installation.
 
If you are using PKI certs, on the primary site properties window, why have you selected HTTP or HTTPS and why not only HTTPS ?.
OMFG OK its feature not bug. No one who have 2107 dont see this?

Or noone use PKI ?
 
Solution
OMFG OK its feature not bug. No one who have 2107 dont see this?

Or noone use PKI ?
Hello all,
Same issue.. last night we've updated our infrastrcture to 2107 (from 2103) and now the CLients with the new Client Version 5.00.9058.1018 showing "self-signed" in the console.
But checked direct on the client, it's "PKI".
 
Ok, I wasn't aware about this change. I could see the same behavior in my lab as well. So, yes I see the Client certificate property in console shows as Self-signed whereas the client control panel Client certificate property shows PKI.
 
Ok this issue is resolved in the latest version of ConfigMgr, which is 2309. I will confirm this with Microsoft and respond here later.
 
Back
Top