Hi,

I have deployed System Center Updates Publisher 2011 tool in a Server 2012 R2. Installed server has WSUS role configured and it has Software Update Point configured for SCCM 2012 R2 as well. I have followed the below article and given up it because it doesn't gave me latest Adobe reader software updates. Because partner software update catalogs listed there are bit old. But I have successfully published it to the SCCM.

http://blogs.msdn.com/b/cubaker/archive/2014/04/30/enable-scup-in-configmgr-2012-r2-with-wsus-4-1.aspx

Anyway, I needed the latest Adobe reader DC updates to be deployed using SCUP 2011 and I have downloaded few .msp files from Adobe and imported it to the SCUP 2011 console. I have assigned those updates and published it. But it doesn't publish it to the SCCM. So, I need some assistance from the experts to make this success.

Regards,

Thisaru Perera.

The lastest catalogs can be downloaded here: http://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/sccm.html 

Have you already examined SCUP.log?

Hi there,

I'm with Torsten on this, the SCUP.log is your first port of call.

Other considerations.

Did you configure SCUP with a self-signed certificate or deployed a  signing certificate from your certificate Authority?

Are you running the SCUP console "As administrator"?

If you click "Test connection" in the scup console what are the results?

For the downloading of Adobe catalogues did you need to configure a proxy server in the SCUP console? if so, check these settings are still present.

• Edited by MR_Rossi 20 hours 42 minutes ago Typo - from

Also, have you synced WSUS since publishing?

Have you added the appropriate product(s) and classification(s) to your catalog configuration in the ConfigMgr console?

After adding these, have you synced again?

Have you reviewed wsussync.log on the site server?

Did the publish in SCUP actually complete successfully or did you receive an error?

Hi there,

I'm with Torsten on this, the SCUP.log is your first port of call.

Other considerations.

Did you configure SCUP with a self-signed certificate or deployed a  signing certificate from your certificate Authority?

Are you running the SCUP console "As administrator"?

If you click "Test connection" in the scup console what are the results?

For the downloading of Adobe catalogues did you need to configure a proxy server in the SCUP console? if so, check these settings are still present.

• Edited by MR_Rossi Tuesday, September 08, 2015 11:02 AM Typo - from

I am really sorry for the delayed reply.

I have already went through that article from Adobe. I have downloaded latest .cab files and deployed it but that also didn't publish to the SCCM.

Anyway, I will post the scup.log here if any error occurred.

Regards,

Thisaru Perera.

Yes, I have configured the SCUP with self signed certificate and deployed signing certificate.

Run As Administrator option also didn't fix the issue.

When I click "Test Connection" button in the SCCM integration tab, it was a success.

I did not need to configure a proxy server when I'm downloading Adobe catalogues.

Regards,

Thisaru Perera.

Yes, all the things you have mentioned are listed in the article which I previously posted. I have followed that article and successfully published the updates to SCCM. But all those updates are outdated. Now most of the users have Adobe reader DC. So, I need updates for Adobe reader DC.

Regards,

Thisaru Perera.

So you imported the adobe catalog to SCUP? Then published one or more updates to WSUS? Then initiated a SUP sync and made sure that the sync catogories do contain the Adobe product you published?