I also had a similar issue when I was trying to pre-provision the client in our image. We moved to the client being installed via GPO/Client Push.
On Mon, Oct 5, 2015 at 3:54 PM Mote, Todd <[email protected]> wrote: > If the image wasn’t syspreped correctly that could definitely be a > possibility. In my case the client was trying to use a different cert to > auth to an sccm object that had previously used a another cert. same > system, but because the certs were different it was trying to register a > new object with the same name, and I would end up with the same sorts of > things in the logs. At the beginning of all that in the logs, I seem to > recall there being an entry like “Client registration status = 2” or > something similar, before it started to do the “sleep for” business… > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Beardsley, James > > *Sent:* Monday, October 5, 2015 2:28 PM > *To:* [email protected] > > > *Subject:* [mssms] RE: Problems with client registration > > > > No, certs aren’t expired. Most of these machines are brand new. I think it > might be because the client was installed on the image on accident when our > hardware team was building a new image and the image had a different name. > I’m going to look into that further. Thanks for the input. > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Mote, Todd > *Sent:* Friday, October 02, 2015 3:36 PM > *To:* '[email protected]' <[email protected]> > *Subject:* [mssms] RE: Problems with client registration > > > > Are your certs expiring or are there new ones that the client has selected > to use that were different from the original one? I had similar issues > with clients earlier this summer and the culprit was the client was > choosing a different cert than it had been using. > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Beardsley, James > *Sent:* Friday, October 2, 2015 12:38 PM > *To:* [email protected] > *Subject:* [mssms] Problems with client registration > > > > For the last two to three weeks, I’m seeing this problem more and more > where machines are having trouble completing registration and I have to > delete the client from the console and restart the ccmexec service in order > to fix it. Or in extreme cases, in addition to deleting it from the > console, I have to go on the machine and delete the SMSCFG.ini file, > re-enroll a new client cert, then repair the client (I’m not sure if all of > those steps are required but it fixes the issue nonetheless). In the past, > if there was a duplicate record, the client would still register, but the > old record would go obsolete. It doesn’t seem like that’s happening now > which is requiring some manual intervention described above. I can’t think > of anything that has changed recently that would cause this. Any ideas on > where to begin troubleshooting this? I’ve already confirmed in Hierarchy > Settings that I have it set to “Automatically resolve conflicting records”. > > > > > > *James Beardsley |* Firm Technology Group > > Dixon Hughes Goodman LLP > > > > [image: cid:8644FC49-D5C9-45AE-B387-04FAFC0CC7A5] <http://www.dhgllp.com/> > > > ------------------------------ > > *Confidentiality Notice:* This e-mail is intended only for the addressee > named above. It contains information that is privileged, confidential or > otherwise protected from use and disclosure. If you are not the intended > recipient, you are hereby notified that any review, disclosure, copying, or > dissemination of this transmission, or taking of any action in reliance on > its contents, or other use is strictly prohibited. If you have received > this transmission in error, please reply to the sender listed above > immediately and permanently delete this message from your inbox. Thank you > for your cooperation. > > > > > ------------------------------ > > *Confidentiality Notice:* This e-mail is intended only for the addressee > named above. It contains information that is privileged, confidential or > otherwise protected from use and disclosure. If you are not the intended > recipient, you are hereby notified that any review, disclosure, copying, or > dissemination of this transmission, or taking of any action in reliance on > its contents, or other use is strictly prohibited. If you have received > this transmission in error, please reply to the sender listed above > immediately and permanently delete this message from your inbox. Thank you > for your cooperation. > > >
