Quantcast
Channel: Configuration Manager 2012 - Security, Updates and Compliance forum
Viewing all articles
Browse latest Browse all 6382

Looking for a way to re-sign two old SCUP updates

$
0
0

Today I Expired two old Adobe updates in SCUP that I originally Published back in December, 2014. When I went to Publish the Expired updates, I got a cert error on them both - just like this:

Info Scup2011.4 CabUtilities.CheckCertificateSignature File cert verification failed for \\SCCMServer\UpdateServicesPackages\29f8f68f-d4d5-4ce4-8a52-98623d05e895\27ca1c01-2501-4856-9929-71a69a09857d_1.cab with 2148204801

Scup2011.4 Publisher.GetLocalFileDetails VerifyAndPublishPackage(): Failed to Verify Signature for file: \\SCCMServer\UpdateServicesPackages\29f8f68f-d4d5-4ce4-8a52-98623d05e895\27ca1c01-2501-4856-9929-71a69a09857d_1.cab

I know it's because these two updates were originally published with an old, self signed cert. Now that I'm using a cert from my own CA, it's not publishing them. I can publish new updates all day long.

I've looked at the .cab files and can see the old cert is there. My question, is there a way to re-sign these updates to allow me to publish them again?

I tried the check box to "Sign all software updates with a new publishing certificate when published software updates have not changed but their certificate has changed" option but that doesn't help.

Has anyone wrestled with this?


Orange County District Attorney


Viewing all articles
Browse latest Browse all 6382

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>