SCCM manual client installation does not work only on a specific server

Question

Hi,

I have 2 domains in my environment, lets call them "primary" and "secondary" . SCCM is joined to domain "primary" and I am installing sccm client manually on computer in "secondary" domain.

A week ago, I demoted one of my domain controller in domain "secondary" (server 2012) and replaced it with a fresh (server 2019) domain controller. I assigned the same old fqdn and ip address for the new server. Then I tried to install sccm client manually on this new server, but Client actions tab shows only machine policy and user policy retrival and ClientID manager setup log has the following error:

[RegTask] - Server rejected registration request: 3

I just created a new virtual machine today in the secondary domain and manually installed client, it worked without any problems. There are many servers they are also in secondary domain and communicate with MP successfully. So my problem is not related to the certificate. I believe I need to manually delete old entries that belong to this specific server from sccm database but I do not know where to look for them.

I modified the site maintenance values for the following, I hope these maintenance task might clean up the old entires from the db.

Delete aged discovery data

Delete aged enrolled device

Delete aged inventory history

Delete aged unknown computers

Delete inactive client discovery data

Delete obsolete client discovery data

Thanks,

Selim

Answer 1

Hi @ Selim Atmaca ,

Thanks for your feedback and sharing. We're glad that the question is fixed now. Here's a short summary for the problem, we believe this will help other users to search for useful information more quickly. It's appreciated that you could click "Accept Answer" to the reply.

Problem/Symptom:
SCCM manual client installation does not work only on a specific server.

Solution/Workaround:

Changed the certificate store in SCCM site properties to SMS. Then changed the installation parameter to use SMS store like following:

ccmsetup.exe /mp:MPSERVER /source:ClientSourceLocation SMSSITECODE=XXX CCMCERTSTORE=SMS

The reference link:

https://methmal132.wordpress.com/2018/04/02/how-to-correct-client-certificate-none-error-in-configmgr/

(Note: Microsoft provides third-party contact information to help you understand the problem. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.)

Thanks again for your time! Have a nice day!

Best regards,
Cherry

 

Answer 2

Hi Cherry,

I found the solution on the internet and it solved my problem. I changed the certficate store in sccm site properties to SMS. Then changed my installation parameter to use SMS store like this.

ccmsetup.exe /mp:MPSERVER /source:ClientSourceLocation SMSSITECODE=XXX CCMCERTSTORE=SMS

I am adding the blog post here just in case someone else might have the same problem:

[https://methmal132.wordpress.com/2018/04/02/how-to-correct-client-certificate-none-error-in-configmgr/

Thanks,

Selim Atmaca

Answer 3

Hi @Selim Atmaca,

To narrow down the problem we need more information.

1, Before that, was the domain controller in domain "secondary" (server 2012) an SCCM client? Whether you have performed an uninstall? Do you still see it in the SCCM console?

2, Please help check MP_CliReg.log and MP_RegistrationManager.log to check why the client cannot be registered. The path is C:\Program Files\SMS_CCM\Logs on MP. If possible, please help upload these full logs and ccmsetup.log for our reference.

I will do more research; I will be sharing for you if I have any process.

Thanks for your time!

Best regards,
Cherry