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".
[cid:[email protected]] James Beardsley | Firm Technology Group Dixon Hughes Goodman LLP [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.
