[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1503
  • Last Modified:

SCCM Client unable to register to server on 5 out of 45 servers

I have migrated all of our systems to a SCCM server for patching and software deployment.  65ish laptops.  45 Servers.  The rub is that I have a few servers that are unable to register to the server.  In one of the logs on the system, I get this:
<![LOG[[RegTask] - Client is not registered. Sending registration request for GUID:<REDACTED> ...]LOG]!><time="14:57:40.377+300" date="04-09-2014" component="ClientIDManagerStartup" context="" type="1" thread="5972" file="regtask.cpp:1609">
<![LOG[[RegTask] - Server rejected registration request: 3]LOG]!><time="14:57:41.111+300" date="04-09-2014" component="ClientIDManagerStartup" context="" type="3" thread="5972" file="regtask.cpp:1675">
<![LOG[Sleeping for 292 seconds before refreshing location services.]LOG]!><time="14:57:46.120+300" date="04-09-2014" component="ClientIDManagerStartup" context="" type="1" thread="5972" file="regtask.cpp:196">

I have removed the certificates, the SMSCONF.sys file, completely(as best I can tell) removed all CCM related software and reinstalled.  Same result.  Any ideas?
0
trejwr
Asked:
trejwr
1 Solution
 
BembiCEOCommented:
As SCCM uses agents, make sure the agents on the systems are not too old. You may try to reinstall the agents from the SCCM or to install them manually.
But most issue may be a firewall (i.e. windows firewall) what blocks the communication or any other software (also virus scanner) what may produce trouble).
0
 
trejwrAuthor Commented:
I have reinstalled the agent. I haven't ruled out the firewall or network issues, but it seems odd that some of the ones that are having issues are on the same network as functional ones. All windows firewalls are turned off.
0
 
merowingerCommented:
Are all of them Domain members?
You may have to install the Agent with the flag RESETKEYINFORMATION=TRUE
Also try this:
http://shankarkannappa.wordpress.com/tag/server-rejected-registration-request-3-client-not-receiving-policies/
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
BembiCEOCommented:
Some other issues come into my mind....
Sometimes the agent installs but the service do not start.
Reasons may sometimes just be, that you get certificate errors (schannel in event log), or DCOM permission errors, that a DCOM component could not start due to missing permissions and even make sure, that the install account has the right permissions.

So check the eventlog and compare the membership in the local groups, if there are accounts missing, especially the install account. Also check under which account the agents runs itself.

If you tries to install in the same way than all other machines, you may try to manually remove the agent, check the permissions and try to install again.
0
 
trejwrAuthor Commented:
OK, so I think I about have this figured out. It seems all systems that would not allow the client to register had non-standard self-signed certificates for varying reasons.  This was causing conflict when the SCCM Agent attempted to authenticate to the CA???  Not clear on how this works, but after removing the certs from two systems, I was able to install and register.  I am testing further to finalize this project and will annotate my findings after its completion.
0
 
BembiCEOCommented:
This is why it is sometimes usefull to have your own PKI and used certificates from there.
Yea, by default self signed certs are used and you have to make sure. they are present on the clients.

Self signed certs is a work around for the lifetime of the cert, this ensures that a system can run out of the box, but they start to make trouble as possibly not automatically renewed and some applications start to make trouble if two cerst with the same subject name exists because some application jsut take the first one they can find.

Just to explain the cert behaviour.
0
 
Seth SimmonsSr. Systems AdministratorCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now