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 Configuration Manager Client Certificate set to none

Status
Not open for further replies.

itrider

Member
Messages
11
Solutions
1
Reaction score
0
Points
1
I have noticed in the past couple weeks that my OSD setups install everything, including the agent; however, the agent is not generating the self-signed certificate for the client and therefore cannot download policies and such.

My server(s) are running the latest 1706 with KB4042345.

If I manually uninstall/reinstall the ccmexec agent, the certificate installs successfully and all is well. Thoughts?
 
Solution
The problem is resolved...mostly. I had a support call with M$ and the "stuck in provisioning" is normal and expected they said. The provided the following two TS steps that I should add to my deployment.
However, before adding these steps, I tried one thing. I found an old post about a restart command that was in the OSD and it caused the problem. I looked at my TS OSD and the very last command, which was a restart I have had for 1.5+yrs. I disabled this step and the clients worked successfully.

M$ is going to investigate why this appeared recently for me.
It appears the problem is with the agent being stuck in provisioning mode. If I execute the powershell from KB4016483, it resolves the problem.
 
Unfortunately, no, it is not resolved. I found that now I only have to run the elevated powershell command to get it out of provisioning mode post install rather than a full agent uninstall/reinstall.
 
The problem is resolved...mostly. I had a support call with M$ and the "stuck in provisioning" is normal and expected they said. The provided the following two TS steps that I should add to my deployment.
However, before adding these steps, I tried one thing. I found an old post about a restart command that was in the OSD and it caused the problem. I looked at my TS OSD and the very last command, which was a restart I have had for 1.5+yrs. I disabled this step and the clients worked successfully.

M$ is going to investigate why this appeared recently for me.
 
Solution
Status
Not open for further replies.

Forum statistics

Threads
7,025
Messages
27,489
Members
17,676
Latest member
chew

Trending content

Back
Top