locked
SCCM : big certificate issue on DP RRS feed

  • Question

  • Hello,
    I have a problem in SCCM. I have done a migration from SCCM Srv1 to SCCM Srv2 then I fall on this problem on a new DP on Srv2 :
    (*) Failed to find algorithm ID from registry. Use default algorithm.
    (*) Failed to create certificate store from encoded certificate. Verify the provided Certificate was provisioned correctly. .
    (*) Unknown error (Error: 80092002; Source: Unknown)
    (*) Failed to initialize DP monitoring object. Error code: 0x80092002
    To correct this problem, I already changed in the properties of the DP in the SCCM Console on the Srv2 (primary server). But the error got worse.
    Must :

    I delete a file in the RSA folder on the DP (and how to) ?

    Verify the certificates on the DP and how to ?

    Check the SCCM primary server for some things ?

    Here is the screenshot :

    Ox22
    
    This text was recognized by the built-in Ocrad engine. A better transcription may be attained by right clicking on the selection and changing the OCR engine to "Tesseract" (under the "Language" menu). This message can be removed in the future by unchecking "OCR Disclaimer" (under the Options menu). More info: http://projectnaptha.com/ocrad
    Ox22
    
    This text was recognized by the built-in Ocrad engine. A better transcription may be attained by right clicking on the selection and changing the OCR engine to "Tesseract" (under the "Language" menu). This message can be removed in the future by unchecking "OCR Disclaimer" (under the Options menu). More info: http://projectnaptha.com/ocrad

    imgur.com  / TECVX8v

    Thursday, December 26, 2019 1:52 PM

All replies

  • I have done a migration from SCCM Srv1 to SCCM Srv2

    What exactly does this mean? Did you actuall use the built-in migration tool set or did you do something else?

    I already changed in the properties of the DP in the SCCM

    What exactly does this mean?

    I delete a file in the RSA folder on the DP (and how to) ?

    No, this is almost always a bad thing to do as this doesn't delete the certificate.


    Jason | https://home.configmgrftw.com | @jasonsandys

    Friday, December 27, 2019 12:01 AM