OME Update catalog fails OME Version 2.2.0.2056 - Dell OpenManage Essentials - Systems Management - Dell Community
Systems Management Forums

OME Update catalog fails OME Version 2.2.0.2056

Systems Management

Systems Management
Dell Systems Management Solutions: Dell OpenManage, iDRAC, Repository Manager, Microsoft SCCM, Chassis Managment Controller, and more

OME Update catalog fails OME Version 2.2.0.2056

  • I'm attempting to update the OME catalog on 3 different servers and get the same error on all.  "Import Dell Version Control Catalog for System Update from http//downloads.dell.com/catalog/catalog.cab failed. Exception message: Catalog signature verification failed. Please enable/verify proxy settings if require.

    I checked with our proxy team and they see attempts to http://download.dell.com are working but attempts to http//downloads.dell.com/catalog/catalog.cab are getting forcibly closed by the remote host.  

    Any ideas on how to fix this?

  • Hi,

    Thanks for the query. If http based url is having problem, try accessing ftp based url.

    downloads.dell.com/.../catalog.cab

    or

    ftp.dell.com/.../catalog.cab

    Let us know if this helps.

    Thanks,

    Arun
    Social Media Support
    #IWork4Dell

  • For some reason, post is truncating the url.

    ftp : / / downloads.dell.com / catalog / catalog.cab

    basically, replace http with ftp.

    Thanks,

    Arun
    Social Media Support
    #IWork4Dell

  • I've tried both with the same results. 

  • I had the same issue and resolved it by installing the certificate of the catalog.cab

    1. Download http://downloads.dell.com/catalog/catalog.cab
    2. right click cab file
    3. Properties
    4. Digital Signatures
    5. Select certificate
    6. Details
    7. View certificate
    8. Install certificate

    After import of both certificates I was able to get the latest catalog in OME.

  • I tried this without any luck.

    I contacted my Dell contact and he provided me a link for a fix and that worked.  It specifically addressed an issue with McAfee and even though we don't use McAfee the first solution fixed my issue..

    Link: kc.mcafee.com/.../index

  • The solution provided by Makeafee resolved the issue for me as well.