Patch Manager

[Steve Parker]

Hi All,

Please be aware that we have started hosting the rollup ini files on a http web link from this months version 2010.00 rollups for Windows 2012 R2 and Windows10.

E.G: 

2009.00:

ftp://ftp.ca.com/pub/unicenter/uam/rollups/2009/win2012r2goldx64/upmrollup.ini

2010.00:

https://ftpdocs.broadcom.com/WebInterface/phpdocs/0/ClientAutomation/Content/PatchTuesday/2010/intelli/os/win2012r2goldx64/upmrollup.ini

You may need to adjust you Proxy/Firewall settings to reflect this change.

From next month the remaining content will also be updated. 

Rgds,
Steve

------------------------------
Senior Principal Engineering Solutions Architect
Broadcom
------------------------------

[Wayne Sack]

Hi Steve,

I was trying to download v2010 Intellirollups for Win10/Server 2016-2019 & Win 2012 R2 x64 from UPM.
We get error for upmrollup.ini for both rollups:
2020-10-30 15:21:27,633 [Dloader-3] ERROR [com.ca.pmengine.dlm] - Patch: upmrollup.ini {44a48396-5fdb-45cb-8571-e7d034e5312a} failed with exception detail: hostname in certificate didn't match: <ftpdocs.broadcom.com> != <supportftp.ca.com> OR <downloads.broadcom.com> OR <supportftp.broadcom.com> OR <sdownloads.broadcom.com> OR <rdownloads.broadcom.com> OR <sizer.broadcom.com> OR <ftpdownloads.broadcom.com> OR <sdownloads.ca.com> OR <downloadsutil.broadcom.com> OR <ftpdownloads.ca.com> OR <supportftp.ca.com>

Please advise if this error is related to the change and how we can resolve it.
I was able to download upmrollup.ini manually and it was successful, therefore not being blocked by Firewall.
It certificate related.

Thanks & Regards
Wayne

[Steve Parker]

Hi Wayne,

 

You need to talk with you network team and have the proxy/firewall rules changes to reflect the new name.

 

Rgds,

Steve.

 

[Cristi Mitrana]

While we don't have an issue with the New URL, it looks like some checksums are all mismatched in the new patches:

2020-11-17 12:41:04,066 [Dloader-2] ERROR [com.ca.pmengine.dlm] - Patch: upmdeltarollup.ini {af429997-386f-4e25-a42a-2ae1cd967237} verification failed

2020-11-17 12:41:04,066 [Dloader-2] ERROR [com.ca.pmengine.dlm] - Verification of upmdeltarollup.ini has failed.

2020-11-17 12:42:04,336 [Dloader-2] ERROR [com.ca.pmengine.dlm] - Patch: upmdeltarollup.ini {af429997-386f-4e25-a42a-2ae1cd967237} verification failed

2020-11-17 12:42:04,336 [Dloader-2] ERROR [com.ca.pmengine.dlm] - Verification of upmdeltarollup.ini has failed.

2020-11-17 12:42:04,352 [Dloader-2] WARN  [com.ca.pmengine.dlm] - af429997-386f-4e25-a42a-2ae1cd967237has reached the maximum number of retries.

I've checked the checksum from a direct download (the errors are from a DM that goes through a HTTP(s) proxy) and looks to be fine, the .ini is not altered in transfer.

[Steve Parker]

Hi Cristi,

 

We have had any other customers reporting problems and its working fine on our test systems.

 

Rgds,

Steve.

 

[Cristi Mitrana]

It turns out the access was not correctly set, after we straighten that out and we dealt with the proxy's SSL inspection shenanigans, the downloads in Patch Manager completed fine.