Yep; let's get a few pieces of information to help winnow out the chaff. :) 1) is your SCUP code signing cert self signed, or is it from an existing CA (internal or external)? 2) Do you have a Central Admin site in SCCM or just a single site? 3) Where is your software update point installed, and where is the WSUS server it's pointing to? 4) What OS is on the server(s) from number 3? 5) Where are you running the SCUP console; your workstation or one of the SCCM servers? 6) Are you getting the error when configuring SCUP or when trying to publish a package?
DAMIEN SOLODOW Senior Systems Engineer 317.447.6033 (office) 317.447.6014 (fax) HARRISON COLLEGE ________________________________ From: [email protected] [[email protected]] on behalf of Sherry Kissinger [[email protected]] Sent: Tuesday, October 20, 2015 3:33 PM To: [email protected] Subject: Re: [mssms] RE: creating an application or package from Adobe Reader Your clients might have the cert in both trusted pub and trusted root. But you are talking about the SCUP console itself failing on the cert piece? On the server which has the SCUP console, go to the MMC, add the snap-in for Certificates for the computer account. and go look in the "WSUS\certificates" folder. Take note of what certs you have in there.-- you SHOULD see the one with the same expiration date as the one you see when you run SCUP console as-admin, and look at the left-pull down, Options, Signing Certificate Expiration Date. That's the one you care about (for this). Now go look in the "Trusted Publishers\Certificates" and "Trusted Root ...\Certificates". If you don't already have that cert in ALL three locations... right-click copy the one from the WSUS Certs into the other two locations. also, if the server that happens to be running your SCUP console isn't the same as your top level SUP, or isn't the same as your Primary (or your CAS, if you have a cas in there); you'll want to go check certs on those servers, too. Make sure the cert is in all those locations. On Tuesday, October 20, 2015 1:47 PM, David McSpadden <[email protected]> wrote: Using: http://blogs.technet.com/b/jasonlewis/archive/2011/07/12/system-center-updates-publisher-signing-certificate-requirements-amp-step-by-step-guide.aspx I think I have the cert correctly built and deployed? From: [email protected] [mailto:[email protected]] On Behalf Of David McSpadden Sent: Tuesday, October 20, 2015 2:35 PM To: [email protected] Subject: RE: [mssms] RE: creating an application or package from Adobe Reader So create a GPO to distribute the cert to all machines TR and TP locations? From: [email protected] [mailto:[email protected]] On Behalf Of Charles Hiland Sent: Tuesday, October 20, 2015 2:29 PM To: [email protected] Subject: RE: [mssms] RE: creating an application or package from Adobe Reader Did you create the cert using SCUP? The cert needs to be added to Trusted Root and Trusted Publisher of any machine that will be receiving updates (including the WSUS DB machine). From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of David McSpadden Sent: Tuesday, October 20, 2015 2:13 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] RE: creating an application or package from Adobe Reader I have SCUP 2011 on my SCCM server right now. I am to the point of publishing in SCUP to SCCM and it keeps failing on the cert?? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Juelich, Adam Sent: Tuesday, October 20, 2015 2:09 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] RE: creating an application or package from Adobe Reader You can download previous versions and add them as Applications and then remove them as part of a Supersedence Rule. ----------------------------------------------- Adam Juelich Pulaski Community School District<http://www.pulaskischools.org/> Client Management Specialist 920-822-6075 On Tue, Oct 20, 2015 at 12:50 PM, Damien Solodow <[email protected]<mailto:[email protected]>> wrote: There is an easier way; take a look at SCUP (System Center Update Manager). It’s free from Microsoft, and one of the partner catalogs is for Adobe Reader so you can patch it like you would other things from WSUS. DAMIEN SOLODOW Senior Systems Engineer 317.447.6033<UrlBlockedError.aspx> (office) 317.447.6014<UrlBlockedError.aspx> (fax) HARRISON COLLEGE From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of David McSpadden Sent: Tuesday, October 20, 2015 1:45 PM To: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: [mssms] creating an application or package from Adobe Reader Not sure which way to go on this. I want to uninstall previous version of adobe reader and install the latest updates to the latest version. Anyone have a script or setup similar in SCCM 2012 R2?? This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email. ________________________________ The Pulaski Community School District does not discriminate on the basis of any characteristic protected under State or Federal law. This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email. This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email. This e-mail and any files transmitted with it are property of Indiana Members Credit Union, are confidential, and are intended solely for the use of the individual or entity to whom this e-mail is addressed. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender and delete this message immediately from your computer. Any other use, retention, dissemination, forwarding, printing, or copying of this email is strictly prohibited. Please consider the environment before printing this email.
