locked
ConfigMgr Client Regestration Fails RRS feed

  • Question

  • Hi -

    We are experiecing issues in the "ClientIDManagerStartup.log" when we try to A) do a new install of a client or B) change a client from site A to site B (within the same hierarchy).

    Is anyone well versed in the following error messages in "ClientIDManagerStartup.log"?

    RegTask: Failed to send registration request message. Error: 0x8007000e

    RegTask: Failed to send registration request. Error: 0x8007000e

    Can anyone provide more info? What server role is the client trying to register to?

    Wednesday, June 23, 2010 4:14 PM

Answers

  • Cool, I thought that was a supported model, as long as Central Site is in Native Mode primaries can be either, from the documentation I read.
    It is supported and does work, so nothing to worry about.
    Are you trying to install / assign the client to a mixed mode site?
    0x80040309 = SE_AUDITID_CERTSRV_SETEXTENSION (A certificate request extension changed), but I have no idea what would cause this issue.
    Thursday, June 24, 2010 6:28 AM
  • Can you open the MMC and verify that your certificates are in place on the client.  Other clients in this site are working right, so it is only this one client?

    Post more of the ClientIDManagerStartup.log file.  I wonder if your certs aren't there.  I have had several machines that just refuse to pull down the cert for different reasons and this is the error you will see.


    http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com
    Thursday, June 24, 2010 11:27 AM

All replies

  • Hi,

    Take a look at this post with a similar problem and answer - http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/35b4d207-a9fd-484e-ae0d-56f4ba365228


    Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products
    Wednesday, June 23, 2010 5:01 PM
  • The client will contact the MP and attempt to send data.  Then the MP will accept and send down policy.  We have seen this problem due to client certificates as well as a corrupt install.  Only once have I seen it due to WMI.  I think it just could get the client started at that point.

    Could you tell us the command string you use to install the client.  Just as a test; on the client open the ConfigMgr control panel and click on the Discovery button and see if it has a problem.  Also check to see what Site Code is listed.

     


    http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com
    Wednesday, June 23, 2010 5:34 PM
  • Hi Matthew -

    Here is our install command:

    CCMSETUP.EXE /SERVICE /mp:SERVERNAME.COM CCMHOSTNAME= SERVERNAME.COM SMSSITECODE=XXX FSP= SERVERNAME.COM

     

    Central Site is in Native, Primary SIte is in Mixed.

     

    We also have an intsall command for Native Mode (different then one above), but since items were not working in Native we moved site to mixed mode to troubleshoot.

     

    Same issues with:

    RegTask: Failed to send registration request message. Error: 0x8007000e

    RegTask: Failed to send registration request. Error: 0x8007000e

    We have run the MPn troubleshooter on our MP sites, no issues.

    Wednesday, June 23, 2010 6:18 PM
  • Hi Kent -

    We were able to do all checks listed in the similar post, no issues, i.e. run mplist checks, etc. We are not getting any 500 errors.

    Wednesday, June 23, 2010 6:20 PM
  •  

    Central Site is in Native, Primary SIte is in Mixed.


    You are the first person I've ever heard of that had sites not all in the same mode.

     


    John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
    Wednesday, June 23, 2010 6:26 PM
  • Cool, I thought that was a supported model, as long as Central Site is in Native Mode primaries can be either, from the documentation I read.

    We found what was wrong with the command line, had to remove the CCMHOSTNAME switch because it is specific to Native Mode.

    We had the site up in Mixed Mode, performing Hardware and Software inventory.

    So now we are going back to Native Mode on this site. Different command line:

    CCMSETUP.EXE /SERVICE /mp:SERVERNAME.COM /NATIVE CCMALWAYSINF=1 CCMHOSTNAME= SERVERNAME.COM SMSSITECODE=XXX FSP= SERVERNAME.COM RESETKEYINFORMATION=TRUE

     

    Error results are as follows:

     

    LocationServices.log

    Failed to verify message, sending MP not in allowed list

    Will not refresh list since was refreshed recently

     

    ClientIDManagerStartup.log

    RegTask: Failed to send registration request message. Error: 0x80040309

    RegTask: Failed to send registration request. Error: 0x80040309

     

    CertificateMaintenance.log

    Failed to verify signature for assigned MP.

     

    Any help would be greatly appreciated!

    Wednesday, June 23, 2010 10:43 PM
  • Cool, I thought that was a supported model, as long as Central Site is in Native Mode primaries can be either, from the documentation I read.
    It is supported and does work, so nothing to worry about.
    Are you trying to install / assign the client to a mixed mode site?
    0x80040309 = SE_AUDITID_CERTSRV_SETEXTENSION (A certificate request extension changed), but I have no idea what would cause this issue.
    Thursday, June 24, 2010 6:28 AM
  • Can you open the MMC and verify that your certificates are in place on the client.  Other clients in this site are working right, so it is only this one client?

    Post more of the ClientIDManagerStartup.log file.  I wonder if your certs aren't there.  I have had several machines that just refuse to pull down the cert for different reasons and this is the error you will see.


    http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com
    Thursday, June 24, 2010 11:27 AM