Inheriting VMware Environment: How to Fix a Missing Dependency

If you’re inheriting a VMware environment that’s seen better days, here’s one you’ll likely run into.

We recently took over a neglected virtual environment and began upgrading the client’s vSphere from ESXi 5.5 (yes, really) to version 7.0. We handled the jump from 6.0 to 6.5 with no issues, but hit a snag on the next step: a missing dependency involving “Dell Bootbank OpenManage.”

In this post, we’ll walk you through how we resolved this common issue when inheriting a VMware environment.

Missing dependencies are a common issue in inherited virtual infrastructure, especially when vendor-specific images or old RAID drivers are in play.

In our case, it was a VIB (vSphere Installation Bundle) left behind that blocked the upgrade. These usually aren’t critical, and you can safely remove them in most situations.

Here’s how to resolve a missing dependency during a VMware upgrade:

Before the upgrade begins, you’ll get this message: 

Here’s what to do next.

1. Boot the server back up to it’s current VMware version.

2. Enable SSH on the server and connect.

3. Search for the VIB in question, using the following command:

esxcli software vib list

4. Narrow it down (optional). You can use the following command to filter results, which is especially helpful if you’re comfortable with Linux. 

esxcli software vib list | grep -i OpenManage

5. Remove the VIB using this command:

esxcli software vib remove -n “vib name”

6. Wait for confirmation. It can take a few minutes. Once successful, you’ll see an output like the screenshot below. 

7. Reboot. After one final reboot, you’ll be ready to upgrade to the desired VMware version.

For more detailed reference, check out VMware’s official documentation on esxcli commands.

When inheriting a VMware environment:

•    Always check for legacy drivers or VIBs that aren’t supported in modern builds.

•    Use vendor-specific tools cautiously. They’re often the culprit in dependency errors.

•    Document every step if you’re planning future upgrades or handing off to another admin.

Looking for more tips like this?

Check out our knowledge base for practical, real-world IT fixes and tutorials from our team in the field.