Currently Being ModeratedOct 21, 2012 1:25 PM (in response to pnisima)
Just found this thread - I just started a new discussion with the same problem. I have the fealing, that there is a bug in certadmin.
My certadmin stops with the same error message it cannot find the certificate, my Commen Name for the certificate contains a german "Umlaut" - does your certificate Commen Name contains some french accents?
Maybe we found a solution together.
Currently Being ModeratedOct 21, 2012 1:58 PM (in response to pnisima)
I just solved my problem - I read the KB article again and there it says
"When entering the hexadecimal serial number, ensure that all letters are entered in lower case."
Maybe it is the same with your problem.
Currently Being ModeratedOct 22, 2012 3:15 AM (in response to Christoph Ewering1)
I've already made a new certificate.
I tried to enter the hexadecimal serial number in upper case, next time i will try in lower case.
Currently Being ModeratedNov 28, 2012 10:11 AM (in response to pnisima)
i also had to renew the code signing certificate on mountain lion server. i followed the article (HT5358) and it works. but when i want du update the settings for a device the push fails. there was no need to enroll the device again, but i had to delete all settings for the device, which i configured with profile manager. then the push works. ist that right?
Currently Being ModeratedSep 2, 2013 10:34 AM (in response to pnisima)
Can anyone confirm that if after following the code signing cetrificate renewal process if all devices that were enrolled in Profile Manager continued to work properly with Profile Manager and did not have to delete the trust certifificate or re-enroll any of the devicese? I have over 200 devices enrolled in PM and am stressed over the possibility of haing to re-enroll that many devices.
Thak you in advance.