These forums are now Read Only. If you have an Acrobat question, ask questions and get help from one of our experts.

SCUP Issue

Forum Index > Deployment & Installation > SCUP Issue
2011-02-14 08:09:50
dhalperin
Registered: Feb 13 2011
Posts: 3
Answered

Hi, I am trying to deploy the Adobe X and Flash updates using SCCM and SCUP. The Flash update goes fine and is an .msi. I am having an issue with the Acrobat X patch. IT is an .msp. It seems to import correctly, but when I check the properties on it, "Update Package SOurce" has a red exclaimation point. I tried pointing to the .msp on the local drive as well as a UNC network drive. It seems to take it initially, but when I go to verify the properties again, it once again shows as missing.
 
I know this is new, but any ideas?

My Product Information:
Acrobat Standard 10.0, Windows
Top
2011-02-16 05:01:51
#1
vdobhal
Registered: Sep 1 2010
Posts: 3
Accepted Answer
Hi,

This is a normal, just place the .msp on a shared folder and provide the UNC path of the msp in the "Update Package Source". Publish the catalog and everything should be fine.

I have tried this and it works fine for me.

Thanks,
Top
2011-02-16 07:59:54
#2
dhalperin
Registered: Feb 13 2011
Posts: 3
Doesn't sound right that there would be this type of error outta the box. But I do see it as available. Problem is, it fails everytime I run it. Any ideas?
Top
2011-02-22 11:01:57
#3
tlconard
Registered: Feb 11 2011
Posts: 1
I can publish the catalogs for both Flash and Acrobat 10.0.1 and advertise them to our client PC's, but each time I do the installation fails on the clients. Any thoughts our ideas?
Top
2011-02-24 03:08:39
#4
vdobhal
Registered: Sep 1 2010
Posts: 3
tlconard wrote:
I can publish the catalogs for both Flash and Acrobat 10.0.1 and advertise them to our client PC's, but each time I do the installation fails on the clients. Any thoughts our ideas?
If you are able to publish the catalog successfully, then there should not be any problem with the catalog. Try looking at the log files on the client system at C:\Windows\System32\CCM\Logs ( for x86 systems) or
C:\Windows\SysWOW64\CCM\Logs ( for x64 systems)

Is the certificate instlled under Trusted Root Certification Authorities and Trusted Publishers on the client system. Do the certificates on the SCCM server and the client match?

Is the GPO policy "Allow signed content form intranet Microsoft update location" under: 'Computer Configuration > Administrative Templates > Windows Components > Windows Update' enabled?
Top
2011-02-24 03:38:37
#5
vdobhal
Registered: Sep 1 2010
Posts: 3
dhalperin wrote:
Doesn't sound right that there would be this type of error outta the box. But I do see it as available. Problem is, it fails everytime I run it. Any ideas?
Yes, that seems odd to me also that it works fine for msi and shows an red exclamation mark for an msp.

The help for "Update Package Source" textbox in SCUP specifies the following:

Update Package Source - Specifies the location of the software update source file. Updates Publisher uses this source file to create the hash value used to validate the file on the update server.

So this filed is used to create a hash of the msp/msi file which is provided in the Download URL

This might be an issue with SCUP ver 4.5 and probably would be fixed in SCUP 5.0

But in my and Travis Conard's case this works after providing the UNC path of the same msp file and the catalog is published successfully.

Top