• State Verified Answer
  • Replies 2 replies
  • Subscribers 22 subscribers
  • Views 1077 views
  • Users 0 members are here
Options
Related

Lenovo package - "Installation not possible"

lowdisk

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?

  • 0

    Ok, made some progress.

    I found that when the binary language of the packages is changed to "german" the packages do not get the "Installation not possible" status and can normally be requested by clients.

    However, changing the language on dozens of packages is a lot of click work and, as mentioned above, we have two Patchmanager servers and the older one of those does not show this behavior, meaning packages which have binary language set to "English" can also be published.

    My guess is this is a configuration setting within Patchmanager itself, however I'm sturggling finding it.
    Any help would greatly be appreciated!

  • +1

    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.

SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 200,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.

SolarWinds Customer Success Center Certification SolarWinds Lab Link Accounts
About THWACK Blogs Federal & Government Edit Settings Free Tools & Trials
Legal Documents Terms of Use Privacy California Privacy Rights Security Information
©2021 SolarWinds Worldwide, LLC. All Rights Reserved.