The trusted root key is something different from the client’s cert. The TRK is site specific and owned by the site.
Have you verified that the clients have certs in the local SMS certificate store for the computer account? What does clientidstartupmanager.log say? J From: [email protected] [mailto:[email protected]] On Behalf Of Jason Wallace Sent: Monday, June 8, 2015 7:36 AM To: [email protected] Subject: RE: [mssms] SCCM 2012 R2 SP1 UPGRADE [cid:[email protected]] ? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Denzik, Josh Sent: 08 June 2015 12:48 To: [email protected]<mailto:[email protected]> Subject: [mssms] SCCM 2012 R2 SP1 UPGRADE All, After upgrading to SCCM 2012 R2 SP1 we are now getting errors with our clients self-signed certificates. The clients are showing they do not have a self-signed cert. Here are some of the status messages. This happens if the client is a new or fresh install. I pushed the client to some existing machines and they look fine. Any help would be great!..... Microsoft SQL Server reported SQL message 8169, severity 16: [42000][8169][Microsoft][SQL Server Native Client 11.0][SQL Server]Conversion failed when converting from a character string to uniqueidentifier. : SMSDBMON_ClientKeyData_PfxCertsClientKeyData_Chg_upd [cid:[email protected]] Thanks, Joshua Denzik Senior Systems Engineer | Managed Desktop Team | OCIO-IS phone: 843-792-0306 | email: [email protected]<mailto:[email protected]>
