Lenovo package - "Installation not possible"

We have two Patch Manager servers in two different Active Dirctories.

The older of the two PMs can publish and distribute BIOS-packages from the "Lenovo" catalog without problems.

The more recent PM can publish the packages too but they then get the status "Installation not possible" with a red "-" sign besides them. When I try to open "Update Management" on one of there packages I get the message "The following updates are currently not downloaded to the WSUS Server and may not be available to clients for download."

I'm unsure how to proceed, couldn't find any logs of further errors messages that would point me in the right direction. I worked through the settings of both PM servers but could not find any significant difference in there configurations to explain why one of them works just fine with Lenovo packages and the other does not.
Both PMs are working just fine with other packages.

Both PMs were configured for Lenovo packages as per this KB article:
https://support.solarwinds.com/SuccessCenter/s/article/Patch-Manager-Lenovo-Packages-Fail-to-Publish-due-to-needing-a-prerequisite?language=en_US

Does anyone have an idea what I can do or where I might look to find more information?

Parents
  • Ok, ok, I found it.

    The problem was with the configuration of WSUS on that server.

    For anyone wit the same problem:

    - open the Microsoft WSUS console
    - go to "Options"
    - "Update files and languages"
    - click on "Update languages"
    - place a checkmark on the language that corresponds to the binary langauge of the problematic packages

    Alternatively:

    - duplicate the package
    - edit the duplicated package and change the binary language either to your normal language or to "None"

    I guess the alternate method is more precise but we need to publish hundreds of packages which would take ages to manually duplicate and edit.

Reply
  • Ok, ok, I found it.

    The problem was with the configuration of WSUS on that server.

    For anyone wit the same problem:

    - open the Microsoft WSUS console
    - go to "Options"
    - "Update files and languages"
    - click on "Update languages"
    - place a checkmark on the language that corresponds to the binary langauge of the problematic packages

    Alternatively:

    - duplicate the package
    - edit the duplicated package and change the binary language either to your normal language or to "None"

    I guess the alternate method is more precise but we need to publish hundreds of packages which would take ages to manually duplicate and edit.

Children
No Data