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 SCCM Workgroup Client Not Using Client Cert

  • Thread starter Thread starter reza5
  • Start date Start date
  • Replies Replies 4
  • Views Views 4K
Status
Not open for further replies.

reza5

Member
Messages
6
Solutions
1
Reaction score
1
Points
1
Greetings,
I have been working on installing and configuring SCCM, and have had success (hard earned) in getting it to work with domain clients and Mac clients as well, having successfully deployed a CA server. However, I'm really having a hard time getting the Workgroup client to install correctly. I have done the following:
  • Deployed a Workstation Auth template for Workgroup clients
  • Done a cert request and exported as a PFX
  • Imported the cert on to the workgroup client
  • Installed CCM on the client, but after all of that, the CM client reports that there is no client certificate and CM Console does not show the workgroup client in devices.
Note, I had actually succeeded in installing a workgroup client before deploying the PKI infrastructure (for Mac clients), but now it's failing. I'm sure I'm missing something. I have gone over several tutorials, all of which are mostly similar, but there must be something I'm missing. Can anyone point me in the right direction?
 
Solution
Thank you, Prajwal, for all that hard work and info you have put up on your blog.

I did solve this problem. It had to do with CRL URLs only listed as Active Directory LDAP. I followed the procedure of making CRLs accessible via HTTP and created a new workgroup client cert and new SCCM site cert and that solved the problem.
Thank you, Prajwal, for all that hard work and info you have put up on your blog.

I did solve this problem. It had to do with CRL URLs only listed as Active Directory LDAP. I followed the procedure of making CRLs accessible via HTTP and created a new workgroup client cert and new SCCM site cert and that solved the problem.
 
Last edited:
Solution
Status
Not open for further replies.
Back
Top