vIDM Upgrade Failed: Network properties should be properly assigned on the appliance.

With the recent release of VMware Identity Manager 3.3.5. I took to VMware Lifecycle Manager (LCM) to upgrade my vIDM version from 3.3.4 to 3.3.5. The process, which is normally very simple, failed very quickly during the Precheck validation.

The Error

The Precheck validation failed on the check VMware Identity Manager Network properties check. It appeared that I was missing some OVF properties from the results description provided. The recommendation in LCM led me to the VMware KB article Network lost experience after upgrading to VMware Identity Manager 3.3.4 to 3.3.5 (83587).

Confirming The Error

The KB article recommends running a few commands to validate the OVF properties. Running these commands from the vIDM CLI confirmed my OVF properties were indeed missing.

[email protected] [ ~ ]# /usr/local/horizon/scripts/networkwizard.hzn showovfenv
Detect ovfenv
[email protected] [ ~ ]# /opt/vmware/bin/ovfenv
Unable to find the ovf environment.

Inside vCenter I checked the vAPP Options for the vIDM VM and they were also missing. Quite strange since this was a VM deployed by LCM.

The Solution

The VMware KB article’s solution is to power off the VM and add the missing OVF values. But as my properties / keys were all missing this wasn’t so straight forward. So I went off to compare a working vIDM with correct OVF properties.

What I found was I was missing 10 OVF properties keys. I had to add each of them back in with there corresponding correct value before the Precheck validation Passed.

Manual Validation

Once all keys had been recreated I powered the VM back on. Went to the CLI and re-ran the commands from the article. This time with much better results.

[email protected] [ ~ ]# /opt/vmware/bin/ovfenv
[email protected] [ ~ ]# /usr/local/horizon/scripts/networkwizard.hzn showovfenv
Detect ovfenv
Try custom ovfenv
Try standard ovfenv


Running the vIDM Upgrade process in VMware Lifecycle Manager should now pass the Precheck for network properties. Assuming all other checks have passed you should be able to perform a successful upgrade of vIDM.

In my specific case I believe the root cause of the problem was that at some point in the past I had removed vIDM from the vCenter inventory and imported it back in via the VMX. This must have removed the OVF properties defined on it.


Network lost experience after upgrading to VMware Identity Manager 3.3.4 to 3.3.5 (83587)

Workspace ONE Access/vIDM Backup/Restore Procedure -- OVF Export Issue Workaround (79131)

Leave a Reply

Your email address will not be published. Required fields are marked *