Unsolved
This post is more than 5 years old
39 Posts
0
7251
August 30th, 2016 03:00
Remote update error - "Unable to verify Update Package signature"
Hello,
From the moment I've updated DELL OME to 2.2.0.2056 version I'm not able to deploy updates remotely and I always get the error: "Unable to verify Update Package signature"
I mention that I've already used all the three sources available in Catalog Source -> Online Source
- downloads.dell.com/.../catalog.cab
- ftp.dell.com/.../catalog.cab
- ftp.dell.com/.../catalog.cab
and also the option "Skip Signature and Hash Check" in "System Update Task"
The result is the same, cannot update, error: "Unable to verify Update Package signature"
Thanks in advance,
Augustin
No Events found!
DELL-Arun Mo
116 Posts
0
September 6th, 2016 03:00
Hi,
Thanks for the post. Can you please check windows event manager under "OpenManage Essentials" group whether it reported any error or failure?
augustinm
39 Posts
0
September 6th, 2016 08:00
Hi,
I can not see anything.
In fact all I can see is related to OmeDAService, OmeHostService in "Event sources"
All are Informational events.
Kind regards,
Augustin
FCRN
1 Message
0
July 19th, 2018 19:00
I know this is an old thread, but just though I'd share our solution to this same problem so it might help someone else who comes across this post via a search engine like I did.
1. Had to change our Catalog Source in OME to https://downloads.dell.com/catalog.cab
By default the site is http. The missing "S" was the first part of the puzzle.
2. Purged our download folder C:\Program Files\Dell\SysMgt\Essentials\SystemUpdate\Packages. It had a number of files in it, but none of them were actually valid. I noted that when using the original catalog source (http), the files would download instantly. Our internet connection is fast, but not that fast for >1gb of files, so it was clear something was not right! Also, when taking any of these files and trying to update the server via iDRAC, it would fail with a message that the package contents were not valid.
3. We had to bypass all filtering and SSL interception being done by our proxy.